Lab Guidelines
List of Labs and Weights
-
Use of CL112D machines and simple OpenGL program (1%)
-
Basic OpenGL 3D orthographic projection drawing system (9%)
-
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.
- Of course you can develop your lab in any environment you want, but make sure that what you hand in will work in the CL112D environment.
- 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 (uploading files, naming conventions, etc.)
NOTE: Grading of labs is relative to the lab specification, not the example lab.
The example lab is just that - an example.
It may not follow the lab spec exactly in order to demonstrate features.
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.
A well-organized lab will facilitate the coding of later labs.
-
For labs that add features to previous labs, incrementally develop the lab.
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
For CSE581, Autumn '11, you are to zip up a Visual Studio 2011 project into a file and upload it using the Carmen dropbox.
Last Lab CANNOT be Handed in Late
The last lab CANNOT be handed in late!
Last updated 3/11/08