With regards to SliceTiming I have scanned agar phantom on GE MR750 (a.k.a. Discovery) running DV-24 using short fMRI sequence planned in 8 combinations:
| Code | SeqNum | ORDER | ACQUISITION | HEAD_TOP_SLICE | HEAD_BOTTOM_SLICE |
|------+--------+-------------+-------------+----------------+-------------------|
| s06 | 6 | Top-Down | Sequential | 1 | 44 |
| s07 | 7 | Bottom-Up | Sequential | 1 | 44 |
| s08 | 8 | Top-Down | Sequential | 44 | 1 |
| s09 | 9 | Bottom-Up | Sequential | 44 | 1 |
| s10 | 10 | Top-Down | Interleaved | 1 | 44 |
| s11 | 11 | Bottom-Up | Interleaved | 1 | 44 |
| s12 | 12 | Top-Down | Interleaved | 44 | 1 |
| s13 | 13 | Bottom-Up | Interleaved | 44 | 1 |
Unfotrunately TriggerTime was not saved with DICOMs but I have found FloatSlopRTIATimer (or RTIA_timer) to have something to do with SliceTiming.
I can share the DICOMS (224MB). (Or produce more if needed.) Detailed report can be found on https://github.com/nikadon/cc-dcm2bids-wrapper. At the bottom of the README file I have placed number of tables containing:
-
SeriesNumber, -
ImagesInAcquisition, -
InStackPositionNumber, -
InstanceNumber, -
SliceLocation, -
TriggerTime, FloatSlopRTIATimer
for each acquisition.
I am not sure about the reliability of the FloatSlopRTIATimer for SliceTiming estimation.(?)