Hi,
Thanks for the upload - I'm wondering if the problem is the esize,ecode
numbers ( the first 8 bytes , in the unzipped file, after the 001 0 0 0
indicating an extension is present )?
The file currently has:
30 03 00 00 ea 03 00 00
which gives an invalid ecode error - I think changing this to:
30 03 00 00 06 00 00 00
should solve the problem.
Many Regards
Matthew
>
> thanks,
>
> Brandon
>
> On Fri, 8 Jan 2010 13:43:08 -0000, Matthew Webster
> <[log in to unmask]>
> wrote:
>
>>Hi,
>> Can you confirm that you have both vox_offset and num_exts set
>>appropriately in your NIFTI file?
>>Many Regards
>>Matthew
>>> Matt, thanks... I'll have the latest version of FSLView installed, but I
>>> think the problem is a bit more subtle. FSLView handles the NIfTI
test
>>> data
>>> set from http://nifti.nimh.nih.gov/nifti-1/data (SIRP + XML), but when I
>>> add
>>> an extension to this file, or create a new NIfTI data set with an
extension,
>>> FSLView ignores the vox_offset and reads all bytes after the 352. Thing
>>> is,
>>> MRIcroN reads in my modified files just fine. I'm wondering if
FSLView
>>> uses
>>> some different methods to deal with extensions.
>>> cheers...
>>> Brandon
>>> On Thu, 7 Jan 2010 12:16:00 -0000, Matthew Webster
>>> <[log in to unmask]>
>>> wrote:
>>>>Hi,
>>>> It looks like you're using an older version of fslview - if you
>>>> install
>>>>the latest version of FSL you should be able to view NIFTI files with
extensions normally.
>>>>Many Regards
>>>>Matthew
>>>>> Brandon
>>>>> On Tue, 8 Dec 2009 16:23:38 +0000, Matthew Webster
>>>>> <[log in to unmask]>
>>>>> wrote:
>>>>>>Hi,
>>>>>> Could you let me know what FSLview version you are using?
>>>>>>Many Regards
>>>>>>Matthew
>>>>>>> I'd like to re-visit this post.
>>>>>>> Can anyone help me with learning what FSLview needs to properly view
>>>>>>> a NIfTI
>>>>>>> object with an extension?
>>>>>>> thanks,
>>>>>>> Brandon Whitcher
>
>
|