Difference between revisions of "2015 Winter Project Week: Multiframe DICOM"
From NAMIC Wiki
| (2 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
** Diffusion Profiles | ** Diffusion Profiles | ||
** Parametric Maps | ** Parametric Maps | ||
| + | ** Ultrasound Objects | ||
** Derived Objects | ** Derived Objects | ||
* Review the options for a dcm2dcm tool | * Review the options for a dcm2dcm tool | ||
| Line 29: | 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> | ||
| − | * | + | * In-depth code and standard review during QIICR breakout session |
| + | ** dcmseg (seg==Segmentation), dcmiod (iod==Information Object Definition), dcmfg (fg==Functional Groups) libraries explored | ||
| + | ** prototype converters to/from nrrd for segentation objects | ||
| + | * Identified issues with multiframe MR import in slicer | ||
| + | ** gdcm and dcmtk based readers in ITK cannot currently extract orientation/spacing from per-frame functional groups | ||
| + | ** plan is to look at fixing itkDCMTKImageIO once the version of DCMTK has dcmiod and dcmfg integrated | ||
| + | ** nearer-term a pydicom-based reader could be written for slicer DICOMPlugin | ||
</div> | </div> | ||
| + | <h3>References</h3> | ||
| + | * There are several Slicer/ITK bugs related to improper handling of "21st Century DICOM" objects using [http://www.na-mic.org/Bug/view.php?id=3930 legacy code designed for older objects]. | ||
</div> | </div> | ||
Latest revision as of 16:42, 8 January 2015
Home < 2015 Winter Project Week: Multiframe DICOM
Key Investigators
- Steve Pieper, Isomics
- Andrey Fedorov, BWH
- Michael Onken, Open Connections / DCMTK
Project Description
Objective
- Review progress on DICOM Enhanced Multiframe Object support in DCMTK
- Segmentation Objects (see Iowa2DICOM)
- Diffusion Profiles
- Parametric Maps
- Ultrasound Objects
- Derived Objects
- Review the options for a dcm2dcm tool
- Convert legacy acquisitions to multiframe objects
- Correctly encode derived objects
Approach, Plan
- Try to build Slicer with latest DCMTK that includes Multiframe Object support
- Try simple programs to exercise API
Progress
- In-depth code and standard review during QIICR breakout session
- dcmseg (seg==Segmentation), dcmiod (iod==Information Object Definition), dcmfg (fg==Functional Groups) libraries explored
- prototype converters to/from nrrd for segentation objects
- Identified issues with multiframe MR import in slicer
- gdcm and dcmtk based readers in ITK cannot currently extract orientation/spacing from per-frame functional groups
- plan is to look at fixing itkDCMTKImageIO once the version of DCMTK has dcmiod and dcmfg integrated
- nearer-term a pydicom-based reader could be written for slicer DICOMPlugin
References
- There are several Slicer/ITK bugs related to improper handling of "21st Century DICOM" objects using legacy code designed for older objects.
