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

Re: 19990322: ldm problem

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 19990322: ldm problem
  • Date: Fri, 26 Mar 1999 11:09:22 -0700 (MST)
On Fri, 26 Mar 1999, Clint Rowe wrote:

> Robb:
> 
> 
> > 
> > Clint,
> > 
> > The reason for the 3 different sources is that the 3 top tier nodes feed
> > each other from their own satellites. It's a race condition on what source
> > a product will come from.  This is why the IDD is robust. This is good
> > because it shows all the system are operating, it doesn't mean you are
> > getting duplicates.  The only way a duplicate should show up at your site
> > is if a upstream site is receiving FOS and NOAAport. The products don't
> > match because the sequence numbers are different even though the rest of
> > the product is exactly the same, the ldm thinks they are different
> > products. I know this is confusing.
> > 
> 
> 
> Okay, I understand why there are multiple feeds, but it still doesn't
> explain why I'm still getting duplicates.  When I watch the feeds, all the
> products have the 999 code indicating their from NOAAport, not FOS (correct?).
> But when I looked in the files being stored, there were duplicate entries
> throughout.
> 
> I started looking at my pqact.conf file for clues as to how duplicate entries
> could be generated and I think I found an answer.  BN (before NOAAport), I
> had duplicate entries in pqact.conf -- one for domestic products and one for
> international products with the same header.  I don't know why it was like 
> this,
> I'm pretty sure that's how I grabbed it out of Unidata pqact.conf examples.
> Anyway, AN (after NOAAport), with products being labelled IDS|DDPLUS in the
> data stream, it appears that they get processsed by both entries in 
> pqact.conf.
> Eliminating one entry and changing the feedtype to WMO seems to have done the
> trick.

Clint,

You are correct, the ldm must be considering IDS|DDPLUS as one feedtype.
This will change when the NOAAport feedtypes are created in the future.

Thanks for looking into this,
Robb...


> 
> ====================================================================
> Clinton M. Rowe
> Associate Professor 
> Meteorology/Climatology Program                  phone:(402)472-1946
> Department of Geosciences                          fax:(402)472-4917
> University of Nebraska-Lincoln                  address@hidden
> 

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