VisTrails Home

GeometryProcessing/Spring2009/Schedule/Surface Generation Extraction1

From VisTrailsWiki

Revision as of 12:11, 21 January 2009 by Jmeier (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search
  • John Meier

I liked the structure of Tuesday's lecture: 1) the build-up to the topic of marching cubes from marching tets, and 2) examination of the aspects of marching cubes that have been "solved", like how to prevent ambiguous surface extraction by automatically generating the intersection lookup table, and optimizing runtime with structures likes octrees or span spaces. The biggest mental hurdle for me among the lecture topics was the reason for building an octree of an implicit surface from the bottom up as a preprocessing step, which Carlos cleared up well (once the structure is built, it can be queried for any constant). The analogy to sorting an array before searching for elements was intuitive and appreciated. I have a remaining question due to my lack of experience: What steps would take place when using marching cubes to extract a surface from an implicit representation? (i.e., when would the ability to quickly query an octree for multiple values be useful?).

Personal tools