Assignment Schedule

Problem sets will be released as they are assigned. Links and due dates for the assignments can also be found in the schedule.

  • Assignment 1 (released on February 2, due by February 9)
  • Assignment 2 (released on February 10, due by February 16, 11:59PM Eastern)
  • Assignment 3 (released on February 16, due by February 23, 11:59PM Eastern)
  • Assignment 4 (released on February 23, due by March 2, 11:59PM Eastern)
  • Assignment 5 (released on March 2, due by March 9, 11:59PM Eastern)
  • Assignment 6 (released on March 9, due by March 18, 11:59PM Eastern)
  • Assignment 7 (released on April 13, due by April 20, 11:59PM Eastern)

Grading

Each assignment is weighted equally. Late assignments will be penalized 10% every 24 hours.

Assignment Submission

We will be using Gradescope for written and code assignment submission and grading. The login code for this class will be posted on Piazza: please create an account and add yourself to this class using that code. Each assignment consists in a set of exercises taken from the textbook.

Written exercises can be uploaded to Gradescope either as a scanned PDF or as a series of images (be sure they are legible). If you prefer to work in LaTeX, it's even better! These assignments might require writing code to help find answers.

Each assignment has a coding part, where you are asked to complete missing pieces of a python notebook. Following the links in the textbook, you can open the notebooks using Deepnote. You can work directly in Deepnote. Once you are satisfied with your work, upload the notebook to Gradescope; we prepared an automated battery of tests that will grade your work. We will also quickly double check all the submitted notebooks. Please have a look at the textbook appendix for more details.

Collaboration Policy

Collaboration is encouraged on both written and coding assignments, but the work you submit for assignments is expected to be entirely your own. That is, the writing must be yours, and you must fully understand everything that you hand in. Discussing the details of how to solve a problem is fine, but you must write the solution yourself. To avoid plagiarizing, you should not be looking at someone else's solution while you write down your own. If you collaborated significantly (use your own discretion for "significantly") on a problem, list the people you collaborated with next to your solution. If you feel like you have plagiarized the work of others, you have the opportunity to bring it to our attention within 72 hours. The course may impose local sanctions that may include an unsatisfactory or failing grade for work submitted, but the course will not refer the matter for further disciplinary action except in cases of repeated acts.