Scrum

Monday, January 5, 2015

January 05, 2015, at 03:38 AMerika
Yesterday: (Friday, Dec 12) Motivated work by tweaking Gallery on website, looking into HTML5, javascripting, jQuery, image carousels to consider developing an example countdown timer for desired dates/times. Details on the given page.

This helped motivate me to tackle the block-based separation (see image), including visualizing resulting adjacency. Assumes there are at least 4 solid points in an existing object. Only relies on prior frame to-date. Block checking involves O(nk) space and time, which can be reduced by more intelligent checking.

(Over break) Found a simple blender doll to help with building synthetic examples over time. Modified code base to iteratively load in different obj files, where vertices are in-order and corresponding. This is akin to incorporating animation files, where points are transformed across keyframes over time.

Incorporated logic for segmenting based on block adjacency. ie. Determining which vertices belong to which core block. Added support for showing edges from block adjacency segmentation/re-grouping. Need to handle outlier vertices.

Dropped into career counseling at Waterloo. Recognized that there are many options always open, and its a matter of selecting one and pursuing it. One exercise parsed down a long list of values and needs within a job. Alongside the standards needs of a supportive supervisors, clear directions, good salary, job security and leisure time/work-life balance, my top priorities include feeling productive, having a routine, belonging and interacting with people, in an honest cooperative environment. Problem solving comes naturally within computer science, and location is somewhat important - either near mountains, or family and friends - somewhere that I can be involved in and feel a part of a community.

Today: Review the status of the implementation. Re-schedule user experience validation test for a colleague. Create series of synthetic examples from blender manikin and possible double pendulum. Implement transformation-based validation (ie. modification of original step 2 of process), and process for reliance on prior frames. Generate a file-loading for test cases so there is consistency in process validation.

Write up (mathematical foundation, computational/theoretical implementations) for future writing/papers:

  • distance-based segmentation
  • block-based segmentation/checking

Consider laying out how I'd like the thesis to look and how I'd like it to describe the various implementations and stages along the way. Read more...

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. When there are hiccups along the road or the path is unclear, its important to remind oneself why we do the things we are doing, and evaluate whether any changes need to be made and if so, what needs to be done.

BlogIt Side bar

Recently Written

erika: end hiding comments and categories

erika: end hiding comments and categories

Group-Specific Sidebar

Blix theme adapted by David Gilbert, powered by BlogIt