Subject: sp5 evaluations

(This message is being sent to CPSC 215 Students and TA's)

I'll be sending those out shortly.  The test input files
were sp5a.txt sp5b.txt and sp5c.txt which are now all in
sp5data.  The files are LOGICALLY identical but have differences
in the presence of comments and blank lines.  Your model
parser MUST be insensitive to blank lines and comments.

If its not, your raytracer will fail in weird and wonderous
ways when presented correct input.  So please correct those
problems ASAP. See me if you can't figure it out.

-------------------------------------------------
I don't like like surprises and I would think being surprised
with a grade of D or F would be a particularly unpleasant
surprise. A few students seem to be operating in a state of
denial in which they appear to be thinking that if they can come
up with a 65 average on quizzes and tests they will magically be
awarded a C- at the end of the semster.  That would be false.

Students who submit functionally complete programs that compile
cleanly but fail miserably in execution will generally earn a
grade in the neighborhood of 60 and thus MAY BE ABLE to make a
C- in the course. Students who continually submit nothing or
programs that are grossly incomplete from a functional
perspective should EXPECT to make an F in the course and should
not be surprised when they do.

As it states in the syllabus:

Grading:

The final grade for the course will be computed based upon the
following distribution (To earn a grade of C or better in the
course it is necessary to make at least a C in the Lab and to
have at least a 50 average in the project component of the course).