Difference between revisions of "2013 Summer Project Week:Deformable transforms"
From NAMIC Wiki
m (Use cases added) |
|||
Line 35: | Line 35: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
− | * Should it be handled | + | * Should it be handled on what level? |
− | ** | + | ** MRML level (Transformable, VolumesLogic?) |
− | ** ''' | + | ** '''Using modules (BRAINSResample, Resample Scalar/Vector/DWI Volume)''' - Subject Hierarchy would know what module can transform what objects using what transforms and use them |
* Invertability / reversibility | * Invertability / reversibility | ||
** '''Should it create clones of the 'hardened' objects?''' - in Subject Hierarchy | ** '''Should it create clones of the 'hardened' objects?''' - in Subject Hierarchy | ||
Line 58: | Line 58: | ||
* Look at the DICOM transform logic | * Look at the DICOM transform logic | ||
** Make frame of reference concept explicit in Slicer? | ** Make frame of reference concept explicit in Slicer? | ||
+ | |||
+ | Use cases: | ||
+ | * RT fractions: Contours are made on the planning CT, which we want to warp to fit the day 2 CT (and be able to warp day 2 dose to match the day 1 dose in terms of geometry so that we can accumulate them) | ||
+ | * PET-CT: Follow the progress of a tumor by registering the CT images together and applying this transform to the PET images so that the tumors have the same coordinate frame | ||
</div> | </div> |
Revision as of 21:24, 17 June 2013
Home < 2013 Summer Project Week:Deformable transformsKey Investigators
- Queen's: Csaba Pinter, Andras Lasso
- Isomics: Alex Yarmarkovich, Steve Pieper
- GE Research: Jim Miller
Objective
Enable handling of deformable transforms in the Transforms module, very similarly to the way linear transforms are handled.
- Drop TransformableNodes under deformable transform (possible already but ignored and hardening for rendering not enabled)
- Harden deformable transform on
- Models (should be straightforward)
- Volumes (confirmation popup window, resampling on choosing yes)
Approach, Plan
The approach is to enhance the Transform node (and Transforms module) to be able to use deformable transform nodes as parents to transformable objects and harden them
The plan for the project week is to discuss the best way to implement it, and start the implementation.
Progress
- Should it be handled on what level?
- MRML level (Transformable, VolumesLogic?)
- Using modules (BRAINSResample, Resample Scalar/Vector/DWI Volume) - Subject Hierarchy would know what module can transform what objects using what transforms and use them
- Invertability / reversibility
- Should it create clones of the 'hardened' objects? - in Subject Hierarchy
- Should we maintain a history in the hardened nodes?
- Harden option on drop (I can't display but can resample) - in Data and Transforms modules
- Plugin mechanism for registering non-linear transforms
- Modules register themselves in the fashion "I can apply X type of transform to Y type objects"
- The application could call these algorithms (instead of registering from outside)
- GUI decision if hardened
- Modules register themselves in the fashion "I can apply X type of transform to Y type objects"
- Where?
- Data module
- Transforms module (display tree, and add a 'Harden' button to the panels)
- Subject Hierarchy right-click -> apply transform to branch
- Harden all the way up or until all the parents are linear or just one level a time?
- Extend to contain bounding box
- In case of non-linear transforms, go down the edges to specify the output bounding box
- Options: resample in source lattice (still cloned), the one above, rsample in target volume
Ideas
- Look at the DICOM transform logic
- Make frame of reference concept explicit in Slicer?
Use cases:
- RT fractions: Contours are made on the planning CT, which we want to warp to fit the day 2 CT (and be able to warp day 2 dose to match the day 1 dose in terms of geometry so that we can accumulate them)
- PET-CT: Follow the progress of a tumor by registering the CT images together and applying this transform to the PET images so that the tumors have the same coordinate frame
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as an enhancement in Slicer core.
References
- Relevant tickets in the SlicerRT system: #247 and #37
- Transforms module documentation