Professor Ramamoorthi, I've come to a milestone with the reference path tracer project. And I've just published it at http://pathray.ebiggs.com/ There're no links to the source distribution but you can download that from this link: http://pathray.ebiggs.com/dist/pathray.src.zip At this point I have no choice but to stop working on it to focus on my other classes as the semester is wrapping up. I feel really bad to just drop this on you late and not give you an opportunity to offer feedback before the semester ends, however it's just sort of how the timing has worked out. Of course, I can be persuaded into continuing to work on it if you believe the work is not C-worthy (the minimum to get a pass on the cs 199 units). It turns out that tackling a cross platform c++ application was a bit of an undertaking for me. But I've learned a lot. I've gone from being really clumsy and uncomfortable with c++ development to feeling like I could put it on a resume now. So the experience has been extremely educational/skill-building for me in that regard. The project itself I believe meets all the requirements we discussed quite well, including a (slow) accurate bare minimum path tracer and separation of direct and indirect illumination. I also included many of my own goals as I was working on this.. such as being able to switch to a faster path tracer and cross platform GUI and threads (verifying the accuracy of this faster path tracer with the slower one was very useful, I should have approached the cs194-13 project this way!).. More info can be found in /doc/DesignNotes.rtf in the src distribution. I should note that if you find the work C-worthy but still not exactly what you're looking for...: while I know that my graduation would make hiring me over the summer difficult or impossible, I've been having fun creating this and intend to continue to develop it as a hobby on my own, and your feedback is very much welcome. As far as the present shortcomings that I plan to address probably some time over the summer: *some types of invalid scenes cause crashes <- this is a MAJOR BUG and completely unacceptable *add spherical luminaires *adjustable tone mapping in the gui *improve Phong and add more reflectance models and transmission, and... *(related to above) improve/clarify the ways of specifying materials in the scene description. *camera interactivity in the gui, perhaps by introducing some opengl *rendering statistics *improve bvh (100k triangle horse mesh seems to be too slow) *improve documentation, source code organization, source code comments *stratified sampling?? metropolis light transport???? These were all on my todo list before getting to a first version, but alas, I've simply ran out of time with my 16 unit schedule. Nevertheless I sincerely hope you're happy with the present results, Eric Biggs