Difference between revisions of "2012 Project Week:4DImageSlicer4"
From NAMIC Wiki
Line 26: | Line 26: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</div> | </div> | ||
Line 81: | Line 53: | ||
This work will be delivered to the NA-MIC Kit as a core functionality of 3D Slicer v.4 | This work will be delivered to the NA-MIC Kit as a core functionality of 3D Slicer v.4 | ||
+ | |||
+ | ==Pre-meeting notes== | ||
==References== | ==References== |
Revision as of 23:03, 9 January 2012
Home < 2012 Project Week:4DImageSlicer4Key Investigators
- BWH: Andrey Fedorov
- Isomics: Steve Pieper
- BWH: Junichi Tokuda
- MGH: Jayashree Kalpathy-Cramer
- GE: Emma Zhu
- GE: Jim Miller
Objective
To discuss the architecture and work on implementing support for 4d images in Slicer4.
Our primary use case is to provide support for IO and visualization of DCE MRI, with the application specifically to prostate imaging.
Approach, Plan
Progress
Initial experiments showed the feasibility of the proposed approach:
- DicomToNrrdConverer works for DCE data
- B-values field can be used to store timestamps
Questions:
- are VTK plotting capabilities as in RT module available from python
- a ChartViewer (like a SliceView or 3D View that can be packed in a layout) is under development - Jim
- python vs c++ for the DCE GUI module
- DWI volume has B-values vector, but only the last B-value is saved in the NRRD volume by Slicer -- is this expected?
- what should be included in the DCE GUI module? plan: simplified version of the Volumes DWI panel, adjusted for DCE needs
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a core functionality of 3D Slicer v.4