Difference between revisions of "2011 Summer Project Week DTI PairWise Registration"
From NAMIC Wiki
Line 35: | Line 35: | ||
* Main BatchMake script written | * Main BatchMake script written | ||
* Individual steps called as threads via BatchMake | * Individual steps called as threads via BatchMake | ||
− | * | + | * Further testing / improvement needs to be achieved... |
+ | |||
+ | bin/DWIProcessPipeline [--returnparameterfile <std::string>] | ||
+ | [--processinformationaddress <std::string>] | ||
+ | [--xml] [--echo] [--runChoice <Do_not_run|Run | ||
+ | |Condor>] [--registration <MD|FA>] | ||
+ | [--interpolation <linear|bs|ws>] [--copy] | ||
+ | [--nolog] [--skullStrip] [--scale] [--computeAD] | ||
+ | [--computeRD] [--computeColorFA] [--computeMD] | ||
+ | [--computeFA] [--initialTransform <std::string>] | ||
+ | [-f <std::string>] [--createIDWI] [--createB0] | ||
+ | [--manualOrientation <std::string>] | ||
+ | [--computeOrientation] [--imNN2 <std::string>] | ||
+ | [--imNN1 <std::string>] [--im3 <std::string>] | ||
+ | [--im2 <std::string>] [--im1 <std::string>] | ||
+ | [--rootName <std::string>] [--outputDir | ||
+ | <std::string>] [--templateType <DTI|scalar>] [-t | ||
+ | <std::string>] [--inputType <DWI|DTI|scalar>] | ||
+ | [-i <std::string>] [--] [--version] [-h] | ||
+ | |||
+ | |||
</div> | </div> |
Revision as of 14:40, 24 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 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
- Further testing / improvement needs to be achieved...
bin/DWIProcessPipeline [--returnparameterfile <std::string>] [--processinformationaddress <std::string>] [--xml] [--echo] [--runChoice <Do_not_run|Run |Condor>] [--registration <MD|FA>] [--interpolation <linear|bs|ws>] [--copy] [--nolog] [--skullStrip] [--scale] [--computeAD] [--computeRD] [--computeColorFA] [--computeMD] [--computeFA] [--initialTransform <std::string>] [-f <std::string>] [--createIDWI] [--createB0] [--manualOrientation <std::string>] [--computeOrientation] [--imNN2 <std::string>] [--imNN1 <std::string>] [--im3 <std::string>] [--im2 <std::string>] [--im1 <std::string>] [--rootName <std::string>] [--outputDir <std::string>] [--templateType <DTI|scalar>] [-t <std::string>] [--inputType <DWI|DTI|scalar>] [-i <std::string>] [--] [--version] [-h]
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer extension.