Problem set grading policy
From 6.034 Wiki
(→Late problem sets) |
|||
| Line 13: | Line 13: | ||
We've come up with a policy on turning in problem sets late. | We've come up with a policy on turning in problem sets late. | ||
| - | The main point is that we hope you don't do it, because it makes things difficult for us. Start your problem sets early, and ask your questions in tutorial. If you have a legitimate reason that you need an extension, ask the TAs well in advance. | + | The main point is that we hope you don't do it, because it makes things difficult for us. Start your problem sets early, and ask your questions in tutorial. If you have a legitimate reason that you need an extension (not just procrastination), ask the TAs well in advance. |
If you want to turn in a problem set late, you ''must'' do these things: | If you want to turn in a problem set late, you ''must'' do these things: | ||
Revision as of 22:01, 27 September 2006
What is GraderBot?
Problem sets are graded automatically. The tests measure whether you understand the general AI concepts, but the problem sets make sure you can apply these concepts in real code. In order to test that the code you wrote works and meets the requirements of the problem, we run the code on an expanded version of tester.scm, called the "hidden tester".
The public test cases -- the ones that you should be sure to pass before submitting -- are included in the hidden tester, and will be worth at least 33% of the points.
The Scheme code you submit needs to run without human intervention! The TAs do not have time to balance your parentheses or define your undefined variables. Your best bet is to run tester.scm right before you submit. If tester.scm does not run, then GraderBot will not be able to give you a grade.
So far, the TAs have been forgiving, and have gone and fixed people's code until it worked, and then given "partial credit" by deducting 20% of the grade that comes from the TA's modification of the code. If this goes on, you may find the TAs give less and less partial credit over time. Submitting code that doesn't run is negligent, and is completely avoidable with the help of the tester.
Late problem sets
We've come up with a policy on turning in problem sets late.
The main point is that we hope you don't do it, because it makes things difficult for us. Start your problem sets early, and ask your questions in tutorial. If you have a legitimate reason that you need an extension (not just procrastination), ask the TAs well in advance.
If you want to turn in a problem set late, you must do these things:
- E-mail the TAs before midnight, telling them not to expect your problem set.
- Submit your problem set in the usual way when you're done.
- E-mail the TAs and tell them that you're done.
Problem sets that are turned in 0-2 days late will lose 25% of the points they would otherwise get (this is different from losing 25 points).
Problem sets that are turned in more than 2 days late will lose 50% of the points. (We want to release solutions by then. If you submit after this, you're on your honor not to look at the solutions or the hidden tests until you submit.)
Problem sets that are turned in more than a week late will get no credit.
