Hello,

I have functional MRI scans acquired using Magnetom Cima.X scanner for resting state and task. I have used dcm2niix version v1.0.20220720. A warning stating that the slice timing appears corrupted comes up. When we look into the created .json file, the slice timing values are written as -0.001. 

Along with this, there is another warning which is "Warning: Assuming mosaics saved in reverse order due to 'sSliceArray.ucImageNumb'"

We have tried using  dcm2niix v1.0.20241211. It doesnot give any warnings. But the slice timing is not written in the created .json file.

Could you please help with this.

Thanks.

1. What version of Siemens software are you using (XA30, XA60, XA61)?
2. Obviously, releases of dcm2niix that predate XA60 will not support the private tags from that version. You will want to use the latest stable version (v1.0.20241211):
  https://github.com/rordenlab/dcm2niix/re...
3. You can confirm that the latest stable version of dcm2niix extracts slice times from both Siemens Product as well as CMRR research sequences by converting the validation dataset:
  https://github.com/neurolabusc/dcm_qa_xa...
4. If this still fails, upload one of the JSON files created by dcm2niix when it converts an image.

The software version is "syngo MR XA61".

Great. The validation datasets demonstrate that the latest stable release extracts slice times from a CimaX running XA61 for both the product and CMRR research sequences:
  https://github.com/neurolabusc/dcm_qa_xa...
Therefore, if you do not have slice times, my first guess is that critical DICOM tags were stripped from your dataset prior to dcm2niix (persumably from an anonymization stage). You can test this by downloading images directly from the scanner console to a USB device, without having a PACS manipulate the images. If you still have an error, upload the JSON that dcm2niix creates. This is also a great opportunity to work with the Siemens Research Collaboration Manager associated with your center.