Here's a weird thing - it looks like the forecast hours that were missing, are
eventually coming through at seemingly random times later on.
My 12 UTC and 18 UTC 1 deg GFS runs from today now look complete, but for the
12 UTC run, while most of the data came in between 9:30 and 11:07 AM CST
(1530-1707 UTC), the 72h forecast data came in around 00 UTC 25, the 96h
forecast data came in around 0337 UTC 25, the 126 came in around 1920 UTC 24,
the 189h came in around 1921 UTC 24, 240h came in at 0330 UTC 25,etc..
Maybe that's a clue?
Pete
<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx
________________________________
From: conduit <conduit-bounces@xxxxxxxxxxxxxxxx> on behalf of Pete Pokrandt via
conduit <conduit@xxxxxxxxxxxxxxxx>
Sent: Sunday, November 24, 2019 4:56 PM
To: Leuthold, Michael S - (leuthold) <leuthold@xxxxxxxxxxxxxxxxx>;
conduit@xxxxxxxxxxxxxxxx <conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] 20191123: Spotty CONDUIT reception last 24 hours
At UW-Madison AOS (we feed direct from NCEP) we continue to see complete
forecast hours for the hours that come through, but many (half a dozen is
typical) completely missing forecast hours.
Hopefully someone can take a look on the NCEP end on Monday.
Pete
<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>-----
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx
________________________________
From: conduit <conduit-bounces@xxxxxxxxxxxxxxxx> on behalf of Leuthold, Michael
S - (leuthold) <leuthold@xxxxxxxxxxxxxxxxx>
Sent: Saturday, November 23, 2019 12:20 PM
To: conduit@xxxxxxxxxxxxxxxx <conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] 20191123: Spotty CONDUIT reception last 24 hours
Arizona is also missing Conduit files. Our primary feed is Unidata.
Mike
On 11/23/2019 11:06 AM, Tyle, Kevin R wrote:
Thanks Tom ...
Hmm, this seems to contradict Pete's observation recently posted on the CONDUIT
list. Also, to add to the conundrum, UW-MSN is our primary upstream CONDUIT
feed ...
_____________________________________________
Kevin Tyle, M.S.; Manager of Departmental Computing
Dept. of Atmospheric & Environmental Sciences
University at Albany
Earth Science 228, 1400 Washington Avenue
Albany, NY 12222
Email: ktyle@xxxxxxxxxx<mailto:ktyle@xxxxxxxxxx>
Phone: 518-442-4578
_____________________________________________
________________________________
From: Unidata User Support
<support@xxxxxxxxxxxxxxxx><mailto:support@xxxxxxxxxxxxxxxx>
Sent: Saturday, November 23, 2019 12:23 PM
To: Tyle, Kevin R <ktyle@xxxxxxxxxx><mailto:ktyle@xxxxxxxxxx>
Cc: support-conduit@xxxxxxxxxxxxxxxx<mailto:support-conduit@xxxxxxxxxxxxxxxx>
<support-conduit@xxxxxxxxxxxxxxxx><mailto:support-conduit@xxxxxxxxxxxxxxxx>
Subject: 20191123: [conduit] Spotty CONDUIT reception last 24 hours
Hi Kevin,
re:
>I've noticed a bunch of missed products since yesterday afternoon on our CO=
>NDUIT feed. Anyone else?
The real-time stats volumes for both Unidata (conduit.unidata.ucar.edu)
and UW/AOS (idd-agg.aos.wisc.edu) are measurably less than for the same
times yesterday. FYI: both of these machines REQUESTs their CONDUIT
feed directly from NCEP.
Here are links to the CONDUIT volumes referred to above:
idd-agg.aos.wisc.edu
https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?CONDUIT+idd-agg.aos.wisc.edu
conduit.unidata.ucar.edu
https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?conduit.unidata.ucar.edu
My conclusion is that the products you note as being missed were never sent .
Cheers,
Tom
--
********************************************************************** <
Unidata User Support UCAR Unidata Program <
(303)497-8643 P.O. Box 3000 <
support@xxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxx>
Boulder, CO 80307 <
---------------------------------------------------------------------- <
Unidata Web Support http://www.unidata.ucar.edu/support <
---------------------------------------------------------------------- <
_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
conduit mailing list
conduit@xxxxxxxxxxxxxxxx<mailto:conduit@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit:
https://www.unidata.ucar.edu/mailing_lists/
