Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readImageDicomFileSeries doesn't read segmentation dicom correctly #991

Open
jadh4v opened this issue Nov 9, 2023 · 1 comment
Open
Assignees
Labels

Comments

@jadh4v
Copy link
Collaborator

jadh4v commented Nov 9, 2023

When using readImageDicomFileSeries for reading a multiframe dicom file of SOP class = 1.2.840.10008.5.1.4.1.1.66.4 which is Segmentation modality.
The file is read but with incorrect spacing and image dimensions. I suspect that it doesn't find the pixel spacing in the dicom tags (even though the info is present in the dicom tags), hence it defaults to spacing = [1, 1, 1] and also does not reconfigure the frames into fewer z-slices based on number of unique labels (for e.g. number of frames = number of labels * expected z-slices).

Since readImageDicomFileSeries uses gdcm as backend, this could be a fix for gdcm.

Test data: https://data.kitware.com/#user/61d87b684acac99f42cd366c/folder/654d0c3dfdc1508d8bec1baf
Expected image size: [512, 512, 134], spacing: [0.9765625, 0.9765625, 3]
Actual image size: [512, 512, 536], spacing: [1, 1, 1]

@jadh4v jadh4v added the bug label Nov 9, 2023
@thewtex
Copy link
Member

thewtex commented Dec 1, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants