Difference between revisions of "2008 Engineering review at Utah"
From NAMIC Wiki
Line 29: | Line 29: | ||
** Status of spline-based methods | ** Status of spline-based methods | ||
** Intertability | ** Intertability | ||
+ | ** How to incorporate registration/atlases/atlas building in to slicer3 | ||
+ | |||
+ | * General architecture issues | ||
+ | ** How to provide coherent user interfaces for specific tasks | ||
+ | *** Pipelines for specific data or analyses | ||
+ | *** E.g. see Siemens workstation software with modules/pages | ||
+ | ** Command-line vs built in modules | ||
+ | *** Policies for supporting one versus the other |
Revision as of 22:18, 29 February 2008
Home < 2008 Engineering review at UtahWill, Ross, and Guido will consult with other people and schedule the event.
The date is now set at: March 24-27, 2008.
Proposed discussion items:
- DTI processing modules/pipeline
- Infrastructure for DWI/DTI data types
- How to handle coordinate frames
- Preprocessing pipeline for DWI->DTI->analysis
- Filtering
- Registration
- Estimation
- White mater mask
- User interfaces/interaction
- Analysis of DTI data
- Tractography
- Atlases
- Derived quantities
- Hypothesis testing
- Infrastructure for DWI/DTI data types
- Shape analysis pipeline (Should Martin S. be here?)
- How to organize data
- How to break pipeline in to steps
- Segmentation, preprocessing, parameterization, visualization
- How to accommodate new modules/techniques
- The general problem of registration and atlases
- Status of spline-based methods
- Intertability
- How to incorporate registration/atlases/atlas building in to slicer3
- General architecture issues
- How to provide coherent user interfaces for specific tasks
- Pipelines for specific data or analyses
- E.g. see Siemens workstation software with modules/pages
- Command-line vs built in modules
- Policies for supporting one versus the other
- How to provide coherent user interfaces for specific tasks