Final Project

Here's your opportunity to explore an additional topic not covered in the previous assignments. It can be an extension of one of the homework assignments, a portion of your graduate research, a significant module of a final project for another course, or a brand-new project. Hopefully you can connect what you've learned in this course to your research area or other interests. The scope of your assignment should be carefully defined so that it can be successfully completed in about a month.

Teams of two are strongly encouraged, but you may do an individual project with persmission from the instructor. The project must include a significant programming component related to computer graphics. You will share your results through an in-class presentation to your peers and a publication-quality writeup.

Proposal

As you choose your topic and begin to flesh out the details, keep in mind that implementing new data structures or algorithms can take much longer than anticipated. Also be warned that designing and implementing even relatively simple user interfaces require alot of effort (and is not particularly relevant to this course).

Your proposal should be formatted using html or pdf. The document should include:

A brief summary (~200 words) of the technical problem you are going to investigate.
A list of the specific research papers and other sources you've collected for background reading. Talk with the instructor if you are unable to find at least 3 relevant research papers. Briefly describe the contributions of each paper and how your project relates to this work.
A timeline for your assignment with a list of the tasks you will execute and who will do what. It's ok to list optional tasks that you will work on once the core features are functional. You will be graded relative to the completion of the core tasks, so make sure your plan is feasible.

Final Report

Your final report should be formatted using html or pdf and follow a standard technical writing format (e.g., motivation, related work, algorithm/technique, results, conclusions, and bibliography). All students are encouraged to format their final report for submission to a relevant academic graphics or graphics-related conference (SIGGRAPH, Eurographics, etc.). Your report should describe the technical details of your project; in particular, we want to know about:

Any algorithms or data structures you implemented.
The core features of your assignment and how you tested them.
The challenges that you overcame (or failed to overcome). Note: As you're working on your project, save "blooper" images or video that show your intermediate results or mistakes, and include them in your report & presentation.
Any known bugs or limitations in your implementation, and potential avenues for future work.
How long it took you to complete the assignment, and who did what.

Make sure to acknowledge (in proper bibliographic format) all references you consulted to complete the assignment and the extent of any collaboration with other students or outside sources. As with the other assignments, submit your source code, any necessary data files, and sample images or video showing the results.

The final project reports are due Thursday April 24th. You may not use any late days for the report. We will not accept any late material unless accompanied by a note from the Dean of Students office.

Please include a representative 200x200 image with your submission for the project index page (see last year's projects). All projects reports will be posted online by default. If you do not want your project report posted online please send the instructor an email.

Final Project Presentation

On the last few days of class each individual/team will have 15-20 minutes to present their final project to the class. Attendance and participation (asking good questions) at your classmate's presentations is mandatory.

Summarize prior work as necessary. You don't need to discuss papers we covered in class.
Be technical: What were the challenges? How did you solve them?
Please give a live demo of your project if possible (depends on the project of course).
Teams of 2 or 3: All should present, and make it clear who did what.
Practice and time yourself.