Place and Time:
Tuesday and Thursday from 9am to 10:30am
Wean 5409 after the first two weeks of class, 1305 NSH before that
http://www.cs.cmu.edu/~jkh/462_f02This is the primary online source for information about the course, including assignments, lecture notes, and administrative details.
The class newsgroup is cmu.cs.class.cs462. This group will serve as a Q&A forum. Feel free to ask questions or exchange information. We'll read the group and answer. We'll also post important official announcements there, as well as in the WWW page and occasionally via email.
Unofficial errata for the textbook is available here: http://www.cs.washington.edu/education/courses/cse591/CurrentQtr/about/watt_errata.pdf
Grading for the class will be split up as follows:
I can't accurately predict where the letter grade cutoffs will be, but an "A" will require at most 90% (900 points), a "B" will require at most 80% (800 points), 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 exam.
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.
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 make one available to us for demos.
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.
This is not a user interface course. We suggest you keep user interface hacking to a minimum (or at least don't let it interfere with getting the graphics working).
Programming assignments should be turned in on the day they are due in class by midnight.
Written homeworks will be collected at the end of 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 REALLY good excuse or a penalty of 10% of the value of the assignment/day.
Cheating will not be tolerated. If someone is caught cheating, they will automatically be given 0 points on the assignment, homework, or test that they cheated on, as well as being reported to the authorities. Depending on the severity of the offense, more drastic measures will be taken as 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 someone else's code (with the exception of utilities that the class provides) constitutes 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.