@thewtex thanks for the response!
I thought it is probably not very helpful if I submit an issue demonstrating the problem in Slicer, since there are potentially other sources of error, so I wanted to reproduce the problem with ITK.
I googled for “itk read dicom series”, and came across the python example here: https://itk.org/ITKExamples/src/IO/GDCM/ReadDICOMSeriesAndWrite3DImage/Documentation.html.
However, when I run this example (after adding import sys
) on the dataset referenced from the thread mentioned in the initial post (the dataset itself is available here: https://www.dropbox.com/s/re37n46wvktez5c/mf.dcm.bz2), I get the error below:
WARNING: In /Users/kitware/Dashboards/ITK/ITKPythonPackage/standalone-build/ITK-source/Modules/IO/GDCM/src/itkGDCMSeriesFileNames.cxx, line 109
GDCMSeriesFileNames (0x7fe8869d7bb0): No Series were found
No DICOMs in: .
Looks like this DICOM file is not even recognized as DICOM by ITK GDCMSeriesFileNames
.
Checking it with dcmdump
, it is clearly a valid DICOM file (and it comes from David Clunie).
$ dcmdump mf.dcm|more 2.3.6
# Dicom-File-Format
# Dicom-Meta-Information-Header
# Used TransferSyntax: Little Endian Explicit
(0002,0000) UL 214 # 4, 1 FileMetaInformationGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =LegacyConvertedEnhancedMRImageStorage # 28, 1 MediaStorageSOPClassUID
(0002,0003) UI [1.3.6.1.4.1.5962.99.1.7321.1421.1542625430036.1.1.1.2.1] # 56, 1 MediaStorageSOPInstanceUID
(0002,0010) UI =LittleEndianExplicit # 20, 1 TransferSyntaxUID
(0002,0012) UI [1.3.6.1.4.1.5962.99.2] # 22, 1 ImplementationClassUID
(0002,0013) SH [PIXELMEDJAVA001] # 16, 1 ImplementationVersionName
(0002,0016) AE [OURAETITLE] # 10, 1 SourceApplicationEntityTitle
# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0008) CS [ORIGINAL\PRIMARY\M\NONE] # 24, 4 ImageType
(0008,0012) DA [20181119] # 8, 1 InstanceCreationDate
(0008,0013) TM [060350.036] # 10, 1 InstanceCreationTime
(0008,0016) UI =LegacyConvertedEnhancedMRImageStorage # 28, 1 SOPClassUID
(0008,0018) UI [1.3.6.1.4.1.5962.99.1.7321.1421.1542625430036.1.1.1.2.1] # 56, 1 SOPInstanceUID
(0008,0020) DA [19991231] # 8, 1 StudyDate
(0008,0021) DA [19991231] # 8, 1 SeriesDate
(0008,0023) DA [19991231] # 8, 1 ContentDate
Is LegacyConvertedEnhancedMRImageStorage IOD expected to be supported by ITK?
Is there another example you can point me to that is recommended that I can use to reproduce the problem and report the issue?