Re: out of memory or dimension too large for Octave's index type

[Nicholas Jankowski]

On Tue, Jun 17, 2014 at 9:43 AM, dkeck <address@hidden> wrote:
> I am using glpk to solve an optimization problem of the form 'Ax<=b'.
> A submatrix of 'A' with size 5280 x 4608 fails to be built with "out of
> memory or dimension too large for Octave's index type"-error. These are
> 24,330,240 elements which are far below the 2e9 element border
> (http://octave.1599824.n4.nabble.com/error-memory-exhausted-or-requested-size-too-large-for-range-of-Octave-s-index-type-td3357172.html).
>
> The complete size of A will be 7398 x 4608 in the current scenario. And
> should also work fine:
> http://www.gnu.org/software/octave/doc/interpreter/Compiling-Octave-with-64_002dbit-Indexing.html
>
> But I could not test it yet.
>
> Does anybody have an idea what could cause the "out of memory"-error here?
>
> Regards,
> Daniel

Physical limits: what version of Octave? 32 or 64bit? what are your
machine's memory specs?

Operation limits: what else is in memory when you're building A? how
are you building A? have you preallocated for the final array size, or
are you forcing duplicate copies? Safe to assume that A is an double
precision array?