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

Re: motherlode slowness

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: motherlode slowness
  • Date: Tue, 25 Sep 2001 14:18:57 -0600
Hi Daryl,

One other thing to consider when you're watching motherlode is that
there are two feed types that almost always have latencies.   

The NMC2 feedtype is a data stream out of NWS constrained by T1 line
that is too narrow for all the data.  It's consistently 40 to 60 minutes
late - you'll always see high latencies on that one.  

And, the FNEXRAD can be late due to the process involved in creating
that feed.  Periodically, someone at a remote site picks radar products
"of interest"  and after that there's processing involved to duplicate
the products from the NEXRAD feed onto the FNEXRAD feed.

Just a FYI.  It sounds like neither of these cases explain what you saw
yesterday.

Anne
-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************