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

From NAMIC Wiki
Jump to: navigation, search
Line 34: Line 34:
 
* Discussed approach to be taken, concerns regarding performance
 
* Discussed approach to be taken, concerns regarding performance
 
* Node count can explode into the thousands, performance analysis needed
 
* Node count can explode into the thousands, performance analysis needed
** Initial unscientific performance analysis run, results concerning
+
** Initial test performance analysis run, results concerning
 
*** Create hierarchies with 1500 and 7000 nodes, observed
 
*** Create hierarchies with 1500 and 7000 nodes, observed
 
*** Create hierarchy with 250 * 5 (1 volume, 4 transforms per frame) nodes
 
*** 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
 
**** 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
 
***** Deep copy used
**** Passable results, not smooth
+
**** Allocate nodes, add to scene ~25 seconds
 +
**** Able to drag slider, occasional stuttering
 +
**** [https://www.assembla.com/spaces/perklabsandbox/documents/bhSQdG2NOr4RtcacwqjQWU/download/bhSQdG2NOr4RtcacwqjQWU Run1]
 +
**** [https://www.assembla.com/spaces/perklabsandbox/documents/bnuv4q2NOr4OkvacwqEsg8/download/bnuv4q2NOr4OkvacwqEsg8 Run2]
  
  

Revision as of 13:56, 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 test 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
        • Allocate nodes, add to scene ~25 seconds
        • Able to drag slider, occasional stuttering
        • Run1
        • Run2


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