Taking the Exam

This guide covers the technical aspects of taking exams: how grading works, proctoring setup, debugging strategies, and how to get help. Keep this page handy during exams as your technical reference.

For exam rules and policies, see Exam Rules & Policies.

ESSENTIAL: Submit After Every Exercise

Critical

Submit after every exercise. Every time you submit, the Autograder runs and adds points to your total. This locks in your points and prevents losing everything if you run out of time.

You can move on to the next exercise while it runs
Check to make sure your points are there
If you don't get points, return to the exercise while it's still fresh
There is no reason not to submit after each exercise

Comment Out Print Statements

Comment out print statements before submitting. Leaving in large print statements can dramatically slow down your code or crash the kernel completely. You will not be compensated for correct solutions that fail due to excessive printed output.

Grading

Summary: Submit after every exercise and confirm the autograder awarded you points.

Exam grading works like notebooks, but with a much shorter submission window. Once your test ends, it ends - no exceptions.

Scoring Cap

Your score is calculated as [points earned] / [scoring cap]. You may not need to complete all exercises for 100%.

Example: 18 possible points, 15 point cap → earning 12 points = 80% (12/15). No extra credit for exceeding the cap.

Autograder

The Autograder is the final arbiter of grades. It runs your code in a clean environment, top to bottom, similar to restarting the kernel. The Autograder is what runs when you hit submit.

Key differences from running the test cell interactively:

Clean environment: The kernel is restarted and it runs from top to bottom. In interactive mode if you run a=5 and then delete the cell, a is still 5 until the kernel restarts, even if the code is gone. This means if you defined functions or ran things in a different order, you may see different results.
Error handling: If one exercise errors, it skips and continues - you can fail ex2 but still get credit for ex0, ex1, ex3
Time limit: Interactive mode has a higher time/resource limit, to give you more freedom to solve and debug. Once you submit it, the limit is lower (but still generous).

Autograder Timeout

The process runtime may have reached the allocated threshold of x second(s)

If the Autograder times out, you receive no credit for that submission. The grade report will show this message and the grade card won't update. This is why you must submit after every exercise - if you only submit at the end, you risk getting 0 points.

Manual Grading

We do not do manual grading under any circumstances. If you believe your code failed due to a bug, see "Reporting Possible Bugs" below.

Partial Credit

We do not grant partial credit for exercises.

Typical Exercise Layout

Exercises on the exam will follow a similar structure:

Prompt -> Combined Solution + Demo Block -> Test Cell

(Sometimes) "Run Me!!" Cell

This is a cell that exists before the prompt for some exercises. It's used to load data that may be needed for that exercise if you didn't complete the previous problem. This should be easy to notice, as the error on your solution/demo cell will traceback to this var missing.

Prompt

Specifies what your task is, what the inputs and outputs are, as well as some other overall context.

Demo Code

Each exercise has demo code (usually below your solution area) that runs your code against sample data. Use this for quick checks and obvious errors. Since this is in the same cell as your solution code, you simply run this cell when ready to see the demo output.

Testing Cells

Testing cells run multiple randomized test cases. Focus on the message and the input/output variables provided - use these to debug, not the test code itself.

Proctoring Setup

Your exam is proctored using Honorlock (GT O/MSA) or Proctortrack (edX VMM).

What Proctoring Does

Quick scan of your room (not always)
Records your webcam
Records your screen
Confirms single monitor usage
May perform other simple setup checks

Testing Your Setup

Go to the practice proctored exam in your LMS and start it. If proctoring starts and you can see the exam, your setup is good.

For edX VMM students: The system only lets you start the exam once. To test again, make a private Piazza post with your edX username requesting a reset.

Browser Requirements

Section	Browser	Notes
GT O/MSA	Chrome required for Honorlock	May have other browsers open
edX VMM	Any Proctortrack-compatible browser	Have a backup browser ready

Proctoring Troubleshooting

Environment & Software

Pre-installed Packages

You may import any packages already installed in Vocareum. See the full list of installed packages.

Installing packages is NOT allowed. Vocareum lets you install them, but they won't work in the autograder.

If working locally, your environment may differ from Vocareum. Test your code in Vocareum before submitting.

Using a Local IDE

