CS4620/5620 Introduction to Computer Graphics
CS4621/5621 Computer Graphics Practicum
Fall 2012


Dec 14:  Results from the Rendering Contest.

Nov 21:  PA3B has been released. It is due on December 7, 2012 before midnight. The description is in CMS.

Nov 3:  PPA2 has been released. It is due on November 14, 2012 before midnight. The description is in CMS.

Oct 15:  PA2 has been released. It is due on October 24, 2012 before midnight. The updated description and code has been posted in CMS. Also, please see the FAQ at the FAQ page.

Sep 26:  HW2 has been released. It is due on October 5, 2012 before class. The description is in CMS.

Sep 19:  PPA1 has been released. It is due on October 4, 2012 before midnight. Grab the description and code in CMS. FAQ page is here with tutorial videos.

Sep 12:  PA1 has been released. It is due on September 26, 2012 before midnight. The updated description and code has been posted in CMS. Also, please see the tutorial videos in the FAQ page.

Sep 5:  The deadline of HW1 is changed to September 19 at the beginning of class. We also added some clarification to the problems. The new PDF is availble here.

Sep 4:  HW1 is available here. It is due on September 17 via CMS and in class.

Aug 22:  Register on piazza.

Aug 22:  Welcome!

About CS4620/4621, 5620/5621 Introduction to Computer Graphics

Kavita Bala ( )
     ofc hrs: Mon 3:30PM - 4:30PM in 5142 Upson


Pramook Khungurn (Ph.D. TA, )
     ofc hrs: Tuesday 5:00PM - 6:00PM in 5128 Upson
Daniel Schroeder (Ph.D. TA, )
     ofc hrs: Thursday 7:45PM - 8:45PM in 328B Upson
John DeCorato ( undergraduate TA)
     ofc hrs: Monday 5:00PM - 6:00PM in CSUG lab (361 Upson)
Sean Ryan ( undergraduate TA)
     ofc hrs: Wednesday 4:30PM - 5:30PM in Rhodes 590

Staff List:

Time and place:
CS4620: MWF 2:30PM - 3:20PM, Phillips Hall 219
CS4621: F 3:35PM - 4:25PM, Location Hollister 110


Foundations of 3D Computer Graphics
first edition (recommended)

Shirley & Marschner,
Fundamentals of Computer Graphics
third edition (recommended)
The second edition is available as an ebook via the library (link). Search for "Peter Shirley". Or authenticate at the link above, and then directly go to this link for the book.

Supplemental books and materials:




There will be 3 homeworks.

Programming assignments

There will be 4 programming assignments.


The prelims account for 40%, programming assignments (done in pairs) for 40%, and homeworks (done alone) for 20%. All numbers are within 5 percent of the final allocation and are not set in stone.



The principle is that an assignment is an academic document, like a journal article. When you turn it in, you are claiming that everything in it is your original idea (or is original to you and your partner, if you're handing in as a pair) unless you cite a source for it.

You are welcome (encouraged, even) to discuss projects among yourselves in general terms. But when it comes to writing up the homeworks or implementing the projects, you need to be working alone (or only with your partner if you are doing a project as a pair). In particular, it's never OK for you to see another student's homework writeup or another team's program code, and certainly never OK to copy parts of one person's or team's writeup, code, or results into another's, even if the general solution was worked out together. Homeworks can be discussed in general terms, but must be worked on alone.

You're also welcome to read any published sources—books, articles, public web sites—that help you learn. If you find an idea in one of these sources that becomes part of your solution (or even gives you the whole solution), that's fine, but it's imperative that you credit that fact on your homework or in a comment in your code. Otherwise you would be falsely claiming to have invented the idea yourself.

Academic Integrity

In this course we expect complete integrity from everyone. School can be stressful, and your coursework and other factors can put you under a lot of pressure, but that is never a reason for dishonesty. If you feel you can't complete the work on your own, come talk to the professor or the TAs, or your advisor, and we can help you figure out what to do. Think before you hand in!

Clear-cut cases of dishonesty will result in failing the course.

For more information see Cornell's Code of Academic Integrity.