- Third exam
- Next Monday (May 4)
- Comprehensive exam re putting together ray tracing ideas
- Mainly math, maybe a little programming
- Likely to pose some ray tracing scenario common to all questions, then ask 3 - 4 questions about building a ray tracer for it
- Individual questions similar in style to other exams
- Rules similar to other exams, e.g., open references
- Project presentations
- Wednesday, May 13, noon
- Plan to talk for 10 - 15 minutes, for an audience who knows ray tracing and general math, but not your specific area
- Describe problem/question
- Discuss/show methods/models/research/results, including demos as appropriate
- Discuss conclusions/further work
- Donuts and cider
- SOFIs
- Fill them out via http://go.geneseo.edu/sofi_survey
- Useful to me in improving courses
- Interleave with coding
- Short code-test-debug cycles
- One cycle per function
- Stubs = simple place-holder for function not written yet
- Drivers = simple place-holders for making calls
- Top-down coding = start coding with main function, work down from there
- Small, simple, test cases
- Test case selection
- Black box tests = based on special cases of problem, independent of code
- White box tests = based on code “coverage”
- “Assume-it-works” tests
- Regression test = keep all tests you do in a “library” rerun them all when you make changes
- Example: triangles in my ray tracer
- Some examples from you that don’t seem to have the right triangles in them
- What a simple 1-triangle test case should look like
- What the ray tracer draws it like
- Debugging this could proceed either...
- By looking at this and maybe related examples and trying to
reason out what the problem could be
- e.g., parallel sides of “triangle” could be because the third vertex ends up at infinity
- (There are some suspicious looking 0s in the triangle transformation matrix that could be leading to division by 0)
- Or by tracing it in the debugger and seeing where things go wrong
- By looking at this and maybe related examples and trying to
reason out what the problem could be
- Some examples from you that don’t seem to have the right triangles in them
- Finish testing and debugging example