| Time: | 5:00-6:15 Tuesday and Thursday | ||||||||||||||||||
| Place: | MEC 339 | ||||||||||||||||||
| Instructor: | Greg Humphreys, humper@cs.virginia.edu Office Hours: Friday 2-4 (Olsson 216) |
||||||||||||||||||
| TA: | Nolan Goodnight, ngoodnight@cs.virginia.edu Office Hours: TR 3:00-5:00 in Olsson 227 (Graphics Lab) |
||||||||||||||||||
| Goals: | This course provides a broad overview of the theory and practice of rendering. We will discuss classic rendering algorithms, although most of the course will focus on either fundamentals of image synthesis or current methods for physically based rendering. The final project will be a rendering competition. | ||||||||||||||||||
| Assignments: | Assignments are due at 11:59:59 PM on the day in question. See the late policy below for some more information about turning in assignments on time. All assignment descriptions will be made available as soon as possible.
|
||||||||||||||||||
| Software: | Required:
Potentially useful:
|
||||||||||||||||||
| Background: | Students should have a good working knowledge of computer graphics at the level of CS445 or its equivalent. Solid knowledge of integral calculus and some basic geometric algorithms is also a must. It is also expected that students have been exposed to probability at a high school level. We will review key relevant concepts in probability, statistics, and signal processing, but some previous exposure to any or all of these topics will make that material go down a lot smoother. | ||||||||||||||||||
| Texts: | Physically Based Rendering: From Theory to Implementation, by Matt Pharr and Greg Humphreys | ||||||||||||||||||
| Grading: | Grading will be based solely on the quality of your programming assignments, written assignments, and final project. There will be no exams. Each assignment (programming and written) will be worth 10% of your grade, and the final project will be worth 50%. The "Hello, World" assignment will not count towards your grade except in the sense that you will not pass the course if you do not complete it. | ||||||||||||||||||
| Honor Code: | The honor code applies to all work turned in for this course. In particular, all code and documentation should be entirely your own work. You may consult with other students about high-level design strategies, but you may not copy code or use the structure or organization of another students program. Said another way, you may talk with one another about your programs, but you cannot ever look at another student's code nor let another student look at your own code. Obviously, you may collaborate freely with your project partner. | ||||||||||||||||||
| Late Policy: | You should strive to complete your assignments on time. To cope with unforeseen circumstances, you will be allowed four days of grace during the semester, to be used as you see fit. After these days are gone, assignments can be turned in one day late for 50% credit. After two days, assignments will not be accepted. No late days may be used for the final project or the final project writeup. Notice that these are calendar days, not weekdays, not class days, and not non-holiday days. The clock is running during weekends, spring break, and while you're partying. Exceptions can be made for sickness and/or family emergencies; see the instructor.
Note in particular that computer downtime is not an excuse for lateness. Computers crash and networks go down; the world is an imperfect place. Be prepared. Do not start assignments at the last minute. Do not forget to leave time for the render to complete (this is especially true of the final project). |