To the graders of cs112b1 Please, study also the "homework submission rules" and the "programming homework format guidelines" links from the course homepage. In general, I would like you to finish grading within two weeks of the submission deadline (within one week of the late submission deadline). The homework is in /cs/course/cs112b1/current/homework/spool, in each student's directory, stored under the login name. Each homework is in its own directory. I asked the students to submit one .doc file per homework, containing the solution to all the non-programming assignments and the documentation to all the programming assignments. With the programming assignments, they have to submit a separate sourcefile and if needed, separate data files. I will always put a grade file GRADE-01, GRADE-02, etc. into the student's corresponding homework directory, where you must place scores for different parts of the student's homework. It will also have space for some comments: the students do expect comments! It would also be helpful to make comments on the .doc file and source files (maybe the script files, too, but then you may mention this on the GRADE-?? file so that the student knows where to look). Do not worry about lateness deduction: I will do that by a program. In general, the grade file will contain lines ending with something like "(33):" or someting like "(-13):" (a deduction) you should write a positive or negative score correspondingly after the colon that is not greater in absolute value than the number in parentheses (leaving it blank is also OK). You do not have to add up the scores or worry about lateness discounts: I have programs to do this automatically. You should divide the work between yourselves by problem, not by student: this gives more consistent grading. I will always put a file with the homework solution into the same place where the original homework was posted. This solution is not necessarily exactly what I want from the student. It may be less complete (just indicating what is correct) or it may be more complete: this will always be made clear. If there are separate remarks for the grader then I will also put a grader copy into /cs/course/cs112b1/current/homework/hw. If the program does not run at all it cannot get more than 30% of the total points. Of course, if it runs it does not automatically get 30%, since it may do something unreasonable. Even if the program runs and seems to have the desired behavior on the examples, look at the source code since this may still reveal that it is basically incorrect. If the program does something different or less than what was specified, then much should depend on whether the student states this clearly in the external documentation. A typical example is when the program requires special restrictions on the environment to run: e.g. it works only if you call it from a certain directory, or it blows up with certain (not too exotic) kinds of input. You have to compile and run all the programs. When helpful, I will provide test files or a script for this, and put it, say for homework 02, into /cs/course/cs111/current/homework/hw/02. I do not have strict rules on how much to give for style, etc. But you do not have to make any extra effort to understand what the program does: it must be written in a way that explains itself: by its structure, by its comments or both. And, it should not have obvious and great inefficiencies (unless authorized in advance) or tortured structure. You do not have to reward "effort": a student can get 0 for an answer even if the answer is long, if it is completely wrong. You do not have to hunt especially for cheating but if you find evidence (the same very idiosynchratic solution for something, or the same errors unlikely to come from common misunderstanding) please, report them to me.