You're welcome to work locally, but we don't officially support it. With copy/paste disabled, you'd have to manually re-type code into Vocareum. We strongly recommend using Vocareum directly.

If you insist on local development:

Package versions may differ
Code must pass the Vocareum Autograder
"It ran locally" is not an exception

Debugging

Test cells run your solution on many randomly generated test cases
Test case variables (inputs, expected outputs, your outputs) are available after running test cells - use these to debug. See quick reference guide: Exam Test Case Variables
Visual comparison isn't enough - if the code says they're different, they probably are. Use programmatic techniques to test for difference (for numbers, subtract, for dataframes, use assert_frame_equal). More examples are in the above guide.
Read the entire traceback when errors occur
Assume the test is bug-free and continue working. Submit a bug report using the template below if you have good reason, but don't spend more than a few minutes on it.
- The later you take the exam (after hundreds of students), the less likely you've found a bug
- Most bugs are identified within 24 hours of the exam window opening

Getting Support from TAs

Contact TAs via private Piazza post to Instructors - include your email and relevant info
Piazza is the only valid communication method
TAs CAN help with: Platform issues, bug inquiries
TAs CANNOT help with: Exam content, debugging assistance, clarifying problem statements

TA availability: 8am - 11pm Eastern Time. Issues outside these hours will be addressed when TAs come on duty.

Issue Workflow

Troubleshoot → Document → Continue Working

Troubleshoot: Follow steps in Vocareum Troubleshooting or Proctoring Troubleshooting, plus any exam release notes
Document: File a report (see templates below) - don't spend more than 5 minutes
Continue working: Don't wait for a response

Reporting Issues

Platform Issue Template

Use for Vocareum outages, proctoring service issues, etc. Spend less than 1 minute on this.

Note

Copy/paste is disabled - just type the key info quickly into a Piazza post, you don't need to worry about formatting. It's more important that all of the information is there, and you don't waste too much time.

- Email/username:
- Issue: [vocareum outage / proctoring outage / other - explain]
- Time started: [include timezone]
- Steps tried: [list troubleshooting steps and results]
- Need additional time? [yes/no]

If resolved before TA reply:
- Time resolved: [include timezone]
- Additional notes:

Potential Bug Template

Before Reporting

We thoroughly test exams before release. The overwhelming majority of reported "bugs" are issues with student solutions. We investigate all reports, but if it's your code, we'll explain after the exam window closes.

Before submitting:

Check your output against expected output using test case variables
Submit your work - this gives us a snapshot to reproduce the issue
Make a private Piazza post
Continue working - don't wait for a response

- Email/username:
- Exercise number:
- Explanation: [what's happening, what should happen, why you believe your code is correct]
- Screenshot: [attach]

Missed Exams

If you miss an exam due to misunderstanding the window or length, you receive a 0. We cannot extend windows or offer alternative assignments.

GT O/MSA Students

If you have compelling, documented justification (medical condition, family emergency):

Contact the Division of Student Life to document your situation
They will reach out to us with confirmation
You may be eligible for an Incomplete grade
To resolve, you'd take the equivalent exam in a future semester

Per GT policy, incompletes are for "small" amounts of missed work. More severe circumstances may require withdrawal.

edX VMM Students

If you have compelling, documented justification:

Contact edX support and explain your situation
They will coordinate with instructors
edX may offer free re-enrollment in a future semester
Progress transfer is at the discretion of 6040 staff

Frequently Asked Questions

Grading

When/where will my grade be posted? - Vocareum is the source of truth. If you see points in the "Grades" pane, we have them. LMS grades (Canvas/edX) update after the window closes.
How many times can I submit? - Unlimited. Submit after each exercise.
My code passes in the notebook but fails when I submit - Your solution must pass the Autograder. See the Autograder section above.
Can I get manual grading? - No. See "Manual Grading" above.
Can I get partial credit? - No.

Proctoring

How do I show my room to the proctoring software? - Rotate the camera or use a mirror.
What's the best time to take the exam for TA availability? - TAs are available 8am-11pm Eastern. You can take the exam outside those hours, but issues will be addressed when TAs come on duty.

Support

What if I need help during the exam? - See "Getting Support from TAs" above. Do NOT make public posts about exam material.
Can I reach staff outside Piazza? - No. Piazza is the only monitored platform.