HI - normally this happens when you run out of RAM or swap space -
but you only have a small number of subjects so I'd be surprised if
this is it. Check your filtered_func_data and var_filtered_func_data
inside the *.gfeat/*.feat higher-level directories, as movie loops
(etc) in FSLView to check that the input data is ok....
Cheers, Steve.
On 17 Apr 2007, at 13:34, Julius Fridriksson wrote:
> Good afternoon - I am running a higher level FEAT analysis (within
> group
> t-test) for a dataset including a group of stroke patients. All data
> have been co-registered in standard space (using cost functions and
> "updatefeatreg . -gifs", etc.). I keep running into a problem with
> this
> analysis (see error below):
>
> /usr/local/fsl/bin/feat_model design
>
> cat ../design.lcon | awk '{ print }' > design.lcon
>
> /usr/local/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 --fc=design.fts --ols --nj=10000
> --bi=500 --se=1 --fm --zlt=100000 --zut=100000
> Log directory is: stats
> Setting up:
> flame(25400) malloc: *** vm_allocate(size=1559744512) failed (error
> code=3)
> flame(25400) malloc: *** error: can't allocate region
> flame(25400) malloc: *** set a breakpoint in szone_error to debug
> terminate called after throwing an instance of 'std::bad_alloc'
> what(): St9bad_alloc
>
> echo 6 > stats/dof
>
> /bin/rm -f stats/zem* stats/zols* stats/mask*
> Rendering using zmin=2.3 zmax=8
>
>
> If anyone can give any insight into this problem, I would be much
> obliged. Thanks very much - Julius
------------------------------------------------------------------------
---
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director, Oxford University FMRIB Centre
FMRIB, JR Hospital, Headington, Oxford OX3 9DU, UK
+44 (0) 1865 222726 (fax 222717)
[log in to unmask] http://www.fmrib.ox.ac.uk/~steve
------------------------------------------------------------------------
---
|