Since many of the public datasets give slicetiming in milliseconds, I can imagine this has come up before, but I do not see it in the documentation. Doese fmriprep recognize this and convert, or are the results just wrong?
(presume bids validator is off)
The bids-standard specifies that slice timing should be given in seconds, and from what I can see fmriprep goes along with the spec and will not attempt to convert the times.
This is correct. The very likely result is that
3dTshift will error.
Perfect. Thanks for the clarification!