Difference between revisions of "2012 Winter Project Week:ScriptView"
| Line 26: | Line 26: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | Our approach is create a template MRML scene file and reuse it for each subject. MRML scene stores relative paths to items in the scene such as volumes. Python script is passed to Slicer to load | + | Our approach is to create a template MRML scene file and reuse it for each subject. MRML scene stores relative paths to items in the scene such as volumes. Python script is passed to Slicer to load the scene per subject and save image.<foo>. |
Revision as of 16:21, 13 January 2012
Home < 2012 Winter Project Week:ScriptView
Subject1.
Subject2.
Subject3.
Key Investigators
- GE Research: Albert Montillo
Many thanks to : Steve Pieper (Isomics)
Objective
Programmatically setup 3D Slicer to view data from different subjects while applying the same consistent view. Save screen image to PNG.
Approach, Plan
Our approach is to create a template MRML scene file and reuse it for each subject. MRML scene stores relative paths to items in the scene such as volumes. Python script is passed to Slicer to load the scene per subject and save image.<foo>.
Progress
The python script has been tested on folder with multiple subject subfolders. All subject folders use same file names for scene elements so that same MRML file works for all subjects. MRML scene need only be setup once, for one subject, then reused for each subject.
Delivery Mechanism
This work will be delivered as a python script.
