- Prepare (due Thu 8/29, Late due 9/7)
- Content below if you need a refresher on Python or central tendency
- Canvas quizzes
- Class engagement – See on the class forum
- Homework – None
Content
1.A – Welcome to the class!
1.B – Central Tendency
1.A – Welcome to the class!
1.B – Central Tendency
This post outlines what the in-person exam retakes will be like.
This post outlines the Practicum 2 part of Exam 2. See the in-person Exam 2 or Practicum 2 Update posts for details on the other parts. Study exams are in the Box folder.
This post outlines the in-person part of Exam 2. See the Practicum 2 or Practicum 2 Update posts for details on the other parts.
This is the same as Exam 1’s logistics in that problems are graded on an ESNU scale. How many points each rubric level is worth depends on the question. A question’s worth depends on how many questions in the exam are testing the same concept (more questions for that concept means fewer points for each question). The goal is that an exam with only S’s on every question results in a 90% because it indicates a Satisfactory level of understanding of all the concepts the exam is testing, rather than Exemplary.
This post outlines the Practicum 2 Update part of Exam 2. See the in-person Exam 2 or Practicum 2 posts for details on the other parts. Study exams are in the Box folder.
This post outlines the in-person part of Exam 1. See the Practicum 1 or Practicum 1 Update posts for details on the other parts.
For the questions that do not have a clear correct or incorrect answer or where partial credit is warranted, the following rubric will be used.
The number of points earned is distributed across the problems based on the number of learning goals they are testing. The rubric will be converted to points as follows:
This post outlines the Practicum of Exam 1. See the in-person Exam 1 or Practicum 1 Update posts for details on the other parts.
This is the same as Exam 1’s in-person exam, with the following addition:
The regrade window for the Practicum will open immediately upon release, so you can gain clarification to help you with the Practicum Update. It will remain open for 7 days, in accordance with our usual regrade request policy.
This post outlines the Practicum Update part of Exam 1. See the in-person Exam 1 or Practicum 1 posts for details on the other parts
This module is 100% optional. It is intended as supplementary material if you plan to use git with your Jupyter Notebooks.
Here is a guide on how to submit properly formatted .ipynb files for homework and exams.
This is important because a common way to detect bugs that the autograder might find is to first restart the kernel and run everything. Moreover, it is the equivalent of ensuring that you are submitting a polished notebook.
Here is a tool that you can use to verify whether your notebook is correctly formatted (instructions are in the “How to confirm it is correctly formatted” section):
restart_run_all_verification_tool.ipynb
It is part of the code that we use to verify your notebook and deduct points, in other words, if your notebook pass the tests in this tool, you should expect no penalty.
Go to the button labeled “Kernel” at the top of the page.

Click on the “Kernel” button to open this dropdown menu. Now click “Restart & Run All …“.

This box will then appear. Click the red button.

IMPORTANT NOTES:
After all cells have successfully run, make sure to SAVE the notebook before submitting it.
After setting the file_path variable to your homework notebook’s file path, run the entire notebook. The output of the last cell should indicate whether your notebook is correctly formatted. If it is not, it should provide you with additional information about the first cell it finds with this issue.
After following the instructions above, your notebook code cells’ “[#] ” labels will be in numerical order. Make sure to confirm that all code cells are run. This is a properly formatted .ipynb file.


After you submit the notebook to Gradescope, you can click the “Code” button to see how Gradescope renders your notebook. This would also be the version that TA will see during manual grading.
In example 1, the cell following “[1]” is not “[2]”, and it’s clear that the next cell is run multiple times, so it is deemed an improperly formatted .ipynb file.
In example 2, although this .ipynb file below is in numerical order, the first cell in the file does not start with “[1]” and there is no markdown cells before it, so it is deemed an improperly formatted .ipynb file.
example 1:
example 2:
If you have correctly followed the above instructions but the cell numbering is still weird, it might be due to some defects in your environment.
As an example, the cell following cell “[6]” should be numbered as “[7]”. However, if there is a markdown cell between these two code cells, the counter unexpectedly counts that markdown cell as the 7th cell due to some environment issue.

Currently, as the libraries are still in development and we might encounter this weirdness unavoidably , we will consider this behaviour as acceptable if you clearly follow the instructions above to create a clean notebook.
If you want to fix this issue, some current suggestions are: