In general, it is a good idea to make sure you have the latest release of dcm2niix (v1.0.20181125), but this is especially crucial for the Siemens Vida, as it introduces a completely new interpretation of Siemens DICOM (the XA10 format), that is completely different from prior generations. You can get the latest dcm2niix from here
https://github.com/rordenlab/dcm2niix/releases
or if you prefer a drag-and drop interface:
https://github.com/rordenlab/MRIcroGL12/releases
There are a couple of specific things to be aware of with a Vida:
a.) The XA10 format no longer includes the CSA header. This means that the BIDS file generated by dcm2niix will be much more sparse than other Siemens systems. This is not an issue with dcm2niix, but reflects the spartan nature of XA10. I would strongly suggest that you export a PDF for your protocol from the scanner, as the DICOMs do not include details like dwell time, etc.
b.) In the past, Siemens users were advised to save EPI data as mosaic format, as these were saved faster and tended to use less disk space. In contrast, the mosaic format should NEVER be used on a Vida. The Vida mosaics do not store slice orientation, dwi data or many other parameters required for analyses.
c.) The Siemens console provides options to de-identify your data. It is crucial you do not select any form of Siemens de-identification. Even the basic level strips out many parameters required for analyses. If you want to anonymize your data, you should do it later with a separate tool (e.g. gdcmanon).
These are not limitations of dcm2niix that can be remedied by future versions, they are core attributes of the XA10 data. For more details visit
https://github.com/rordenlab/dcm2niix/issues/236
########################################################################
To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1
|