CSE 120 Nachos Threads Project Regrade Guidelines

Summer 2010

As the primary point of the Nachos projects is to provide a learning experience, you can earn up to half of the points that you missed by correcting your project and submitting it for regrading. Certain parts of the project – specifically the synchronization code – must work correctly in order to complete the subsequent projects anyway, so this may be a very worthwhile use of your time. For other parts, you will have to judge whether your time is better spent correcting and testing a previous part to gain partial credit, or writing more test cases/extra credit for the current project and potentially getting full credit. Other than direct dependencies, you should complete the current project before attempting to correct previous parts.

To submit code for regrading, please follow these guidelines:

• Create a file named REGRADE in code/threads/. For each part being resubmitted, include:
  1. A brief description of what you changed.
  2. The relevant code and context that you changed. This will generally be the entire body of the corrected method(s).
  3. The names of your test cases verifying that your code is correct.
• Test cases: you must submit test cases for all code to be regraded. Corrected code will not be regraded without corresponding test cases. If you already had a test case that did not work (because of a bug in the test) or because you used it incorrectly (such as a test that should have triggered an ASSERT but did not), it is acceptable to correct that test and use it as your test case.
• Submit your updated Project 1 code along with your code for Project 2.
• I encourage you to come to office hours/lab hours to get help with your projects (including parts being resubmitted).