In GDDIAG, try setting the packing variable "GPACK" to "NONE". The
default, if "GPACK" is set to <blank> is to use "GRIB/16" packing. I
think you may have unconvered a bug in the packing process which is not
treating a grid whose points are all set equal to "RMISSD" properly.
Kevin Tyle, Systems Administrator **********************
Dept. of Atmospheric & Environmental Sciences ktyle@xxxxxxxxxxxxxxxx
University at Albany, ES-235 518-442-4578 (voice)
1400 Washington Avenue 518-442-5825 (fax)
Albany, NY 12222 **********************
On 10/08/2010 12:20 PM, Evan Lowery wrote:
I've found a possible bug (or user error) with GDDIAG and the MASK
grid function, but wanted to check with everyone here before sending
out an official support request.
Within a GEMPAK grid file (test.grd), I have a temperature field
(TEMPA) which needs to be masked to only show values between a certain
temperature range (>=80F). I run this process daily, and have never
had a problem up until this point. When NO temperatures in TEMPA are
>=80F, the MASK function generates an erroneously large number rather
than -9999.00 (RMISSD).
Using GDLIST (tempa.dat) I see that TEMPA:
MINIMUM AND MAXIMUM VALUES 1.03 60.00
Goal: only keep temperatures >=80F
Using GDLIST (tempb.dat) I see that TEMPB:
MINIMUM AND MAXIMUM
I would expect all TEMPB values to be -9999.00 (RMISSD) since no
temperatures are greater than 80F, but instead it blows up and returns
a very large value.
MASK Masking function MASK (S1, S2) = RMISSD IF S2 = RMISSD
= S1 otherwise
In this example TEMPA had no values >=80F, but my csh scripts are
constantly mining through temperature grids, and "usually" there are
Has anyone ever experienced this type of result? If yes, do you know
a work around to get the grid (TEMPB) with all values = -9999.00
(RMISSD) rather than erroneously large values?
gembud mailing list
For list information or to unsubscribe, visit: