CSCE 4813 - Homework 5
Due Date - Dec 9, 2008

1. Problem Statement:

The goal of this assignment is to generate graphics images of "physically based" moving objects. In particular, your task is to generate a sequence of images that shows N objects moving through the scene with motion determined by simulated physics. Students have the choice of three possible motion sequences:

The book has one section on physically-based models (p561) and a sample particle system program in the appendix (p746). Both are probably more complex than you need for this project, but they may give you some ideas and useful information. There is also a wealth of information online if you search for keywords above.

2. Design:

There are several design issues for this assignment. First, what objects are you going to use, and how are you going to represent position and velocity information? Second, what graphics techniques will you use to generate images of these objects (ie material properties, light properties, shading model). Do you want to vary the colors and/or material properties over time in the simulation? What would be easy to start with, and what would be fun to include in the final program once the motion calculations are completed?

3. Implementation:

This is a complex assignment, so it is especially important "grow your solution" incrementally. For example, you may want to simply print out the positions (px,py,pz) and velocities (vx,vy,vz) of 5-10 points to see what they look like (and even plot them in a spreadsheet) prior to sending them to the graphics routines. Similarly, you may want to test/debug bouncing of one object before going to N objects. As a general principal, you will receive more credit for a working program that completes 1/2 the tasks than you will for a non-working program that attempts all of the tasks.

4. Testing:

Test your program to check that it operates correctly for all of the requirements listed above. Also check for the error handling capabilities of the code. Save your testing output in text files for submission on the program due date.

5. Documentation:

When you have completed your program, write a short report (less than one page long) describing what the objectives were, what you did, and the status of the program. Does it work properly for all test cases? Are there any known problems? Save this report in a separate text file to be submitted electronically.

6. Project Submission:

In this class, we will be using electronic project submission to make sure that all students hand their programming projects and labs on time, and to perform automatic analysis of all programs that are submitted. When you have completed the tasks above go to the class web site to hand in your documentation, program, and testing files. You are welcome to use either the "submit" or the "file upload" method.

The dates on your electronic submission will be used to verify that you met the due date above. All late projects will receive reduced credit (50% off if less than 24 hours late, no credit if more than 24 hours late), so hand in your best effort on the due date.

You should also PRINT a copy of these files and hand them into your instructor in the department office. Include a title page which has your name and uaid, and attach your hand written design notes from above.

NOTE: We will have a "show and tell" day on the last day of class where students can demo their final projects to each other, and talk about what they had the most fun/difficulty with on the final project.