Professional Documents
Culture Documents
✍️ Midterm Assignment
⏲️ Due Date:
Tuesday, 18 July 2023 at 23:59:59, UK Time. (but hopefully, it won’t take you more than a few hours to complete it)
This is worth 25% of your final grade.
📝 Instructions:
1. Go to the #general channel of our Slack workspace to find a GitHub Classroom link. Do not share this link with anyone else, this is a private assignment for you.
2. Click on the link, sign in to GitHub if needed and then click on the green button Accept this assignment.
3. You will be redirected to a new repository created for you. The repository will be named me204-2023-midterm-assignment--yourusername, where yourusername is
your GitHub username. The repository will be private and will contain only a README.md file with the instructions for the assignment.
4. All your instructions will appear to you there. Don’t edit the README file, just follow the instructions and complete the assignment.
This assignment, a problem set, incorporates the key topics covered in the first week of the course, such as dplyr, xml2, rvest, writing custom functions, using
Quarto Markdown to generate HTML files, and working with GitHub.
“How do I submit?”
You don’t need to click t osubmit anything. Your assignment will be automatically submitted when you commit AND push your changes to GitHub. You can push your
changes as many times as you want before the deadline. We will only grade the last version of your assignment.
✔️ How you wil be assessed:
1. You will be granted a maximum of 100 points for the whole assignment. You will see how much each task is right next to the tasks’ names.
2. This assessment is worth 25% of your final grade.
3. You will be assessed on correctness, efficiency, and style. (see expectations below)
4. You will lose points if the filenames are not correct or if you do not follow the instructions precisely.
5. You can only expect to get full marks if you have done a pristine job. That is, we can’t find any mistakes in your code, your code is efficient and your markdown
file is so well formatted and well documented (with comments) that it is an absolute pleasure and joy to read.
Marking scheme expectations
Percentage Mark Letter Grade Equivalent
80+ A+
70-79 A
65-69 A-
60-64 B+
50-59 B
48-49 B-
42-47 C+
40-41 C
39 or less F
You should expect to earn around B+ or A- points (good and very good scores!) if you have followed all instructions correctly, although you might have made some
inefficient choices in your code or your markdown is not well formatted. For instance, if you did not create custom R functions when it could have made your code
more efficient, you didn’t use good data types or the layout and aesthetics of your markdown file were not particularly clear and easy to follow.
You should expect closer to an A if, on top of following all instructions to the letter, your code looks really neat and organised, to a point where we felt impressed.
The HTML produced by your code is well-formatted and easy to read.
You should expect more >70/100 (the upper band of A and beyond) only if, on top of being correct and well-formatted and efficient, your submission contained
some advanced tidyverse operations and functions that were really impressing, advanced, well documented and well reasoned!
You should expect less than 55/100 if you did not follow the instructions or if you did not produce the right output files or if you did not use any functions or any of
the dplr/tidyverse functions we have been exploring in class.
You will receive feedback by Friday, 21 July 2023.
◄ ✍ (Optional) Formative Assignment Jump to... 🗓️ Week 02 – Day 01: Neat functions,
(W01 D04) Due 14 July testing and debugging ►