[ADMB Users] memory allocation error

Ian Taylor - NOAA Federal ian.taylor at noaa.gov
Tue Aug 27 11:29:09 PDT 2013

Hi Mark,
I don't have any good ideas on how the change in operating would have
messed up your old model.

However, ADMB's default memory settings were improved last year with 100x
increases in GRADSTACK_BUFFER_SIZE and CMPDIF_BUFFER_SIZE. Therefore, your
model might work just fine if you simply delete that block of lines related
to memory and run with the defaults.

Since your model is monstrous, it may need adjustment, but the error
messages you get will hopefully be specific enough to tell you which
setting(s) to increase, rather than the uninformative allocation error that
you got.

On Tue, Aug 13, 2013 at 9:11 AM, dave fournier <davef at otter-rsch.com> wrote:

> I would run it in debug mode and find out the line where it crashes.
> Otherwise a common cause of this is that the program is getting a bad
> number somehow
> and doing something like this
>    dvector v(1,n);   // n contains garbage which is interpreted as a huge
> number.
> ______________________________**_________________
> Users mailing list
> Users at admb-project.org
> http://lists.admb-project.org/**mailman/listinfo/users<http://lists.admb-project.org/mailman/listinfo/users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.admb-project.org/pipermail/users/attachments/20130827/c781221c/attachment.html>

More information about the Users mailing list