[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: out of memory or dimension too large for Octave's index type
From: |
dkeck |
Subject: |
Re: out of memory or dimension too large for Octave's index type |
Date: |
Tue, 17 Jun 2014 07:22:12 -0700 (PDT) |
Octave 3.8.0 32-bit.
4GB RAM of which 3,25 are visible to the OS (WinXP 32bit) of which are 60%
in use before building A. So 1.3 GB of free space for A.
There are only temporary variables in the workspace visible while building
A.
A_final=[A_1;A_2;...] where A_INT are preallocated with zeros but A_final is
not preallocated but simply build as shown here.
What does "are you forcing duplicate copies" mean in this respect?
Yes, 'A' should be a double precision array since I did not modify any A_INT
while preallocating.
--
View this message in context:
http://octave.1599824.n4.nabble.com/out-of-memory-or-dimension-too-large-for-Octave-s-index-type-tp4664823p4664826.html
Sent from the Octave - General mailing list archive at Nabble.com.
- out of memory or dimension too large for Octave's index type, dkeck, 2014/06/17
- Re: out of memory or dimension too large for Octave's index type, Nicholas Jankowski, 2014/06/17
- Re: out of memory or dimension too large for Octave's index type,
dkeck <=
- Re: out of memory or dimension too large for Octave's index type, Nicholas Jankowski, 2014/06/17
- Re: out of memory or dimension too large for Octave's index type, dkeck, 2014/06/17
- Re: out of memory or dimension too large for Octave's index type, Nicholas Jankowski, 2014/06/17
- Re: out of memory or dimension too large for Octave's index type, dkeck, 2014/06/17
- Re: out of memory or dimension too large for Octave's index type, dkeck, 2014/06/26
- Re: out of memory or dimension too large for Octave's index type, Dmitri A. Sergatskov, 2014/06/26
- Re: out of memory or dimension too large for Octave's index type, Tatsuro MATSUOKA, 2014/06/27
- Re: out of memory or dimension too large for Octave's index type, dkeck, 2014/06/27
- Re: out of memory or dimension too large for Octave's index type, Philip Nienhuis, 2014/06/27
- Re: out of memory or dimension too large for Octave's index type, dkeck, 2014/06/28