Difference between revisions of "2008 Winter Project Week:MRMLScenesForExecutionModel"
From NAMIC Wiki
| Line 28: | Line 28: | ||
Goal: pass MRML scenes and subscenes back and forth between Slicer3 and command line executables/plug-ins. | Goal: pass MRML scenes and subscenes back and forth between Slicer3 and command line executables/plug-ins. | ||
| + | |||
| + | MRML scenes are currently used as wrappers to pass transforms and model hierarchy nodes to command line executables/plug-ins. Does this infrastructure need to be expanded to support other node types? Or is a separate mechanism needed to pass complete scenes? | ||
| + | |||
| + | Id remapping is major concern when passing scenes. A second concern is how to indicate that a subscene is to be replaced. | ||
</div> | </div> | ||
Revision as of 14:11, 2 January 2008
Home < 2008 Winter Project Week:MRMLScenesForExecutionModel Return to 2008_Winter_Project_Week |
Key Investigators
- GE: Jim Miller
- Kitware: Brad Davis
- BWH: Nicole Aucoin
- Isomics: Alex Yarmarkovich, Steve Pieper
Objective
Integrate MRML Scenes into Execution Model modules.
Approach, Plan
Goal: pass MRML scenes and subscenes back and forth between Slicer3 and command line executables/plug-ins.
MRML scenes are currently used as wrappers to pass transforms and model hierarchy nodes to command line executables/plug-ins. Does this infrastructure need to be expanded to support other node types? Or is a separate mechanism needed to pass complete scenes?
Id remapping is major concern when passing scenes. A second concern is how to indicate that a subscene is to be replaced.
Progress
Jun 2007 Project Week
MRML Scenes for the Execution Model including Transforms
Jan 2008 Project Half Week
