I have a problem loading some DICOM images recorded as slices of the coronal plane where the axial images show up distorted.
Let me give some more information. I have MRI scans of the femur with two different sequences captured at same time (no participant movement) with a SIEMENS machine:
axial scans of the lower legs with:
so, voxel size is 0.989 (med/lat) x 1 (sup(/inf) x 0.989mm (ant/post)
coronal scans of the femur with:
so, voxel size of this volume is 0.92 (med/lat) x 0.92 (sup(/inf) x 0.9mm (ant/post)
Both DICOM series load to Slicer and I can view images in all 3 planes, so far so good!
However, the axial images in the coronal scans (sequence 2) are distorted and I cannot figure out why and how to fix it.
Images below show the axial plane approximately at the same height (femoral head). In sequence 1, the femoral head appears as a circle, that seems to be correct.
In sequence 2, the femoral head is distorted an shows as an ellipse. It appears that the anterior/posterior axis is shrinked or something like that.
I have some more coronal scans of femurs and it seems to be the case in all of them, i.e. femoral head is not a sphere. Unfortunately, I do not have the other sequence to prove that something is wrong.
Does anyone has an idea what could case the problem here and how I can fix this? Is this a common problem with DICOM files from SIEMENS?
Thank you in advance,
A couple things to consider: make sure you load the data via the DICOM module and pay attention to any warnings during the load process.
Also you should be aware that SliceThickness is not the same as the out of plane spacing. That is you can have thick slices that are close together or thin slices that are far apart. For volume reconstruction the out of plane spacing is determined by the differences between Image Position Patient in the series. So if you manually adjusted the spacing based on the slice thickness it could explain the distortion.
It can also be the case that slices are acquired at irregular intervals, meaning they don’t form a regular volume. In this case Slicer will create a nonlinear transform that in most cases will put the slices back into a regular volume (you can harden that transform if you want to resample the image data into the regular spacing).
Is there any chance you can share an anonymized example that demonstrates this issue? We take geometric accuracy very seriously. Whether it’s a problem with Slicer or the Siemens data we’d like to get to the bottom of it.
thank you for the immediate reply.
No warnings appear when I load sequence 2 via the dicom module. When I load sequence 1, a warning appears, but I am pretty sure that this sequence is loaded correct because it shows the anatomically correct representation of the femoral head as a sphere.
I did not consider that SliceThickness and out of plane spacing can differ, thank you for pointing that out. However, I did not change any of the values manually, therefore, I guess this is not the problem.
When importing sequence 2, no transform is created by Slicer, I guess it is forms a regular volume.
Of course, I can share those anonymized DICOM files to you, I’ll upload them and send you a link in a private message because they should not be published.
I just had a call with the radiologist and she says that in such big scans (wide field of view) the parts on the edges are always distorted. Therefore, it could be, that this is not really a problem with the DICOM images but just with the scanning procedure. If that is really the case, do you think it is possible to create a non-rigid transform to “correct” the coronal scans? I have two participants with axial and coronal scans which could be used to find the appropriate transform for all other coronal scans (same scanner, same procedure). Is there any type of transform (or module) which you could recommend for this case?
Hi Willi -
Thanks for sharing the anonymized data though through a private message. I looked through the coronal acquisition dicom geometry and it appears to be loading correctly, so I tend to agree with the hypothesis that there is distortion in the scan itself. It’s possible you could correct for this with image-based registration. Let us know if you find out more.