HW #3 Hints and FAQs

Should we track the features of images pairwise, or track them sequentially like example4 does?

Is my understanding of homography correct in that we just need to have 4 pair-point correspondences between each frame and that they may be unique from frame to frame? In other words, let's say I track points A, B, C, and D from frame1 to frame2, and I create the mapping between those two. Then, maybe from frame2 to frame3 I track A, B, C and E because D is lost or whatever. This still works right, because the projection only depends on tracking 4 point-pairs, not necessarily tracking points across the entire sequence.

Can I divide HW#3 into multiple programs so I implement it step by step? I.e., Can I track the features first and store the features in a file for later use? This can save me time because I won't have to re-execute some steps again and again when debugging and running later steps.

Since many images may overlap at a given output pixel, how should compositing combine the (resampled) pixels from all of the contributing images?

Compile Heckbert's code into a library file, say called libheckbert.a and then link this library file with your C++ code in your Makefile.
Include the appropriate .c files from Heckbert's code in your Makefile plus make some simple changes to the source code that modifies the declarations (because it is invalid in C++ to declare parameters outside the method head). For example, in pmap_poly.c change
pmap_poly(p, ST) poly *p; double ST[3][3];

to: int pmap_poly( poly* p, double ST[3][3])
Add all of the .h files from Heckbert's code at the beginning of your main() function file and also add
extern "C" { your-list-of-heckbert's-c-functions }