Description

In this project, you will propose and implement a project of your choosing. This project may be completed individually or in pairs. The project should be related to physically-based simulation or another area of computer graphics. The project consists of multiple steps. You may complete the pre-proposal and proposal stages at any time up to the deadline, even at the beginning of the course. Starting early gives you more time for feedback, negotiation, and completing the project itself.

  1. Pre-proposal (due Feb 13, before class). Email me a short paragraph describing what you want to do. This should be a concrete idea, but full details will be delayed until the full proposal. Be careful to define the scope of the project. If you wish to work with a partner, one email including both your name and your partner's name is fine.
  2. Feedback. I will reply to the pre-proposals with feedback by noon Feb 14. Ideas that seems reasonable in topic and scope will be approved at this time.
  3. Negotiation (ends Feb 15, at 5pm). If your pre-proposal is not approved, you will have until this time negotiate a suitable idea (by email or in office hours). You may also negotiate changes to approved pre-proposals.
  4. Proposal (due Feb 22, due at the beginning of class). 2-3 pages. This document should describe in detail the problem you intend to solve, including background, an overview of what you are proposing to do, and a list of concrete goals. Your proposal should state what functionality you will be able to demonstrate during the presentation. Be sure to carefully define the scope of your project. If your project will be done with a partner, one proposal with both names is sufficient.
  5. Complete the project.
  6. Write up your project. Your write-up should be at least 3 pages (excluding figures, which are encouraged but not required), but it may be as long as you need. The write-up should tell me what you have accomplished. It should discuss each of the concrete goals from the proposal, indicating whether the goal was reached (fully or partially). Examples of additional things you might include are problems that you encountered, things you learned while doing the project (whether it be simulation concepts, programming tools, debugging tricks, etc.), or what you might do differently if you were to do the project over. It is okay if you do not meet all of your proposed objectives, provided you have made a reasonable effort do so and are able to draw lessons from it in the write-up. Write-ups are due at the beginning of the final exam period and should be turned in on paper. If you did the project with a partner, one copy with both names is fine.
  7. Presentation. Each project will include a 10-minute presentation to the class explaining what you have done, how you did it, what works, and what does not. During this presentation, you should run your program to demonstrate what it can do, including the items listed in your proposal. If the project was done with a partner, you will present together. Presentations will occur during the final exam time slot.

Project Ideas

Below are some ideas for a project. You are also encouraged to come up with your own idea. Students often choose to implement a published graphics paper (or a portion of such a paper) on a topic that interests them, but this is not required.