• Setup Middle Reactive Input; drop down menu with foods + entry field for amount in grams
• Compute current total for all macronutrients based on input
• Plot current totals on main plot object

• Implement a page to display a barchart
• Make the barchart interactive
• Make the barchart sorted

Reflect on changes of plan/ what we couldn't implement

Congratulations on finishing milestone 4! We can see you put a lot of work into this project, nice work! Below we list some specific feedback you can use to improve your project.

• Submission instructions: mechanics: 4/4

• Improving your app: mechanics: 20/20

o The information requested for the submission on Canvas is not including what has been modified, the source, team member, and commit/s.
o There is one improvement to the application by each team member and the changes are not only minor fixes.

• Reproducibility 12/20
  o Testing: rubric={mechanics:1/5, accuracy:5/5}
  • The tests are passing in the github action workflow 1/5
  • There are 3 test_that() statements in the file tests/testthat/test-shinytest2.R  5/5
  o Continuous Integration and Deployment: rubric={mechanics:1/5, accuracy:5/5}
  • There should be one workflow badge in the README.md 5/5 mechanics
  • The deployment workflow deploy_app.yaml is passing. 1/5 accuracy

• Tie it all together: rubric={mechanics:20/20, accuracy:20/20, viz:6/10}
  o The main plots take time to load (-4)

• Reflection: reasoning: 6/6
  o There is a reflection-milestone4.md file 
  o reflection-milestone4.md is included in the docs folder
  o When reviewing reflection-milestone4.md and comparing it with the milestone1 sketch, it's not difficult to comprehend the alterations that were made and the reasons behind them.  

• Take Targets and Totals Implemented in Steps 1 and 2
• Plot Current Values as Proportions (i.e. current/total) as a pie(?) chart for each nutrient.
• Display % and grams as text remaining for each nutrient

Update ReadMe after App Development

• Setup Reactive Inputs for Setting Macro Targets
• Implement Button to Switch between Input Types
• Setup Main Plot Object
• Plot Targets as horizontal lines on Main Plot Object

• Merge datasets in https://open.canada.ca/data/en/dataset/a289fd54-060c-4a96-9fcf-b1c6e706426f into one.

(This is not necessarily part of milestone 1, but doing so might help the data description part and also help all members have a better understanding of some statistics of the data)

Group 9

Congratulations on finishing milestone 1! We can see you put a lot of work into this project, nice work!
Below we list some specific feedback you can use to improve your project.
We provide tick boxes for you to use in the future as you address these concerns to improve the final grade of your project.
If anything is unclear, please feel free to ask questions in this issue thread.

Submission instructions

rubric={mechanics:4}

Well done!

Section 1: Motivation and Purpose

rubric={reasoning:8,writing:2}

- [ ] proposal.md: There isn't a minimal description of the app. What will the app do? What is it's main purpose? -2 reasoning

Section 2: Description of the data

rubric={reasoning:8,writing:2}

• proposal.md - Dataset description section: There is not evidence data quality analysis. Are there missing values? Are these values an important percentage of the dataset?. -1 reasoning

Section 3: Research questions and usage scenarios

rubric={reasoning:12,writing:2}

- [ ] proposal.md - Persona: IPersona**: In the persona description it is not specified their needs as user and/or the potential benefits that the app could for this person -2 reasoning

• proposal.md - Persona: The level of detail provided in the persona description is not sufficient and the number of words in it is less than 200-300 words. -2 reasoning

Comments:
-What is lacking is information on what the app provides and how it will help Bob (benefits).

Section 4: Description of your app & sketch

rubric={viz:10, writing:2, reasoning: 3}

Well done!

Section 5: Team work contract and collaborative documentation

rubric={reasoning:4}

Well done!

Code of Conduct

rubric={reasoning:1}

Well done!

Contribution guidelines

rubric={reasoning:1}

Well done!

Once all components are complete

Congratulations on finishing milestone 2! Below is the grading scheme for this deliverable.

Mechanics: 2/4
o The links are missing in the canvas submission. -2 mechanics

Developing your Shiny App: mechanics: 10/15, quality: 5/5, viz: 10/15, accuracy: 7/7
o There is not one branch by each team member. -5 mechanics
o The elements of the app aren't organized effectively. -5 viz

• I would consider reorganizing the layout of features in the app. When testing it out, I didn’t find it to be super intuitive and it took a few minutes for me to understand what was being plotted. Specifically, because the buttons to plot are placed on the left column (before the food entry) it made me think there would be another to add the food entries after. I see now that it will update once I input a food and click them, but this order is not standard in UIs
• Use consistent labeling/naming of the plot buttons, one should not be a question and the other not.
• There is an overlap between the plots and labels (ex “Weights” and the macronutrient plot)
• I couldn’t see my own manual input for the weight of foods because the input box isn’t sized appropriately.
• Review spelling, ex. “Macroutrient Totals”
• Minor comment, but consider giving the user the option for either the slider or manual input (maybe a drop-down) and then just let one appear and have 1 plot button.
• “About”, “Data” and “Download” pages are blank
• I like your “Statistics” page with food rankings I think that’s a creative and useful feature!

Reflection: reasoning: 6/6

README: reasoning: 6/6

Grade 46/58. Great job! Please let me know if you have any questions or would like to discuss any of these points further.