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

20000128: Using /p tag

Steve,

Here is the crux of your trouble. If you use our pqing ingest
version 5.0.9 program to read data in off your satellite dish, then you
will get the PIL tags as advertised, just as the university sites who
get the NOAAport data downstream of our ingestion do. That is a change we made
last summer when it became apparent that WMO identifiers alone weren't
carrying all the information necessary to define the product.

If you get your data from Alden via the internet, then they need to use
the most recent version of pqing to place those tags in the LDM identifiers...
if that is how they are placing the data into their queue.  

Steve Chiswell
Unidata User Support

>From: address@hidden (Steve Adams)
>Organization: .
>Keywords: 200001282239.PAA24512

>>From address@hidden Fri Jan 28 15:18 CST 2000
>>
>>Steve,
>>
>>Your ldmConnect message from pqact could be caused by the decoders
>>package program ldmConnect not being installed in your ~ldm/bin
>>directory- which is likely when you installed your new ldm version
>>and moved the runtime link so that bin/ now points to ldm-5.0.9/bin/
>>rather than ldm-5.0.8/bin/.
>
>Oops! You're right. We'll fix that up.
>
>
>>Your previous message said that you did see pil tages with -f DDPLUS.
>>Since DDS|PPS is the same as DDPLUS, then using DDPLUS will match
>>on the bitwise comparison of either PPS or DDS. The Creating
>>AFOS-like pil tags" message would be emitted in verbose logging as I mentione
> d
>>before, so you would want to invoke your pqing with the -v option to test thi
> s.
>>My understanding is that you are ingesting off the Alden Satellite feed.
>>Is pqing running with -f DDPLUS or -f PPS? Your previous message stated:
>>>but DDPLUS is working:
>>>Jan 28 19:18:15 awis pqact[12411]:      269 20000128191815.414  DDPLUS 257  
> SR
>>> US57 KWBC 281913 /pRRANEW
>
>The light bulb is turning on!!!!!!!!!!!!
>
>We run pqing on our satellite feed with a feedtype of DDPLUS. It now
>appears that it is working, with /p tags indicated.
>HOWEVER, we do not run pqing on the internet feed, whose products are
>identified by DDS, PPS and IDS feedtypes. These feedtypes do not have
>/p tags.
>
>Now... the questions...
>
>1. Should we be seeing /p tags for the PPS/DDS (internet) feedtypes?
>2. Should we be running pqing for the internet feed, and if so,
>      how do we define the source or "port"?
>3. As it stands, if the internet version of a product comes in first
>      and is acted on by pqact, but it does not act on the entries
>      that use the /p tag because there is none for the internet version,
>      then when the satellite version comes in with the /p tag, will
>      pqact throw it out because it is already in the queue? Thus the
>      pqact.conf entries that require the /p tag are never acted on
>      in this case? Which leads me back to #2 question?
>
----------------------------------------------------------------
>Stephen D. Adams
>Vice President - Research and Development
>Agricultural Weather Information Service, Inc.
>ph: (334) 826-2149 ex103       email: address@hidden
>    (334) 826-2152 (FAX)       http://www.awis.com
>----------------------------------------------------------------
>