Research data

NIfTI header slice timing map

Expand declared slice order into file-index ranks and relative offsets.

Your inputs

Start with an example

Your inputs stay in your browser.

Your result

Example result

How it works

Decode the spatial slice dimension and temporal unit bits. Expand the declared six-code acquisition sequence inside a meaningful start/end interval, invert it to file-index ranks and multiply by slice_duration. Preserve padded slices and unknown timing separately.

For seven slices, timed indices 1–5 and alternating increasing 2, acquisition order is 2,4,1,3,5. The file-index ranks are null,2,0,3,1,4,null; the endpoints are padding.

Limits

Extracted NIfTI-1 metadata only: 64 KiB JSON, native integer ranges, up to 32767 slice rows and an 8 MiB report. Require positive duration, a nonzero slice axis/code and 0 ≤ start < end < slice count for known timing. End 0 and one-slice intervals remain unknown under this explicit header policy; NiBabel applies different reader conveniences. Seconds, milliseconds and microseconds convert; unspecified units keep raw offsets, while spectral/reserved temporal units reject. No image loading, orientation, absolute acquisition time, multiband inference or slice-timing correction.