Project 4

The 4th project is an opportunity for you to explore some aspect of computer graphics research that is interesting to you. Your objective is to select a research paper, understand it thoroughly, and implement the algorithms/techniques it describes. You will work with a partner on this project using pair programming. The main deliverables are:

1. Proposal (10 pts.): Submit a 2-3 page proposal that describes your project and includes a schedule with weekly milestones, a discussion of the major risks in your project and how you will resolve them, a bibliography, and a (suggested) rubric for grading your results, which account for a total of 75 pts. Your proposal must be approved by me before continuing.


2. Concept Presentation (5 pts.): Give a 15 minute talk to the class explaining the what and how of your project.


3. Documentation (5 pts.): Document your progress with weekly status reports (1-2 pages) that describes what you've accomplished, how your accomplishments compare to your projected schedule, any major stumbling blocks you encountered and how you overcame them, how many hours you spent on the project in the last week, and proposed changes to your schedule and/or rubric. Your weekly report should be uploaded each Tuesday before class time to your Sakai dropbox.


4. Final Presentation (5 pts.): Give a 10 minute talk in which you describe your project and demo your results.


5. Project results (75 pts.): Upload a zip file including all of your code, images, etc. as well as an html write up.

Identify abstracts you find interesting then locate the actual papers. The Siggraph conference also has interesting videos that that provide a look at new research results.
Research papers often present incremental work. You should look back through prior work to find the original paper, which is likely to be the simplest, as a place to start.

WARNING: These papers omit a lot of detail. It is up to you to fill in the missing pieces. This is not something you can do at the last minute, so allow a lot of time.

GRADING: You and I will agree on a grading rubric before your project is approved. If you run into unforeseen technical problems, and this is not unusual, it is up to you to (a) offer a revised rubric and schedule, (b) document the time you have spent on the project to justify your request. An example of an unforeseen technical problem that this is intended to cover is a minor step that turns out turns out to be a major project in and of itself; you should identify these types of problems early on.