You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does the nibabel.nicom dicom wrapper support multi-frame dicoms with multiple volumes?
I have a dicom with frame index ordering: "Temporal Position Index", "Stack ID", "In Stack Position Number". Loading the dicom and attempting to access the image_shape attribute
Traceback (most recent call last):
File "/home/akuurstr/.config/JetBrains/PyCharm2024.2/scratches/heudiconv_bruker_dicom_conversion.py", line 65, in <module>
mw.image_shape
File "/usr/lib/python3.10/functools.py", line 981, in __get__
val = self.func(instance)
File "/virtualization/python_virtualenvs/heudiconv/lib/python3.10/site-packages/nibabel/nicom/dicomwrappers.py", line 770, in image_shape
raise WrapperError('Non-singular index precedes the slice index')
nibabel.nicom.dicomwrappers.WrapperError: Non-singular index precedes the slice index
It seems MultiframeWrapper wants the stack position number to be the slowest changing index.
The text was updated successfully, but these errors were encountered:
AlanKuurstra
changed the title
nicom MultiframeWrapper fails to return image_shape attribute with multi-volume data
nicom MultiframeWrapper fails to return image_shape attribute with multi-volume mri data
Nov 21, 2024
The code currently assumes we don't need to reorder the DimensionIndexValues, mostly out of expediency and lack of a clear need. Your dataset appears to show that we do need to check for and allow this. Can you share the dataset?
Does the nibabel.nicom dicom wrapper support multi-frame dicoms with multiple volumes?
I have a dicom with frame index ordering: "Temporal Position Index", "Stack ID", "In Stack Position Number". Loading the dicom and attempting to access the image_shape attribute
fails with error:
It seems MultiframeWrapper wants the stack position number to be the slowest changing index.
The text was updated successfully, but these errors were encountered: