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

19990622: Matching PIL id's in pqact


Tom,

Several weeks ago, we implemented a change to the ingest software
which now adds the pil-like identifier to the DDPLUS|IDS NOAAport
datastream product headers. Text products which contain a line that
conforms to a PIL have the string appended to the LDM product
identifier as "/pPIL_ID" Note that this change only affects the 
product identifier as seen in the LDM, and does not modify the
data product in any way. Two of the three top tier sites have
already upgraded to the new ingest software, so almost all 
products available on the IDD have the pil-like identifiers
appended. With the additional product identifier appended to the 
end of the WMO identifier, we have been able to implement
this change basically without anyone noticing it. Of course,
we will notify everyone when all top tier ingest sites are
using the updated ingester so that all data on the IDD
will have the tag regardless of where it was ingested.

In the example you show below, the product that begins with:

 742
 SRUS51 KPHI 221222
 RR1PHL
 ...

will be identified in the LDM data stream as:

 SRUS51 KPHI 221222 /pRR1PHL

So, you can use a pqact.conf line such as:

 DDPLUS ^SRUS51 KPHI .* /pRR1PHL

The "/p" identifier is analogous to the "/m" identifier which
is appended to the model data products in the HDS feed,
and can be used to differentiate between products issued under
common WMO headers. Note that WMO headers frequently have some
communitaction identifiers following the DDHHMM group, such as
RTDxx, COR, AAA, etc. which is generally not useful for most IDD
data processing- but in general, the IDD products will look like:

TTAAii CCCC DDHHMM [COM] [/pPIL_ID]


Since not all products have PILs, the "/p" tag will only be placed on
those products which contain a pil-like line. Some products, such
as some METAR bulletins, contain second lines that look like AFOS PILS
while other METAR bulletins do not. As a result, you will see some
METAR bulletins with /pMETAR appended, while some do not. While
the METAR string is not an actual PIL, it does conform to what
a PIL looks like, so the /p tag represents a "pil-like" tag.
Thus, for surface METAR decoding, you should still use the ^SA.*
pattern and not the /p tag. 

To date, nobody has complained about any problems caused by the addition
of the pil tags, so we plan to have the final top tier site upgrade
as soon as they can.

We hope that the community finds this addition to be a valuable
resource for use in the IDD. If you want to observe the pil tags
in action, you can use the "ldmadmin watch" command or "notifyme"
command to show the datastream headers.

As always, support questions can be addressed to address@hidden.

Good luck-

Steve Chiswell
Unidata User Support


On Tue, 22 Jun 1999, Tom Grzelak wrote:

> 
> Hi!
> 
> I would like to set up my pqact.conf file to route certain reports to
> specifc programs/people.  As long as the reports have unique headers, it is
> straight-forward.  But I am not sure how to handle the following situation:
> 
> I have a single header which is used for SEVERAL different reports.  It is
> the second and/or third line which makes the report unique.  How would I
> set up a pqact.conf line item to do pattern matching on more than one line?
> 
> For example:
> Here's a desired product with a header which is used for several other
> undesired products.
> 
> 742 
> SRUS51 KPHI 221222
> RR1PHL
> .BR PHL  0622 DH12/PPP
> PHL .03,ABE .01,ACY .14,MIV .06,ILG .05
> WRI .07,NXX .04,DOV .11,PNE .10,EWR T
> TTN .08,SMQ .03,MPO .01,GED .08,VAY .26
> 12N .02,RDG .02,BLM .05,WWD .05
> CDW .05
> .END
> 
> In this example, a pattern match on the header line AND the second line
> would allow this DESIRED product to be sent to the right person/program.  
> 
> THE BIG QUESTION: How do you do a pattern match for the second line?
> 
> DDPLUS  ^SRUS51 KPHI
>         PIPE
>         -close -strip /usr/bin/mailx address@hidden
> 
> Thanks!
> Tom
> ===============================================================
> Tom Grzelak                        address@hidden
> Manager - Computing Services
>  ----> Center for Environmental Prediction
>  ----> Department of Environmental Sciences  
> 
> Rutgers University
> 14 College Farm Road                  Voice: 732-932-4923     
> New Brunswick, NJ 08901-8551          Fax: 732-932-8644
>                 http://www.envsci.rutgers.edu
> ===============================================================
>