CSE 143X: Computer Programming I/II (accelerated), Autumn 2012

Regrade Policy

You may request to have your work 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 back a point on an assignment that shouldn't have been taken off but you might lose other points that should have been taken off. Or you might get points back on one exam question only to find that you should have lost points on some other exam question.

Homework and exams are graded differently and regrade requests are handled differently for each:

• Homework

  Students are encouraged to first discuss homework grading with their individual TA. If you aren't sure why you lost a point or if you disagree with the TA's evaluation, you should start by talking to your TA to see if you can resolve it directly. If not, you can request a regrade.

  For homework regrade requests, email our head TA, Allison Obourn (aeobourn at cs.washington.edu). Mention which assignment you want regraded and briefly describe why you think you deserve a higher score.

• Exams

  Exams are graded collectively by the course staff, so individual TAs have less power to deal with exam grading issues. A TA can correct obvious errors like an addition error or an obviously correct answer that has been marked as incorrect. For more detailed grading issues, you should request a regrade.

  For exam regrades, give your exam to Stuart along with a short note describing what part of the exam you think was graded incorrectly.

  You are required to test some exam solutions for programming problems before turning them in for a regrade. You can use the following testing programs to do so:

  • Test9.java (for testing answers to midterm question #9)
  • PracticeIt printTwos problem (for testing answers to final exam question #2)
  • FinalTest4.java (for testing answers to final exam question #4)
  • PracticeIt printLeaves problem (for testing answers to final exam question #5)
  • PracticeIt tighten problem (for testing answers to final exam question #8--note the different method name "tighten" versus "makeFull")
  • FinalTest9.java (for testing answers to final exam question #9)

  You can use these testing programs to find out how close your solution is to being correct. If you find that your solution was either correct or close to being correct, then turn in your correct solution to our catalyst dropbox and then in your note to Stuart, describe how close you were to having the right answer. You still have to turn in your original exam to have the regrade take place. Please note: This is not an opportunity to turn in a second answer. It is intended to allow you to show how close your original answer was to being right.