Winter 2000 COM3370 Computer Graphics
Assignment 3
Introduction
In this assignment, you will finish up your ray tracer. (you may integrate the next assignment with your ray tracer but it is not required.) The required features to add this time are:
planes and/or polygons
texture map, either computed or read from a file
bump map
Optional addition:
general quadrics
or just something other than planes and spheres, e.g. cylinders or ellipsoids
General description
- Continue to develop the ray tracing program you started in the last assignments. Your scene will again consist of 2 or more opjects, with each given by its
-
type: sphere, plane, polygon, quadric
-
defining spatial data:
-
sphere: center (x, y, z), radius
-
plane: point, normal vector
-
polygon: list of vertices in 3-space
-
quadric: list of coefficients? or type and relevant information
e.g. cylinder, point and vector (or two points) to define the axis, radius
-
color (R, G, B)
-
texture, none or which map (one available map is enough fo this project)
-
bump, none or which function, try one on a plane, one on a sphere
-
coefficients: ka, kd, ks, kt (ambient, diffuse, specular, transmitting).
- At least one of your spheres must be reflective to show the reflection of you planar textures and bumps.
- At least one of your spheres must have a bump map.
- At least one of your planes must have a texture map.
- At least one of your planes must have a bump map.
See Building a Ray Tracer - Page Two and
Building a Ray Tracer - Page Three for sample images. Note that the small images on that page are links to larger images.
Due
By midnight Tuesday, August 16, 2001.
Grading
The usual grading guidelines apply for late work.
For the performance parts of this program:
- polygons - 30 points; (planes but not polygons - 20)
- bump map on plane - 15 points
- bumpmap on sphere - 15 points
- texture map on plane - 15 points
- Quality of your image(s) - 10
Code, comments, ease of use - 15 points
Turn in:
- your source code. Your code should be well organized and commented.
- a makefile, if necessary.
- a README file containing:
- your name, the date, and the assignment number
- a list of the files in the folder with comment for each explaining its purpose
- instructions on how to run your program
- a description of any bug that you have not been able to fix. A documented bug will not cost you as much as an undocumented one.
- You may include data files for up to three scenes.
- Please do NOT email ppm files or executable code. I will generate them from your source code.
Harriet Fell
College of Computer Science, Northeastern University
360 Huntington Avenue #161CN,
Boston, MA 02115
email: graphics@harrietfell.com
Phone: (617) 373-2198 / Fax: (617) 373-5121
Last Updated: June 12, 2001, 2:38 p.m.
The URL for this document is:
http://www.ccs.neu.edu/home/fell/COM3370/COM3370prog3.html