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

[Support #SBB-325304]: Re: 20110712: CONDUIT request -- fire weather grids

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: [Support #SBB-325304]: Re: 20110712: CONDUIT request -- fire weather grids
  • Date: Tue, 23 Aug 2011 09:36:16 -0600
Hi again Justin,

Oops, the meeting I thought I had to run to is on Thursday...

I put together a compressed tar file of the latest version of the GEMPAK
GRIB tables used by 'gribinsert' for you to grab:

machine:   ftp.unidata.ucar.edu
user:      anonymous
pass:      address@hidden
directory: pub/gribinsert
file:      tables_1_4_1.tar.gz

Here is what you should do to upgrade ncep-ldm2.woc.noaa.gov with these tables:

<as 'ldm'>
cd ~ldm/etc
mkdir tables_1_4
cp *.tbl tables_1_4

ftp ftp.unidata.ucar.edu
  <user> anonymous
  <pass> address@hidden
  cd pub/gribinsert
  binary
  get tables_1_4_1.tar.gz
  quit

rm *.tbl && tar xvzf tables_1_4_1.tar.gz
ls -alt *.tbl

Comments:

- you will note that a number of the tables provided are actually
  links to other versions of the same tables.  Not to worry.

- if there is a 'gribinsert' instance running when you update the
  tables it may or may not read/use new entries.  Subsequent
  'gribinsert' invocations, however, will.

  The reason that a running 'gribinsert' may or may not use the
  new table entries is that it reads a table and then uses that
  information for as long as it continues to run _except_ when
  a different table of the same kind (e.g., g2varsncep1.tbl instead
  of g2varsncep0.tbl, etc.) is indicated by items in the GRIB
  file being processed.

- our NOAAPort ingest package uses the same set of GEMPAK tables
  as 'gribinsert'.  I upgraded one of our NOAAPort ingest machines
  yesterday afternoon with the new tables and then took a look to
  see if there were any "unknown" fields this morning -- unfortunately
  there were a few (4).  This means that I will be making further
  modifications to the GEMPAK GRIB tables in the coming days.

- the switch to a new set of tables should have _no_ effect on the
  number/volume of data being inserted into the LDM queue.  'gribinsert'
  uses the GEMPAK tables to create descriptive LDM/IDD Product IDs 
  that end users can key on in ldmd.conf REQUEST and pqact.conf pattern-action
  lines.  If GRIB table information can't be found for a product being
  processed by 'gribinsert', a error/warning is issued in its log file
  and the product is inserted with a not quite so descriptive Product ID;
  it is _not_ discarded.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: SBB-325304
Department: Support CONDUIT
Priority: Normal
Status: Closed