2014 Project Week:MultidimensionalDataSupport - Revision history

Lasso at 16:48, 10 January 2014

2014-01-10T16:48:18Z

Lasso at 16:18, 10 January 2014

2014-01-10T16:18:37Z

Lasso at 16:15, 10 January 2014

2014-01-10T16:15:32Z

Lasso at 08:53, 10 January 2014

2014-01-10T08:53:42Z

Lasso: /* Project Description */

2014-01-10T08:35:24Z

Project Description

JChris.FillionR: /* Key Investigators */

2014-01-07T00:38:25Z

Key Investigators

Lasso at 21:13, 6 January 2014

2014-01-06T21:13:20Z

Lasso at 20:44, 6 January 2014

2014-01-06T20:44:48Z

Lasso at 18:51, 28 December 2013

2013-12-28T18:51:48Z

Lasso at 18:50, 28 December 2013

2013-12-28T18:50:28Z

@@ Line 2: / Line 2: @@
 <gallery>
 Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
-Image:Markups-sequence.png|Sequence can be created from any MRML node (markup sequence) - '''[http://screencast.com/t/yUsn0nKoYitB see video!])'''
+Image:Markups-sequence.png|'''[http://screencast.com/t/yUsn0nKoYitB Click here to see the video!]'''<br>Sequence can be created from any MRML node (markup sequence)
 Image:Multi_label_statistics.png|4D labelmap statistics module
 Image:Trackedus-sequence.png|Multidimensional data browser (tracked ultrasound sequence)

@@ Line 2: / Line 2: @@
 <gallery>
 Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
 Image:Dce-mri-sequence.png|Multidimensional data editor (DCE-MRI sequence)
 </gallery>
@@ Line 41: / Line 42: @@
 * Large number of time points can be loaded: tracked ultrasound sequence with 2000 time points is loaded within 15 seconds, can be replayed at 30fps - see video at http://screencast.com/t/2sJbQpWf2l
 * Example 4D data processing module created: labelmap statistics
 </div>
 </div>

@@ Line 2: / Line 2: @@
 <gallery>
 Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
-Image:MultidimEditor.png|Multidimensional data editor
+Image:Dce-mri-sequence.png|Multidimensional data editor (DCE-MRI sequence)
-Image:MultidimBrowser.png|Multidimensional data browser
+Image:Trackedus-sequence.png|Multidimensional data browser (tracked ultrasound sequence)
 </gallery>
@@ Line 39: / Line 40: @@
 ** DCE-MRI: http://screencast.com/t/Oy8InJnz9FE
 * Large number of time points can be loaded: tracked ultrasound sequence with 2000 time points is loaded within 15 seconds, can be replayed at 30fps - see video at http://screencast.com/t/2sJbQpWf2l
-* Implementation is available: https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/src
+* Example 4D data processing module created: labelmap statistics
 </div>
 </div>
@@ Line 48: / Line 49: @@
 * 4D Cardiac CT volume rendering
 * DCE-MRI review

@@ Line 35: / Line 35: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Progress</h3>
-* Sequence of any kind of nodes can be stored in a multidimensional data node - see video of markup sequence at http://screencast.com/t/yUsn0nKoYitB
+* Sequence of any kind of nodes can be stored in a multidimensional data node
 * Large number of time points can be loaded: tracked ultrasound sequence with 2000 time points is loaded within 15 seconds, can be replayed at 30fps - see video at http://screencast.com/t/2sJbQpWf2l
 * Implementation is available: https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/src

@@ Line 35: / Line 35: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Progress</h3>
-* Initial implementation is available: https://subversion.assembla.com/svn/slicerrt/trunk/MultidimData/src
+* Sequence of any kind of nodes can be stored in a multidimensional data node - see video of markup sequence at http://screencast.com/t/yUsn0nKoYitB
 </div>
 </div>
 ==Use cases==
 * Tracked ultrasound image sequence review

@@ Line 12: / Line 12: @@
 * Kitware Jean-Christophe Fillion-Robin
 * UHN: Kevin Wang
 ==Project Description==

@@ Line 30: / Line 30: @@
 <h3>Approach, Plan</h3>
 * Even after extensive MRML scene optimization, handling of large data sets (more 1000+ nodes) is not feasible due to the inefficiency of MRML widgets (node selector combo boxes, scene hierarchy trees; due to each widget maintaining its own qMRMLSceneModel)
-* Plan: store one sequence bundle node in the scene and store each bundle as a private scene inside that sequence bundle node
+* Plan: store one node per sequence and store each item inside that sequence node (similarly to MultiVolume, but for any node type)
 </div>
 <div style="width: 27%; float: left; padding-right: 3%;">

@@ Line 15: / Line 15: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Objective</h3>
-* Add support for node sequences (e.g., time sequence, multi-parametric images, etc.)
+* Add support for node bundle sequences (e.g., time sequence, multi-parametric images, etc.)
 ** All node types: not just volumes but also transforms, models, markups, and any custom nodes
-** Large data sets: up to 5000 sequence items, with any number of nodes in each item, any size of nodes
+** Large data sets: up to 5000 bundles, with any number of nodes in each bundle, any size of nodes
 * Operations:
 ** Import from sequence metafile (time sequence of a 2D image and multiple tool tracking data)
@@ Line 23: / Line 23: @@
 ** Load from scene file
 ** Browsing sequence items: automatic replay, prev/next item; ability to show multiple items at the same time
-** Modification of sequence items: add/delete, change sequence item name, parameter
+** Modification of sequence items: add/delete, change bundle name, parameter
 </div>
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Approach, Plan</h3>
-* Some prototyping work has been completed: even after extensive MRML scene optimization, handling of large data sets (more 1000+ nodes) is not feasible due to the inefficiency of MRML widgets (node selector combo boxes, scene hierarchy trees; due to each widget maintaining its own qMRMLSceneModel)
+* Even after extensive MRML scene optimization, handling of large data sets (more 1000+ nodes) is not feasible due to the inefficiency of MRML widgets (node selector combo boxes, scene hierarchy trees; due to each widget maintaining its own qMRMLSceneModel)
 </div>
 <div style="width: 27%; float: left; padding-right: 3%;">
@@ Line 34: / Line 35: @@
 </div>
 </div>