Grading Policy

Grading

15%      In-class test
35%      Final exam
50%      Assignments

    • There will be three assignments in total, with weights 10, 15 and 25 percent of the total grade, respectively. Assignments will be roughly tri-weekly. The assignments will have a written portion and a programming portion.

    Late Assignments

    Assignment due dates: Assignments are due by 11:59pm on the due date. Assignments (including the written part) should be submitted to the TA in electronic form. Exact submission instructions will be provided with the first assignment. The written portions if hand-written should be legibly scanned and submitted electronically as well.

  • Late penalties for assignments:

    • For each day late, including weekends, 15 percent of the total possible points will be deducted (a day ends at the due time). 
    • No work will be accepted if it is more than five days late.

    Email & Newsgroup Traffic

      • Please do not send email directly to the TAs. They will not be replied.
      • Main forum for answering questions about class or about the assignments is the class bulletin board. The TAs will be monitoring the board.
      • Appropriate use of the board: clarifications on assignment, on lecture material, general concerns about the course, or other remarks that are appropriate for all students to see/participate in.
      • Do NOT broadcast pieces of your code or answers to written assignments to the bulletin board. Specific or general implementation questions whose answer would benefit all students in the class are appropriate. However: the bulletin board is NO replacement for the tutorial hour. That should be the main forum for asking/answering questions of this sort.
      • Questions of the form "I cannot find the problem with my code; here it is, can you help me" are unlikely to be replied, so don't count on it. If you have a question with code, take it to the TA office hours or to the tutorials.

        Academic Honesty

      • Academic honesty is a very serious matter and can result in very serious consequences. Note that academic offences may be discovered and handled retroactively, even after the semester in which the course was taken for credit. This is a challenging class aimed at teaching you the fundamentals of computer graphics. You wont learn much if you cheat but you might get a good grade if you get away with it. If all you want is a good grade take an easier class where you wont have to cheat!

         

        For purposes of this class, academic dishonesty is defined as:

        •  Any attempt to pass off work on a test that didn't come straight out of your own head.
        • Any collaboration on written or programming assignments (its ok to share ideas on programming assignments but the code MUST be your own) in which the collaborating parties don't clearly and prominently explain exactly who did what, at turn-in time.
        • Any activity that has the effect of significantly impairing the ability of another student to learn. Examples here might include destroying the work of others, interfering with their access to resources (eg. digital cameras), or deliberately providing them with misleading information.