Difference between revisions of "2013 Summer Project Week:Deformable transforms"

From NAMIC Wiki
Jump to: navigation, search
Line 40: Line 40:
 
*** Should it create clones of the 'hardened' objects?
 
*** Should it create clones of the 'hardened' objects?
 
*** Should we maintain a history in the hardened nodes?
 
*** Should we maintain a history in the hardened nodes?
 +
*** Harden option on drop (I can't display but can resample)
 
** Plugin mechanism for registering non-linear transforms
 
** Plugin mechanism for registering non-linear transforms
 
*** Modules register themselves in the fashion "I can apply X type of transform to Y type objects"
 
*** Modules register themselves in the fashion "I can apply X type of transform to Y type objects"
 +
**** The application could call these algorithms (from the modules) at first (instead of registering from outside)
 
*** GUI decision if hardened
 
*** GUI decision if hardened
 +
** Where?
 +
*** Data module
 +
*** Transforms module (display tree, and add a 'Harden' button to the panels)
 +
** Harden all the way up or until all the parents are linear or just one level a time?
 +
** Subject Hierarchy right-click -> apply transform to study
  
 +
* 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
 +
 +
* Look at the DICOM transform logic
 +
** Make frame of reference concept explicit in Slicer?
 +
 +
TODO: Clean this list up
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 21:02, 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, Resample Scalar/Vector/DWI Volume)
    • Invertability / reversibility
      • Should it create clones of the 'hardened' objects?
      • Should we maintain a history in the hardened nodes?
      • Harden option on drop (I can't display but can resample)
    • 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 (from the modules) at first (instead of registering from outside)
      • GUI decision if hardened
    • Where?
      • Data module
      • Transforms module (display tree, and add a 'Harden' button to the panels)
    • Harden all the way up or until all the parents are linear or just one level a time?
    • Subject Hierarchy right-click -> apply transform to study
  • 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
  • Look at the DICOM transform logic
    • Make frame of reference concept explicit in Slicer?

TODO: Clean this list up

Delivery Mechanism

This work will be delivered to the NA-MIC Kit as an enhancement in Slicer core.

References

Retrieved from "https://www.na-mic.org/w/index.php?title=2013_Summer_Project_Week:Deformable_transforms&oldid=82038"