Grading
| assignments / homework | 45% |
| final project | 25% |
| quizzes | 10% |
| midterm | 20% |
Grading is done on an absolute, but adjustable scale. This means that there is no curve. Anyone earning at least 94% = A, 90% = A-, 87% = B+, 84% = B, 80% = B-, etc. This scale may go down, but it will not go up.
In order to earn an A+ you must do most of the optional assignments, perform exceptionally well on the final, and exceed expectations in general.
Programming Assignments
Assignments are due by midnight on their due date and will not be accepted late for full credit. Each student is granted two assignment extensions with no penalty during the semester. To request an assignment extension, you must complete this form within 24 hours of the due date, and the assignment must be received within 72 hours of the original due date. Assignments turned in on time receive no penalty, and students who do not use their late penalties receive extra credit at the end of the semester. Assignments can be submitted up to one week late for half credit.
Individual extensions will be granted for medical reasons (see the Short-term Illness Notification policy) or other circumstances beyond your control that must be presented with an official Dean’s excuse. I do not grant extensions after an assignment is due. If you have personal reasons to ask for an extension, and you do so at least a week in advance, it’s possible to get one, so please ask.
Exams
Exams will be held during the lecture time and in the same room. The final will also be in the same room. See the Calendar page for dates and times.
Course Policies
Quizzes and Exams taken online or in-class must be your own work, you should not collaborate on them unless you’re given explicit permission to do so. This means you don’t talk to anyone or look up anything on the web unless you’re given instructions otherwise.
On programming assignments, you may consult with the professor about any aspect of the assignment. You may consult with other students only in a general way, e.g., about debugging or code issues, or questions about wording on the assignment. You cannot actively work with someone unless the assignment specifically grants permission to work together with another student. You can ask for hints or help, but if you do you must acknowledge this in your README that you submit with each assignment. Similarly, if anyone looks at your code to offer you help, guidance, or words of encouragement you must acknowledge this in your README.
Consult means you can discuss the programs before writing code, and get help with debugging your program, but you should write your own code. Writing one program and making multiple copies of it is NOT acceptable! For each assignment you are expected to include a list of the people with whom you have consulted (including students, TA’s, tutors, professors) as part of your submission. That is, you must include the names of everyone who helped you as well as the names of everyone you helped.This is required, it’s called the README file, and failure to provide it will result in rejection of the assignment as complete (you can resubmit).
Grading Policies
All care will be taken to make sure that grades are accurately calculated and reported. However, mistakes happen. If there is an error in your grade, due to a grading mistake or a reporting mistake I want to fix it. Please report the error: here
All grading error requests MUST be made within 3 days (days count as weekdays while Duke is in session) from the initial grade being posted. No grade change requests will be accepted more than 3 days after a grade is posted.
Textbook
Fundamentals of Computer Graphics, Third Edition, by Peter Shirley, Michael Ashikhmin, and Steve Marschner, Pearson, ISBN-10: 1568814690, ISBN-13: 978-1568814698
This book is available at the Duke bookstore.