20041130: CONDUIT model name changes effect on end user 12Z GFS/ETA processing (fwd)

Hi Yoshiro,

Yes, there have been name changes..please see attached message below.


You may want to subscribe to:

address@hidden


and/or

address@hidden (CRAFT and CONDUIT combined)

and

address@hidden

at:

http://www.unidata.ucar.edu/mailinglist/mailing-list-form.html

so you get these messages.


Let us know if we can help further...

Cheers,

Jeff
---------------------------------------------------------------------
Jeff Weber                                    address@hidden        :
Unidata Program Center                        PH:303-497-8676        :
University Corp for Atmospheric Research      3300 Mitchell Ln       :
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
---------------------------------------------------------------------

---------- Forwarded message ----------
Date: Tue, 30 Nov 2004 13:02:35 -0700
From: Unidata Support <address@hidden>
To: address@hidden, address@hidden, address@hidden
Subject: 20041130: CONDUIT model name changes effect on end user 12Z
    GFS/ETA processing

>From: Unidata User Support <address@hidden>
>Organization: Unidata Program Center/UCAR
>Keywords: IDD CONDUIT AVN GFS ETA NAM

Users of the Unidata IDD CONDUIT feed:

This morning, a previously announced change in model names was instituted
by NCEP:

AVN -> GFS
ETA -> NAM

The name change created changes in the headers of products in the IDD
CONDUIT datastream.  The full set of GFS and ETA data was sent in the
CONDUIT datastream, but sites using ~ldm/etc/ldmd.conf requests or
~ldm/etc/pqact.conf processing entries that were not modified to
reflect the header changes did not receive and/or process the data.

NCEP has offered to revert the model names to older values (e.g., AVN
and ETA) starting with the 18Z runs today.  The name change will be
reimplemented for the 12Z run on Thursday, November 2.  This gives
users 2 days to update their ldmd.conf and/or pqact.conf CONDUIT
entries so that the receipt and processing of the GFS and NAM data can
continue.

The GFS header changes that were seen this morning looked like:

was:

...CONDUIT 112  /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.avn_CY.12...
...CONDUIT 113  /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.avn_CY.12...
...CONDUIT 114  /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.avn_CY.12...

changed to:

...CONDUIT 112  /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.gfs_CY.12...
...CONDUIT 113  /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.gfs_CY.12...
...CONDUIT 114  /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.gfs_CY.12...

The change to the ETA should have looked similar.

In short, the header changes looked like:

MT.avn -> MT.gfs
MT.eta -> MT.nam

We recommend that you change your ldmd.conf request and/or pqact.conf
processing regular expressions to support these header changes.
For instance, if your pqact.conf action line for CONDUIT GFS data
looked like:

#
# CONDUIT GFS grids (avn, mrf, ensg)
# ----------------------------------------------
#
CONDUIT MT.(avn|mrf|ensg)
        PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUIT.log
        -e GEMTBL=/home/gempak/GEMPAK5.7.3/gempak/tables


we suggest changing it to a pattern that can be used for the old and
new names:

#
# CONDUIT GFS grids (avn/gfs, mrf, ensg)
# ----------------------------------------------
#
CONDUIT MT.(avn|gfs|mrf|ensg)
        PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUIT.log
        -e GEMTBL=/home/gempak/GEMPAK5.7.3/gempak/tables


A similar modification is needed for the ETA/NAM data.  For instance:

change:

# CONDUIT ETA grids
# Grid #104 (90km):     MT.eta.*#104
# Grid #212 (40km):     MT.eta.*#212
# Grid #215 (20km):     MT.eta.*#215
# Grid #216 (45km):     MT.eta.*#216
# Grid #218 (12km):     MT.eta.*#218
HDS|CONDUIT     (/mETA|MT.eta)
        PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib2_ETA.log
                -e GEMTBL=/home/gempak/GEMPAK5.7.3/gempak/tables

to:

# CONDUIT ETA grids
# Grid #104 (90km):     MT.eta.*#104
# Grid #212 (40km):     MT.eta.*#212
# Grid #215 (20km):     MT.eta.*#215
# Grid #216 (45km):     MT.eta.*#216
# Grid #218 (12km):     MT.eta.*#218
HDS|CONDUIT     (/mETA|MT.eta|MT.nam)
        PIPE    decoders/dcgrib2 -d data/gempak/logs/dcgrib2_ETA.log
                -e GEMTBL=/home/gempak/GEMPAK5.7.3/gempak/tables


Please remember to check the integrity of your pqact.conf entries
and then send a HUP signal to the pqact(s) running on your system:

ldmadmin pqactcheck

 -- if there are not errors detected run:

ldmadmin pqactHUP


If you are restricting the CONDUIT data you are ingesting through an
~ldm/etc/ldmd.conf regular expression, it must be updated to allow for
the new model names.

For instance, if you were requesting only the AVN and ETA model data
using:

request CONDUIT "MT.(avn|eta)"  upstream_feed_hostname

you should update the request to support both the old and new model names:

request CONDUIT "MT.(avn|gfs|eta|nam)"  upstream_feed_hostname


Remember that your LDM will need to be stopped and restarted after
making changes to ~ldm/etc/ldmd.conf:

ldmadmin stop
ldmadmin start

Please let us know if you continue to experience difficulty in receipt
and/or processing of the CONDUIT data.

Cheers,

Tom Yoksas
Jeff Weber