Re: - exceeding 32-bit counting?

Hi Ashton-

Sorry, you're confusing two issues.  Making your grid double does absolutely nothing as far as GMT is concerned.  All grid are internally converted to float so this is just waste of CPU time and disk space.

As for 32/64: This pertains mostly to integer counters (if # of points exceed largest value an integer can hold than chaos ensues) and ability to allocate space > 2 Gb.  Sometimes 32-bit processes are limited to 2 or 4 Gb even though your system may have 16 Gb etc.
I note that even cellphones have 64-bit chips these days so if you are trying to tackle a 16 Gb grid with a 32-bit operating system then think again!

-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]