Hello,
I have a NIFTI file that I converted from the raw DICOMS, and when I checked the orientation with 3dinfo, this was the output:
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: -92.188 [R] -to- 98.312 [L] -step- 1.500 mm [128 voxels]
A-to-P extent: -132.969 [A] -to- 57.531 [P] -step- 1.500 mm [128 voxels]
I-to-S extent: -69.308 [I] -to- 55.192 [S] -step- 1.500 mm [ 84 voxels]
Number of time steps = 146 Time step = 2.20000s Origin = 0.00000s
– At sub-brick #0 ‘?’ datum type is short
– At sub-brick #1 ‘?’ datum type is short
– At sub-brick #2 ‘?’ datum type is short
** For info on all 146 sub-bricks, use ‘3dinfo -verb’ **
I then used 3drefit (3drefit -orient RAI data.nii.gz), but when I checked the orientation again with 3dinfo, the output was the same:
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: -92.188 [R] -to- 98.312 [L] -step- 1.500 mm [128 voxels]
A-to-P extent: -132.969 [A] -to- 57.531 [P] -step- 1.500 mm [128 voxels]
I-to-S extent: -69.308 [I] -to- 55.192 [S] -step- 1.500 mm [ 84 voxels]
Number of time steps = 146 Time step = 2.20000s Origin = 0.00000s
– At sub-brick #0 ‘?’ datum type is short: 0 to 2327
– At sub-brick #1 ‘?’ datum type is short: 0 to 2264
– At sub-brick #2 ‘?’ datum type is short: 0 to 2297
** For info on all 146 sub-bricks, use ‘3dinfo -verb’ **
Is there something wrong with the way I’m using 3drefit, or is there a different way to check the orientation?