Each graded Volume has an Initial Submission Deadline and a Final Submission Deadline. Submit a genuine attempt (e.g., you make a real attempt at the exercises in the volume) 1 by the initial deadline to earn the first 50%.
After the deadline, we will remove your ability to submit code and run our automatic grader (autograder) on your code, which runs it against the public test cases that came with your exercises, and potentially private test cases that we didn’t release to you. It’s your responsibility to test your code with different inputs to make it robust.
Then, your TA may leave comments on your GitHub submission page for the volume, as seen in the cs1010 command (e.g., the “Check status” or submission page).
GitHub calls this page a pull request, or PR. You do not need to create or
manage the PR yourself. The cs1010 command does that for you.
If your TA asks you to make changes, address every actionable comment and submit again by the final deadline to earn the remaining 50%. If your TA leaves no comments, your initial submission receives 100% and you do not need to submit again.
How Grading Works (Summarized)
- Work on the Volume: Write, build, test, and format your programs
- Make your initial submission: Submit a genuine attempt by the initial deadline
- Read your results and TA comments: Staff run the autograder, and your TA reviews your code on the PR
- Revise if needed: Address every actionable comment and submit again by the final deadline
How the 50% + 50% Is Awarded
- You submit a genuine attempt on time, and your TA leaves no comments: You receive 100%. No further submission is needed
- You submit a genuine attempt on time, and your TA asks for changes: You receive 50% for the initial submission. Address every actionable comment and submit again by the final deadline to earn the remaining 50%
- Your first submission is late: You cannot receive the initial 50%. The submission is considered only for the final 50%, and your TA is not required to grade it or leave comments during the initial review
Do Not Wait Until the Final Deadline
A late first submission is not eligible for the initial 50%, and your TA may not provide first-round feedback.
Your Submission Page and PR
Run cs1010 from inside the Volume folder and choose
Submit/save current work, then Continue and submit this content.
The helper checks the folder, saves your work online, and shows a View your submission link. This opens the Files changed view of your PR, where you can see the submitted code and read comments from your TA.
Your PR Is Your Submission Page
cs1010creates and updates the PR for you. You do not need to know how Git works, create another repository, or open another PR. Later submissions update the same page, so its comments and discussion stay together.
Reading and Responding to TA Comments
Your TA may leave comments beside particular lines of code and an overall review summary. A comment is actionable if it asks you to change something or explain a decision.
Address every actionable comment before submitting again. If a comment is unclear, or you believe it does not apply, reply below the comment and ask your TA. You can also speak to your TA or use the usual help channels.
If a Comment Is Unclear
Ask your TA before guessing. Replying on the PR keeps the question beside the relevant code and gives your TA the context needed to help.
Where to Find Your Comments and Results
Use the cs1010 command and go to the “Check your work and submission” menu.
- TA feedback: “View your submission” link - right click or highlight to copy.
- Autograder results: “Grading results” link - same idea.
What Is Graded
Correctness
Automated tests compare your program’s behaviour with the exercise requirements. Staff may use private tests in addition to the tests in your Volume folder, so passing every provided test does not guarantee that you have implemented every requirement.
Your program must match the required output exactly, including spacing, capitalization, ordering, and line breaks. Remove any extra debugging output.
Passing
make testDoes Not Guarantee Full CorrectnessThe grading suite may include private tests. Add your own tests for cases and execution paths that are not covered by the tests in your Volume folder.
C Standards and Code Quality
Your TA uses the C Standards for Exercise Volumes when reviewing your code on the PR. The review includes formatting, names, comments, program structure, function interfaces, pointer declarations, pointee types, and the other standards on that page.
Timeline
| Days | Stage | What happens |
|---|---|---|
| 1-7 (Thursday to Wednesday 23:59) | Initial work | Work on the Volume and submit it by the initial deadline |
| 8-10 (Thursday to Saturday) | TA review | Staff run the autograder, and your TA may leave comments on the PR |
| 11-14 (Sunday to Wednesday 23:59) | Revision | If your TA left comments, address them and submit again |
| 15-18 (Thursday to Sunday) | Regrade | Staff recheck revised code when another submission was required |
Before You Submit
Submission Checklist
- Run
make. Fix build errors and investigate warnings- Run
make testand investigate every failure- Test edge cases and different execution paths
- Run
make formaton all submitted C source files. Submission checks reject code that would change when formatted- When sanitizers are enabled, make sure the build and tests produce no sanitizer errors or diagnostics
Common Questions
My program passed all of my tests but failed during grading. Why?
The tests in your Volume folder are not the complete grading suite. Staff may use private tests. Add tests for cases that the provided tests do not cover.
Can I hard-code outputs since I know the inputs?
No. Hard-coding outputs for known inputs instead of implementing the specified behaviour attempts to bypass grading. You will receive no credit for the affected tests.
I don’t understand / disagree with a comment. Who can I talk to?
Talk to your TA first. Open the PR using the submission link shown by cs1010,
then reply below the relevant comment. You can also use the usual help channels.
Footnotes
-
The teaching team will judge this and our decision is final ↩