Stories
Slash Boxes
Comments

SoylentNews is people

posted by cmn32480 on Friday December 30 2016, @05:08PM   Printer-friendly
from the like-this-year-hasn't-been-long-enough dept.

Phys.org (among many other sites) is reporting on a leap second being added before the end of 2016:

As if 2016 has not been long enough, the year's dying minute will last an extra second to make up for time lost to Earth's slowing rotation, timekeepers say.

Countries that use Coordinated Universal Time—several West African nations, Britain, Ireland and Iceland—will add the leap second during the midnight countdown to 2017—making the year's final minute 61 seconds long.

For others, the timing will be determined by the time zone they live in, relative to UTC.

"This extra second, or leap second, makes it possible to align astronomical time, which is irregular and determined by Earth's rotation, with UTC which is extremely stable and has been determined by atomic clocks since 1967," the Paris Observatory said in a statement.

The observatory houses the International Earth Rotation and Reference Systems Service (IERS), responsible for synchronising time.

"The sequence of dates of the UTC second markers will be: 2016 December 31 23h 59m 59s, 2016 December 31 23h 59m 60s, 2017 January 1, 0h 0m 0s," the IERS website states.

Here is the original IERS announcement. There have been times in the past when the addition of a leap-second caused havoc — it is non-trivial to update the clocks on all the systems in an organization at the same time. When activity "A" happens before activity "B", but because of inconsistent system clocks the timestamps imply otherwise, things can go sideways in a hurry.


Original Submission #1Original Submission #2

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by requerdanos on Saturday December 31 2016, @01:50AM

    by requerdanos (5997) Subscriber Badge on Saturday December 31 2016, @01:50AM (#447718) Journal

    Maybe once the error accumulates to 10 minutes or more in a few centuries, we can deal with a correction.

    Let me get this straight. You are proposing replacing the inconvenient leap second with the supposedly more workable ten leap minutes?

    Re:Simple solution is not so simple

    Mmm hmm.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by AthanasiusKircher on Saturday December 31 2016, @06:43AM

    by AthanasiusKircher (5291) on Saturday December 31 2016, @06:43AM (#447781) Journal

    You are proposing replacing the inconvenient leap second with the supposedly more workable ten leap minutes?

    Actually, no. What I'm proposing is that we postpone this problem so far into the future that it's very unlikely anyone will give a darn about "mean solar time" by that point as a "universal" time standard. A few centuries in the future, we'll either all be run by AIs, have folks living on other planets so the idea of UTC would be rather meaningless, or whatever. Also, most people will likely adjust their schedules to the gradual drift of clocks over time, so nobody would even care to "correct" that 10 minutes, just as most people don't care about the DST shift a week or two after it happens.

    Even if we wanted for some bizarre reason to "fix" that problem in that far future -- by the time this ACTUALLY becomes a problem that the clocks are far enough off that anyone would give a damn, the earth's rotation will likely have slowed to the point that adding leap seconds is going to become a regular occurrence, so the current UTC system will ALREADY seem like an unworkable permanent solution. (It already IS an unworkable solution for the true long-term -- thousands of years -- due to the fact that we KNOW the earth's rotation will slow down, and at some point we WILL need more than an extra second per month.) Adding in 10 minutes or whatever by that point will be the LEAST of our problems.

    Also, we already have a time standard that tracks astronomical noon. It's called UT1. (Technically, the definition is a little more complicated than that, but there it is.) UTC is meant to be a pragmatic time standard that's precise enough for common, everyday people to use. Common everyday people don't care whether their clocks are off from solar zenith at Greenwich or whatever by a few seconds or a few minutes. Tinkering with the timeline on a variable basis every month (right now it has only happened in June or December, but theoretically could happen in other months) is a huge issue that will itself become obsolete too. Whether we continue the UTC plan for the next few centuries or not, we'll still have to face choices about changing implementation eventually.

    In the meantime, perhaps we can just dispense with a pain-in-the-ass half solution that is only convenient for observatories and very inconvenient for just about everyone else who designs a computer system which might be sensitive to arbitrary introduction of extra seconds. (Or removal of! Let's not forget that the current UTC standard allows skipping a second too! We haven't had the need yet, but given the variability in earth's speed, it could happen. How many systems will break when that wacko scenario happens, because nobody read the detailed timespecs and realized they might need to DELETE a second!)

    And maybe enough astronomers do benefit from having something that isn't quite as precise as UT1 but is as arbitrarily variable (but not more than a second) like UTC. That's great. Let them have their own time standard too. But why again are we ALL coupling our clocks to THAT standard for the 99.99% of computers and other systems that don't care when solar zenith occurs at Greenwich??

    • (Score: 0) by Anonymous Coward on Saturday December 31 2016, @08:34PM

      by Anonymous Coward on Saturday December 31 2016, @08:34PM (#447939)

      Leap seconds are a non problem for average people who do not operate to the precision of one second nor to the accuracy of one second per year. Only computers care and we have hacks to handle that situation. The first rule before taking action should be: don't make the situation worse!

      Anyone who truly cares about precision timekeeping already has a proper solution; the others don't care enough for a new system system em implemented.