Hi Rutger,
The only 2 issues I know about with linux crashing are that in the past we
saw programs crashing because the linux machine had been hacked; the other
possibility is that running with certain NVidia drivers can cause programs
(in general) to crash. It might be worth trying on a different machine.
To "resume", temporarily edit fsl/tcl/feat.tcl and change the line
for { set slice 0 } { $slice < $DIMZ } { incr slice 1 } {
to start at (eg) 38. Then start FEAT normally, and it will create a new
group-FEAT directory; once it has started running the stats (at 38) copy
in all the stats directories from the previous run (which you can then
delete). Hopefully this should work ok.
Thanks, Steve.
On Tue, 6 May 2003, Goekoop, R. wrote:
>
> Dear FSL community,
>
> For a complex study design which takes a few days of processing time, we use
> FEAT higher level analysis adapted to call FLAME separately for each slice,
> on a Linux-system. For some unknown reasons, the FEAT-process frequently
> interrupts without clues appearing in any of the logfiles. Until we fix that
> problem, would it be possible to have FEAT carry on with the higher-level
> analysis from where it left off (for example: from stats38 onward), instead
> of having to start all over again? Hope this is the case,
>
> Regards,
>
> Rutger Goekoop
>
> Drs. R. Goekoop, MD.
> Department of Neurology
> Vrije Universiteit Medical Centre
> P.O. Box 7057, 1007 MB
> Amsterdam, the Netherlands
> Phone: +31 20 444 0316
> E-mail: [log in to unmask] <mailto:[log in to unmask]>
>
>
>
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
|