Print

Print


OK, then update to the latest version (4.1.6) and this
should fix it.  The old version was known to take a long
time in some circumstances.

All the best,
	Mark


On 26 Aug 2010, at 15:05, McWhinney, Sean wrote:

> I'm running 4.1.3
> ________________________________________
> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf  
> Of Matthew Webster [[log in to unmask]]
> Sent: August-26-10 11:02 AM
> To: [log in to unmask]
> Subject: Re: [FSL] Featquery never finishes
>
> Hello,
>          cat $FSLDIR/etc/fslversion
>
> will give you the full FSL version number.
>
> Many Regards
>
> Matthew
>
>> Hi,
>>
>> Thanks for getting back to me. I'm running FSL 4.1 which appears to  
>> be the newest, and my structural images are 255x255x71 I believe.  
>> Is there a ballpark time I can expect invwarp to require?
>>
>> Sean
>> ________________________________________
>> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf  
>> Of Mark Jenkinson [[log in to unmask]]
>> Sent: August-26-10 10:55 AM
>> To: [log in to unmask]
>> Subject: Re: [FSL] Featquery never finishes
>>
>> Hi,
>>
>> Are you running the latest version of FSL?
>> The invwarp command used to take a long
>> time to run but should work more quickly now.
>> What resolution are your structural images?
>> That might have an impact too.
>>
>> All the best,
>>       Mark
>>
>>
>>
>> On 26 Aug 2010, at 14:30, Sean McWhinney wrote:
>>
>>> I'm quite new to fMRI analysis and so the data I'm currently working
>>> with is my first experience with FSL. Simply put, attempting to run
>>> Featquery on Feat directories with nonlinear registration seems to
>>> cause it never to finish. A featquery directory is created with
>>> report.log & html files, but the log file never gets farther than
>>> "Found nonlinear warp field... Starting warp field inversion...".
>>> Featquery never seems to progress beyond this point. Using 'top'
>>> from terminal indicates that the invwarp process is in fact running,
>>> and taking a large amount of CPU power, but it seems that this never
>>> finishes regardless of how much time I give it.
>>>
>>> Any thoughts would be greatly appreciated!
>>>
>>
>