Difference between revisions of "2008 Winter Project Week Tractography Meeting Notes"
From NAMIC Wiki
| Line 7: | Line 7: | ||
== ROI definitions and impact on different methods == | == ROI definitions and impact on different methods == | ||
| − | * Force all methods to use the same ROIs? | + | * Force all methods to use the same ROIs? |
| + | * Classes of ROIs? | ||
* For streamline methods larger ROIs than the tract itself good | * For streamline methods larger ROIs than the tract itself good | ||
* For shortest path methods, connections stop at ROI | * For shortest path methods, connections stop at ROI | ||
Revision as of 17:25, 9 January 2008
Home < 2008 Winter Project Week Tractography Meeting NotesContents
Notes from Presentations and Discussions
Data quality, NAMIC DTI pipeline
- Issues?
- White matter mask?
ROI definitions and impact on different methods
- Force all methods to use the same ROIs?
- Classes of ROIs?
- For streamline methods larger ROIs than the tract itself good
- For shortest path methods, connections stop at ROI
Methods:
- Streamline Slicer2 (Sonia)
- Streamline Fiberviewer (Casey)
- Stochastic Slicer3 (Tri)
- Shortest path, volumetric (John)
- Shortest path, volumetric (Tom)
Review and define metrics to compare results, which methods to compare?
Current metrics: tensor invariants (FA, trace, mode, norm), volume, length.
- 12 different tracts
- Tracts voxelized -> volumetric result from tracts
- Missing parts of a tract, how should be penalized?
- Statistics along the tracts, should we sum along the tract to get one measure?
- Distributions across the tract
- Atlas (Casey)
