NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi, re: > Yes. I'm referring to the level3 (NEXRAD3) products. We noticed a drastic > decline at > about 1250Z. And the stats sites have now reappeared for me showing a large > drop at > about 13Z for NEXRAD3. We're trying to figure out if this was from source or > something > on our side. The latency plot for unidata1.cmc.ec.gc.ca shows what appears to be a network outage/hiccup/problem around the time you are referring to: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+unidata1.cmc.ec.gc.ca Since unidata1.cmc.ec.gc.ca feeds NEXRAD3 from our primary top level IDD relay cluster, idd.unidata.ucar.edu: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_topo_nc?NEXRAD3+unidata1.cmc.ec.gc.ca the question boils down to whether or not there was a marked decrease in NEXRAD3 products, or if the network latency was the sole cause of the decrease you are investigating. A check of a randomly selected real server back end of the idd.unidata.ucar.edu cluster (uni18.unidata.ucar.edu) does not show a decrease in NEXRAD3 products: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+uni18.unidata.ucar.edu it is safe to assume that the network event that is shown in the latency plot above was the cause for your decrease in NEXRAD3 products. What caused this network event can not be ascertained from the real time stats plots, but I can say that other machines that are feeding NEXRAD3 from idd.unidata.ucar.edu did not see the same decrease in products as you. Here is one example: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+chinook.unl.edu The fact that the NEXRAD3 volume plot from chinook.unl.edu exactly matches the volume plot from the randomly chosen real server back end machine above, uni18.unidata.ucar.edu, shows that there was no systematic problem with the NEXRAD3 feed from idd.unidata.ucar.edu. I would interpret this to mean that your problem was likely caused closer to your machine than to us. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: QRQ-873801 Department: Support IDD Priority: Normal Status: Closed =================== 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.