Operating system: MacOS Ventura
Slicer version: 5.7.0
Hello,
I am trying to load an image set including a 3D MRI with RT files containing volumetric and dosimetric information that have been exported from a DICOM viewer. I want to view the volume segmentations on the images in Slicer. I have installed SlicerRT, QuantitativeReporting and Sandbox extensions.
When I import the dicom files through the dicom import button, I get an error message saying that some files failed to load. the volumetric MRI appears correctly and the RT files do not load correctly. the RT files have a .dcm extension.
here is the Python error log:
AttributeError: module âmodulesâ has no attribute âdicomsroimportexportâ
[Python] DICOM Plugin failed: module âmodulesâ has no attribute âdicomsroimportexportâ
[Python] Warning in DICOM plugin Scalar Volume when examining loadable Unnamed Series: Reference image in series does not contain geometry information. Please use caution.
[VTK] vtkITKArchetypeImageSeriesReader::ExecuteInformation: Cannot open /Volumes/Crucial X8/SLICER/SLICER test AVM case 2/Avm_Case_02_Gp/Rm_Stereotassica_Cmc - 330253576/unnamed_0/IM-0001-10000-0001.dcm. ITK exception info: error in unknown: Could not create IO object for reading file /Volumes/Crucial X8/SLICER/SLICER test AVM case 2/Avm_Case_02_Gp/Rm_Stereotassica_Cmc - 330253576/unnamed_0/IM-0001-10000-0001.dcm
[VTK] Tried to create one of the following:
[VTK] BMPImageIO
[VTK] BioRadImageIO
[VTK] DCMTKImageIO
[VTK] GDCMImageIO
[VTK] GiplImageIO
[VTK] JPEGImageIO
[VTK] LSMImageIO
[VTK] MGHImageIO
[VTK] MINCImageIO
[VTK] MRCImageIO
[VTK] MetaImageIO
[VTK] NiftiImageIO
[VTK] NrrdImageIO
[VTK] PNGImageIO
[VTK] ScancoImageIO
[VTK] StimulateImageIO
[VTK] TIFFImageIO
[VTK] VTKImageIO
[VTK] MRMLIDImageIO
[VTK] Bruker2dseqImageIO
[VTK] GE4ImageIO
[VTK] GE5ImageIO
[VTK] HDF5ImageIO
[VTK] JPEG2000ImageIO
[VTK] You probably failed to set a file suffix, or
[VTK] set the suffix to an unsupported type.
[VTK] Algorithm vtkITKArchetypeImageSeriesVectorReaderFile (0x7fe46d86f670) returned failure for request: vtkInformation (0x600008bd2940)
[VTK] Debug: Off
[VTK] Modified Time: 630465
[VTK] Reference Count: 1
[VTK] Registered Events: (none)
[VTK] Request: REQUEST_INFORMATION
[VTK] ALGORITHM_AFTER_FORWARD: 1
[VTK] FORWARD_DIRECTION: 0
[Python] Could not read scalar volume using GDCM approach. Error is: FileFormatError
[VTK] vtkITKArchetypeImageSeriesReader::ExecuteInformation: Cannot open /Volumes/Crucial X8/SLICER/SLICER test AVM case 2/Avm_Case_02_Gp/Rm_Stereotassica_Cmc - 330253576/unnamed_0/IM-0001-10000-0001.dcm. ITK exception info: error in unknown: Could not create IO object for reading file /Volumes/Crucial X8/SLICER/SLICER test AVM case 2/Avm_Case_02_Gp/Rm_Stereotassica_Cmc - 330253576/unnamed_0/IM-0001-10000-0001.dcm
[VTK] Tried to create one of the following:
[VTK] BMPImageIO
[VTK] BioRadImageIO
[VTK] DCMTKImageIO
[VTK] GDCMImageIO
[VTK] GiplImageIO
[VTK] JPEGImageIO
[VTK] LSMImageIO
[VTK] MGHImageIO
[VTK] MINCImageIO
[VTK] MRCImageIO
[VTK] MetaImageIO
[VTK] NiftiImageIO
[VTK] NrrdImageIO
[VTK] PNGImageIO
[VTK] ScancoImageIO
[VTK] StimulateImageIO
[VTK] TIFFImageIO
[VTK] VTKImageIO
[VTK] MRMLIDImageIO
[VTK] Bruker2dseqImageIO
[VTK] GE4ImageIO
[VTK] GE5ImageIO
[VTK] HDF5ImageIO
[VTK] JPEG2000ImageIO
[VTK] You probably failed to set a file suffix, or
[VTK] set the suffix to an unsupported type.
[VTK] Algorithm vtkITKArchetypeImageSeriesVectorReaderFile (0x7fe46d9a0450) returned failure for request: vtkInformation (0x600004b85080)
[VTK] Debug: Off
[VTK] Modified Time: 630560
[VTK] Reference Count: 1
[VTK] Registered Events: (none)
[VTK] Request: REQUEST_INFORMATION
[VTK] ALGORITHM_AFTER_FORWARD: 1
[VTK] FORWARD_DIRECTION: 0
[Python] Could not read scalar volume using DCMTK approach. Error is: FileFormatError
[Python] Could not load: Unnamed Series as a Scalar Volume
[FD] [49433:149507:1222/162444.029558:ERROR:gl_context_cgl.cc(118)] Error creating context.
I tried to export the ROIs from Horos to Osirix ROI format and .xml but cannot load these either.
Could the issue lie with the file metadata (they could be corrupted when exported from the Dicom viewer)? or rather the Slicer program itself?
sidenote: the same cases have been segmented in Brainlabâs Elements software and exported, and these load correctly on Slicer.