I have received DICOM data from an external partner. After importing the files, the DICOM browser lists a lot of series, but they all look exactly the same in the series list. I can only distinguish them by opening the metadata window and looking at the file path. (The patient info is the same, and the study info only differs by the StudyTime, which contains an uninterpretable value, probably filled in by anonymization software.)
It would be very useful for me to have this file path as additional column in the series list. Is this possible?
Usually a DICOM series is stored in hundreds of files, with random file names, often spread across in several directories, so they are not a good indication of content. For the rare occasion when filenames are useful, you have the metadata browser.
I agree that more useful information could be shown in the series list. Do you see any other field in the metadata browser that would better indicate what’s in the series?
Thank you for the hint and the ticket. Unfortunately, I could not load the RTIMAGES:
The Slicer-2017-05-06 Nightly with SlicerRT gave me Could not load: Unknown - as DWI Volume as a Diffusion Volume,
and Slicer 3.6.2 4.6.2 with SlicerRT said Could not load: 0: RTIMAGE: 744483668-0 as a RT.
However, I don’t currently need to solve this, because my project has moved into a different direction.
I thought SlicerRT is only available for Slicer 4.0 and above, but in any case, those versions are at least 5-6 years old, and many features - including RTIMAGE reading - is not present yet.
As for the new nightly, the message you get is not from SlicerRT, but from another DICOM plugin, which suggests that SlicerRT is not properly installed, or maybe there are some other issues related to the DICOM plugins. Can you load dose volumes correctly? (meaning that it appears with a rainbow color palette, and is shown as dose volume in subject hierarchy)
If you can share those DICOM files with us (preferably anonymized), then I can take a look.
Sorry for my misleading typo: I meant Slicer 4.6.2 (and fixed that now).
As a Slicer newbie, I don’t know anything about the ‘dose volumes’ you mention. However, some RTSTRUCT file loads fine in both Slicer versions, so SlicerRT seems to be installed correctly. (It is the only installed extension.)
Unfortunately, my project does not currently allow to find out whether I can share the files.
If RTSS is loaded correctly, then SlicerRT is correctly deployed indeed. Unfortunately without at least one RTIMAGE file I cannot find out why it fails to load. Can you share the log after the failed load? You can find it in the menu Help / Report a bug.
FYI, as RTIMAGE is a radiation therapy image modality, and RT involves irradiation with a planned dose, the 3D dose distribution needs to be calculated and evaluated. This is what dose volume is.