So I've had a chance to look at this now - the files that are coming through
appear to be complete, but there are entire forecast hour files that are just
missing.
For the 12 UTC 20191123 GFS 1 degree data, we are missing the 15h, 87h, 162h,
168h, 303h and 354h forecasts completely. Everything else appears to be there.
For the 18 UTC 20191123 GFS 1 degree data, we are missing the 24h, 117h, 303h,
330h, and 348h forecasts completely. Everything else is there.
The missing forecast hours for the 0.5 deg GFS are different than for the 1
deg. for the 12 UTC 20191123 run I'm missing the 240h and 354h completely -
everything else appears to be there.
For the 18 UTC 20191123 0.5 deg GFS run, I'm missing the 51h, 72h, 108h, 225h,
249h, 267h, and 360h forecasts completely. everything else appears complete.
Definitely seems to be a problem on the ingest side.
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: Saturday, November 23, 2019 12:59 PM
To: Tyle, Kevin R <ktyle@xxxxxxxxxx>; support@xxxxxxxxxxxxxxxx
<support@xxxxxxxxxxxxxxxx>
Cc: GREGORY J TRIPOLI <tripoli@xxxxxxxxxxxx>; conduit@xxxxxxxxxxxxxxxx
<conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] 20191123: Spotty CONDUIT reception last 24 hours
Upon further review, we do seem to be having issues. Our 12 UTC GFS model
updates stopped at 12 UTC, but I don't know why, the files look the right size
and apparently were the size that was specified in the .status file, or else my
grib2 to grib1 conversions would have stopped working, and they all worked fine.
I have to leave in a few minutes and can't look further into this until tonight.
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 Tyle, Kevin R
<ktyle@xxxxxxxxxx>
Sent: Saturday, November 23, 2019 12:06 PM
To: support@xxxxxxxxxxxxxxxx <support@xxxxxxxxxxxxxxxx>
Cc: conduit@xxxxxxxxxxxxxxxx <conduit@xxxxxxxxxxxxxxxx>
Subject: Re: [conduit] 20191123: Spotty CONDUIT reception last 24 hours
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
Phone: 518-442-4578
_____________________________________________
________________________________
From: Unidata User Support <support@xxxxxxxxxxxxxxxx>
Sent: Saturday, November 23, 2019 12:23 PM
To: Tyle, Kevin R <ktyle@xxxxxxxxxx>
Cc: support-conduit@xxxxxxxxxxxxxxxx <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 Boulder, CO 80307 <
---------------------------------------------------------------------- <
Unidata Web Support http://www.unidata.ucar.edu/support <
---------------------------------------------------------------------- <
