Re: [ldm-users] [gb2param.c:89] [GB -1]

• To: Steve Emmerson <emmerson@xxxxxxxx>, Benjamin Schwedler <benjamin.schwedler@xxxxxxxx>
• Subject: Re: [ldm-users] [gb2param.c:89] [GB -1]
• From: Jason Craig <jcraig@xxxxxxxx>
• Date: Wed, 10 Sep 2014 18:43:35 +0000

They have been updated on NCEP's official grib2 table list:
http://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_table4-2-0-19.shtml


            -Jason-

On 09/10/2014 06:39 PM, Steve Emmerson wrote:

On Wed, Sep 10, 2014 at 10:08 AM, Benjamin Schwedler <benjamin.schwedler@xxxxxxxx <mailto:benjamin.schwedler@xxxxxxxx>> wrote:

    Bruce,

    These two particular products switched from GRIB1 to GRIB2 on
    September 3rd.  Could be that these parameters are not in the GRIB
    tables.

    Category 19, parameters 217, 233, and 234.


That's exactly what that error message means.

Does anyone know what the table entries should be?

--Steve Emmerson


    Ben



    On 09/10/2014 10:44 AM, Bruce Haynie - NOAA Federal wrote:

    Fellow LDMers:

    We keep getting the following errors in our LDM noaaport ingest
    machines:

    Sep 10 15:20:20 rafterman noaaportIngester[27804] ERROR:
    [gb2param.c:89] [GB -1] Couldn't get parameter info: disc=0,
    cat=19, id=234, pdtn=0
    Sep 10 15:20:20 rafterman noaaportIngester[27804] ERROR:
    [gb22gem.c:74] [GB 1] Couldn't get parameter values
    Sep 10 15:20:20 rafterman huckleberry(feed)[27843] INFO: sending:
     39070 20140910152020.305     HDS 181243814  YLXA57 KKCI 101500
    !grib2/ncep/AWC_CIP/#130/
    FHRS//LVL
    Sep 10 15:20:20 rafterman noaaportIngester[27804] ERROR:
    [gb2param.c:89] [GB -1] Couldn't get parameter info: disc=0,
    cat=19, id=234, pdtn=0
    Sep 10 15:20:20 rafterman noaaportIngester[27804] ERROR:
    [gb22gem.c:74] [GB 1] Couldn't get parameter values
    Sep 10 15:20:20 rafterman huckleberry(feed)[27843] INFO: sending:
     43317 20140910152020.318     HDS 181243815  YLXA55 KKCI 101500
    !grib2/ncep/AWC_CIP/#130/
    FHRS//LVL

    Per the messages above, it appears they are only associated with
    some products in the HDS feed.  I've seen a few other references
    to this problem in the archives, but they don't seem to apply in
    this case... although I could be wrong about that :-).  This has
    been occurring for a while now before all of the ldm updates
    started rolling out in recent days/weeks. We are running ldm
    6.12.6 on our ingest boxes and downstream hosts.  Any idea what's
    going on and how to fix?

    Thanks!

    Bruce


    _______________________________________________
    ldm-users mailing list
    ldm-users@xxxxxxxxxxxxxxxx  <mailto:ldm-users@xxxxxxxxxxxxxxxx>

For list information or to unsubscribe, visit:http://www.unidata.ucar.edu/mailing_lists/

-- Benjamin R. J. Schwedler

    NWS Aviation Weather Testbed - NextGen/AWT Development Meteorologist
    CIRA/Colorado State University
    NOAA/Aviation Weather Center
    7220 NW 101st Terrace
    Kansas City, MO 64153-2371
    816.584.7268  <tel:816.584.7268>


    _______________________________________________
    ldm-users mailing list
    ldm-users@xxxxxxxxxxxxxxxx <mailto:ldm-users@xxxxxxxxxxxxxxxx>
    For list information or to unsubscribe,  visit:
    http://www.unidata.ucar.edu/mailing_lists/




_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/

• References:
  • [ldm-users] [gb2param.c:89] [GB -1]
    • From: Bruce Haynie - NOAA Federal
  • Re: [ldm-users] [gb2param.c:89] [GB -1]
    • From: Benjamin Schwedler
  • Re: [ldm-users] [gb2param.c:89] [GB -1]
    • From: Steve Emmerson