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

Re: NCEP TIGGE parameters

Doug,

Yes, all data sent on CONDUIT have the .status...... file for each file
inserted.
Those extra parameters come under the data2/TIGGE directory, so the
status file
is .status.data2/TIGGE/etc.

I had one table update (for snow water equivalent) to send to NCEP so
that
the parameter name is correctly added into that metadata string (between
the
"!" characters).

I sent off a note to ask if NCEP would continue to keep these TIGGE
files separate in there directory structure from the other data/nccf.*
ensemble files since it will
mean updated documentation to the pattern action lines.

Steve Chiswell
Unidata User Support


On Thu, 2006-10-05 at 11:15 -0600, Doug Schuster wrote:
> Are the status files being generated for the TIGGE stream now?
> 
> On Oct 4, 2006, at 4:09 PM, Steve Chiswell wrote:
> 
> > Doug,
> >
> > If NCEP continues to maintain these extra TIGGE files in a different
> > data directory (aka data2/TIGGE), you can request: "TIGGE|prod/gefs".
> >
> > The ftpprd directory has pgrb2a, pgrb2b and the data2/TIGGE have
> > pgrb2c.
> > In your pqact.conf pattern, if you aren't going to match on the ncep
> > file name
> > parts, which depend on the file path structure at NCEP, you can start
> > with the /ge[pc] and then the parts between the "!" characters will
> > follow the standard formatting.
> >
> > I have:
> > CONDUIT             /(ge.*)\.t..z\.pgrb2.* !(.*)!
> > You can insert your regex for your fields in the "!" and change your
> > escaped references in the action accordingly.
> >
> > I'll check this when the 18Z data comes accross.
> >
> > Steve Chiswell
> > Unidata User Support
> >
> > On Wed, 2006-10-04 at 14:55 -0600, Doug Schuster wrote:
> >> Steve,
> >>
> >> What will the full path be to subscribe the TIGGE feed in
> >> ldmd and pqact?
> >> Currently I'm using
> >>
> >> in ldmd:
> >> REQUEST CONDUIT "data/nccf/com/gens/.*"
> >> idd.unidata.ucar.edu PRIMARY
> >> REQUEST CONDUIT "^.status\.*data/nccf/com/gens/.*"
> >> idd.unidata.ucar.edu PRIMARY
> >>
> >> in pqact.conf:
> >> CONDUIT
> >> data/nccf/com/gens/(....)/gefs.(........)/(..)/pgrb2a/ge(.)(..).t 
> >> (..)z.pgrb2(.*)
> >> !(.*)/(.*)/(.*)/(.*)/(..........)(..)F(...)/(HGHT|TMPK|UREL;VREL| 
> >> CAPE|PMSL|TMXK06|TMNK06|CLD06|PRES)/(.*)
> >> (.*) (.*)! (.*)
> >>          FILE    -close
> >>          /datazone/tigge/daily_output/kwbc/\(12)/z_tigge_c_kwbc_ 
> >> \(12)\(13)00_0\(14)_al_glob_prod.grib2
> >>
> >> Doug
> >>
> >> On Wed, 04 Oct 2006 14:21:51 -0600
> >>   Steve Chiswell <address@hidden> wrote:
> >>> Brent and Justin,
> >>>
> >>> The CONDUIT top level feeds are currently using a
> >>> pattern for ensemble
> >>> "prod/gefs"
> >>> which matches the original data files, but not the other
> >>> files
> >>> data2/TIGGE.
> >>>
> >>> I'll modify the top levels to include that other
> >>> data2/TIGGE pattern.
> >>>
> >>> Steve
> >>>
> >>> On Wed, 2006-10-04 at 16:08 -0400, Justin Cooke wrote:
> >>>> Brent,
> >>>>
> >>>> I see everything but snow depth water equivalent being
> >>>> sent to CONDUIT:
> >>>>
> >>>> Oct  4 06:40:21 ldm1 pqact[7183] INFO:    43712
> >>>> 20061004104021.027
> >>>> CONDUIT 000  data2/TIGGE/gep10.t06z.pgrb2canl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/HGHT/300 Pa
> >>>> PRES! 000000
> >>>> Oct  4 06:40:21 ldm1 pqact[7183] INFO:    41993
> >>>> 20061004104021.029
> >>>> CONDUIT 001  data2/TIGGE/gep10.t06z.pgrb2canl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/HGHT/50 Pa
> >>>> PRES! 000001
> >>>> Oct  4 06:41:07 ldm1 pqact[7183] INFO:    22266
> >>>> 20061004104101.476
> >>>> CONDUIT 002  data2/TIGGE/gep14.t06z.pgrb2cf00
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/TMPK/300 Pa
> >>>> PRES! 000002
> >>>> Oct  4 06:40:21 ldm1 pqact[7183] INFO:    74798
> >>>> 20061004104013.976
> >>>> CONDUIT 003  data2/TIGGE/gep12.t06z.pgrb2canl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/UREL;VREL/300
> >>>> Pa PRES! 000003
> >>>> Oct  4 06:40:21 ldm1 pqact[7183] INFO:    60563
> >>>> 20061004104013.977
> >>>> CONDUIT 004  data2/TIGGE/gep12.t06z.pgrb2canl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/HGHT/2
> >>>> K*m**2*kg-1*s-1 POTV!
> >>>> 000004
> >>>> Oct  4 06:40:21 ldm1 pqact[7183] INFO:    65291
> >>>> 20061004104013.979
> >>>> CONDUIT 005  data2/TIGGE/gep12.t06z.pgrb2canl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/UREL;VREL/2
> >>>> K*m**2*kg-1*s-1
> >>>> POTV! 000005
> >>>> Oct  4 06:40:21 ldm1 pqact[7183] INFO:    27970
> >>>> 20061004104013.980
> >>>> CONDUIT 006  data2/TIGGE/gep12.t06z.pgrb2canl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/CINS/0 -
> >>>> NONE! 000006
> >>>> Oct  4 06:41:37 ldm1 pqact[7183] INFO:     2560
> >>>> 20061004104131.841
> >>>> CONDUIT 009  data2/TIGGE/gep07.t06z.pgrb2cf06
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F006/LAND/0 -
> >>>> NONE! 000009
> >>>> Oct  4 06:40:51 ldm1 pqact[7183] INFO:    30627
> >>>> 20061004104043.278
> >>>> CONDUIT 007  data2/TIGGE/gep07.t06z.pgrb2cf00
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/TMPK/0 -
> >>>> NONE! 000007
> >>>> Oct  4 06:40:05 ldm1 pqact[7183] INFO:    64275
> >>>> 20061004104003.900
> >>>> CONDUIT 031
> >>>> data/nccf/com/gens/prod/gefs.20061004/06/pgrb2a/ 
> >>>> gep07.t06z.pgrb2aanl
> >>>> !grib2/ncep/SPEC62MRF/#000/200610040600F000/HGHT/0 -
> >>>> NONE! 000031
> >>>>
> >>>> Justin
> >>>> Brent A. Gordon wrote:
> >>>>> Justin,
> >>>>>
> >>>>> Would you please verify that these additional
> >>>> parameters are being
> >>>>> successfully injected into the CONDUIT stream.
> >>>>>
> >>>>> Steve,
> >>>>>
> >>>>> Have all the CONDUIT users switched to the WOC LDM
> >>>> system?
> >>>>>
> >>>>> Brent
> >>>>>
> >>>>> Doug Schuster wrote:
> >>>>>> Brent,
> >>>>>>
> >>>>>> Will all of these be available through CONDUIT?
> >>>>>> On the CONDUIT stream I'm currently not seeing:
> >>>>>>
> >>>>>> Geopotential Height at 300mb and 50mb.
> >>>>>> Temperature at 300mb.
> >>>>>> U+V at 300mb and +2PVU surface
> >>>>>> CIN
> >>>>>> Skin Temp
> >>>>>> Orography
> >>>>>> Land Sea Mask
> >>>>>> Snow depth water equivalent.
> >>>>>>
> >>>>>> Also, could you point me to an NCEP ftp site and
> >>>> directory where
> >>>>>> this data is available as a backup?  And did you
> >>>> mention in
> >>>>>> a previous conversation that you could provide an ftp
> >>>> download
> >>>>>> script with the capability to select individual
> >>>> paramters?
> >>>>>>
> >>>>>> On Wed, 04 Oct 2006 07:39:32 -0400
> >>>>>>  "Brent A. Gordon" <address@hidden> wrote:
> >>>>>>> Doug,
> >>>>>>>
> >>>>>>> Let me try to set straight what NCEP said about the
> >>>> TIGGE parameters
> >>>>>>> at a telcon this past Summer.  We agreed that they
> >>>> do conform to WMO
> >>>>>>> standards, however we also pointed out that NCEP was
> >>>> using different
> >>>>>>> (yet still WMO acceptable) ways to encode its
> >>>> operational GRIB2
> >>>>>>> data. What is still undefined is how the gap is to
> >>>> be bridged
> >>>>>>> between NCEP operational data requirements and TIGGE
> >>>> research
> >>>>>>> requirements.
> >>>>>>>
> >>>>>>> As it stands right now, NCEP will not be modifying
> >>>> its operational
> >>>>>>> data sets for TIGGE requirements.  This is something
> >>>> that we are
> >>>>>>> currently negotiating with NCAR to do.  This is much
> >>>> the same as
> >>>>>>> ECMWF does for many other operational institutions.
> >>>>>>>
> >>>>>>> The underlying issue here is that NCEP has been
> >>>> producing and
> >>>>>>> disseminating its operational data in GRIB2 format
> >>>> long before the
> >>>>>>> TIGGE standard was defined (without input from the
> >>>> operational side
> >>>>>>> of NCEP).  The format we are using for our GRIB2
> >>>> data is compliant
> >>>>>>> with the WMO standard for GRIB2.  Unfortunately,
> >>>> there is a lot of
> >>>>>>> room in the WMO GRIB2 standard for interpretation of
> >>>> how things
> >>>>>>> should be encoded.  As we now have several customers
> >>>> using our GRIB2
> >>>>>>> data to run their operations, a change to our
> >>>> standard is not
> >>>>>>> readily possible. NCEP is now able to provide 48
> >>>> parameters for the
> >>>>>>> TIGGE archive via the CONDUIT feed.  These are
> >>>> operational data
> >>>>>>> however and will not have the special TIGGE
> >>>> headings. Those
> >>>>>>> parameters are:
> >>>>>>>
> >>>>>>> Geopotential Height at 1000, 925, 850, 700, 500,
> >>>> 300, 250, 200, and
> >>>>>>> 50 mb
> >>>>>>> Temperature at 1000, 925, 850, 700, 500, 300, 250,
> >>>> 200 mb, and 2 m
> >>>>>>> U & V at 1000, 925, 850, 700, 500, 300, 250, 200 mb,
> >>>> 10 meters, and
> >>>>>>> +2 PVU surface
> >>>>>>> CIN
> >>>>>>> CAPE
> >>>>>>> Skin Temp
> >>>>>>> Snow depth water equivalent
> >>>>>>> Orography
> >>>>>>> Land Sea mask
> >>>>>>> Max Temp
> >>>>>>> Min Temp
> >>>>>>> Surface Pressure
> >>>>>>> Total Cloud Cover
> >>>>>>>
> >>>>>>> Brent
> >>>>>>>
> >>>>>>>
> >>>>>>> Doug Schuster wrote:
> >>>>>>>> Hi Brent,
> >>>>>>>>
> >>>>>>>> With regards to the prior email, it appears there
> >>>> are some differences
> >>>>>>>> between NCEP's GRIB-2 encoding of certain TIGGE
> >>>> parameters, and the
> >>>>>>>> TIGGE defined GRIB-2 encoding.
> >>>>>>>> NCEP has previously indicated that it has reviewed
> >>>> and approved of
> >>>>>>>> the GRIB-2 encoding of TIGGE parameters
> >>>>>>>> defined here:
> >>>>>>>>
> >>>> http://tigge.ecmwf.int/tigge/d/show_archive/table=parameters/
> >>>>>>>>
> >>>>>>>> Is NCEP in the process of modifying its parameter
> >>>> encoding of
> >>>>>>>> available TIGGE variables to match
> >>>>>>>> the TIGGE defined encoding?
> >>>>>>>>
> >>>>>>>> Also, could you provide us will a list of TIGGE
> >>>> conforming GRIB-2
> >>>>>>>> parameters that
> >>>>>>>> will be available by the end of the October?
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Doug
> >>>>>>
> >>> -- 
> >>> Steve Chiswell <address@hidden>
> >>> Unidata
> > -- 
> > Steve Chiswell <address@hidden>
> > Unidata
-- 
Steve Chiswell <address@hidden>
Unidata