15-464 Administrative Information for Fall 2005

Time: Tuesday and Thursday from 3:00-4:20pm
Place: Doherty Hall 2105

Online Resources

The class web page is at
http://graphics.cs.cmu.edu/nsp/course/15-464/Fall05/

This is the primary online source for information about the course, including assignments, lecture notes, and administrative details.

The class newsgroup is cmu.cs.class.cs464. This group will serve as a Q&A forum. Feel free to ask questions or exchange information. We will read the group and answer. We will also post important official announcements there, as well as in the WWW page and occasionally via email.

Prerequisite

Required Text

Grading Information

Grading for the class will be as follows:

Assignments and Homework

There will be two kinds of assignments: Programming assignments and written homeworks. All programming assignments and homeworks must be your own work (except for the code that we give you as part of the assignment). You may talk with others about the assignments, but please solve the problems and write the code yourself.

The final project may be done in groups of two or three. If you want to do a group final project, please coordinate this with the instructor.

Please test your programs in the WeH 5336 lab. All programs must compile and run on the Linux PCs in WeH 5336.

Late policy

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

Written homeworks will be collected before class starts on the day they are due.

Late days: A total of five late days may be taken during the semester on the first three programming assignments. No late days are permitted on the written homeworks, although your worst homework will be dropped from the grading. No late days are available for the final project. Extensions beyond these late days require a REALLY good excuse or a penalty of 10% of the value of the assignment/day.

Cheating Policies

Cheating will result in immediate penalties ranging from 0 points on the relevant assignment, homework, or test to failure of the course. All cheating cases are reported to the university, and severe offenses are brought before an Academic Review Board for consideration of further measures.

Course policy is that 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.

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.