Assignment Information

All assignments must be done individually, unless the assignment is explicitly designated as a group assignment. All members of a group receive the same grade (no exceptions). Only one member of a group submits the assignment. The instructors/staff do not arbitrate group disputes; group members must handle any and all problems. A group assignment may be done individually, but it must be understood that the amount of work is significantly greater and no extra marks are given for this additional work.

Students repeating the course (for whatever reason) cannot reuse program code that was part of a group project because it is impossible to determine the individual's contribution. Hence, they must do a different project. If another assignment question happens to be the same as one you were assigned in a previous term, you are not permitted to resubmit the same code. You must delete your old code and start over. Self-plagiarism is defined as an academic offence under University guidelines. Contact your instructor if you have any questions about this point.

Assignments are distributed through the course's git repository. To gain access to the repository, follow the directions given in assignment 0, which can be found on Piazza.

Review the assignment coding guidelines before starting each assignment.

Submissions

Assignments must be submitted using the Marmoset Submission and Testing Server.

If you are having issues submitting to Marmoset, ask course staff for help on Piazza. If you are close to a deadline, you can e-mail your files to the course ISC (but please only do this as a last resort) until you resolve your issues with Marmoset.

See this page to find out how to submit to marmoset through a shell using the command line.

Note: Marmoset is not a compiler! Do not submit C++ code to Marmoset, without first attempting to compile it yourself. For each problem on Marmoset where the deliverable is C++ code, if you have five or more submissions marked "Did not compile", a mark will permanently be deducted from your score on that problem.

Lates

• Assignments are due on the due-date at the time specified on the top of the assignment.
• Late assignments are not accepted.
• An assignment not handed in receives a mark of 0, unless there is a documented reason.
• If a documented reason is available, talk to the instructor within one week of the assignment due date to see if an accommodation can be made.
• The weight of the missing assignment is distributed across future assignments and/or exams (instructors will decide on the appropriate distribution).

Marking

• An assignment is marked on the following criteria:
  1. testing
  2. correctness
  3. hand-marking
• Note, a correctly-working program is only one component of the assignment mark.
• Use only relative paths in includes, not absolute (unless specified otherwise in assignment).

Returning and Remarking

• Handmarking grades and comments are returned through the MarkUs System. (Typically only some questions are handmarked.)
• Correctness grades are viewed on the Marmoset webpage. (Check Piazza for when results are "released".)
• You have two weeks from when an assignment is handed back to email the Instructional Support Assistant, stating the question(s) to be remarked and a reason why the current mark is incorrect.
• All requests are processed after the deadline to ensure fairness and consistency in marking.
• Changes to your code are not permitted as part of a remark request.

Work Environment

Assignments must compile and run on one of the linux.student.cs.uwaterloo.ca computers. See CPU/Applications Hosts for a complete list of server computers.

---