Difference between revisions of "Documentation/Nightly/Extensions/Sequences"

From Slicer Wiki
Jump to: navigation, search
(Added links to sample data)
Line 26: Line 26:
 
|
 
|
 
|}
 
|}
−
 
−
 
−
Definitions:
 
−
* Sequence: Contains an ordered array of data nodes, each data node is tagged with an index value.
 
−
* Data node: A regular MRML node, one item in the sequence. Data nodes are stored privately inside the sequence, therefore not visible in the main scene (where the sequence node is in). Singleton nodes are not allowed to be stored as data nodes. Sequence nodes can be data nodes, therefore sequence of sequence nodes can be used to represent higher-dimensional data sets.
 
−
* Sequence index: The index describes the dimension of the data node sequence. The index name (such as "time"), unit (such as "s"), and type (such as "numeric" or "text") is the same for the whole sequence. The index value is specified for each data node. The index type information is used for sorting (numerical or string sorting) and matching of the index values (in case of a numerical index we can find the closest data node even if there is no perfectly matching index value).
 
−
* Sequence browsing: A sequence node only contains the data nodes, but does not store any node relationships, such as parent transform, display properties, etc. These relationships can be only defined for the virtual output nodes that are generated by the Sequence browser module. Several browser nodes can be created to visualize data from the same sequence, which allows visualization, comparison of multiple different time points from the same sequence.
 
−
* Virtual output node: The sequence browser node creates a copy of the selected privately stored data node in the main scene.
 
  
 
<!-- ---------------------------- -->
 
<!-- ---------------------------- -->
Line 46: Line 38:
  
 
<gallery widths="200px" perrow="3">
 
<gallery widths="200px" perrow="3">
−
Image:CardiacCtReplay.gif|4D Cardiac CT
+
Image:CardiacCtReplay.gif|4D Cardiac CT ([https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/data/SampleSceneCardiacCt.mrb download scene])
−
Image:UltrasoundToolGuidance3dOnly.gif|Tracked ultrasound with tool tracking
+
Image:UltrasoundToolGuidance3dOnly.gif|Tracked ultrasound with tool tracking ([https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/data/SampleSceneUsGuidedNeedleInsertion.mrb download scene])
−
Image:ShapeModelSequenceBrowsing3dOnly.gif|Model deformation
+
Image:ShapeModelSequenceBrowsing3dOnly.gif|Model deformation ([https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/data/SampleSceneModelDeformation.mrb download scene])
 
Image:SequenceEditor.png|Sequences module for creating and editing sequences
 
Image:SequenceEditor.png|Sequences module for creating and editing sequences
 
Image:SequenceBrowser.png|Sequence browser module for browsing and replaying sequences
 
Image:SequenceBrowser.png|Sequence browser module for browsing and replaying sequences
Line 55: Line 47:
 
<!-- ---------------------------- -->
 
<!-- ---------------------------- -->
 
{{documentation/{{documentation/version}}/extension-section|Tutorials}}
 
{{documentation/{{documentation/version}}/extension-section|Tutorials}}
−
 
+
* Sample scenes:
 +
** [https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/data/SampleSceneCardiacCt.mrb Cardiac CT: sequence of volumes, real-time volume rendering]
 +
** [https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/data/SampleSceneModelDeformation.mrb Deformation of a 3D model]
 +
** [https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/data/SampleSceneUsGuidedNeedleInsertion.mrb Ultrasound-guided needle insertion: moving tracked ultrasound image and tools, synchronized replay of image ad transforms]
 +
* Usage:
 +
** Load the downloaded .mrb scene file into Slicer
 +
** Go to the Sequence browser module to browse the data set
 
<!-- ---------------------------- -->
 
<!-- ---------------------------- -->
 
<!--
 
<!--
Line 64: Line 62:
 
{{documentation/{{documentation/version}}/extension-section|References}}
 
{{documentation/{{documentation/version}}/extension-section|References}}
 
-->
 
-->
 +
 +
<!-- ---------------------------- -->
 +
{{documentation/{{documentation/version}}/module-section|Information for Developers}}
 +
{{documentation/{{documentation/version}}/module-developerinfo}}
 +
 +
