Difference between revisions of "2011 Summer Project Week DTI PairWise Registration"
Line 13: | Line 13: | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
− | We are developing a pipeline which performs DTI pair-wise registration. The goal is to create a user-friendly Slicer3 extension which performs such a registration automatically, instead of running Slicer3 modules individually ( | + | We are developing a pipeline which performs DTI pair-wise registration. The goal is to create a user-friendly Slicer3 extension which performs such a registration automatically, instead of running Slicer3 modules individually (dtiprocess, BRAINSFit, BRAINSDemonWarp, ResampleDTI Volume...). Such a wrapper will generate and use scalar features (e.g FA,MD) to drive the registration between two DTI images. |
Line 24: | Line 24: | ||
Our approach is to develop a C++ based Slice3 extension, which writes a BatchMake script, in order to call external modules as threads to perform individual steps of the pipeline. | Our approach is to develop a C++ based Slice3 extension, which writes a BatchMake script, in order to call external modules as threads to perform individual steps of the pipeline. | ||
− | Our plan for the project week is to | + | Our plan for the project week is to develop/enhance the module. |
</div> | </div> |
Revision as of 19:30, 16 June 2011
Home < 2011 Summer Project Week DTI PairWise Registration
Key Investigators
- UNC: Clement Vachet, Francois Budin, Martin Styner
- IOWA: Joy Matsui, Mark Scully, Hans Johnson
Objective
We are developing a pipeline which performs DTI pair-wise registration. The goal is to create a user-friendly Slicer3 extension which performs such a registration automatically, instead of running Slicer3 modules individually (dtiprocess, BRAINSFit, BRAINSDemonWarp, ResampleDTI Volume...). Such a wrapper will generate and use scalar features (e.g FA,MD) to drive the registration between two DTI images.
Approach, Plan
Our approach is to develop a C++ based Slice3 extension, which writes a BatchMake script, in order to call external modules as threads to perform individual steps of the pipeline.
Our plan for the project week is to develop/enhance the module.
Progress
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)
- ITK Module
- Slicer Module
- Built-in
- Extension -- commandline YES
- Extension -- loadable YES
- Other (Please specify)