Difference between revisions of "2013 Summer Project Week:Deformable transforms"
From NAMIC Wiki
m |
|||
| Line 6: | Line 6: | ||
==Key Investigators== | ==Key Investigators== | ||
* Queen's: Csaba Pinter, Andras Lasso | * Queen's: Csaba Pinter, Andras Lasso | ||
| − | * Isomics: Alex Yarmarkovich | + | * Isomics: Alex Yarmarkovich, Steve Pieper |
| − | * | + | * GE Research: Jim Miller |
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
| Line 14: | Line 14: | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
Enable handling of deformable transforms in the Transforms module, very similarly to the way linear transforms are handled. | Enable handling of deformable transforms in the Transforms module, very similarly to the way linear transforms are handled. | ||
| − | * Drop TransformableNodes under deformable transform | + | * Drop TransformableNodes under deformable transform (possible already but ignored and hardening for rendering not enabled) |
* Harden deformable transform on | * Harden deformable transform on | ||
** Models (should be straightforward) | ** Models (should be straightforward) | ||
| Line 25: | Line 25: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | The approach is to enhance the Transforms module to be able to use deformable transform nodes as parents to transformable objects | + | 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. | The plan for the project week is to discuss the best way to implement it, and start the implementation. | ||
| Line 35: | Line 35: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * Questions |
| − | * | + | ** Should it be handled on the MRML level (Transformable, VolumesLogic?) or in a CLI (BRAINSResample) |
| + | ** Ivertability / reversibility | ||
| + | *** Should it create clones of the 'hardened' objects? | ||
| + | *** Should we maintain a history in the hardened nodes? | ||
</div> | </div> | ||
| Line 43: | Line 46: | ||
==Delivery Mechanism== | ==Delivery Mechanism== | ||
| − | This work will be delivered to the NA-MIC Kit as an enhancement | + | This work will be delivered to the NA-MIC Kit as an enhancement in Slicer core. |
==References== | ==References== | ||
* Relevant tickets in the SlicerRT system: [https://www.assembla.com/spaces/slicerrt/tickets/247#/activity/ticket: #247] and [https://www.assembla.com/spaces/slicerrt/tickets/37#/activity/ticket: #37] | * Relevant tickets in the SlicerRT system: [https://www.assembla.com/spaces/slicerrt/tickets/247#/activity/ticket: #247] and [https://www.assembla.com/spaces/slicerrt/tickets/37#/activity/ticket: #37] | ||
* [http://www.slicer.org/slicerWiki/index.php/Documentation/4.2/Modules/Transforms Transforms module documentation] | * [http://www.slicer.org/slicerWiki/index.php/Documentation/4.2/Modules/Transforms Transforms module documentation] | ||
Revision as of 20:01, 17 June 2013
Home < 2013 Summer Project Week:Deformable transforms
Key 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
- Questions
- Should it be handled on the MRML level (Transformable, VolumesLogic?) or in a CLI (BRAINSResample)
- Ivertability / reversibility
- Should it create clones of the 'hardened' objects?
- Should we maintain a history in the hardened nodes?
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
