Hello, I am importing DICOM Dixon images and am getting inconsistent ordering of the image types. Slicer correctly identifies that there are 4 image types, but does not order them in a consistent way. Other software (e.g. Horos) consistently orders them. Dixon images involve 4 series, a water image (W), a fat image (F), and two raw images from which the water and fat images are derived, one referred to as the in-phase (IP) and the other referred to as the opposite-phase (OP).
Horos consistenly loads the water and fat pair first (in one series), then the OP series, then the IP series.
We have DICOM data from one patient imaging session where the whole lower half of the body was acquired in 4 slabs, each a Dixon set of 4 images. In Slicer, slab 1 loads as follows:
Image Type 1: IP
Image Type 2: OP
Image Type 3: F
Image Type 4: W
Slab 2 loads in the order OP-W-IP-F
Slab 3 loads in the order W-IP-F-OP
Slab 4 loads in the order OP-F-W-IP
These slabs were all acquired on the same scanner in the same imaging session, but somehow the Slicer ordering of Image Types for each one is unique!
My question therefore is how Slicer assigns the order, and whether there is a way I can enforce a consistent ordering for Dixon images. Alternatively, is there a way I can incorporate the image type into the name of the imported volume? For example, if instead of “Image Type 1” being appended to the node name, could “Image Type W” be appended? The DICOM Metadata browser shows the (0008,0008) ImageType field as “ DERIVED, PRIMARY, W, W, DERIVED” for the Water images (or “ DERIVED, PRIMARY, OP, OP, DERIVED” for the OP images, etc.).
Thanks for any insight/help you can provide!