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

Hi Justin,

re:
> How were you able to determine that most of the fields were interpreted
> by gribinsert?

I downloaded firewx files from the FTP resource that Becky included in
a previous email, and then ran gribinsert (v1.4) on my workstation here
in Unidata.  The number of fields for which a "GB" error/warning was issued
was small.  My interpretation of this result is that there are not many
modifications/additions needed to the GEMPAK tables used for GRIB/GRIB2
cracking (cracked to extract metadata used to create meaningful LDM/IDD
Product IDs).

re:
> Were you able to connect your LDM to the CONDUIT box we've broken out?
> It can be reached at: 140.90.33.32

I didn't try this before sending you the note yesterday afternoon.

(few minutes later)

OK, I verified that I can REQUEST CONDUIT data from 140.90.33.32.
I did this from the Unidata machine that is regularly REQUESTing
CONDUIT data from WOC machines: daffy.unidata.ucar.edu, 128.117.140.208.

A 'notifyme -vl- -f CONDUIT -h 140.90.33.32' shows that data is being
made available on 140.90.33.32:

[ldm@daffy ~]$ notifyme -vl- -f CONDUIT -h 140.90.33.32
Aug 17 15:11:30 notifyme[20306] NOTE: Starting Up: 140.90.33.32: 
20110817151130.000 TS_ENDT {{CONDUIT,  ".*"}}
Aug 17 15:11:30 notifyme[20306] NOTE: LDM-5 desired product-class: 
20110817151130.000 TS_ENDT {{CONDUIT,  ".*"}}
Aug 17 15:11:30 notifyme[20306] NOTE: NOTIFYME(140.90.33.32): OK
Aug 17 15:12:01 notifyme[20306] INFO:    71719 20110817151158.353 CONDUIT 000  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/1 - HYBL! 000000
Aug 17 15:12:01 notifyme[20306] INFO:    71692 20110817151158.360 CONDUIT 001  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/2 - HYBL! 000001
Aug 17 15:12:01 notifyme[20306] INFO:    71553 20110817151158.365 CONDUIT 002  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/3 - HYBL! 000002
Aug 17 15:12:01 notifyme[20306] INFO:    71449 20110817151158.365 CONDUIT 003  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/4 - HYBL! 000003
Aug 17 15:12:01 notifyme[20306] INFO:    71153 20110817151158.366 CONDUIT 004  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/5 - HYBL! 000004
Aug 17 15:12:01 notifyme[20306] INFO:    70768 20110817151158.366 CONDUIT 005  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/6 - HYBL! 000005
Aug 17 15:12:01 notifyme[20306] INFO:    70411 20110817151158.370 CONDUIT 006  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/7 - HYBL! 000006
Aug 17 15:12:01 notifyme[20306] INFO:    69979 20110817151158.371 CONDUIT 007  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/8 - HYBL! 000007
Aug 17 15:12:01 notifyme[20306] INFO:    69529 20110817151158.371 CONDUIT 008  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/9 - HYBL! 000008
Aug 17 15:12:01 notifyme[20306] INFO:    69129 20110817151158.372 CONDUIT 009  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/10 - HYBL! 000009
Aug 17 15:12:02 notifyme[20306] INFO:    68675 20110817151158.378 CONDUIT 010  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/11 - HYBL! 000010
Aug 17 15:12:02 notifyme[20306] INFO:    68195 20110817151158.378 CONDUIT 011  
data/nccf/com/ruc/prod/ruc2a.20110817/ruc2.t14z.bgrb20f18.grib2 
!grib2/ncep/RUC2/#000/201108171400F018/PRES/12 - HYBL! 000011
 ...

These are not, however, FireWx products... presumably, you added the FireWx 
products into
the mix of model output that is being inserted into the LDM queue on 
140.90.33.32?

re:
> From our gribinsert log it appears that we are successfully sending
> firewx fields to the broken-out CONDUIT box, but until someone receives
> data from it I can't be sure.

It would be most useful for testing if my Unidata workstation could be
ALLOWed to REQUEST CONDUIT data from 140.90.33.32.  My workstation is:

gale.unidata.ucar.edu
128.117.156.80

re:
> Becky is going to ask the developers about the GEMPAK questions you had.

OK, thanks.  The just of my questions was to find out if _ALL_ of the
FireWX fields are being correctly decoded into GEMPAK grids.  If they
are, it should mean that the GRIB/GRIB2 tables used in the decoding
contain the information for all of the fields in the FireWX products.

re:
> Thanks again for working on this.

No worries.  Sorry for the delays!

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