I'm not an expert, but I have a feeling you might indeed be running into
a memory-related, 32-bit processing limit! You say avwmerge should
create a file < 10GB. I don't think any 32-bit program can access such a
large memory block (2 or 4 GB limit). I know in linux it's possible to
compile the kernel with up to 64GB memory allocation, but I think this
is a curiosity. I couldn't imagine a vanilla mac OS being able to do it
either, though I know even less about mac than I do about 32-bit
Perhaps some of the more experienced members on the list have a
suggestion about alternative analysis setups (which likely depends on
what exactly you're setting up).
Christopher Bailey <[log in to unmask]>
MSc (engineering physics & maths)
Center for Functionally Integrative Neuroscience
Aarhus University Hospital, Denmark
On Sat, 2004-08-21 at 17:33, Paige Scalf wrote:
> HI all,
> I know the RAM/SAWP issue has been addressed on this
> list before; I'm getting the "can't allocate region" messages even
> though I should have plenty of available swap.
> I'm trying to run flame on a set of 360 copes from lower level
> analysis. I'm using a dual G5 with one GB of RAM, and I have
> 70 GB free on the root drive. OS is some variant of 10.3. I think
> the G5 should be able to automatically allocate up to 64GB of
> swap, all of which should be available to it on my system.
> I'm getting the error message after FLAME calls avwmerge -T across
> the registered copes and varcopes. This should create a file of
> <10 GB.
> Any idea why I'm getting this error? Is this reflecting an upper
> limit on some FSL routine, or is there some memory
> allocation problem that I don't understand?
> Thanks for your help.