Difference between revisions of "2014 Winter Project Week:MRB Extension Dependencies"
From NAMIC Wiki
| (3 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
==Key Investigators== | ==Key Investigators== | ||
| − | Steve Pieper, Isomics | + | * Steve Pieper, Isomics |
| − | Jean-Christophe Fillion-Robin, Kitware | + | * Jean-Christophe Fillion-Robin, Kitware |
| − | Jim Miller, GE | + | * Jim Miller, GE |
| − | Nicole Aucoin, BWH | + | * Nicole Aucoin, BWH |
| − | Alex Yarmarkovich, BWH | + | * Alex Yarmarkovich, BWH |
==Project Description== | ==Project Description== | ||
| Line 17: | Line 17: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
| − | MRB's (and Scenes in general) may reference nodes or panels (via module selection) which may have been installed on the MRB author's machine but not available on the machine of the person who downloaded the MRB. In this circumstance, the person who downloaded the MRB may not be able to access all the information in the MRB. For example, SceneView restores may not function properly. Furthermore, the user is not provided | + | MRB's (and Scenes in general) may reference nodes or panels (via module selection) which may have been installed on the MRB author's machine via Extensions but not available on the machine of the person who downloaded the MRB. In this circumstance, the person who downloaded the MRB may not be able to access all the information in the MRB. For example, SceneView restores may not function properly. Furthermore, the user is not provided any guidance on how to rectify the situation. |
| + | |||
| + | The goal of this project is to develop a design whereby the Slicer will track a Scene's dependency on Extensions and provide a mechanism for the user to download the missing Extensions. | ||
</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> | ||
* Talk through the issues in | * Talk through the issues in | ||
| − | # tracking (nodes, modules, extension) information inside a MRML structure | + | # tracking (nodes, modules, extension) dependency information inside a MRML structure |
# automatically downloading needed extensions at MRB download time | # automatically downloading needed extensions at MRB download time | ||
* Develop a preliminary design and plan | * Develop a preliminary design and plan | ||
| Line 28: | Line 30: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | Options |
| + | # Track (nodes, modules, extension) dependency information inside MRML | ||
| + | # Record all Extensions available on MRB author's machine inside MRML | ||
| + | |||
| + | Notes | ||
| + | * Just because an Extension was used to author an MRB does not mean that Extension is needed to view the contents of the MRB. | ||
</div> | </div> | ||
</div> | </div> | ||
Latest revision as of 12:46, 25 November 2013
Home < 2014 Winter Project Week:MRB Extension Dependencies
Key Investigators
- Steve Pieper, Isomics
- Jean-Christophe Fillion-Robin, Kitware
- Jim Miller, GE
- Nicole Aucoin, BWH
- Alex Yarmarkovich, BWH
Project Description
Objective
MRB's (and Scenes in general) may reference nodes or panels (via module selection) which may have been installed on the MRB author's machine via Extensions but not available on the machine of the person who downloaded the MRB. In this circumstance, the person who downloaded the MRB may not be able to access all the information in the MRB. For example, SceneView restores may not function properly. Furthermore, the user is not provided any guidance on how to rectify the situation.
The goal of this project is to develop a design whereby the Slicer will track a Scene's dependency on Extensions and provide a mechanism for the user to download the missing Extensions.
Approach, Plan
- Talk through the issues in
- tracking (nodes, modules, extension) dependency information inside a MRML structure
- automatically downloading needed extensions at MRB download time
- Develop a preliminary design and plan
Progress
Options
- Track (nodes, modules, extension) dependency information inside MRML
- Record all Extensions available on MRB author's machine inside MRML
Notes
- Just because an Extension was used to author an MRB does not mean that Extension is needed to view the contents of the MRB.
