Will fmriprep slice timing correction work for my multiband slice timing?

1

Hi all, I have the following slice timing for my multiband data :

[ 0, 0.0775, 0.1575, 0.2375, 0.315, 0.395, 0.475, 0.5525, 0.6325,
0.7125, 0.79, 0.87, 0.95, 1.0275, 1.1075, 1.1875, 1.265, 1.345,
1.425, 1.5025, 1.5825, 1.6625, 1.74, 1.82, 1.9, 0, 0.0775, 0.1575,
0.2375, 0.315, 0.395, 0.475, 0.5525, 0.6325, 0.7125, 0.79, 0.87,
0.95, 1.0275, 1.1075, 1.1875, 1.265, 1.345, 1.425, 1.5025, 1.5825,
1.6625, 1.74, 1.82, 1.9, 0, 0.0775, 0.1575, 0.2375, 0.315, 0.395,
0.475, 0.5525, 0.6325, 0.7125, 0.79, 0.87, 0.95, 1.0275, 1.1075,
1.1875, 1.265, 1.345, 1.425, 1.5025, 1.5825, 1.6625, 1.74, 1.82,
1.9 ]

Will fmriprep read this accurately for slice timing? I ask since it is ascending but it starts back from zero two other times.

Thanks!
Katrina

2

FMRIPREP uses AFNI’s 3dTshift to perform slice-timing correction. I’m not personally very familiar with the limits of STC, but if you’ve been able to use 3dTshift on such data in the past, I expect that it should work.

If not, please let us know, and we’ll try to fix it before the 1.0 release.

@ChrisGorgolewski may have more experience here.

1 Like
3

I don’t have much to add. It will run, it should not crash (if it does tell us!). Whether doing slice timing correction when TR is so short is a good idea is still an open question though.

PS To make sure the slice timing is defined correctly in your metadata you can use the BIDS validator.

4

Great, thanks so much for your thoughts!