NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi all,
I hate to bother you, but I'm stuck.
We have a recent installation of GEMPAK 7.2 on a new server, and can't get
nagrib2 to work properly. Upon running nagrib2, it will read the grib2 file
properly, but doesn't write any grids to the new gempak file.
For starters, our input looks like this:
GBFILE = gfs.t12z.pgrb2.0p25.f000
GDOUTF = test.grd
PROJ =
GRDAREA =
KXKY =
MAXGRD = 4000
CPYFIL = gds
GAREA = dset
OUTPUT =
G2TBLS =
G2DIAG =
OVERWR = NO
PDSEXT = NO
This returns:
Opening WMO Originating Center Table wmocenter.tbl...
Opening WMO GRIB2 Parameter Table g2varswmo2.tbl...
Opening Local GRIB2 Vertical Coordinate Table g2vcrdncep1.tbl...
Creating the GEMPAK grid file...
GEMPAK grid file is ready...
MESG# GDT# DIS# CAT# ID# PDT# VCD# GEMPAK_TIME LEVL1 LEVL2 VCRD PARM
1 0 0 2 2 0 220 151006/1200F000 0 PBLR
UREL
2 0 0 2 3 0 220 151006/1200F000 0 PBLR
VREL
Opening Local GRIB2 Parameter Table g2varsncep1.tbl...
3 0 0 2 224 0 220 151006/1200F000 0 PBLR
VRATE
Opening WMO GRIB2 Vertical Coordinate Table g2vcrdwmo2.tbl...
4 0 0 2 22 0 1 151006/1200F000 0 NONE
GUST
5 0 0 3 5 0 100 151006/1200F000 10 PRES
HGHT
[......................]
319 0 0 3 0 0 109 151006/1200F000 -2 POTV PRES
320 0 0 2 192 0 109 151006/1200F000 -2 POTV
VWSH
321 0 0 3 1 0 101 151006/1200F000 0 NONE
PMSL
322 0 0 3 193 0 100 151006/1200F000 500 PRES
HGHT5
GRID FILE: test.grd
GRID NAVIGATION:
PROJECTION: CED
ANGLES: 0.0 0.0 0.0
GRID SIZE: 1440 721
LL CORNER: -90.00 0.00
UR CORNER: 90.00 -0.25
GRID ANALYSIS BLOCK:
ANALYSIS TYPE: BARNES
DELTAN: 4.000
DELTAX: -9999.000
DELTAY: -9999.000
GRID AREA: -90.00 -180.00 90.00 180.00
EXTEND AREA: -90.00 -180.00 90.00 180.00
DATA AREA: -90.00 -180.00 90.00 180.00
Number of grids in file: 0
Maximum number of grids in file: 4000
First time in file:
Last time in file:
322 GRIB messages were read or scanned from the GRIB file:
gfs.t12z.pgrb2.0p25.f000
0 grids were written to the GEMPAK file:
test.grd
We've run the gammit of most obvious solutions--there aren't any previous grid
files in the directory, so we're not crossing projections with a previously
created file; and it doesn't appear to be a permissions issue, as both dcgrib2
and nagrib can both create grib2 and grib files, respectively.
In closing, nagrib2 actually creates the grid files (test.grd in this case),
with what appears the proper projection, it just doesn't write any grids to
that file (gdinfo output to follow):
GRID FILE: test.grd
GRID NAVIGATION:
PROJECTION: CED
ANGLES: 0.0 0.0 0.0
GRID SIZE: 1440 721
LL CORNER: -90.0000 0.0000
UR CORNER: 90.0000 -0.2500
GRID ANALYSIS BLOCK:
ANALYSIS TYPE: BARNES
DELTAN: 4.000
DELTAX: -9999.000
DELTAY: -9999.000
GRID AREA: -90.00 -180.00 90.00 180.00
EXTEND AREA: -90.00 -180.00 90.00 180.00
DATA AREA: -90.00 -180.00 90.00 180.00
Number of grids in file: 0
Maximum number of grids in file: 4000
[GDU 2] Did not find any matching grids.
We're stumped. Has anyone run across this before, or have any solutions?
We're thinking of building nagrib2 from GEMAPK 6.10 in instead, to see if an
older version solves the problem.
Thanks for any help or insight you can provide!
-Tom
-----------------------------------------
The information contained in this message is intended only for the personal and
confidential use of the recipient(s) named above. If the reader of this message
is not the intended recipient or an agent responsible for delivering it to the
intended recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, distribution, or copying
of this message is strictly prohibited. If you have received this communication
in error, please notify us immediately, and delete the original message.
gembud archives: