Hi Matt,
I was under the impression that our tools were fine with
normal nifti extensions, as our fundamental nifti library is
the sourceforge c++ library which I believe copes fine
with well formed extensions. So can you upload the file please?
All the best,
Mark
On 19 Apr 2010, at 18:27, Matt Glasser wrote:
> Hi Mark,
>
> Caret is putting an extension in the file. fslstats -R gives 0.000000
> 74409981039121866167130168540266496.000000 on a file that contains
> only 0s
> and 1s (an ROI file), so I am assuming it is not okay either. When
> I remove
> the extension from the file then FSLView and fslstats work normally.
>
> Thanks,
>
> Matt.
>
> -----Original Message-----
> From: FSL - FMRIB's Software Library [mailto:[log in to unmask]] On
> Behalf
> Of Mark Jenkinson
> Sent: Monday, April 19, 2010 12:06 PM
> To: [log in to unmask]
> Subject: Re: [FSL] FSLView (and perhaps other FSL tools) do not
> respect
> vox_offset
>
> Hi,
>
> Are you using an extension, or just modifying the vox_offset?
>
> Can you also test some command line programs (e.g. fslhd, fslstats) to
> see if they are OK or not with your files.
>
> All the best,
> Mark
>
>
> On 19 Apr 2010, at 18:01, Matt Glasser wrote:
>
>> Hi,
>>
>> I have noticed that FSLView (and perhaps other FSL tools) do not
>> respect vox_offesets different from 352 bytes. This results in
>> loading files that are misaligned with garbage in the first few rows
>> of the matrix. Supporting different values of vox_offset would help
>> make FSL more interoperable with other softwares like Caret that use
>> this feature of
> NIFTI:http://nifti.nimh.nih.gov/nifti-1/documentation/faq#Q21
>> I am aware it is possible to strip out the header extension to get
>> files to load with FSL, though.
>>
>> Thanks,
>>
>> Matt.
>
|