Yesterday: Wrap up thesis review. Provided decent feedback at the defense dry-run of colleague. Need to ensure better preparation for clear questions next time.
Cleaned up some discussion about applications as an automated patrol mechanism, adding it to the core motivation notes.
Attempted to get Matlab working with the Kinect. Depth is fine, but the colour causes matlab to crash. Bug report sent.
Stumbled across/remembered auto point tracking tool available from Tyson Hedrick at University of North Carolina. May need to skim through the implementation to see how its related to my own objectives (at least for when I'm looking for feature points down the road).
Today: Document last Wednesday's discussion in latex for possible future writing/papers. Visualize graph representation of the point clouds within this process. Tweak/implement transformation-based validation (ie. step 2 of process). Generate a file-loading for test cases so there is consistency in process validation.
Meeting with Faramarz. Decide whether to apply for TA-ship next January or not.
Roadblocks: Not being overwhelmed, being realistic, and taking it baby-step by baby-step.
Where Does this Fit In: Having 3D synthetic examples to work with is important in validating the developed reconstruction process. Developing good visualizations - as well as a mathematical discussion of the process - along the way helps demonstrate proof-of-concepts, provides affirmation of skill sets for resource/backing requests, and justifies the direction to be taken. Determining a path to follow.