Hi,
Thanks for the help Matt and Mark. I think that some of the volumes
of dewarp were corrupted (some of them probably weren't written due
to the space issue). Rerunning epidewarp.fsl after having cleared the
space issue and then going from there worked perfectly.
Best,
Jeremy
On May 8, 2009, at 12:26 PM, Mark Jenkinson wrote:
> Hi,
>
> Those errors definitely indicate corrupt image files.
> I would run things again from the beginning if you are
> still seeing these errors.
>
> All the best,
> Mark
>
> On 8 May 2009, at 17:21, Jeremy Young wrote:
>
>>> Hello,
>>>
>>> Actually, after clearing up space and running again, I am getting
>>> the same error. Should I try running epidewarp.fsl again?
>>>
>>> Jeremy
>>>
>>>
>>> On May 8, 2009, at 10:02 AM, Jeremy Young wrote:
>>>
>>>> Hello,
>>>>
>>>> I forgot to include that. When I try to open dewarped it is fine.
>>>>
>>>> I figured out what was wrong just now though: I ran out of space
>>>> on the hard drive I was using.
>>>>
>>>> Jeremy
>>>>
>>>>
>>>> On May 7, 2009, at 4:24 PM, Matt Glasser wrote:
>>>>
>>>>> What happens if you open dewarped in FSLView? Do you get the
>>>>> same error?
>>>>> If so, I am afraid that file is corrupted.
>>>>>
>>>>> Peace,
>>>>>
>>>>> Matt.
>>>>>
>>>>> -----Original Message-----
>>>>> From: FSL - FMRIB's Software Library
>>>>> [mailto:[log in to unmask]] On Behalf
>>>>> Of Jeremy Young
>>>>> Sent: Thursday, May 07, 2009 1:18 PM
>>>>> To: [log in to unmask]
>>>>> Subject: [FSL] eddy correct error
>>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to eddy correct an output from epidewarp.fsl. This
>>>>> has worked
>>>>> for all my other subjects, except for the curret one. Here is
>>>>> my command
>>>>> and the error message:
>>>>> eddy_correct dewarped.nii data 0
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 2306840
>>>>> number missing = 1625320 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> ++ WARNING: nifti_read_buffer(dewarped.nii.gz):
>>>>> data bytes needed = 3932160
>>>>> data bytes input = 0
>>>>> number missing = 3932160 (set to 0)
>>>>> etc.
>>>>>
>>>>> What does this mean? Would a simple restart fix this or is
>>>>> there something
>>>>> else that's wrong?
>>>>>
>>>>> Thanks!
>>>>> Jeremy
>>>>>
>>>>>
>>>>
>>>
>>
>
>
|