Appendix E — Assignment E
Instructions
You may talk to a friend, discuss the questions and potential directions for solving them. However, you need to write your own solutions and code separately, and not as a group activity.
Do not write your name on the assignment.
Make R code chunks to insert code and type your answer outside the code chunks. Ensure that the solution is written neatly enough to understand and grade.
Render the file as HTML to submit.
There are 5 points for cleanliness and organization. The breakdown is as follows:
Must be an HTML file rendered using Quarto (1.5 pts).
There aren’t excessively long outputs of extraneous information (e.g. no printouts of unnecessary results without good reason, there aren’t long printouts of which iteration a loop is on, there aren’t long sections of commented-out code, etc.). There is no piece of unnecessary / redundant code, and no unnecessary / redundant text (1 pt)
The code follows the tidyverse style guide for naming variables, spaces, curly braces, etc. (1 pt)
The code should be commented and clearly written with intuitive variable names. For example, use variable names such as
number_input
,factor
,hours
, instead ofa
,b
,xyz
, etc. For repetitive code chunks, either copy the comments or just leave a comment mentioning that the comment is the same as in the previous occurrece of the code chunk (1.5 pts)
- The assignment is worth 100 points, and is due on 20th Feb 2024 at 11:59 pm.