Steven Longay's CPSC453 Fall 2009 Page
Contact: slongay at cpsc.ucalgary.ca
View Ray Tracing Competition Results Here
In case someone missed it, here are my notes from the exam review. The writing is pretty messy and its full of spelling mistakes but it might be better then nothing.
If you need some time off of studying check this out! They even have some sudo code at the end.
Kimberly from my TuTh tutorial has made some nice comparison images between her raytracer and maya.
Here is an image from her program
Here is an image from maya
Notice how similar they are, obviously the maya raytracer is more advanced but its nice to know that what you learn in this class is really the basis of what is used in commercial products.
Lab 0 - Setting up your personal computer
Lab 1 - Course Intro and C++ Review
Lab 2 - OpenGL/GLUT intro
Lab 3 - Everything you've ever wanted to know about GLUT. And more!
Lab 4 - Tips for Assignment 1
Lab 5 - More on makefiles, rendering text, double buffering and questions on Assignment 1
Lab 6 - Transformations and Viewports
Lab 7 - Assignment 1 DEMOS
Lab 8 - Tips for Assignment 2 and the rest of Assigment 1 Demos
Lab 9 - Stuff on assignment 2. Drawing Curves and some openGL to know for drawing in 3D
Lab 10 - Subdivision - Chaiken and B-Spline, open and close cases
Lab 11 - Surface of Revolution and Tensor Product Surfaces
Lab 12 - Question and answer period for assignment 2.
Lab 13 - Intro to Qt
Lab 14 - Assignment 2 Demos
Lab 15 - Virtual Trackball and Assignment 2 demos
Lab 16 - Assignment 3 Overview
Lab 17 - Viewing and Lighting
Lab 18 - OpenGL Lighting and Materials
Lab 19 - Playing with lighting, QImage and ppm files
Lab 20 - Ray-tracing 1 - Taught by Luke Olsen
Lab 21 - Ray-tracing 2 - The wednesday lab will be taught by Luke Olsen
Lab 22 - Ray-tracing 3 - more advanced topics
Lab 23 - Assignment 3 Demos
Lab 24 - Final Lab! Ray-tracing Questions
Assignment Note: On assignment 1 most marks were lost on documentation. Things to keep in mind for future documentation writeups:
- Tell me how to compile your program, unless you have a makefile and I can just type make (which should be the case). If you have multiple files and I have to compile them myself you will loose some marks here.
- Tell me how to use your program. A lot of people lost marks because I had to delve into code to figure out your control scheme, or I just didn't bother to mark it at all. Be sure you explain your control scheme here or have some onscreen info.
- When reading your algorithms, they should be detailed enough that I feel I could implement them myself after reading it. That being said it should not be sudo code either. Find a nice medium, but "Add points in a zig-zag pattern between the two given points" doesn't cut it.
Note: To award those who put in extra effort I will be submitting the best two assignments I receive to the prof. If you are thinking of grad school, scholarships or a job he has offered to write letters of references for those who do exceptional work on the assignments. This is retroactive so I will be submitting the best of assignment 1 and all future assignments.
The instructions on how to submit assignments here
Here are the marks for the assignments. Last 4 digits of ID number are shown. If you have any questions about your mark send me an email and ill forward you your mark breakdown. If you havnt done a demo yet, your mark here will be very low, it will be updated after your demo