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
.
From: conduit <address@hidden> on behalf of Herzmann, Daryl E [AGRON] <address@hidden>
Sent: Wednesday, October 28, 2020 11:55 AM To: address@hidden <address@hidden> Cc: address@hidden <address@hidden> 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 */ |
_______________________________________________ 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 address@hidden For list information or to unsubscribe, visit: https://www.unidata.ucar.edu/mailing_lists/