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

20011107: ARPS-GEMPAK SNAFU

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: 20011107: ARPS-GEMPAK SNAFU
  • Date: Wed, 7 Nov 2001 13:56:04 -0700

Kevin,

dcgrib decodes the grib parameters found in the $GEMTBL/grid configuration
files.

If you are only seeing wmo standard parameters (eg 1-127) ie u=33, v = 34, then
you have to create the model center specific table with the parameter numbers
from 128 to 255. This depends on the model center you are using for
creating your grib output.

If you are having trouble opening an output file in a program, then you
need to look at the diagnostic return codes (iret) from the various
routines that you are calling.

Steve Chiswell
Unidata User Support



On Wed, 7 Nov 2001, Kevin M. Lux wrote:

> I'm running ARPS and it can generate every output format except GEMPAK.
> ARPS has a program to convert its output to GEMPAK, but I haven't been
> able to get it to work.  It compiles on IRIX, but doesn't create the
> GEMPAK file when it runs.  It doesn't compile on our Linux machine for
> some other stupid reason.  I've managed to take grib output and convert
> it with dcgrib, but there's a problem.  I only get u, v, q, theta, and
> p.  ARPS produces a whole lot more variables than that, but I'm not
> getting them.  I know that I get all of the variables when I choose
> GrADS output.  Is there something that converts GrADS to GEMPAK?  The
> reason I'm going through all this trouble is that I already have code
> that lets me compute odd parameters like vorticity tendency terms, but
> it's only good for GEMPAK.
>
> Kevin
>
>