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

Re: 19990716: CONDUIT latencies (fwd)

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: 19990716: CONDUIT latencies (fwd)
  • Date: Tue, 20 Jul 1999 07:55:56 -0600 (MDT)

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

---------- Forwarded message ----------
Date: Tue, 20 Jul 1999 08:46:04 -0500 (CDT)
From: "Robert R. Mullenax" <address@hidden>
To: "David J. Knight" <address@hidden>
    address@hidden
Subject: Re: 19990716: CONDUIT latencies


That would probably explain why we never received the MRF in
any siginificant amount when we tried the NMC2 feed, our
T1 is just too small, and the chances of us getting a T3 are
about the same as me being elected President.  So it probably
would not have mattered how close to the feed source we were.

Robert Mullenax