Hello Justin,
Can you confirm if you are using FSL 5.0.9 or a previous version, as this bug should have been fixed in FSL 5.0.9.
Kind Regards
Matthew
> On 3 Apr 2017, at 15:52, Justin <[log in to unmask]> wrote:
>
> My test case:
>
> flirt -in test1.nii -ref test2.nii -omat test.mat
>
> cat test.mat
> 0x1.2af96e1ccb468p+0 -0x1.12c747a4369a4p-5 -0x1.1d2466b3d1ea7p-6 -0x1.181d7fcff3be4p+5
> 0x1.e191e99929de1p-5 0x1.06b7d5be033b2p+0 0x1.9bbf7d9b24057p-3 -0x1.c9adc08b34347p+3
> -0x1.44867f099974p-9 -0x1.42fb4812d50fap-2 0x1.32dd20e7ac9eap+0 0x1.065dafb6a3465p+5
> 0x0p+0 0x0p+0 0x0p+0 0x1p+0
>
> FSL was installed with: sudo apt-get install fsl
>
> flirt version: FLIRT version 6.0
>
> OS: Ubuntu 16.04
>
> Outputs appear to be written as hexadecimal which causes issues when I try to read the values.
|