Difference between revisions of "2011 Summer Project Week DTI PairWise Registration"
From NAMIC Wiki
| Line 23: | Line 23: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | Our approach is to develop a C++ based | + | Our approach is to develop a C++ based Slicer3 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. | Our plan for the project week is to develop/enhance the module. | ||
| Line 32: | Line 32: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | + | * Command line / UI via GenerateCLP (cf. screenshot) | |
| + | * Main BatchMake script written | ||
| + | * Individual steps called as threads via BatchMake | ||
| + | * Current testing on example data... | ||
</div> | </div> | ||
Revision as of 14:02, 24 June 2011
Home < 2011 Summer Project Week DTI PairWise Registration
Screenshot
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 Slicer3 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
- Command line / UI via GenerateCLP (cf. screenshot)
- Main BatchMake script written
- Individual steps called as threads via BatchMake
- Current testing on example data...
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer extension.
