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

From NAMIC Wiki
Jump to: navigation, search
Line 37: Line 37:
 
* Questions
 
* Questions
 
** Should it be handled on the MRML level (Transformable, VolumesLogic?) or in a CLI (BRAINSResample)
 
** Should it be handled on the MRML level (Transformable, VolumesLogic?) or in a CLI (BRAINSResample)
** Ivertability / reversibility
+
** Invertability / reversibility
 
*** 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?

Revision as of 20:11, 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)
    • Invertability / 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