Difference between revisions of "2014 Project Week:MultidimensionalDataSupport"

From NAMIC Wiki
Jump to: navigation, search
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2014.png|Projects List </gallery> ==Key Investigators== * Queen's: Andras Lasso * BWH: Andriy Fedorov * Iso…')
 
Line 15: Line 15:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Objective</h3>
 
<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
 
** 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:
 
* Operations:
 
** Import from sequence metafile (time sequence of a 2D image and multiple tool tracking data)
 
** Import from sequence metafile (time sequence of a 2D image and multiple tool tracking data)
Line 23: Line 23:
 
** Load from scene file
 
** Load from scene file
 
** Browsing sequence items: automatic replay, prev/next item; ability to show multiple items at the same time
 
** 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>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Approach, Plan</h3>
 
<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)
 +
* Plan: store one sequence bundle node in the scene and store each bundle as a private scene inside that sequence bundle node
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
Line 34: Line 35:
 
</div>
 
</div>
 
</div>
 
</div>
 +
==Use cases==
 +
* Tracked ultrasound image sequence review
 +
* Adaptive RT image sequence review
 +
* 4D Cardiac CT volume rendering
 +
* DCE-MRI review

Revision as of 18:50, 28 December 2013

Home < 2014 Project Week:MultidimensionalDataSupport

Key Investigators

  • Queen's: Andras Lasso
  • BWH: Andriy Fedorov
  • Isomics: Steve Pieper
  • Kitware Jean-Christophe Fillion-Robin
  • UHN: Kevin Wang

Project Description

Objective

  • 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 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)
    • Save into scene file
    • 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 bundle name, parameter

Approach, Plan

  • 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

Progress

Use cases

  • Tracked ultrasound image sequence review
  • Adaptive RT image sequence review
  • 4D Cardiac CT volume rendering
  • DCE-MRI review