Hi,

Yes, this is absolutely fine and we would recommend it (though it is much more common that the images are already oriented in the standard orientation, but this command does not hurt as in that case it simply does nothing to the data).

All the best,

Mark

On 3 Jun 2017, at 12:10, Ramesh Babu <[log in to unmask]> wrote:

Dear Mark,

I have a question? Can I do reorientation of fmri by using the same script used for T1 image? fslreorient2std fmri.nii fmri.nii.gz.

Is it suggested to do reorientation for fmri?

Thanks

Ramesh

On Sat, Jun 3, 2017 at 9:26 AM, Ramesh Babu <[log in to unmask]> wrote:

Thank you Mark

On Fri, Jun 2, 2017 at 12:54 PM, Mark Jenkinson <[log in to unmask]> wrote:

Hi,

It is fine to continue with this data, as no information has been lost.  The output of almost all processing steps with use FLOAT32 for storage, so this is totally normal.

All the best,

Mark

On 2 Jun 2017, at 05:55, Ramesh Babu <[log in to unmask]> wrote:

Dear Experts,

To reorient my data to standard space, I used fslreorient2std grp110_t1.nii grp110_t1.nii.gz

After reorientation data type is changed, which I have highlighted in the output of fslinfo. And data size also doubled (22.9 to 45.9 MB). Can I continue with this data type or should I change it? If I have to change data type, how to change the data type?

$ fslinfo grp110_t1.nii
data_type      INT16
dim1           256
dim2           256
dim3           175
dim4           1
datatype       4
pixdim1        1.000000
pixdim2        1.000000
pixdim3        0.999996
pixdim4        0.007554
cal_max        0.0000
cal_min        0.0000
file_type      NIFTI-1+


$ fslinfo grp110_t1.nii
data_type      FLOAT32
dim1           175
dim2           256
dim3           256
dim4           1
datatype       16
pixdim1        0.999996
pixdim2        1.000000
pixdim3        1.000000
pixdim4        0.007554
cal_max        0.0000
cal_min        0.0000
file_type      NIFTI-1+

Thanks

Ramesh