Dear FMRIB,
I'm getting a peculiar result using avwmaths++ with a 4D NIfTI, where
the pixdims of the output are altered (see below). This *doesn't* seem
to be a problem when using avwmaths instead of avwmaths++
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% avwhd++ test.nii
...
dim0 4
dim1 91
dim2 109
dim3 91
dim4 40
dim5 1
dim6 1
dim7 1
vox_units mm
time_units s
datatype 16
...
pixdim0 0.0000000000
pixdim1 2.0000000000
pixdim2 2.0000000000
pixdim3 2.0000000000
pixdim4 1.0000000000
pixdim5 1.0000000000
pixdim6 1.0000000000
pixdim7 1.0000000000
...
qto_xyz:1 2.000000 0.000000 0.000000 0.000000
qto_xyz:2 0.000000 2.000000 0.000000 0.000000
qto_xyz:3 0.000000 0.000000 2.000000 0.000000
qto_xyz:4 0.000000 0.000000 0.000000 1.000000
...
sto_xyz:1 0.000000 0.000000 0.000000 0.000000
sto_xyz:2 0.000000 0.000000 0.000000 0.000000
sto_xyz:3 0.000000 0.000000 0.000000 0.000000
sto_xyz:4 0.000000 0.000000 0.000000 0.000000
% avwmaths++ test.nii -Tmean test_mean.nii
-Tmean
% avwhd++ test_mean.nii
...
dim0 3
dim1 91
dim2 109
dim3 91
dim4 1
dim5 1
dim6 1
dim7 1
vox_units mm
time_units s
datatype 16
...
pixdim0 0.0000000000
pixdim1 1.0000000000
pixdim2 1.0000000000
pixdim3 1.0000000000
pixdim4 1.0000000000
pixdim5 1.0000000000
pixdim6 1.0000000000
pixdim7 1.0000000000
...
qto_xyz:1 1.000000 0.000000 0.000000 0.000000
qto_xyz:2 0.000000 1.000000 0.000000 0.000000
qto_xyz:3 0.000000 0.000000 1.000000 0.000000
qto_xyz:4 0.000000 0.000000 0.000000 1.000000
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Thanks in advance,
Ged.
|