Hi there,
generally speaking, it seems that you cannot have enough swap and RAM for
FSL. More specifically, I talked our IT people into giving me 1GB of RAM
and 5GB of swap on a SuSE 8.1/AthlonXP 1800+ machine. I observed a RAM
consumption of ca.1GB AND a swap usage of an additional 2GB during FILM -
but my 4D data file has only 170MB...! So there you are. Until you haven't
got adequate RAM and/or swap, it is nearly impossible to tell whether a
"file not found" error didn't result from a lack of memory. Took me some
time, too, to figure that out.
Best wishes,
Cornelius
On Fri, 08 Oct 2004 21:18:03 +0100, Axel Thielscher
<[log in to unmask]> wrote:
> Hi - I try to analyze an EP image series created with AFNI using the
> GLM-module of FSL. I used 3dAFNItoANALYZE provided by AFNI to transform
> the
> EP BRIK to an 4D-Analyze-File. The size of this file is either around
> 630 MB
> (voxel values stored as integer) or 1.3GB (voxel values stored as
> floating
> point) and it contains 1280 volumes of one session.
>
> The analysis with FEAT doesn't work with either of the two files. More
> specifically, the command
> /usr/local/fsl/bin/film_gls -rn stats -noest filtered_func_data
> design.mat
> 11.12 3201
> fails and is apparently unable to read to file.
>
> My computer: Red Hat Linux 9, Intel P-4, 1GB RAM, 2GB swap space
>
> Does this problem stem from insufficient swap space? The analysis with
> AFNI
> works fine, but I would be happy to use the more advanced features such
> as
> prewhitening etc. provided by FSL. How much memory do you recommend for
> input file sizes as quoted above? Can this failure be caused by a
> different
> problem?
>
> Thanks,
> Axel
>
--
Cornelius Werner
Institut fuer Medizin (IME)
AG Kognitive Neurologie
Forschungszentrum Juelich
52425 Juelich
Germany
Tel. +49-(0)2461-61-8609
|