* Sequence: Contains an ordered array of data nodes, each data node is tagged with an index value.
 +
* Data node: A regular MRML node, one item in the sequence. Data nodes are stored privately inside the sequence, therefore not visible in the main scene (where the sequence node is in). Singleton nodes are not allowed to be stored as data nodes. Sequence nodes can be data nodes, therefore sequence of sequence nodes can be used to represent higher-dimensional data sets.
 +
* Sequence index: The index describes the dimension of the data node sequence. The index name (such as "time"), unit (such as "s"), and type (such as "numeric" or "text") is the same for the whole sequence. The index value is specified for each data node. The index type information is used for sorting (numerical or string sorting) and matching of the index values (in case of a numerical index we can find the closest data node even if there is no perfectly matching index value).
 +
* Sequence browsing: A sequence node only contains the data nodes, but does not store any node relationships, such as parent transform, display properties, etc. These relationships can be only defined for the virtual output nodes that are generated by the Sequence browser module. Several browser nodes can be created to visualize data from the same sequence, which allows visualization, comparison of multiple different time points from the same sequence.
 +
* Virtual output node: The sequence browser node creates a copy of the selected privately stored data node in the main scene. This copy is the virtual output node.
  
 
<!-- ---------------------------- -->
 
<!-- ---------------------------- -->

Revision as of 02:11, 23 January 2014

Home < Documentation < Nightly < Extensions < Sequences


For the latest Slicer documentation, visit the read-the-docs.


Introduction and Acknowledgements

Author: Andras Lasso (PerkLab, Queen's University), Matthew Holden (PerkLab, Queen's University), Kevin Wang (Radiation Medicine Program, Princess Margaret Hospital, University Health Network Toronto), Gabor Fichtinger (PerkLab, Queen's University)
Contact: Andras Lasso, <email>lasso@cs.queensu.ca</email>
Project website: http://www.slicerrt.org
License: Slicer license

SparKit  
NA-MIC  

Extension Description

MultidimDataLogo.png

Multidimensional data is an extension of 3D Slicer to allow creating and visualization of higher-dimension data nodes, such as 4D volumes, models changing in time, markups changing in time, sequences of transforms, scene camera trajectory, or even sequence of sequences.

Highlights:

  • Sequences can be created from any MRML nodes
  • Multiple sequences can be replayed sycnhronized, in real-time, visualizing the contents in 2D and 3D

Modules

Use Cases

  • 4D Cardiac CT (download scene)

  • Tracked ultrasound with tool tracking (download scene)

  • Model deformation (download scene)

  • Sequences module for creating and editing sequences

  • Sequence browser module for browsing and replaying sequences

Tutorials

Information for Developers

Work in progress
 Section under construction.


  • Sequence: Contains an ordered array of data nodes, each data node is tagged with an index value.
  • Data node: A regular MRML node, one item in the sequence. Data nodes are stored privately inside the sequence, therefore not visible in the main scene (where the sequence node is in). Singleton nodes are not allowed to be stored as data nodes. Sequence nodes can be data nodes, therefore sequence of sequence nodes can be used to represent higher-dimensional data sets.
  • Sequence index: The index describes the dimension of the data node sequence. The index name (such as "time"), unit (such as "s"), and type (such as "numeric" or "text") is the same for the whole sequence. The index value is specified for each data node. The index type information is used for sorting (numerical or string sorting) and matching of the index values (in case of a numerical index we can find the closest data node even if there is no perfectly matching index value).
  • Sequence browsing: A sequence node only contains the data nodes, but does not store any node relationships, such as parent transform, display properties, etc. These relationships can be only defined for the virtual output nodes that are generated by the Sequence browser module. Several browser nodes can be created to visualize data from the same sequence, which allows visualization, comparison of multiple different time points from the same sequence.
  • Virtual output node: The sequence browser node creates a copy of the selected privately stored data node in the main scene. This copy is the virtual output node.

Information for Developers

Troubleshooting

Retrieved from "https://www.slicer.org/w/index.php?title=Documentation/Nightly/Extensions/Sequences&oldid=37090"