R. Clayton (rclayton@clayton.cs.monmouth.edu)
Wed, 17 Jan 2001 19:01:09 -0500 (EST)
Your fourth assignment has been graded. I ran tests with the wildness
parameter values 0, 50, and 100, four tests per value. The results of each
test appears as
*A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
The bottom line is the character input to your recognizer and the top line is
the output generated by your recognizer (output is marked with a leading *). A
group of characters indicates that your recognizer output several guesses for
the input character appearing underneath.
*A B C DGP EM FHK G NH I J K L M N O P QG R S T U V W X Y Z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
A question mark indicates your recognizer didn't output any guess for the input
character underneath.
*A BFH ? DP E F G H I J K LTG M N O P GLT KNR S LTG ? V ? X GLT Z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Long output is folded to take up multiple lines.
*A B C D E F G H I J K L M NMHRQPKIFEDB QOS P Q RNKQPMIHFEDB SQOG L U V
A B C D E F G H I J K L M N O P Q R S T U V
*MKAZYXVRQN X K Z
W X Y Z
Because these are probabilistic test results, for the most part I used them to
determine if and where in the 90s a program should go. Programs that didn't
made it into the 90s were graded mostly on the basis of the code.
Just a few reminders as you put the final touches on your fifth assignment:
Many many people lost many many points by not following the input
specifications given in the assignment. A smaller number of people lost
points because I couldn't parse their output, but it could have been a larger
number if I hadn't diddled my test code.
Make sure your program follows the input and output specifications given in
the assignment. Output in particular is going to be important for the fifth
assignment because your code is going to be generating a lot of output and if
my test code can't handle it, you're stuck because I'm not going to look at
it otherwise.
You should also start commenting your code at the procedure level. A line or
two describing the procedure's function, and input and output parameters are
usually all you need. If you can't write a good one or two line procedure
comment, you should take that as a signal to look at your procedure code
again, with an eye towards simplifying it.
If you allocate it, delete it.
No magic numbers.
No array overflows (I'm going to be going after them in the fifth
assignment).
This archive was generated by hypermail 2.0b3 on Thu May 17 2001 - 12:00:05 EDT