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

Re: data feed source request

Hi Chuck, 

I am sorry I have strung you along..

The issue is that we prefer to have only one feed per institution, this
eliminates chewing up bandwidth, that is why we have you feed from:


Which feeds directly from motherlode or thelma (our machines) and fails to

In theory, this should be sufficient for you as well, since you feed from:

However, I see ldm.meteo.psu.edu has had some latency issues lately.

We may want to investigate deeper the initial feed to PSU. 

 Pennsylvania State


 Pennsylvania State
 EMS Environment


 Pennsylvania State
 Meteorology Research

This is what PSU currently has running per our records, with
ldm.meteo.psu.edu being the "master" server. If one of the other dept's
has a faster/bigger machine we may want to re-evaluate the structure of
the feed.


Any input? I was seeing some strange NNEXRAD requests from
ldm.meteo.psu.edu it appeared as if you were only getting radar from
FTG|CYS|GJX but being a top tier NNEXRAD site:


For clarification:

navierldm.meteo is now ldm.meteo right?

It would be advisable to request NNEXRAD ".*" so downstream sites could
choose a smaller subset.

I know with the NMC2 (conduit) feed volume factors into the equation..

Thanks everyone,

____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
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, 1 Aug 2002, Charles Pavloski wrote:

> Hi Jeff,
> I am seeing at least one stream (nexrad) at this point from 
> ldm.meteo.psu.edu, so
> I guess we should go ahead and setup the failover server your leisure.
> Thanks
> Chuck P.