Exam Regrade Policy

You may request to have your exam regraded, but when you do so, you are submitting it for a complete regrade. Your score can go down as a result. For example, you might get points back on one exam question only to find that you should have lost points on some other exam question.

Exams are graded collectively by the course staff, so individual TAs have little power to deal with exam grading issues. Please submit regrades by the following date.

• Midterm regrade requests must be submitted by Sunday, March 3rd at 11:00 pm. Regrades cannot be submited before Monday Feb 25h at 8:00 am.
• Final regrade requests must be submitted by Friday, April 5th (first Friday of spring quarter) at 11:00 pm. Regrades cannot be submitted before Sunday March 24th at 8am. Regrades will not be processed until after the deadline so you will not receive an email with the result of the regrade until the second week of Spring quarter.

To check if your solution is correct, we have provide some testing programs:

• Midterm:
  • Test3.java
  • Test5.java
• Final:
  • Test7.java (this one does not print any points since there are no "external points" in the criteria for problem 7, this is just to help you verify if your solution is correct)
  • Test8.java

If you believe a problem was incorrectly graded, you must:

• Submit a regrade request using this Google Form. The form has a series of questions asking which problems you want graded. Please follow the directions at the beginning of the form very carefully. Regrade requests that do not follow the directions may be denied.
• If you think there was an issue with the scan of your exam, indicate so in the regrade request and Hunter will check back to the original paper exam.
• Specific rules for specific problems
  • On the midterm, if you can find one line in the Stacks & Queues problem that can be added/removed to make your solution correct, include that information in the request. Hunter will charge 5 points for a single-line addition or subtraction. (That is, on a 20 point problem, your score is capped at 15/20)
  • On the midterm, if you can one .next in the ListNode problem that can be added/removed to make your solution correct, include that information in the request. Hunter will charge 1 point for a single addition/removal of a .next.
  • On the final, if you can find one line in the LinkedIntList problem that can be added/removed/changed to make your solution correct, include that information in the request. Hunter will charge 5 points for a single-line addition, subtraction, or change. The one line change may be calling a switchFronts method that was included in the LinkedIntList class that will swaps the front fields of this list and a given one. (That is, on a 20 point problem, your score is capped at 15/20)

Note: This is our first quarter using Gradescope, so we appreciate your flexibility as we figure out the details of how this works