Re: 20011218: LDM and duplicate products

Gregg, 

DPA products have always been part of the HRS feed,
as well as the RCM products (SDUS4x).


-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-COMET Case Study Library                  FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Thu, 20 Dec 2001, Gregory Grosshans wrote:

> I was looking for 'already' and 'product' in the ldmd.log file and didn't
> find any occurrences.  Its not creating any unique problems (e.g. dup product
> in same directory).
> 
> Via the NOAAPORT feed I inject the single site radar products into the LDM
> queue as feedtype 'NNEXRAD' using the pq_insert call.
> 
> Via the UNISYS feed I inject the single site radar products into the LDM
> queue using pqinsert with the feedtype of 'WSI'.
> 
> From the NOAAPORT feed I strip off the NOAAPORT CCB and WMO header so the
> product is exactly the same as the UNISYS product.   It turns out products
> from the NWS Multicast feed do not have WMO headers or the CCB header (a
> NOAAPORT header).
> 
> I'm running LDM-5.1.2 on HPUX.
> 
> On a radar related note, does the NNEXRAD feed in the IDD contain the DPA
> product (SDUS8i)?
> 
> Thanks,
> Gregg
> 
> Jeff Weber wrote:
> 
> > Hi Gregg,
> >
> > It appears that if the duplicate entry was delivered via pqinsert, you
> > would see a "Product already in queue" in your ldmd.log file...However, if
> > the duplicate is received via pqing, it may not show in the
> > logs...generally, the products off the dish (via pqing) should arrive
> > first, and I am not certain if the duplicates would be logged via that
> > scenario..
> >
> > What are you looking for in your logs?
> >
> > Are you grepping "product already in queue" ?
> >
> > Is this creating any unique problems (i.e. duplicate products being filed
> > in same dir?)
> >
> > Let me know if you see anything like "product already in queue" in your
> > ldmd.log files.
> >
> > If not, and you are not getting duplicates filed, we will need to
> > investigate further..and dig deeper into the code.
> >
> > Thank you,
> >
> > -Jeff
> > ____________________________                  _____________________
> > Jeff Weber                                    address@hidden
> > Unidata Support                               PH:303-497-8676
> > NWS-COMET Case Study Library                  FX:303-497-8690
> > University Corp for Atmospheric Research      3300 Mitchell Ln
> > http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
> > ________________________________________      ______________________
> >
> > On Tue, 18 Dec 2001, Unidata Support wrote:
> >
> > >
> > > ------- Forwarded Message
> > >
> > > >To: address@hidden
> > > >From: Gregory Grosshans <address@hidden>
> > > >Subject: LDM and duplicate products
> > > >Organization: UCAR/Unidata
> > > >Keywords: 200112181622.fBIGMBN10222
> > >
> > > What feature in LDM controls the logging mechanism to indicate a
> > > duplicate product has been received?   I expect single site radar data
> > > to be dup'ed but do not see it in ldmd.log, even with increasing the
> > > verbosity of the pqact by 1, via 'kill -USR2 {pqact pid}.
> > >
> > > I'm ingesting a UNISYS radar feed (consisting of single site and mosaic
> > > imagery) into LDM with a feedtype of 'WSI' via pqinsert.  The single
> > > site radar products from NOAAPORT (SDUS[2357]i)  are inserted into the
> > > LDM queue via the pq_insert call as feedtype 'NNEXRAD'.   With the
> > > NOAAPORT feed I strip off the CCB and WMO Header so the product looks
> > > just like it does from the Unisys feed (and the NWS radar multicast
> > > feed).
> > >
> > > I've stored a product receive via UNISYS and via NOAAPORT and they are
> > > identical, byte for byte.
> > >
> > > Thanks,
> > > Gregg Grosshans
> > > SPC
> > >
> > >
> > > ------- End of Forwarded Message
> > >
> > >
> 
>