NOAA is aware of the issue, and has it on their list to fix. I spoke via email
with them today, and they said that due to resource constraints, the IT team
that is designated to resolve this issue is still about a month away in getting
freed up.
The person I spoke with said if we don't hear anything by after Thanksgiving, I
should contact her again.
FYI.
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 Herzmann, Daryl E
[AGRON] <akrherz@xxxxxxxxxxx>
Sent: Wednesday, October 28, 2020 11:55 AM
To: conduit@xxxxxxxxxxxxxxxx <conduit@xxxxxxxxxxxxxxxx>
Cc: ncep.list.pmb-dataflow@xxxxxxxx <ncep.list.pmb-dataflow@xxxxxxxx>
Subject: [conduit] CONDUIT LDM Clock Drift
Greetings (emailing the right list this time!),
It has been mentioned a few times on this list that there is a clock drift
issue with the CONDUIT LDM feed emitting from NCO/IDP. I'd like to ping this
issue again and see if NCO can please check that system clocks are being synced
there. The attached plot of feed latency shows the building of latency with
time from my monitoring, which is a tell tale sign of clock drift .
thanks!
daryl
--
/**
* daryl herzmann
* Systems Analyst III -- Iowa Environmental Mesonet
* https://mesonet.agron.iastate.edu
*/