Volumes display Image Spacing and Image Origin wrong?

Support
1

When I load a CT Lung series (axial) into Slicer 4.13, and switch to the “Volumes” Module, and the “Image Spacing” and “Image Origin” display: [1mm, 1mm, 1mm] and [0, 0, 0] as picture below.

image
image698×326 28.8 KB

But when I dcmdump the random dcm file, the relative DICOM tag values are:

(0020,0032) DS [-173.100 \ -180.000 \ -272.500] # 26, 3 ImagePositionPatient,

(0020,0037) DS [1.000000\0.000000\0.000000\0.000000\1.000000\0.000000] # 54, 6 ImageOrientationPatient

(0028,0030) DS [0.703125\0.703125] # 18, 2 PixelSpacing.

(0018,0050) DS [1.250000] # 8, 1 SliceThickness

And the dicom MPR image is as follow:

image
image1197×859 107 KB

So, why Image Spacing of Volumes Module is: [1, 1, 1], not: [0.703125, 0.703125, 1.25].
And the x, y of ImageOrigin is [0, 0], not: [-173.100, -180.00].

2

There’s probably more going on - check the logs to see if there are any error messages or other warnings. We try very hard to make sure DICOM files are properly interpreted in 3D, but weird things can happen, possibly due to inconsistencies in the data. If you can share a public example that replicates the issue for sure we’ll look into it.

3

Thank you for your reply.

I have uploaded the sampleData to Google Driver, pop the sensitive dicom tags. Please download the data by link to look into why ImageOrigin and ImageSpacing is not displayed as expected.

link is: https://drive.google.com/file/d/1RnD_xzYptdIY5nfiPeQsDSlC4airhcx2/view?usp=drive_link

Thank you very much.

4

The link to Google Drive is not public.
What is the value of the SOP Class UID (0x0008,0x0016)?
Most likely the series is stored in Secondary Capture IOD.

Adding spatial information to the Secondary Capture IOD is a fairly common practice, even if it was not part of the IOD until 2024, s. CP-2330. Probably the recent version of Slicer will work with this series (you are using the old version 4.13).

5

I’m so sorry the google drive link is private, I’m new to Google driver.

This is the new data link: https://drive.google.com/file/d/1RnD_xzYptdIY5nfiPeQsDSlC4airhcx2/view
anyone can download and view the data.

I have try this data with the Slicer 5.6.2-linux-amd64, and this problem always exist.

And I test this data with the most new stable Release: 5.8.1, and this problem have been solved. And I want to know why?

5.8.1-pro
5.8.1-pro577×404 37.2 KB

@issakomi @pieper @lassoan

1 Like
6

anyone can download and view the data.

I have looked, yes, it is Secondary Capture IOD.

And I want to know why?

S. the post above.

2 Likes