CS 551/651: Image Synthesis
Assignment 1: Heightfield Intersection
Due: February 10
For this assignment, you will improve pbrt's support for rendering terrain in scenes like landscapes and seascapes. Terrain is often represented as an elevation map, or what we will call a heightfield: a 2D table indicating the height of a surface above each point of a uniform grid. In other words, a heightfield is tabulated form of a height function z(x,y) stored in a 2D array.
pbrt has no native support for rendering directly from heightfield data. Instead, it converts heightfields into triangle meshes by connecting adjacent height values in the array. This approach is general but relatively inefficient; by converting to triangles we lose the orderly structure of the heightfield, which can be exploited to render more efficiently. Your assignment is to apply techniques similar to those used for grid-based acceleration structures to develop a fast intersection routine for heightfields.
Click here to download a zip file containing several pbrt scene files, heightfield data, and textures. The UNIX version of pbrt should build the heightfield shape plugin by default. If you're using windows, copy the heightfield.vcproj file to pbrt/win32/Projects/ and add the project file in the pbrt solution. After you have built the heightfield plugin, run pbrt on scenes: hftest.pbrt and landsea-0.pbrt, and you should see output images (hftest.exr and landsea-0.exr) that look like this:

Your assignment is to write a fast heightfield intersection algorithm, which will allow you to render higher resolution terrains more quickly than the current implementation. You should do this by modifying the existing 'pbrt/shapes/heightfield.cpp' file; you do not need to change other pbrt files. Specifically, you need to:
Your implementation of Intersect() and IntersectP() will likely use an acceleration structure like a uniform grid or kd-tree. You should start by reading this paper on a fast method for marching rays through uniform grids. Also feel free to peruse the pbrt source for examples, but make sure you understand any code that you borrow.
Once you have the fast intersection routines working, add the following additional features:
Here are some example images of what you should see after completing the steps above:

Write a web page and mail the URL to the TA.. The page should contain the following:
This homework will be graded according to the following system:
0 - Little or no work was done
* - Significant effort was put into the assignment, but rendering does not
work fully
** - The intersection routine was functionally complete, but step 3 doesn't
work at all.
*** - Intersection and texture mapping worked, but normal interpolation
didn't.
**** - Intersection and normal interpolation worked, but texture mapping
didn't.
***** - All requirements satisfied, and the implementation is faster than the original
Note that only ONE star is available for intersection routines that aren't functional from all viewpoints, regardless of texture mapping and/or normal interpolation.