Yesterday: Starting to develop a Blender script for outputing vertices to file. This way non-visible vertices will be flagged as null, but still present/in-order.
- have low expectations for how much is created for the resulting objects, based on the current example scenes
- ... therefore consider building a synthtetic example where it moves in front of the camera
- have vertex visibility based on camera? current display view? (which means I need to set a camera within the scenes
- re-work scenes so that the camera is animated around the objects for increased object observation
For the matlab code:
- adapt the import sections to accept these text files, and select the subset of vertices that are visible for a frame to work with
- this means that when selecting the current visible vertices, they may not have been visible in prior frames - adapt the code to accept that there is no history
- for vertices that have previously been assigned an object but are not currently visible, update their transformations based on how the object has changed. options include:
- object remained unchanged - apply the same transformation for where we expect that vertex to be
- object has split - flag the vertex has being invalid/inconsistent/unknown... future dealings with this vertex should observe which object it was previously associated with, and how that object was divided over time (time-graph representation of object construction/destruction and the observed transformation for each frame?)
- be able to select and show the developing state of a given object - ideally would be able to rewind and see how it has changed; or alternatively rewind and re-incorporate the more expansive object into transformation stream
Today: TA preparations and tutorials. Identify what needs to be done for potential position application (resume, Gallery? updating). Continue building the codebase for incremental updater. Flag for performance and accuracy (high object count) improvement the different sections within matlab, and be able to justify why the datastructure thus far is of less importance for tomorrow's supervisor meeting.
Roadblocks: Handling high numbers of objects in a scene - ie. ensuring correct segmentation.
Where Does this Fit In: TA responsibilities practise development and group management skills, ensure motivation within the field, and financial stability for project development. Getting object segmentation for known correspondences is one of the key stages for final development. Ensuring fast implementations, and recognizing areas for speed-up guides future directions when fewer correspondences are available and temporarily inconsistent in their visibility, non-feature points must be incorporated, and noisy information is present. Developing objects based on observed visibility is a key step in the project stages.