Computer Science 110
The Art & Science of Computer Graphics

You have a great deal of freedom in choosing what to model for this project. However, it must be an effective demonstration of your modeling skills. Projects of appropriate scope and difficulty might involve:

• a single model that you shoot with several cameras,
• a "study" - a collection of models that focus on a concept (e.g., shadow effects as the sun rises, moves across the sky, and sets), or
• a short animation.

Choosing to produce an animation will demonstrate your willingness to spend extra time in careful planning, but there is no "extra credit" for choosing this option. Any of the above can result in a good project (and hence, a good grade).

Your project should include substantial new work. You are encouraged to use your previous labs or class shared models, but be sure that the bulk of your work is new. Any work borrowed from your own previous labs, class examples, and shared models must be clearly cited!

The final project will account for 20% of your course grade.

By 11:00 AM, Monday, April 12, 2010, submit a project proposal.

Your proposal should answer the following questions:

1. Of all of your lab models developed this semester, which two do you think were most successful and why?
2. What modeling skills (e.g., materials, realistic object design) do you think you need (or would like) to spend more time developing?
3. What do you want to do for your final project? Include drawings if you wish.
4. What aspects of your proposed project would address those skills you mentioned in question 2?

Everyone should arrange to meet with me during the week of April 12 to discuss your proposal and to finalize a "grading contract" for your project based on your proposed project. We will set goals and an implementation schedule for your project. Your grade will be based, in part, on how completely you meet these goals (see below).

As the end of the semester approaches, Kendade 307 will become very busy. As your models become more complex, rendering times will increase. Plan ahead!

Here are some suggestions and requests:

• Log out when you leave the lab to make sure computers are available for others.
• Use the Linux systems in Clapp 202.
• Use other computers, either by installing Mead (if you have or have access to a Mac) or by using the bootable CDs. This is especially helpful for those times when you need to render complex images.
• When developing models, you will render your images many, many times. To shorten rendering times, turn off anti-aliasing, use a lower image quality, and replace surface images with regular materials. When you want to generate a better image, turn these features back on.

Submission is similar to the procedure you have used for labs all semester:

1. In a comment at the top of your main model file, describe how your project has met the goals we agreed to in your grading contract.
2. Submit your nicely-formatted and appropriately commented model file, any necessary surface or grain image files needed to render your model, and the images it generates in a folder named with your last name and "Final". For example, I would submit a folder "TerescoFinal". When you have your model file and your generated images ready in that folder, you can drag it to the submit folder.
3. Create a new section of your wiki page, where you describe your project and include a number of images that you have produced. Include both "artistic" information about what you're trying to model and technical information about how you convinced Mead to do it.
4. Clearly cite any usage of class examples and shared models, both in comments in your model file and on your wiki entry.

You will have a chance to show off your work on this project (in addition to the work you've done throughout the semester) to classmates and guests at a "gallery opening" to be held at 2:00 PM, Friday, May 7, 2010, in Kendade 307.

Your grade, which totals 20% of the course grade, will be based on:

• Completeness of your proposal (10 points)
• Model code documentation (comments) (10 points)
• Model code style (good names, use of object hierarchy, defined names, functions) (10 points)
• Wiki presentation (10 points)
• Satisfaction of grading contract obligations (60 points)