Operating system: MAC OS
Slicer version: Slicer 4.11.20200930 r29402 / 002be18
Expected behavior: read a dicom in the windows (axial, coronal, sagittal)
Actual behavior: it doesn’t work, even if my dicom is correct.
Is it a bug on mac or do i do something wrong ?
I try the same dicom on slicer on windows and it works well.
I try others dicom on mac and I have the same dysfunction.
The screenshots show very sparse volumes (e.g., 3 slices very far from each other). For volumes that do not appear as you expect, could you go to Volumes module and take a screenshot of the “Volume information” section?
Did you get any warning while loading the volumes into the scene?
An imaging study often contains various reconstructions for various purposes. In general, you can ignore those that are not useful for you. However, if you expect to find complete volumes and instead you find incomplete/sparse volumes then check if your data set is complete (you have all the image slices). Unfortunately, most commonly used DICOM file formats contain each image slice in a separate file and there is no way to tell if a file is missing because it was not acquired or it was just lost while you were copying files.
Thank you for your answer.
Here is the requested screenshot.
I don’t get any warning while the loading of the dicom.
And as i said, the same dicom on windows works, that’s why I think that the dicom is not the issue. I was able to do it a few months ago on mac with still the same dicom and now it’s impossible.
And I tried with other dicoms, and it’s the same problem.
Could you choose that “Active Volume” to be the same as the volume selected in the slice view and post that screenshot?
(currently, Active volume is “3: …” and the displayed volume in the slice view is "4: …)
This looks perfect then. This volume consists of two axial frames, far from each other, so that’s why it has so low resolution in the two non-axial views.
If you expect more frames in this series than just two then check your DICOM files. You might have lost or corrupted some files when you copied them over between different computers.
Thank you !!
I deleted all the corrupted dicoms, tried to recover my original dicom, and you are right !!
I feel like a fool, but I’m really glad you fixed this problem.
To learn from my mistakes, can you explain to me where do you find the gap between the frames? Is the “image spacing” that must be 0?
I’m still not very familiar with the 3D slicer, I’m trying to learn little by little, but I’m far from using it well.
Thank you very much for your responsive responses, whenever I find this extremely helpful!
Happy that you are there.
Most commonly used DICOM file format is still the one file per image slice. In this format, each DICOM file contains position and orientation of the image slice and there is no way to tell if there is a larger gap between certain slices because the image was acquired with varying spacing (e.g., to reduce dose) or a slice was acquired but lost along the way.
DICOM does not use image spacing to define acquisition geometry, as the spacing between slices may not be uniform and slices may not be even parallel.
Enhanced DICOM information objects solve most of these issues, but they are still very rarely used (although the standard was defined more than a decade ago).
All right, I understand a little better.
Thank you very much 
