Difference between revisions of "2012 Winter Project Week:PairWiseDTIRegistration"
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
Image:PW-SLC2012.png|[[2012_Winter_Project_Week#Projects|Projects List]] | Image:PW-SLC2012.png|[[2012_Winter_Project_Week#Projects|Projects List]] | ||
Image:DTI-Reg_UI.jpg| DTI-Reg user interface | Image:DTI-Reg_UI.jpg| DTI-Reg user interface | ||
| + | Image:DTIReg_Extension_Slicer4_CDash.jpg| DTI-Reg CDash | ||
| + | Image:DTI_Reg_Extension_Slicer4.jpg| DTI-Reg Slicer 4 extension | ||
</gallery> | </gallery> | ||
| Line 34: | Line 36: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | + | *Advertised [http://www.nitrc.org/projects/dtireg/ DTI-Reg] to several collaborators (NITRC project) | |
| + | **Part of the general [[Projects:AtlasBasedDTIFiberAnalyzerFramework| atlas-based DTI analysis framework]] from UNC/Utah | ||
| + | *Discussion with J-C with respect to Slicer4 extensions | ||
| + | *First attempt to build DTI-Reg built as a Slicer4 extension (cf images) | ||
| + | ** Dependent packages would need to be extensions as well: (DTIProcess...) | ||
| + | **CMake files still need to be cleaned (using Slicer or individual libraries to compile the whole project) | ||
</div> | </div> | ||
Latest revision as of 16:11, 13 January 2012
Home < 2012 Winter Project Week:PairWiseDTIRegistration
DTI-Reg user interface
DTI-Reg CDash
DTI-Reg Slicer 4 extension
DTI registration/processing pipeline in Slicer3
Key Investigators
- UNC: Clement Vachet, Martin Styner
- IOWA: Mark Scully, Hans Johnson
Objective
We focus on enabling the use of advanced DTI processing within NA-MIC and on automatizing steps to perform atlas-based DTI population analysis. One component is pair-wise DTI registration which can be directly performed by DTI-Reg, a C++ application developed in that regard.
Approach, Plan
DTI-Reg is an open-source C++ application that performs pair-wise DTI registration. Individual steps of the pair-wise registration pipeline are performed via external applications, called via BatchMake. Starting with two input DTI images, scalar FA maps are generated via dtiprocess. Registration is then performed between these FA maps, via BRAINSFit or BRAINSDemonWarp, which provide different registration schemes: rigid, affine, BSpline, diffeomorphic, logDemons. The final deformation is then applied to the source DTI image via resampleDTI.
Progress
- Advertised DTI-Reg to several collaborators (NITRC project)
- Part of the general atlas-based DTI analysis framework from UNC/Utah
- Discussion with J-C with respect to Slicer4 extensions
- First attempt to build DTI-Reg built as a Slicer4 extension (cf images)
- Dependent packages would need to be extensions as well: (DTIProcess...)
- CMake files still need to be cleaned (using Slicer or individual libraries to compile the whole project)
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer extension
