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

Re: 20000913: Multiple feed types, dupilicate data, and downstreamclients (fwd)


===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Fri, 15 Sep 2000 15:32:24 -0500
From: Steven Danz <address@hidden>
To: Robb Kambic <address@hidden>
Subject: Re: 20000913: Multiple feed types, dupilicate data,
     and   downstreamclients

Well.... I wrote both ingesters from scratch, and both insert products
into the queue as a feedtype of WMO.  I'm guessing the IDS|HDS|DDPLUS
on the client end is something that ldmd or the stats gathering stuff is doing.

It's all running now, so I'm waiting to see if this fixes my problem...

Thanks for your help!

Steven


> Steven,
>
> The feedtype is designate at the product inject time, so if some products
> are injected as DDPLUS that will be the feedtype through the whole system.
> I suspect that one ingestor is using feedtype WMO and the other is using
> feedtypes IDS|DDPLUS|HDS.  The WMO feedtype is really an alias for
> feedtypes IDS|DDPLUS|HDS.  The SSEC NOAAport ingest splits the data stream
> into 2 types of feeds (text | binary), ie, IDS|DDPLUS and the other HDS.
> This also helps to make the pqact entries more efficient by eliminating
> the needs to check all the products in WMO. ie,
>
> IDS|DDPLUS  <pattern> <action> <params>
>
> HDS  <pattern> <action> <params>
>
> Robb...