Hi,

Do you have particularly high-resolution images?
It is possible that the combination of 17 hi-resolution
images might be beyond your 6GB.  If you get the
same error when running fslstats then that is a bad sign.
It is also pointless to try fslstats on your firstseg image
if it has not been converted to a single volume, since
it sounds like the boundary correction has failed.

If it is the case that you are running out of memory
then the possible solutions are to find a machine
with more memory, increase the swap on your
machine (which will be a slow solution), or do less
structures at a time.  For instance, just do groups
of structures that could overlap (as then the
boundary correction will deal better with the overlap);
something like a set of structures in the left
hemisphere only.  Anyway, this depends on whether
the problem is a lack of memory due to very
high-resolution images or not.

So let us know what your image resolution (and
number of voxels in each direction) are and we
can see if that is the problem.

All the best,
	Mark




On 9 Dec 2009, at 15:27, John wrote:

> Hi,
>
> I ran run_first_all. On reviewing the _all_fast_firstseg file in  
> fslview I
> have a multi-volume output file. A different volume for each segmented
> structure. The intensites for the structures are as they should be  
> and no
> boundary values are defined (as expected I believe). My problems are  
> thus:
>
> I believed (from the FIRST note online) that I would be left with a
> '_all_fast_firstseg' image which is only a single volume, ie lots of
> structures visible on one FSLview screen rather than a multi-volume  
> file. In
> the log file: first_post.e21131.1 the output: Image Exception :  
> #99 :: Out
> of memory: Aborted, was recorded.
>
> Additionally, when i tried to run fslstats '_all_fast_firstseg' -l  
> 16.5 -u
> 17.5 -V, i get the same error as recorded in the log file.
>
> I'm running FSL 4.1.4 on CentOS 5.3 with 6Gb ram.
>
> I think this problem may be similar to the previous posts but I  
> don't think
> a solution was recorded
>
> 026110 	2009-09-07 	18:30 	225 	Re: Out of memory Aborted FIRST‏  
> [ *.logs]
> ls -l
> 026093 	2009-09-05 	11:18 	66 	Re: Image Exception : #99 :: Out of  
> memory
> Aborted FIRST
> 026078 	2009-09-04 	18:50 	163 	Image Exception : #99 :: Out of memory
> Aborted FIRST
>
>
> Any help would be great, many thanks
> John McLean
>