I’m trying to visualize a modified dose cube. I succed in loading it, but the cube is displayed in the original format (like short: from 0 to 65536 values). I am wondering why is the DICOM Tag “(3004,000e)” aka DoseGridScaling ignored. I thought this should rescale the values into dose.
My first suspicion is that your object is being interpreted by the Slicer DICOM image loader rather than the SlicerRT DICOM dose loader. This would explain your symptoms.
Would it be possible for you to post your error log?
Do you have the SlicerRT extension installed?
Here is the log text:
Loaded volume from file: /home/george/test.dcm. Dimensions: 512x512x105. Number of components: 1. Pixel type: unsigned short.
“Volume” Reader has successfully read the file “/home/george/test.dcm” “[0.69s]”
Can I “convince” SlicerRT to interpret the input?
Yes I have the extension installed. I am using slicer under Ubuntu.
Based on the log it seems that you use the Add data dialog. Please use the DICOM browser instead. Click on the DCM button in the top left corner, import your study folder, and load from the patient browser. You need to use the DICOM browser to load all DICOM files.
Yes it did work. Thank you. I tried to visualize a dose distribution recalculated with another TPS, inserting the recalculated dose into the dicom of the original dose. Because of the same IDs the original dose was overwritten in the dicom database…
Next time, try generating a new SOP Instance UID for your new dose. I guess that would allow both objects to appear in the browser. Good luck!