This sounds like it might the "4-bytes missing" error - see "NIFTI
read error - update" in the archives. It might be worth running
fslcorrecthd on the file as a test...
Many Regards
Matthew
> Mark,
>
> I've uploaded an example EPI image (m014... - ref: 524174) of 10 for
> which fsl_motion_outliers fails to write the confound EV .txt file.
> I've compressed it for a quicker transfer, but I'm not compressing
> the files when running the command (incidentally, compressing the
> files doesn't overcome the problem).
>
> You should see that the file seem fine when examining the timeseries
> in FSLView. However, when I input the uploaded image into the
> fsl_motion_outliers command I get the following report:
>
> "WARNING: nifti read buffer (m014...)
> databytes needed = 5242588
> databytes input = 5242584
> databytes missing = 4 (set to 0)
> ...
> Found 17 outliers over 7.3336688
> ..."
>
> In contrast, when I input a colleague's image I get the following
> report:
>
> "...
> Found 17 outliers over 306639456.0000
> ..."
>
> I guess there must be something wrong with the image(s) I'm
> uploading inputing to the command, but they are simply excessive
> movers from a dataset successfully analysed using FEAT.
>
> Thanks for your time,
>
> Dan.
>
> On Oct 6, 2009, at 1:03 PM, Mark Jenkinson wrote:
>
>>> "nifti bufffer"
>
> Daniel Shaw M.Sc.
> PhD student
> Brain & Body Centre
> University of Nottingham
> University Park
> Nottingham
> NG7 2RD
>
>
>
>
> This message has been checked for viruses but the contents of an
> attachment may still contain software viruses, which could damage
> your computer system: you are advised to perform your own checks.
> Email communications with the University of Nottingham may be
> monitored as permitted by UK legislation.
>
|