Difference between revisions of "2014 Project Week:MRMLSceneSpeedUp"

From NAMIC Wiki
Jump to: navigation, search
m (Created page with '__NOTOC__ <gallery> Image:PW-SLC2013.png|Projects List </gallery> ==Key Investigators== * Kitware: Jean-Christophe Fillion-Robin * Queen's…')
 
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
<gallery>
 
<gallery>
Image:PW-SLC2013.png|[[2014_Winter_Project_Week#Projects|Projects List]]
+
Image:PW-SLC2014.png|[[2014_Winter_Project_Week#Projects|Projects List]]
 
</gallery>
 
</gallery>
  
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>
* Reduce number of observers associated with MRML nodes
+
* Identify what is the next bottle neck.
 +
** Reduce number of observers associated with MRML nodes?
 +
** Improve internal data structure associated with nodes ?
 +
* Follow-up of [[2013_Project_Week:SpeedUp|last year work]].
 
</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>
Approach
+
* Develop a plan for measuring performance.
 
+
* Consider places where we could refactor and centralize some work that is being done redundantly by many widgets and modules (e.g. monitoring node modifications).
*  
 
  
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Progress</h3>
 
<h3>Progress</h3>
*
+
* Collected stats related to Slicer startup time. See http://wiki.slicer.org/slicerWiki/index.php/Documentation/Labs/StartupTimeImprovement

Latest revision as of 16:15, 10 January 2014

Home < 2014 Project Week:MRMLSceneSpeedUp

Key Investigators

  • Kitware: Jean-Christophe Fillion-Robin
  • Queen's University: Andras Lasso
  • Isomics: Steve Pieper

Project Description

Objective

  • Identify what is the next bottle neck.
    • Reduce number of observers associated with MRML nodes?
    • Improve internal data structure associated with nodes ?
  • Follow-up of last year work.

Approach, Plan

  • Develop a plan for measuring performance.
  • Consider places where we could refactor and centralize some work that is being done redundantly by many widgets and modules (e.g. monitoring node modifications).

Progress