Difference between revisions of "Modules:PythonExplodeVolumeTransform-Documentation-3.6"

From Slicer Wiki
Jump to: navigation, search
(Created page with 'Return to Slicer 3.6 Documentation Gallery of New Features __NOTOC__ ===Module Name=== Python Explode Volume Transf…')
 
 
(One intermediate revision by the same user not shown)
Line 8: Line 8:
  
 
{|
 
{|
|[[Image:screenshotBlankNotOptional.png|thumb|280px|User Interface]]
+
|[[Image:PythonExploneVolumeTransformUI.png|thumb|280px|User Interface]]
 
|}
 
|}
 
{|
 
{|
Line 56: Line 56:
 
** ''Input Volume'': the input volume
 
** ''Input Volume'': the input volume
 
** ''Output Volume'': the output volume, the input volume aligned with the XYZ axes (IJK orientation), set as the child of the corresponding IJKToRAS transform.
 
** ''Output Volume'': the output volume, the input volume aligned with the XYZ axes (IJK orientation), set as the child of the corresponding IJKToRAS transform.
|[[Image:screenshotBlankNotOptional.png|thumb|280px|User Interface]]
+
|[[Image:PythonExploneVolumeTransformUI.png|thumb|280px|User Interface]]
 
|}
 
|}
  

Latest revision as of 02:09, 29 April 2010

Home < Modules:PythonExplodeVolumeTransform-Documentation-3.6

Return to Slicer 3.6 Documentation

Gallery of New Features


Module Name

Python Explode Volume Transform

User Interface
Figure 1: Volume loaded with RAS orientation (orientation "From file")
Figure 2: Same volume loaded with IJK orientation
Figure 3: Exploded RAS volume: ijkToRAS transform + IJK volume (see MRML tree widget on the left)
Figure 4: The volume loaded with IJK orientation (from Figure 2) moved under the output transform assumes RAS orientation

General Information

Module Type & Category

Type: CLI

Category: Converters

Authors, Collaborators & Contact

  • Luca Antiga: Orobix Srl & Mario Negri Institute
  • Daniel Blezek: Mayo Clinic
  • Contact: Luca Antiga, luca.antiga@orobix.com

Module Description

This Python module takes a volume in input, extracts its IJKToRAS transform by matrix manipulation, where IJK is the local (VTK-compatible) coordinate system, and generates an IJK-oriented volume in the MRML scene as a child of a IJKToRAS transform node.

Usage

Use Cases, Examples

  • The module is appropriate when a CLI module can only handle non-oriented images (i.e. images oriented as the XYZ axes), like pure-VTK modules.
  • The typical use is as follows: run a volume through this filter, use the output volume as input for the non-orientation-aware CLI module and place the output of this latter module under the IJKToRAS transform generated by the present module by using the MRML tree widget.
  • Use case: you have data generated from a RAS-agnostic program (e.g. fiber tracts generated in Matlab) and you want to place them in your RAS oriented scene in Slicer. What you do is then to load the MR b0 volume with orientation "From file", explode its ijkToRAS Transform, load the fiber tracts and place them under the exploded transform in the MRML tree (note that you may have to invert the transform beforehand if what you move under the transform is a polydata, as in this case). You can then (optionally) right-click on the fiber tract nodes and choose "Harden transforms" in order to have the transform applied to the fiber points. At this point you can save them in RAS.

Tutorials

NA

Quick Tour of Features and Use

  • Explode Volume Transform Parameters:
    • "Keep origin in volume": Toggle the inclusion of the origin in the extracted transform rather than in the output volume. The default is to include the origin in the transform, which produces an output volume node with the origin in 0,0,0 (same as if the node was saved and then loaded with the orientation set to IJK).
  • IO:
    • Input Volume: the input volume
    • Output Volume: the output volume, the input volume aligned with the XYZ axes (IJK orientation), set as the child of the corresponding IJKToRAS transform.
User Interface

Development

Notes from the Developer(s)

NA

Dependencies

Python

Tests

NA

Known bugs

Follow this link to the Slicer3 bug tracker.

Usability issues

Follow this link to the Slicer3 bug tracker. Please select the usability issue category when browsing or contributing.

Source code & documentation

Links to the module's source code:

Source code:

More Information

Acknowledgment

NA

References

NA