Programming Assignment (PA) Schedule

Documents and Dates

• PA0: Setting up AWS and Dask

  • Release Date: Wednesday, 1/13

  • Statement, Codebase, and Grading Criteria

  • Discussion by TA: Thursday, 1/14, 1:00-2:00pm PT (Zoom link on Canvas); Slides PPTX; video on Canvas

  • Due Date: Thursday, 1/21, 11:59pm PT (previously Wednesday, 1/20)

• PA1: Data Exploration with Dask

  • Release Date: Friday, 1/22 (previously Thursday, 1/21)

  • Statement, Codebase, and Grading Criteria

  • Discussion by TA: Monday, 1/25, 1:00-2:00pm PT (Zoom link on Canvas); Slides PPTX; video on Canvas

  • Due Date: Tuesday, 2/16, 11:59pm PT

• PA2: Feature Engineering and Model Selection with Spark

  • Release Date: Wednesday, 2/17

  • Statement and Grading Criteria

  • Discussion by TA: Monday, 2/22, 1:00-2:00pm PT (Zoom link on Canvas); Slides PPTX; video on Canvas

  • Due Date: Wednesday, 3/10, 11:59pm PT (previous Tuesday, 3/9)

Instructions and Caveats

• Team composition:

  • You can work on the PAs in teams of 2 or individually (teams of 1). All remaining students will be randomly paired up by the TAs.

  • Please submit this Google Form on your team composition decision before 11:59pm PT Tuesday 01/12. The TAs will then confirm your team memberships and team IDs.

  • Your teams must be the same for PA0 and PA1. You are welcome to change this for PA2; a different Google Form will be released for this later.

• Discussions outside your team:

  • It is okay to discuss about the assignment with your peers at a conceptual level. It is also okay to post conceptual or high-level questions, logistical questions, and useful references on Canvas Discussions. But do not share any code across teams and do not post any of your solution code for discussion. A team's code submission must be entirely their own.

  • Please review UCSD's honor code and policies and procedures on academic integrity here.

  • Do not go searching for any code posted online by other students or prior editions. We will use advanced program analysis tools to compare your code submissions. These go well beyond basic string or syntactic comparisons to catch plagiarism.

  • If plagiarism is detected in your code or if any other form of academic integrity violation is identified, you will get zero for that component of your score and get downgraded substantially. I will also notify the University authorities for appropriate disciplinary action to be taken, up to and including expulsion from the University.

• There are no late days for the programming assignments. So, plan your work accordingly!