HS Summer2018
| Title | CISC440/640 Computer Graphics |
| Shortened URL | https://goo.gl/th9HB2 |
| Description | A first course in computer graphics covering fundamental concepts and techniques related to rasterization, textures, 2-D and 3-D transformations (including perspective projection), shading, hidden surface elimination, and anti-aliasing, as well as selected topics in modeling, animation, ray tracing, and global illumination. OpenGL will be used for programming; you should have some familiarity with C/C++ or be ready to learn it. |
| When | Tuesdays and Thursdays, 2-3:15 pm |
| Where | ISE 207 |
| Instructor | Christopher Rasmussen, 446 Smith Hall, cer@cis.udel.edu |
| Office hours | Wednesdays, 10 am -- 12 pm |
| TA | Chunbo Song, songcb@udel.edu TA office hours: Mondays, 3-5 pm, 201 Smith Hall |
| Grading |
Graduate students will be given extra tasks to complete or features to implement on each homework, and extra questions to answer on each exam. Programming assignments will be graded on the basis of correctness, efficiency, and originality. This is not an introductory programming class, so coding style is not critical. However, if you want partial credit for something that doesn't quite work, it needs to be well-commented and easy to follow. For the overall course grade, a preliminary absolute mark will be assigned to each student based on the percentage of the total possible points they earn according to the standard formula: A = 90-100, B = 80-90, C = 70-80, etc., with +'s and -'s given for the upper and lower third of each range, respectively. Based on the distribution of preliminary grades for all students (i.e., "the curve"), the instructor may increase these grades monotonically to calculate final grades. This means that your final grade can't be lower than your preliminary grade, and your final grade won't be higher than that of anyone who had a higher preliminary grade. I will try to keep you informed about your standing throughout the semester. If you have any questions about grading or expectations at any time, please feel free to ask me. |
| Piazza |
|
| Academic policies | Programming projects are due by midnight of the deadline day (with a grace period of a few hours afterward...after sunrise is definitely late). A late homework is a 0 without a valid prior excuse. To give you a little flexibility, you have 6 "late days" to use on homeworks to extend the deadline by one day each without penalty. No more than three late days may be used per assignment. Late days will automatically be subtracted, but as a courtesy please notify the instructor (and CC the TA) in an e-mail of your intention to use late days before the deadline. See submission instructions below.
The two exams will be closed book (i.e., no reference materials allowed). Unless otherwise instructed, you are responsible for all material covered up to the day of the exam, both from the assigned readings (everything in the Readings column of the Schedule below) and in lectures (excluding guest lectures). Students can discuss problems with one another in general terms, but must work independently on programming assignments. This also applies to online and printed resources: you may consult them as references (as long as you cite them), but the words and source code you turn in must be yours alone. The University's policies on academic dishonesty are set forth in the student code of conduct here. |
