3 ms·
Can someone ELI5? The Tweet and the "This will cause no issues" feels tongue-in-cheek and the gif suggests there will most likely be issues.
by Nexxxeh 5y ago
Can someone ELI5? The Tweet and the "This will cause no issues" feels tongue-in-cheek and the gif suggests there will most likely be issues.
- heythere22 5y agoAs far as I understand it, the GPS time will stop for 1 second. This means that between ex. 12:00:00 and 12:00:00' there is a wall clock difference of 1 second. The first issue has already been found: https://twitter.com/uputronics/status/1418990637299519493 https://twitter.com/uputronics/status/1418990637299519493
- user-the-name 5y agoNo, GPS time will not stop, and that is the issue. What you describe is a regular leap second, but now for some reason GPS is broadcasting that it will have a leap second that doesn't actually do anything.
- beerandt 5y agoGPS specs a specific window (the broadcast message bit positions) in the ephemeris for specifying leap seconds, so that data window has to be filled with a value, even if it's zero. The issue is that only certain defined gps weeks use those bits for that purpose (when to actually apply the upcoming leap second), and it doesn't happen that often. But anyone who assumed that an upcoming leap second message implies a non-zero value hasn't done their basic homework. It's a regularly recurring message, not only done when required.
- kaydub 5y ago> This will cause no issues It will most certainly cause some issues. I worked somewhere that sold a software appliance back in the day. This software appliance did a bunch of ETL and ran analytics processes. We had a leap second that caused all the ETL jobs to stop working. 400 some appliances in different data centers that we had some connectivity through a VPN. It was not a fun experience but it has always kept leap seconds and time problems in the front of my mind.