• Point totals sum to 91, not 100. With extra credit, the maximum possible would be 94 (but this is still out of 91).
• Extra credit: If you indicated in your README file that you devised a method for dealing with test instances that have attribute values not seen in the training data, we checked your output for two runs:
  1. mushroom.train/mushroom.test
  2. mushroom2.train/mushroom.test
  Both should work correctly.
• Policy on regrades: If you believe that we've made a mistake on grading any part of your assignment, please first send e-mail to the TA who graded that part (or go to one of their office hours). They should pretty quickly be able to either further explain the grading for that question or recognize a grading mistake. If after talking to Kiri or Alin, you still believe that there was a problem, please discuss it with Claire either via e-mail or during office hours.
  ***Please note***: Once you submit your assignment for a regrade we have the option of regrading the entire thing...possibly finding mistakes that we missed during initial grading. Regrades should be brought to our attention within two weeks of handing back the assignments.

	C++	Java	php3	Perl
Most lines of code:	3280	1480	336	652
Least lines of code:	559	328	336	652

1. Read the handout closely. Many points were lost because the specified trace format was not followed.
2. Documentation is important! (~20% of your grade, here) Documentation does not mean commenting every line of your code. This only makes it more difficult to read. Documentation consists of clear instructions on how to run the code, a paragraph description at the beginning of each file (including, for the main file, a description of the input and output and what the program does), a short description with each function, and perhaps most importantly (and most often omitted!), a high-level description of any data structures used.