[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: invalid range
From: |
Ben Abbott |
Subject: |
Re: invalid range |
Date: |
Mon, 01 Jul 2013 22:25:59 +0800 |
On Jul 1, 2013, at 10:20 PM, asha g wrote:
> You'll need to build octave, and include the option "--enable-64" when you
> run configure.
>
> Before doing that, do have you enough RAM for a double vector of length =
> 15.36G? You'll need 122.88 GBytes of RAM just for your vector.
>
>
> This is the RAM I have : I don't understand if that is enough. And if so,
> not sure how octave is built.
>
> total used free shared buffers cached
> Mem: 3022 1539 1482 0 173 728
> -/+ buffers/cache: 637 2384
> Swap: 1951 0 1951
>
>
> Asha G
I think that indicates you have 3.022 GBytes of RAM. If you're just using
niter to count the number iterations, I suggest you try Michael's suggestion.
Ben
- invalid range, asha g, 2013/07/01
- Re: invalid range, Laurent Hoeltgen, 2013/07/01
- Re: invalid range, asha g, 2013/07/01
- Re: invalid range, Ben Abbott, 2013/07/01
- Re: invalid range, asha g, 2013/07/01
- Re: invalid range, Ben Abbott, 2013/07/01
- Re: invalid range, Michael Goffioul, 2013/07/01
- Re: invalid range, asha g, 2013/07/01
- Message not available
- Fw: invalid range, asha g, 2013/07/01
- Message not available
- Re: invalid range,
Ben Abbott <=