[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #DNO-406029]: dcgrib2 accuracy and dcgrib not working with latest gdpoint

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [GEMPAK #DNO-406029]: dcgrib2 accuracy and dcgrib not working with latest gdpoint
  • Date: Fri, 10 Mar 2006 15:29:00 -0700
>Is there any reason why the latest gdpoint doesn't seem to work with
>dcgrib-generated files?

David,

I updated the gdpoint code while fixing the DG_ library calls to use the GEMPAK
file/time interface which allows many of the template, time range etc functions 
that
tha code previously didn't handle. Eg, using GDFILE=eta104|1200 as a template 
etc.

I can check those calls....

Since the ETA104 is providing P03M at 3 hourly intervals, the P06M and P12M are
using the accumulations at the intervening times. The $GEMTBL/grid/wmo*
files specify -.01 as the value to use for missing (parameter 61) rather
than 0 so the decoding does create negative (-.01) values from those tables.
That might be the initial point to look at. Missing is different than 0, but
apparently they didn't want to use -9999. Can you provide the
P03M values for each forecast hour as decoded with dcgrib2 so that we can hand
track what the p06m and p12M are doing?

Steve Chiswell
Unidata User Support

Ticket Details
===================
Ticket ID: DNO-406029
Department: Support GEMPAK
Priority: Normal
Status: Closed