All assignments must be turned in on the due date given; if your assignment is received after midnight (i.e., the next day), it is considered late. You are responsible for ensuring that all files are turned in on time, if a program is turned in late there is a penalty detailed online here.
When you are done with your project and are confident it is satisfactory, you should submit it electronically using the directions available here. You may submit an assignment as many times as necessary, but only the files included in the last submission will be graded. Thus, you should always submit all your project's files -- even if they have not changed since a previous submission. Note, an assignment is considered late if any submission is late, even if your first submission is on time. You may lose points on your assignment if your final submission is incomplete or late.
Homeworks
Homeworks are solo projects, on which you must work by yourself.
- Ray Tracing, due Tuesday, September 1
- Transforms, due Tuesday, September 15
Programming Projects
Programming projects may be done by individually or with a partner. You may choose your own partners for each project. For each group project, only one final program should be handed in.
- Ray Tracer, due Tuesday, September 8
- Hierarchy, due Tuesday, September 22
- Convert one of your JOGL projects to C++ by the end of the day, Friday, October 9
- Introductory interactive animation for the Link's Media Wall by the end of the day, Monday, October 27
Starter Code
Most assignments will include code to get you started. This may consist of completed classes that you will utilize but not modify or classes in which some methods have been completed and others are left for you to fill in. In either case, comments will clearly indicate which sections of the code you may edit and which must not be modified (you can go to these sections directly by using the Tasks view within Eclipse). All starter code may be obtained with the Ambient download tool by following the directions here. The download site for the course is
http://www.cs.duke.edu/courses/cps124/fall09/snarf
Files to Submit
You should submit only code, text, HTML, or PDF, and possibly image files (gif, jpeg, or rgb) or sound files (.au or .wav). You are free to use any programming environment available to complete your work, however, you are responsible for converting it into one of the standard format listed above (most current programs can save or print files to a variety of alternate formats). All files turned in must include your name.
Each programming project should include a README file that includes:
- your name and Net ID
- the date you started the assignment, the date you completed the assignment, and an estimate of the number of hours you worked on it
- list of the students with whom you discussed the assignment. Since assignments are to be your own work, you should keep track of anyone with whom you have had a significant conversation about a program. You are welcome to talk with the course staff about the assignment, and to other students about broad ideas and concepts.
- any books, papers, or online resources that you used in developing your solution
- list of data files needed to run your program (images, models, scripts, or input) and where to find them
- directions for compiling and running the program
- list of systems on which you tested your program
You may also include your impressions of the assignment to help the course staff improve it in the future.
You will lose points on your assignment if it does not include a proper README file.
