Difference between revisions of "2014 Project Week:Shape Registration and Regression"
From NAMIC Wiki
Jfishbaugh (talk | contribs) |
Jfishbaugh (talk | contribs) |
||
| Line 19: | Line 19: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
The first step is to integrate shape matching/registration into Slicer as a command line application. Some key issues to resolve: | 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 | + | * What input parameters should be made available to user? |
* Input/Output format: Paths to data or Slicer Models? | * 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. | * 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 | + | * Dependencies on external libraries and licensing issues. |
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
Revision as of 18:42, 6 January 2014
Home < 2014 Project Week:Shape Registration and Regression
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.
