We want to assess your work fairly. In a class that can approach 1,000 students and has a staff of about 50, mistakes will happen. You’ll need to bring them to our attention.
The procedures are a little different between an exam and an assignment, but the following general principles hold:
If you want to pursue a re-mark request, follow these steps in order. Stop as soon as the issue is resolved (or you get to the end of the list!).
Assignment re-marks are generally handled by the ISAs, in consultation with the instructors. Exam re-marks are generally handled by the instructors, so step 4 is often less useful for exams.
Not getting the Basic Test email in time because you submitted right before the deadline is not enough reason for a re-mark of an assignment. Again, start assignments early, submit early and often, and always run your code in DrRacket.
By default, we will mark the last submission you made before the assignment deadline. However, if you mess up this particular submission, but you made a decent submission before that, we can mark that decent submission instead. Submit a re-mark request letting us know you’d like this and about what time the decent submission was made. Note that we will mark using only one submission; we will not merge work from two different submissions.
Assignments sometimes have restrictions on what built-in functions you may use, or what techniques you must use to do the question. If you don’t follow these restrictions, you may get 0 on the entire question. We will not re-mark your assignment in this case, because the assignment clearly stated the restrictions. Make sure you read the assignment carefully.