I’ve received the data set and it is not legal DICOM.
First of all, the same SOP instance UID is used in all the files, so the DICOM importer imports the first file and ignores the rest.
If I use a workaround and instead of properly using the DICOM module, I just add the data set as non-DICOM data (that uses ITK’s DICOM reader) then the image appears but since the voxel type is short (instead of unsigned char) and the range is off (-1024 to -769), the volume renderer does not show anything.
If you fix the data set to have prober unique identifiers and voxel type and range then Slicer will display it correctly.
RGB volumes are problematic for many reasons, so instead of burning in a colormap I would strongly recommend to save a standard scalar image and apply a color lookup table in the application. You can choose colormap for slice views in Volumes module and apply the same coloring in Volume rendering module by clicking on Synchronize with Volumes module button.
