You may work with one partner on the final project. The design of your final project is up to you. The timeline is below

• Wednesday 14 November 5pm, Written Proposals Due
• Wednesday 21 November 11:59pm, First Progress report
• Wednesday 5 December 11:59pm , Second Progress report
• Tuesday 11 December 1:05pm-4:15pm, presentations/demos
• Saturday 22 December Noon Final report, code due (no Exceptions!)

You should write your proposal in Proposal.md using the provided template. The proposal should be roughly 2 pages of text (1.5+ pages). You proposal should include the following elements

• A high level description of the project and your motivation for pursuing this topic
• A description of ideas that you will be using from class and new ideas you will be exploring
• A list of software tools you will be using. You may leverage third party packages, but be sure to list what code you will be writing and what code you will be importing.
• A list of short term, long term, and reach goals. Short term goals should represent incremental progress you can make in a week. Long term goals should describe what you would consider a successful implementation of your project. Reach goals can be something that might be a nice addition, time permitting, but may not be possible if there are snags in the early stages
• A description on how you plan to evaluate the success of your project.

Intermediate reports should highlight recent progress, discuss current roadblocks, and describe any adjustments you are making to your initial proposal. Intermediate reports can be submitted as markdown files in your git repo. Demos will be during the the lab time on Tuesday December 11th which follows a Thursday schedule. Demos will be roughly 10-15 minutes (depending on number of projects). You final submission should include

• Code implementing your project
• Instructions on how to run your project
• A write-up of 4-6 pages, describing the main technical highlights of your implementation.
• A list of references used. This could include web sites, books, or papers.
• If you used any third party code, be sure to document this in your references.

You project should combine some previous topics from the course and explore at least one new topic. You can aim for realism, efficiency, or artistic effect.

Below are just a few ideas.

• Scene Graph, hierarchical modeling
• 3D game with collision detection, interaction
• Efficient raytracing with data structures, e.g., oct-trees
• Parallel raytracing - CUDA or pthreads
• Photon mapping
• Ray Marching
• Physical systems - Cloth, water.
• metaballs
• Terrain modeling
• Bézier surface, curved surfaces, B-Splines. It may be possible to use OpenGL's tessellation shaders to help with this.
• Boids

You should regularly commit your changes and occasionally push to your shared remote. Note you must push to your remote to share updates with your partner. Ideally you should commit changes at the end of every session of working on the project. You will be graded on work that appears in your remote by the project deadline. You must attend the one and half hour demo session you are assigned below. If you wish, you may attend any of the other demo sessions. All sessions will be in Sci 240 on Tuesday December 11th.

If your project is real time, you should give a quick overview of your project and the tools used e.g., OpenGL shaders, CPU only, CUDA, followed by a real time demo. If your project requires offline rendering, take a few screenshots and display them in a slideshow and discuss the primary rendering steps in your project along with a discussion of how long it takes to process.

I will be happy to take volunteers for the presentation order at any time within a session, but otherwise, we will follow the order below chosen by Python's random.shuffle. If there are any conflicts with this schedule let me know immediately.