Hi Dan,
FSL5.0.9 will warn about files with a TR of 1, as this is often indicative of an input file where the TR was never set correctly. The difference between the FSL versions is that older versions of FEAT allowed a “manual” override of the TR in the GUI, while the newer version always respects the TR in the image header, but warns for unusual values. If a filtered_func file created with an older version of FEAT has a TR of 1, this is indicative of the original timeseries data having a TR 1, which propagated through to the analysis - it might be worth re-rerunning in this case.
The value in the header file to fix is pixdim4.
Hope this helps,
Kind Regards
Matthew
> On 1 Aug 2016, at 10:32, Daniel CM <[log in to unmask]> wrote:
>
> Hi Mathew,
>
> In FEAT, filtered_func_data created with Melodic and/or FEAT in v. 5.0.6 comes up with a false TR of 1 in 5.0.9. Is the only way to correct this, to edit each image manually, and was this a symptom of a greater problem in the earlier versions?
>
> Also, which header value does one change in the nifti file to correct the TR?
>
> Cheers,
> Dan
