Semester Project

tree motion: Jie, Ben
Tree texturing Daniel T. and Alan
terrain Luther and Ryan, Daniel A.
IB rock stuff Joe
feedback cory
relighting timp Ilya.

The purpose of the semester project is to give you experience designing algorithms which mimic things found in nature. The project will be much more useful if you pick a project that both you and I find interesting. To make that happen, I've prepared a list of projects and a one page summary of each project (1/8/08) We'll add the following project to the list: terrain. Do something interesting with terrain. We may add something about billboards for vegetation as well.

You'll also have a most relevant project paper presentation to make.

To get an A, your project does not need to be publishable. Though I may be interested in working with you to prepare your project for publication if you are interested in that and if your project looks promising.

This page highlights each phase of the project. The project also includes a presentation of the most relevant paper related to your project. You can find details about that presentation here: most relevant project paper.

Due dates can be found in the schedule.

Step 1: Pick a project.

You will pick from the list of projects using the project picking algorithm in the syllabus. I anticipate that we'll do the picking on the second day of class.

Step 2: Do a literature review.

Find and summarize the 2 most significant papers related to your project area. List 3 other papers which didn’t make the final set of 2 and say why they weren’t as significant (for your work) as the other 2. Describe how your work will be influenced by the two most significant papers. Note that you should read and study the two most important papers but that you might not read the other 3 as closely. You’ll present one of the two most important paper in class.

In your literature review, include a paragraph which describes what you are going to do solve the problem. Include some argument on why you think that solution might be a solution.

Step 2.5: Proposal

This was in the syllabus and on the schedule, but not included in this list. I had the due date as 2/29 but I am going to move that up to keep momentum going on the project. The proposal is just a matter of answering the five research proposal questions in the CS Handbook. I've reweighted the grades a little so that this is worth 5% not 10% and added that 5% to the final report which is now worth 15%.

Step 3: Write progress reports.

Tell what you’ve done on your project and how long you’ve spent. It should be clear from your report that you spent at least 6 hours per week on the project. You might include things like screenshots and code as appendices. You should include some text that says what problems you've solved and what problems you are working on. I will not be optimistic in grading these progress reports. If it's not clear in the report that you've made significant progress, then I'll assume you haven't made significant progress.

See Schedule for due dates. They come about every other week in March.

Step 4: Do a Demo

Demo your stuff on the last day of classes during class. We will walk around the TMCB as needed for your demos.

Step 5: Turn in the final report.

Write about what you did. What went well? How does your work compare to the state of the art? This should look like a conference or journal paper (though it may not be publishable as such, it's just a semester project).

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License