15-462 Administrative Information for Fall 2002

Place and Time: Tuesday and Thursday from 10:30 to 11:55am


Jessica Hodgins

Alla Safonova

Teaching Assistants:

Joel Micah Donovan

Michael De Rosa

Online Resources

The class web page is at
This is the primary online source for information about the course, including assignments, lecture notes, and administrative details.

The class email list is graphics-spring-07@cs.cmu.edu

Web Resources

OpenGL Website
OpenGL Programming Guide (aka the Red book)
GLUT (OpenGL Utility Toolkit)
GLUT Documentation
FLTK Home Page
FLTK Documentation
C++ Reference
C++ Standard Template Library (STL)


Required Text

Other Texts and Sources

Grading Information

Grading for the class will be divided as follows:

We can't accurately predict where the letter grade cutoffs will be, but an "A" will require at most 90%, a "B" will require at most 80%, etc. To get a good grade, you will be expected to do well in both the programming and the written work (exams and homework). There is a strong correlation between students who come to class and those who do well on the exams.

The programming assignments will also have small amounts of extra credit.

You may use Maple or similar systems to help with algebra on assignments, but where you do, turn in a transcript.

If you use code from the web for help in an assignment, you must turn in a pointer to your source or it will be considered cheating. Obtaining the majority of the code for an assignment from any source is not ethical.

Assignments and Homework

There will be two kinds of assignments: Programming assignments and written homeworks. All homeworks are solo; programming assignments are to be done solo unless otherwise specified. See below for explicit rules about what collaboration is allowed.

For programming assignments, we encourage you to use the software tools we provide (which means working on a platform we support, or bringing the tools up on some other platform yourself.) Supported platforms are the Linux PCs in WeH 5336. If you choose to use something non-standard (at your own risk), you'll need to get an executable compiled in the linux cluster for grading.

Grading on programming assignments is based on your programs' functionality, usability, and on the quality of the animations or images you produce. Programs must of course be your own individual work, although you are free to use the software tools that we provide or comparable tools that perform the same purpose.

Late policy

Programming assignments should be turned in by midnight on the day they are due.

Written homeworks will be collected at the end of the class they are due or can be put in Hodgins's mailbox on the 4th floor of NSH before 9:30am the following day.

Late days: A total of three late days may be taken during the semester on programming projects and assignments. The flexibility provided by those late days is intended to get you through the time where all your classes just happen to have assignments due on the same day. Extensions beyond those three days require a solid good excuse or a penalty of 10% of the value of the assignment/day.

Cheating Policies

Cheating will not be tolerated. If someone is caught cheating, we will follow the procedures outlined in the CMU academic standards.

You may talk about the assignments with others but you must write the code and solve the problems yourself. Sharing answers or using the code of someone else in the class (this year or some previous year) constitutes cheating.

What is considered cheating?

What is not considered cheating?

If you aren't certain whether something is or isn't cheating, even by the spirit if not the letter of these guidelines, please ask.