Slice timing missing in the json file about dcm2niix HOT 2 CLOSED

This is a limitation of your images, not dcm2niix.

dcm2niix assumes that the DICOM files are truthful. However, the first volume of this multiband sequence reports the single band slice timing in the private slice timing tag (0021,1104). Therefore, the reported slice times do not occur within a single TR. This issue is similar to an issue with early versions of the CMRR multiband sequences from many years ago. I suggest you contact the team that created this sequence and have them create accurate DICOMs.

If you need the slice times, you can simply remove all the DICOM images from the first volume (you can use dcm2niix -r y /path/to/dicoms to rename images with the file name commencing with the instance number that can help you identify the first volume. Once the first volume is deleted, dcm2niix will create a JSON with the multi-band slice timing:

	"SliceTiming": [
		1.485,
		0,
		0.99,
		0.0825,
		1.0725,
		0.165,
		1.155,
		0.2475,
		1.2375,
		0.33,
		1.32,
		0.4125,
		1.4025,
		0.5775,
		1.5675,
		0.66,
		1.65,
		0.7425,
		1.7325,
		0.825,
		1.815,
		0.9075,
		1.8975,
		0.495,
		1.485,
		0,
		0.99,
		0.0825,
		1.0725,
		0.165,
		1.155,
		0.2475,
		1.2375,
		0.33,
		1.32,
		0.4125,
		1.4025,
		0.5775,
		1.5675,
		0.66,
		1.65,
		0.7425,
		1.7325,
		0.825,
		1.815,
		0.9075,
		1.8975,
		0.495,
		1.485,
		0,
		0.99,
		0.0825,
		1.0725,
		0.165,
		1.155,
		0.2475,
		1.2375,
		0.33,
		1.32,
		0.4125,
		1.4025,
		0.5775,
		1.5675,
		0.66,
		1.65,
		0.7425,
		1.7325,
		0.825,
		1.815,
		0.9075,
		1.8975,
		0.495	],

You could either copy this timing information to the JSON for the full series, or use just analyze the data without the first volume (if this is a task-based fMRI data, adjust event times by one TR).

from dcm2niix.

Thank you so much. Works for me

from dcm2niix.