Daniel Glen Wrote:
-------------------------------------------------------
> Do you see the same problem if you try to force
> the same geometry with "to3d -geomparent firstdset
> ..." ?
I tried
to3d -geomparent NIFTI -spgr -xFOV 29R-L -yFOV 29S-I -zFOV 29P-A -nofloatscan -prefix newBRIK 3D:0:0:128:128:128:XXX/XXX
The result is the same.
3dinfo -orient -d3 -nijk -o3 -space -prefix newBRIK
RSP 0.453125 -0.453125 -0.453125 2097152 -28.773439 28.773439 28.773439 ORIG
The real position is 28.7734375, which rounded to 28.773438, not 28.773439
I think this bug is reproducible for any binary file in to3d's conversion.