Re: - exceeding 32-bit counting?

Hi Paul,

Yea I didnt think converting the grid to an nd would do anything, but
knowing I'm running a 64 bit kernel, and a 64 bit grdview executable,
I started looking for anything.

Yup, I'm aware of the large memory issues - I'm ok with it (so is my
system......errr....usually).



On Wed, Feb 12, 2014 at 11:51 AM, Paul Wessel <[email protected]> wrote:
> For got to say that given your -J -E settings, regardless of what memory is required to just read your grid into memory, the implied r/g/b array for the image that is also allocated would be close to 8Gb of memory alone. [ 3 x (35.4088 * 1250) x (50 * 1250)].
> -p
>
> On Feb 12, 2014, at 6:08 AM, andrealphus <[email protected]> wrote:
>
>> I've seen a few posts regarding this error, but nothing that seemed to
>> relate....
>>
>> command;
>>
>> ...
>> grdimage $GRD $region -JX35.4088i/50i -C$CPT -E1250 -Q -V -K -O >> $psfile
>> ...
>>
>>
>> it fails at this grdimage call if the resoultion is set to anything
>> greater than 1000 (with the given media size, which is the same as the
>> JX size).
>>
>> The grid its calling ($GRD) is large (17 gb), and I originally thought
>> the issue was because it was a default .grd (format #18), which is 32
>> bit, yes?
>>
>> I reformatted this to a netcdf double 64 bit (format #19), via;
>>
>> grdreformat -V ARCTIC_40m_PS_75N_xyz.grd ARCTIC_40m_PS_75N_xyz_64b.nd=nd
>>
>> And tried the above grdimage call again......same error.
>>
>> Any idea?
>>
>> -ashton
>>
>> To unsubscribe, send the message "signoff gmt-help" to [email protected]
>
> To unsubscribe, send the message "signoff gmt-help" to [email protected]

To unsubscribe, send the message "signoff gmt-help" to [email protected]