Hi - you can just run "top" in a terminal to see if flame is still
running. It probably is - it can take quite a while to run, as it uses
MCMC to get the best possible estimates of group-level activation (simpler
estimators are not sufficient because of the low degrees of freedom).
If top shows that flame is not running then the most likely thing is that
it had stopped because you ran out of swap space.
thanks, Steve.
On Mon, 28 Apr 2003, Darren Schreiber wrote:
> I started my second level analysis running this morning and it has been
> going for about 16 hours. It hasn't updated for about 12 hours though
> and I am wondering if it has frozen.
>
> Two questions -- 1) is it frozen? 2) can some kind of
> counter/clock/time estimator be added to FSL?
>
> Surely, there is plenty of data about FSL's time performance under
> various conditions. I would imagine it not to be too difficult to give
> the user an estimate of time and a progress report.
>
> Darren
>
>
> Here's the last few lines of output:
>
>
>
>
> ln -s ../mask.hdr mask.hdr
>
> ln -s ../mask.img mask.img
>
> /bin/rm -f filtered_func_data.hdr filtered_func_data.img
>
> ln -s ../cope1.hdr filtered_func_data.hdr
>
> ln -s ../cope1.img filtered_func_data.img
>
> /bin/rm -f var_filtered_func_data.hdr var_filtered_func_data.img
>
> ln -s ../varcope1.hdr var_filtered_func_data.hdr
>
> ln -s ../varcope1.img var_filtered_func_data.img
>
> /usr/local/bin/fsl/bin/flame --cope=filtered_func_data
> --vc=var_filtered_func_data --mask=mask --ld=stats --dm=design.mat
> --cs=design.grp --tc=design.con --zt=1.955 --fc=design.fts
>
Stephen M. Smith MA DPhil CEng MIEE
Associate Director, FMRIB and Analysis Research Coordinator
Oxford University Centre for Functional MRI of the Brain
John Radcliffe Hospital, Headington, Oxford OX3 9DU, UK
+44 (0) 1865 222726 (fax 222717)
[log in to unmask] http://www.fmrib.ox.ac.uk/~steve
|