The original .dcm files work fine, but my client recently annotated new versions of the study with color demarcations. Although these new versions are also .dcm files, they will not load as a scalar volume.
The originals were 130KB in size while the new (non-loadable) versions are 4,129K in size.
Thanks for any ideas. The client isn’t able to describe anything he might have done differently.
As described in the documentation, you need to install QuantitiveReporting or SlicerRT extension to import DICOM Segmentation Object or DICOM RT structure set information objects.
We know we cannot expect users to read documentation, so we added an informational message that tells this during DICOM import, but probably it is not the right time (users just click on it and don’t realize that the error that they get during loading is related). We are going to improve this, see details here:
Thanks! I discovered that turning the images into grayscale with Gimp and overwriting them allowed them to be imported. Photoshop also allowed grayscale, but my metadata was altered in odd ways. They appear to have 1mm spacing now instead of 1.2mm, but I can fix in Blender for this task to segment a tumor.
General-purpose image processing applications, such as Gimp, Photoshop, or Blender are OK to use for final editing of DICOM images for publishing or presentations. However, they are expected to cause random data loss/corruption in any exported medical image metadata, which may not even be immediately obvious. Therefore, never even consider using images processed in general-purpose artistic image editing software for any medical image computing applications.
