Difference between revisions of "2013 Summer Project Week:Parameter heirarchy"
From NAMIC Wiki
m (Text replacement - "[http://www.na-mic.org/Wiki/images/" to "[https://na-mic.org/w/images/") |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 36: | Line 36: | ||
** Initial test 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 512x512x4byte, 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 | ||
− | **** Allocate nodes, add to scene | + | **** Allocate nodes, add to scene WITH BATCH PROCESSING |
**** Able to drag slider, occasional stuttering | **** Able to drag slider, occasional stuttering | ||
**** i7-2640M, 6GB RAM, [http://www.newegg.com/Product/Product.aspx?Item=N82E16820227812 2nd gen SSD] | **** i7-2640M, 6GB RAM, [http://www.newegg.com/Product/Product.aspx?Item=N82E16820227812 2nd gen SSD] | ||
− | **** [https:// | + | **** [https://na-mic.org/w/images/0/00/Run1_250.txt Run1 250] |
− | **** [https:// | + | **** [https://na-mic.org/w/images/8/89/Run2_250.txt Run2_250] |
− | **** [https:// | + | **** [https://na-mic.org/w/images/b/b9/Run3_500.txt Run3_500] |
− | **** | + | **** [https://na-mic.org/w/images/e/e6/Run4_1000.txt Run4_1000] |
'''To do''': | '''To do''': |
Latest revision as of 18:27, 10 July 2017
Home < 2013 Summer Project Week:Parameter heirarchyKey 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 512x512x4byte, 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 WITH BATCH PROCESSING
- Able to drag slider, occasional stuttering
- i7-2640M, 6GB RAM, 2nd gen SSD
- Run1 250
- Run2_250
- Run3_500
- Run4_1000
- Slider in widget tied to logic to replace current view volume contents with the contents of the frame indexed by slider value
- Initial test performance analysis run, results concerning
To do:
- Implement importer/exporter for MHA
- Discuss approach to performance, currently performance features are optional
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a Slicer module in the SlicerIGT extension.