Ok - so a few things going on... The dataset has 45 slices and 200 TRs, with a TR of 2.5s. So the test45.1D file you uploaded has the correct number of slices but is just in an ascending format (seqplus). The test.1D file has far too much data in it for what is represented in the dataset. It also looks to be ascending (instead of alt+z) and just repeated over and over again.

Since you said in the first post that your data was in alt+z/altplus, I ran 3dTcat on it with the -tpattern option I get the corrected dataset. Details below!

3dTcat -prefix test -tpattern altplus S014.rs.nii

And now to check the slice timing in the file:

3dinfo -VERB test+orig.
++ 3dinfo: AFNI version=AFNI_21.1.20 (Jun 28 2021) [64-bit]

Dataset File:    test+orig
Identifier Code: AFN_YduHKs1OxYiWsJukmYMxwg  Creation Date: Thu Jul  8 11:18:30 2021
Template Space:  ORIG
Dataset Type:    Echo Planar (-epan)
Byte Order:      LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode:    BRIK
Storage Space:   115,200,000 (115 million) bytes
Geometry String: "MATRIX(2.994091,-0.131374,-0.134763,-114.1122,-0.117991,-2.983872,0.287379,105.7399,0.146623,0.281513,2.983162,-35.87391):80,80,45"
Data Axes Tilt:  Oblique (6.073 deg. from plumb)
Data Axes Approximate Orientation:
  first  (x) = Right-to-Left
  second (y) = Posterior-to-Anterior
  third  (z) = Inferior-to-Superior   [-orient RPI]
R-to-L extent:  -114.112 [R] -to-   122.888 [L] -step-     3.000 mm [ 80 voxels]
A-to-P extent:  -131.260 [A] -to-   105.740 [P] -step-     3.000 mm [ 80 voxels]
I-to-S extent:   -35.874  -to-    96.126 [S] -step-     3.000 mm [ 45 voxels]
R-to-L center:     4.388 [L]
A-to-P center:   -12.760 [A]
I-to-S center:    30.126 [S]
Number of time steps = 200  Time step = 2.50000s  Origin = 0.00000s  Number time-offset slices = 45  Thickness = 0.000
Time-offsets per slice: 0.000 1.278 0.056 1.333 0.111 1.389 0.167 1.444 0.222 1.500 0.278 1.556 0.333 1.611 0.389 1.667 0.444 1.722 0.500 1.778 0.556 1.833 0.611 1.889 0.667 1.944 0.722 2.000 0.778 2.056 0.833 2.111 0.889 2.167 0.944 2.222 1.000 2.278 1.056 2.333 1.111 2.389 1.167 2.444 1.222
. . .

Let me know if you can't replicate this process! You can easily convert the AFNI dataset back to NIFTI using 3dcopy.



Edited 1 time(s). Last edit at 07/08/2021 11:52AM by Peter Molfese.