Difference between revisions of "Documentation/4.1/Modules/MultiVolumeImporter"
From Slicer Wiki
Line 66: | Line 66: | ||
*** User-defined DICOM: the tag specified by the user in the '''Advanced settings''' panel will be used to separate individual frames. | *** User-defined DICOM: the tag specified by the user in the '''Advanced settings''' panel will be used to separate individual frames. | ||
*** User-defined non-DICOM: the directory is expected to contain a list of individual frames saved in a [[Documentation/4.1/SlicerApplication/SupportedDataFormat|image volume format supported by 3D Slicer]], such as NRRD or NIfTI. | *** User-defined non-DICOM: the directory is expected to contain a list of individual frames saved in a [[Documentation/4.1/SlicerApplication/SupportedDataFormat|image volume format supported by 3D Slicer]], such as NRRD or NIfTI. | ||
− | **** '''IMPORTANT''' If you use ''User-defined non-DICOM'' input data type, the frames will be sorted based on the alphanumerical order of the frame filenames. If you have more than 10 frames, you should name them as follows to make sure they are ordered correctly. <span style="color:#008000">'''Correct naming''': frame001.nrrd, frame002.nrrd, ..., frame023.nrrd, ..., frame912.nrrd</span> | + | **** '''IMPORTANT''' If you use ''User-defined non-DICOM'' input data type, the frames will be sorted based on the alphanumerical order of the frame filenames. If you have more than 10 frames, you should name them as follows to make sure they are ordered correctly. |
+ | *****<span style="color:#008000">'''Correct naming''': frame001.nrrd, frame002.nrrd, ..., frame023.nrrd, ..., frame912.nrrd</span> | ||
+ | |||
+ | *****<span style="color:#8B0000">'''Incorrect naming''': frame1.nrrd, frame2.nrrd, ..., frame14.nrrd, ..., frame1045.nrrrd</span>. | ||
| align="right" | | | align="right" | |
Revision as of 17:32, 1 May 2012
Home < Documentation < 4.1 < Modules < MultiVolumeImporterPage under construction. |
WARNING: This module is Work in Progress, which means:
|
Introduction and Acknowledgements
This work is supported by NA-MIC, NAC, NCIGT, and the Slicer Community. This work is partially supported by the following grants: P41EB015898, P41RR019703, R01CA111288 and U01CA151261. | |||||||||||
|
Module Description
This module provides support for importing multivolume (multiframe) data.
Use Cases
Most frequently used for these scenarios:
- importing a DICOM dataset that contains multiple frames that can be separated based on some tag (e.g., DCE MRI data, where individual temporally resolved frames are identified by Trigger Time tag (0018,1060)
- importing multiple frames defined in the same coordinate frame, saved as individual volumes in NRRD, NIfTI, or any other image format supported by 3D Slicer
Tutorials
- Sample datasets are available:
- anonymized prostate DCE MRI DICOM series
- File:Cardiac ECGg CT.tgz (ECG-gated contrast-enhanced cardiac CT) (use "User-defined non-DICOM" parameter option to load it into MultiVolumeImporter). Short movie
Panels and their use
|
|
- Import button: once the panels are populated with the appropriate settings, hit this button to import the dataset into Slicer. Note that depending on the size of the data this operation can take significant time, so be patient!
Related Modules
Once the multivolume dataset is loaded, it can be viewed and further explored using MultiVolumeExplorer module.
References
- Development of this module was initiated at the 2012 NA-MIC Project week at SLC (see http://wiki.na-mic.org/Wiki/index.php/2012_Project_Week:4DImageSlicer4)
Information for Developers
This module is an external Slicer module. The source code is available on Github here: https://github.com/fedorov/MultiVolumeImporter
Known issues that won't be resolved
- bug 1841: multivolumes that contain less than 7 frames will not be saved correctly and the scene containing such objects will not be loaded correctly by Slicer (limitation of the NRRD IO for DWI)
Features to be implemented
- integrate MV importer as a DICOM module plugin
Features under consideration
- should DWI node be a child under the MV hierarchy?
- import multivolumes from ITK 4d images