Difference between revisions of "2013 Summer Project Week:Parameter heirarchy"

From NAMIC Wiki
Jump to: navigation, search
Line 32: Line 32:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
−
* .
+
* Discussed approach to be taken, concerns regarding performance
 +
* Node count can explode into the thousands, performance analysis needed
 +
** Initial unscientific performance analysis run, results concerning
 +
*** Create hierarchies with 1500 and 7000 nodes, observed
 +
*** Create hierarchy with 250 * 5 (1 volume, 4 transforms per frame) nodes
 +
**** Slider in widget tied to logic to replace current view volume contents with the contents of the frame indexed by slider value
 +
***** Deep copy used
 +
**** Passable results, not smooth
  
  
 
'''To do''':  
 
'''To do''':  
−
* Create a large MRML tree and test performance (self-test that can be run on multiple computers), include multiple volumes, transforms, modules; use batch processing node, hide nodes from editor
 
−
* Test copying of node contents from a slider-selected branch of the tree
 
 
* Implement importer/exporter for MHA
 
* Implement importer/exporter for MHA
  

Revision as of 13:26, 21 June 2013

Home < 2013 Summer Project Week:Parameter heirarchy

Key Investigators

  • Queen's: Adam Rankin
  • Queen's: Andras Lasso
  • Queen's: Tamas Ungi

Objective

The goal is to develop a module that creates and utilizes a new hierarchy based on definable parameters. This will allow us to characterize data by time.

Approach, Plan

  • Review existing time hierarchy discussion
  • Learn technical details about hierarchies
  • Discuss architecture of a flexible, abstract parameter hierarchy
  • Implement said hierarchy

Progress

  • Discussed approach to be taken, concerns regarding performance
  • Node count can explode into the thousands, performance analysis needed
    • Initial unscientific performance analysis run, results concerning
      • Create hierarchies with 1500 and 7000 nodes, observed
      • Create hierarchy with 250 * 5 (1 volume, 4 transforms per frame) nodes
        • Slider in widget tied to logic to replace current view volume contents with the contents of the frame indexed by slider value
          • Deep copy used
        • Passable results, not smooth


To do:

  • Implement importer/exporter for MHA

Delivery Mechanism

This work will be delivered to the NA-MIC Kit as a Slicer module in the SlicerIGT extension.


References

Retrieved from "https://www.na-mic.org/w/index.php?title=2013_Summer_Project_Week:Parameter_heirarchy&oldid=82634"