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

20001201: Configuration of nmap

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: 20001201: Configuration of nmap
  • Date: Fri, 01 Dec 2000 10:36:54 -0700
Glenn,

You have a couple of options for how you deal with nmap and
your eta212 and eta215 grids.

Currently, I use the keys eta, eta212 and eta215 in the mod_res.tbl
file. Each of these have their template defined in the 
$GEMTBL/config/datatype.tbl
file, defaults I provide are:

ETA     YYYYMMDDHH_eta211.gem
ETA212  YYYYMMDDHH_eta212.gem
ETA215  YYYYMMDDHH_eta215.gem

If you want the eta212 and eta215 keys to be used with the mod_res.tbl actions
that currently only have eta, then you can just add the additional keys to the 
list, eg:

50mb_HGHT_WIND  $NMAP_RESTORE/stnd/50mb_hght_wind  1.standard     
avn;eta;eta212;eta215
this is pretty easy in "vi" for example using the global search.

Or, if you don't deal with the eta211 grids at all, and would prefer that
the key "eta" meant the 212 grid, then you could change that in the template
file, eg:
ETA     YYYYMMDDHH_eta212.gem


As for the pqact.conf entry and your missing the 30-60 hour grids,
the default maximum number of grids in a grid file from dcgrib is 1500.
There are more than 1500 eta212 and 211 grids, so you need to add the
"-m numgrids" flag to your pqact.conf entry, where numgrids is
large enough to store the complete model run.

Steve Chiswell
Unidata User Support





>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200012011632.eB1GWio05362

>
>
>Steve,
>I'm wondering what is the best way to get my grids to function in nmap.
>Currently the file
>/gempak/tables/nmap/mod_res.tbl
>
>has the eta listed as the data source.  My pattern actions pipe eta212 and
>215.  Should I rename the pqact assignment to eta to match the  mod_res.tbl
>file (make my files eta) or change the mod_res.tbl file to match the
>patterns provided in the pqact (i.e., make mod_res.tbl models eta212? ).
>
>Also, in my griblogs I'm getting:
>Dec 01 15:08:43 dcgrib[28479]:  Error writing grid data:  -11
>Dec 01 15:08:43 dcgrib[28479]: header not found skipped 001201/1200
>         Grid ID  212  66   1   0   0
>Dec 01 15:14:17 dcgrib[28479]:  Error writing grid data:  -11
>Dec 01 15:14:17 dcgrib[28479]: header not found skipped 001201/1200
>         Grid ID  212  15 105   0   2
>Dec 01 15:14:18 dcgrib[28479]:  Error writing grid data:  -11
>Dec 01 15:14:18 dcgrib[28479]: @^L skipped 001201/1200         Grid ID  212
>  16 105   0   2
>
>
>Finally, I've lost eta grids between 30HR to the 60HR period.  Any thoughts
> why?  I think this all occured when I placed 5.6/nmap on-line.   Here's my
> pqacr entry:
>WMO  ^NOAAPORT\.NWSTG\.GRID\.[YZ].[RU].[0-9][0-9]\.KWB[DE]\..*
>     PIPE /npfos/noaaport/nawips/bin/sol/dcgrib -d
>/npraid/noaaport/nawips/logs/%Y%m%d_dcgrib.log
>          -g /npfos/noaaport/nawips/gempak/tables/grid
>          PACK /npfos/noaaport/nawipsdata/hds/YYYYMMDDHH_eta@@@.gem
>
>Thx, Glenn
>
>