Lab Guidelines

List of Labs and Weights

Basic OpenGL 3D orthographic projection drawing system (10%)
3D perspective viewing with camera control and hierarchical modeling (10%)
3D Illumination, Materials, and Decals (15%)
Texture mapping (15%)

Equipment and Programming Environment

The default equipment for the course are the lab workstations in CL112D.
Working in other environments may be possible. We will need to work out arrangements with the grader to see what other environments (s)he can reasonably support.

Grading Criteria

Grading of the labs will be based on the following:

80%: Correctness and adherence to assignment specification. This includes any error checking specified in the lab handout. If no error checking is specified, then you don't have to do it.
10%: Readability and structure of code, use of comments, indentation, etc.
5%: Efficiency and speed (only an issue if its very inefficient)
5%: Adherence to lab procedures (submitting, naming conventions, etc.)

The grader will grade the labs. If you have a problem with the grade you received on your lab, see the grader first. If you can't resolve the dispute with the grader, then see me. However, in order to maintain consistent grading for everyone in the class, I am not very inclined to alter grades that are assigned by the grader.

Due Date & Late Penalties

Unless otherwise specified, a lab is due by 11:59pm on the day it is due.

There is a 10% per day late penalty for every day the labs are open, up to a maximum of 50%. After that, you get zero. Late penalties are imposed precisely at midnight. I don't give extensions to individuals unless its an extreme case of a proven emergency. You have more than enough time to do the labs, especially if you start on them right away. If you wait and run out of time, it's your problem. I give extensions to the class in case of general equipment failure or other, universal, uncontrollable, devastating circumstances.

Copying Labs

Don't. Discussion of lab assignments is allowed and encouraged. However, do your own work. Labs which are too similar will be handed over to the Committee on Academic Misconduct and handled by them.

Suggestions

Don't get behind in the lab assignments.
Probably the biggest reason that some students do poorly in this course is getting behind in the labs and never recovering. Be forewarned, some labs depend partially on previous labs.
Design and implement in a top-down, modular fashion.
Get something working that has the skeleton structure of what you need and then add features to it. Each time you add a feature, test it and make sure everything is still working. It can be tough to debug graphics programs if all you know is that the output is wrong and you're not sure any one module is working.

Lab Submission

You are to submit lab assignments electronically . For each lab, submit all necessary source files. Do not submit the executable. Name the executable according to the lab assignment specification (e.g., lab0)

See the man page on 'submit' if you haven't used it before. The name of the class to use in the submit command changes from quarter to quarter, so check to see what the submission name is for this quarter either on the course newsgroup or class web page. A sample submission for course cis681 would look like:
submit c681aa lab2 main.c subroutine.c routines_681.h
Or, if all of the files are in a subdirectory called 'lab2DIR', then:
submit c681aa lab2 lab2Dir

Last Lab CANNOT be Handed in Late

The last lab CANNOT be handed in late!

Last updated 3/11/08