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

20050610: LDM Latency Issues

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: 20050610: LDM Latency Issues
  • Date: Fri, 10 Jun 2005 08:42:16 -0600
>From: "Rhesa Freeman" <address@hidden>
>Organization: UND
>Keywords: 200506101422.j5AEMiZu001122 IDD CONDUIT

Hi Rhesa,

re: your CONDUIT feed
>We are currently connected to stokes.metr.ou.edu but we are experiencing
>latency between 4000 and 6000 seconds.  We're wondering if there is a
>different upstream host that we can connect to.  Thanks.

Please try feeding from atm.geo.nsf.gov (this is the machine that is
feeding stokes.metr.ou.edu the CONDUIT stream).  We will try to figure out
why stokes is experiencing latency problems with its CONDUIT feed.

>Rhesa Freeman
>Data Manager
>address@hidden
>University of North Dakota
>Regional Weather Information Center

Cheers,

Tom Yoksas
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.