Difference between revisions of "2014 Project Week:Shape Registration and Regression"
From NAMIC Wiki
Jfishbaugh (talk | contribs) |
Jfishbaugh (talk | contribs) |
||
| Line 33: | Line 33: | ||
<h3>Summary</h3> | <h3>Summary</h3> | ||
| − | [[Image: | + | [[Image:Shape_matching_interface.png|thumb|900px|center|Initial tumor data and shape matching interface. ]] |
| + | |||
| + | [[Image:Registered_shape.png|thumb|900px|center|Source shape registered to target shape. ]] | ||
| + | |||
| + | [[Image:First_to_last.png|thumb|900px|center|Source shape with velocity of deformation overlaid on surface. ]] | ||
Revision as of 02:54, 10 January 2014
Home < 2014 Project Week:Shape Registration and Regression
Surface matching in Slicer
Key Investigators
- Utah: James Fishbaugh, Guido Gerig
- Iowa: Hans Johnson
Project Description
Objective
Integrate shape matching and shape regression tools into Slicer as command line applications.
Approach, Plan
The first step is to integrate shape matching/registration into Slicer as a command line application. Some key issues to resolve:
- What input parameters should be made available to user?
- Input/Output format: Paths to data or Slicer Models?
- Output is a time series of surfaces, which is not easily explored in Slicer. Should output be simplified? Output could be the deformed source and/or the deformation field that transforms source to target.
- Dependencies on external libraries and licensing issues.
