You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Converting a dicom directory containing a single EPI series collected on a Philips scanner results in an incorrect value for the repetition time in the resulting nifti header.
Performing a basic fMRI analysis on both the dcmniix output volume (with TR=1.793548) AND a volume where I manually changed the TR to 2.000001 using nifti_tool. The results of the analysis were nonsensical with TR=1.793548 and showed strong activation in visual areas with TR=2.000001.
Output log
Output of step 2:
Chris Rorden's dcm2niiX version v1.0.20220720 (JP2:OpenJPEG) GCC13.2.0 x86-64 (64-bit Linux)
Found 5460 DICOM file(s)
Warning: Discrepancy between reported (2s) and estimated (1.79355s) repetition time (issue 560).
Warning: Images sorted by instance number [0020,0013](1..5460), but AcquisitionTime [0008,0032] suggests a different order (160423..160223)
Philips Scaling Values RS:RI:SS = 4.00757:0:0.0132383 (see PMC3998685)
Convert 5460 DICOM as example-dicom-functional/dicoms/dicoms_func_task-oneback_run-1_20140425155335_401 (80x80x35x156)
Conversion required 1.265110 seconds (1.265096 for core code).
This is a limitation of your DICOM images, not dcm2niix. dcm2niix assumes that DICOM headers are truthful, and is unable to resolve when different values are reported by RepetitionTime (0018,0080) versus both TriggerTime (0018,1060) and AcquisitionTime (0008,0032). When there is a discrepancy, dcm2niix generates a warning (referencing issue 560) and assumes the RepetitionTime is inaccurate, as it reflects the requested rather than acquired TR (e.g. it is known to be inaccurate for Philips data with prospect. motion corr.). I would check the provenance of the DICOM images (to see if an anonymization stage scrambled values) and work with the Philips clinical scientist associated with the center where the data were acquired to resolve this. For more details, see issue 560.
Describe the bug
Converting a dicom directory containing a single EPI series collected on a Philips scanner results in an incorrect value for the repetition time in the resulting nifti header.
Related to #560 and its fix.
To reproduce
git clone [email protected]:datalad/example-dicom-functional.git
dcm2niix example-dicom-functional/dicoms
nifti_tool -disp_hdr -infiles example-dicom-functional/dicoms/dicoms_func_task-oneback_run-1_20140425155335_401.nii
Expected behavior
The repetition in the output nifti header should be
2.000001
.I've confirmed that this is the correct value for TR via
1.793548
) AND a volume where I manually changed the TR to2.000001
usingnifti_tool
. The results of the analysis were nonsensical with TR=1.793548
and showed strong activation in visual areas with TR=2.000001
.Output log
Output of step 2:
Output of step 3:
Version
dcm2niiX version v1.0.20220720 (JP2:OpenJPEG) GCC13.2.0 x86-64 (64-bit Linux)
Troubleshooting
Does the latest commit on the development branch resolve your issue?
I compiled from a fresh git clone and it does not resolve the issue.
The text was updated successfully, but these errors were encountered: