Re: 19990923: LDM feed at Valparaiso U.

On Thu, 23 Sep 1999, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >From: Jon Schrage <address@hidden>
> >Subject: LDM feed at Valparaiso U.
> >Organization: Purdue University
> >Keywords: 199909231958.NAA13970 IDD
> 
> 
> Hello.  This is Prof. Jon Schrage at Valparaiso University.
> 
> I've recently "inherited" the job of taking care of our LDM feed, and it
> looks like we have been having lots of troubles for a long time.  I've
> heard complaints that we hardly ever get any data, but now I see that
> our latencies are absolutely terrible.
> 
> Here's an example of one of our .stats files:
> 
> 19990923185736 IDS|DDPLUS           dusk.ssec.wisc.edu        305
> 361803
> 3620.95 3673@4229 19990923195829
> 19990923185735 IDS|DDPLUS    noaaport.unidata.ucar.edu        677
> 523041
> 3616.34 3660@0341 19990923195715
> 19990923185900 IDS|DDPLUS              nport.alden.com        966
> 715876
> 3576.37 3650@5900 19990923195950
> 19990923181745    FSL2            dion.fsl.noaa.gov          1
> 172188    373
> 4.98 3735@1745 19990923192000
> 19990923185446    NLDN     striker.atmos.albany.edu         10
> 23212    358
> 5.69 3604@3038 19990923195424
> 
> Okay, that didn't paste in too well, but you'll notice that, this hour,
> NO McIdas Area Files showed up.  Lots of other products were way behind,
> too.  This is quite typical.
> 
> To be blunt, I'm not sure where to start with all of this.  I worked
> (and continue to work) at Purdue as a researcher/system-admin/data guy
> after Dan Vietor left, so I'm not totally stupid about all this stuff,
> but I have to admit that I've never come across a system with so many
> networking problems.
> 
> Any advice (contacts, whatever) would be greatly appreciated.
> 
Jon,

I agree with you this has been a problem for a long time. Since, I believe
the main source of the problem is you network connection/banwidth.  The
first thing is either to contact your network folks or ISP about the poor
reception rate.  Also, I would only request the data that you really need.

Here's an URL of all the NOAAport products:

http://www.nws.noaa.gov/noaaport/html/data.shtml


To reduce the number of products at your site, you need to specify the
product patterns you want in the request line of the etc/ldmd.conf file,
ie

request  WMO  "^[A-I]"  feeder.site.edu

In this example, you  would get all products that start with A to I. The
patern can be any regular expression. Also, WMO can bee broken down
into it's sub feed types, DDS, PPS, IDS, and HDS on individual request
lines to the same feeder site. Here's an URL to help with RE if you need
it.

http://www.unidata.ucar.edu/packages/ldm/ws/ldm_patterns.html#s12

Robb...

> Jon Schrage
> address@hidden
> 
> =======================================
> Assistant Prof. of Meteorology --> Valparaiso University
> Postdoc. Research Assistant --> Purdue University
> 
> 
> 
> 
> ------- End of Forwarded Message
> 

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