For all labs except the SPIMbot tournament, you can work individually or with 1 partner. You must credit the collaboration in the partners.txt file for the lab, which will already contain your NetID; if you have a partner, add their NetID on a new line. All partners must make their own submissions, and the submissions are graded individually; the purpose of partners.txt is to prevent collaboration from being flagged by the plagiarism detector.
For the SPIMbot tournament, you must work in teams of 2 or 3, and only one team member should submit.
Each lab is divided into two part. The first part is typically due at 8 PM on Thursday (deviations will be announced). There is no late submission period for this portion, so it’s best if you try to get most of it done during your lab. The second part is typically due Sunday 8 PM (deviations will be announced) and has a late submission period - see below for details.
One lab, other than the SPIMbot tournament (which has no late submission period whatsoever), can be submitted up to 48 hours late without penalty (This applies only to the second portion of the lab). Otherwise, a 10% penalty every 12 hours (or part thereof) will be assessed, up to a maximum of 48 hours. Your final score for a lab is the maximum of your score before the deadline and after each 12 hour late submission period with the appropriate penalty applied. In other words, you can never lower your score from your original submission by submitting it again later.
The late waiver will be automatically applied to the lab for which it would give the largest score increase at the end of the semester. Note that, even with the waiver, you will only be graded for submissions up to 48 hours past the deadline; any submissions later than that will not be graded.
For web homeworks, you can get 100% credit for submission before the deadline. Assignments turned in late will be limited by 80%. The late deadline for web homeworks is one week after the 100% credit deadline.
You only need to modify (some) of the files we provide you. Specifically, don’t try to modify the Makefile and add auxiliary files to your github repo even if your modification is valid and your code does work on EWS machines. Failing to follow this rule can lead to a 0 for the lab, if the grading script can’t compile your code based on the Makefile we distributed. We hand out certain files as read-only; it’s not hard to make them writable (Google it if you don’t know how to), but it’s a strong indicator that you should not be modifying those files.
We run the autograder on an EWS machine. Just because your code works correctly on your personal machine, does not mean it will work on EWS. So even if you work on the labs on your personal machine, it doesn’t hurt to test that your code works on EWS. Again, don’t try to modify the Makefile and add auxiliary files to your github repo even if your modification is valid and your code does work on EWS machines. Failing to follow this rule can lead to a 0 for the lab, if the grading script can’t compile your code based on the Makefile we distributed.
All regrade requests must be submitted within 48 hours of grades being released.