[IDD #GTQ-903655]: NOAAPORT on Feb 19ish

Hi Murray,

re:
> In general it's NOAAPORT2 but for example CXX_N0Q.

OK.

There did appear to be a slowdown in the receipt of the
N0Q product for CXX around 13:45UTC on 20190219:

-rw-r--r--  1 ldm ustaff 11127 Feb 19 07:04 Level3_CXX_N0Q_20190219_1403.nids
-rw-r--r--  1 ldm ustaff 11163 Feb 19 07:01 Level3_CXX_N0Q_20190219_1356.nids
-rw-r--r--  1 ldm ustaff 11026 Feb 19 07:00 Level3_CXX_N0Q_20190219_1349.nids
-rw-r--r--  1 ldm ustaff 11145 Feb 19 06:59 Level3_CXX_N0Q_20190219_1342.nids
-rw-r--r--  1 ldm ustaff 11183 Feb 19 06:57 Level3_CXX_N0Q_20190219_1336.nids
-rw-r--r--  1 ldm ustaff 11138 Feb 19 06:55 Level3_CXX_N0Q_20190219_1329.nids
-rw-r--r--  1 ldm ustaff 11192 Feb 19 06:23 Level3_CXX_N0Q_20190219_1322.nids
-rw-r--r--  1 ldm ustaff 11209 Feb 19 06:17 Level3_CXX_N0Q_20190219_1315.nids
-rw-r--r--  1 ldm ustaff 11255 Feb 19 06:10 Level3_CXX_N0Q_20190219_1308.nids
-rw-r--r--  1 ldm ustaff 11183 Feb 19 06:03 Level3_CXX_N0Q_20190219_1302.nids
-rw-r--r--  1 ldm ustaff 11136 Feb 19 05:56 Level3_CXX_N0Q_20190219_1255.nids
-rw-r--r--  1 ldm ustaff 11275 Feb 19 05:50 Level3_CXX_N0Q_20190219_1248.nids

The file times are in MST which is UTC-7.  The difference in the product
time and the time the product was written to disk before and including
06:23MST was on the order of 1-2 minutes.  At 06:55MST, the difference
grew to 26 minutes and then decreased back to around 1 minute at 07:04 MST.

So, the answer to your question is that yes, there was a slowdown in receipt
for the time period you asked about.

Comment:

The easiest way to investigate latencies being experienced in an IDD feed
is by reviewing the latency plot for your immediate upstream feed site
in the real-time statistics portion of our website:

Unidata HomePage
http:www.unidata.ucar.edu

  Data -> IDD Operational Status
  http://rtstats.unidata.ucar.edu/rtstats/

    Real-time IDD Statistics -> Statistics by Host
    http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex

Find the machine (or note of the cluster) from which you are
getting a feed and then check the latency for the feed in
question.

For instance, I believe you are feeding from the top level
relay cluster, idd.unidata.ucar.edu.  The real-server backend
machines in this cluster are named uni14.unidata.ucar.edu, ...,
uni24.unidata.ucar.edu.  Select any one of these at random,
and check the latency for the NEXRAD3 feed:

uni18.unidata.ucar.edu
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?uni18.unidata.ucar.edu

  NEXRAD3 -> latency
  
http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+uni18.unidata.ucar.edu

As you will see from the plot, we plot the latency values for about 2.5 days,
so you will need to visit the site before this time window advances past
the period you are interested in.

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: GTQ-903655
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.