Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

US DoD Poll On Leap Seconds

Posted by kdawson on Mon Sep 08, 2008 05:59 PM
from the great-leap-forward dept.
@10u8 writes "For time scales to leap, or not to leap, has been the question here before. The ITU-R will be considering leap seconds again in a few weeks. This week the USNO posted a survey about leap seconds by the US DoD. The issue has civil implications as well as technical ones, and there is a demonstrated way to respect the history, remove leaps from navigation and POSIX time, yet keep the sun overhead at noon."
+ -
story

Related Stories

[+] The Future of Leap Seconds 429 comments
@10u8 writes "Since 1972 precision clocks around the world have ticked using atomic seconds, but earth rotation is slowing down. Leap seconds have been inserted in order to keep noon happening at noon, but they upset some timekeepers. Recent discussions have considered discontinuing leap seconds in UTC, and a colloquium in Torino next month will present results. It is a matter of international significance."
[+] U.S. Moves to Kill Leap Seconds 601 comments
blacklite001 writes "Not content with merely extending Daylight Savings Time, the U.S. government now also proposes to eliminate leap seconds, according to a Wall Street Journal story. Their proposal, 'made secretly to a United Nations body,' includes adding 'a "leap hour" every 500 to 600 years.' Hey, anyone remember the last bunch of people to mess with the calendar?"
[+] Vote To Eliminate Leap Seconds 531 comments
Mortimer.CA writes "As discussed on Slashdot previously, there is a proposal to remove leap seconds from UTC (nee 'Greenwich' time). It will be put to a vote to ITU member states during 2008, and if 70% agree, the leap second will be eliminated by 2013. There is some debate as to whether this change is a good or bad idea. The proposal calls for a 'leap-hour' in about 600 years, which nobody seems to believe is a good idea. One philosophical point opponents make is that the 'official' time on Earth should match the time of the sun and heavens."
[+] News: Leap Second To Be Added Dec 31, 2008 255 comments
ammorris writes "Don't be the laughingstock of your friends when you shout 'Happy New Years' a second too early ... The International Earth Rotation and Reference Systems Service has announced that a leap second will be added on December 31, 2008 at 23h 59m 60s, meaning that this year will be exactly one second longer. The last leap second occurred Dec 31, 2005; they are added due to fluctuations in the rotational speed of the earth. You can read all about leap seconds on Wikipedia."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by NoobixCube (1133473) on Monday September 08 2008, @06:03PM (#24926697) Journal

    I thought we had leap years to take care of the discrepancy between our calendar and the actual orbit around the sun. Would a leap second even be made longer by any noticeable amount? What about sporting events? Someone who misses out on a world record by a tiny bit would complain that the record h older had more leap seconds in his race! (Okay, that one was a joke, but the rest I'm serious about)

    • by Anonymous Coward on Monday September 08 2008, @06:05PM (#24926723)

      Compare absolute time vs relative time vs elapsed time vs hammer time...

    • Re: (Score:3, Insightful)

      The leap seconds do the same thing as the leap years (each leap day moves the calendar closer to the orbit, but not exactly to the orbit).

    • by EmbeddedJanitor (597831) on Monday September 08 2008, @06:10PM (#24926771)
      Leap days correct our orbit around the sun to keep December/January in the middle of winter for the Northern Hemisphere.

      Leap seconds correct for the rotation of the earth to keep the sun above at noon.

      If we dispense with leap seconds then this relationship will slowly change and noon will eventually be dark.

      • I suppose I'd know that if I'd R'd TFA... :P

        • Keeping leap seconds synced is pretty important across comms networks.
            • by snowraver1 (1052510) on Monday September 08 2008, @07:21PM (#24927489)
              Not surprised, there is really no need to. Your GPSr doesn't care what time it is in human terms, it just needs a number that it can use to caclulate signals relative to each other. That could be anything, possibly even the number of seconds that have passed since 1970.

              I would be more surprised if they acutally didupdate GPS satellites with leap second fixes. I would think you would have to recilibrate all the satellites.

              *Note* I do office magic, not satellite magic.
              • Re: (Score:3, Informative)

                Not surprised, there is really no need to. Your GPSr doesn't care what time it is in human terms... I would be more surprised if they acutally didupdate GPS satellites with leap second fixes.

                Actually that is one of the jobs of the US Naval Observatory. They constantly update the GPS satelights time and position information. If you have a hand held gps receiver you have an atomic accuracy clock in your hand. The USNO mission is to: 2 Provide astronomical and timing data required by the Navy and other components of the Department of Defense for navigation, precise positioning, and command, control, and communications. http://www.usno.navy.mil/mission.shtml [navy.mil] If you have one clock you know the t

            • by digitig (1056110) on Monday September 08 2008, @07:24PM (#24927517)

              That's correct, because correcting the epoch for leap seconds would cause glitches in positioning as the corrections were applied. Instead, GPS broadcasts a UTC correction so the receiver can convert to UTC if required: ahref=http://www.navcen.uscg.gov/pubs/gps/sigspec/gpssps1.pdfrel=url2html-16574 [slashdot.org]http://www.navcen.uscg.gov/pubs/gps/sigspec/gpssps1.pdf>

      • Re: (Score:3, Interesting)

        Leap days correct our orbit around the sun to keep December/January in the middle of winter for the Northern Hemisphere.

        While true, that is the intent, has any one noticed that this has failed over the last 20 years or so? When I was a child, Winter was Winter, and the first snow fall in the Northeast was usually by Thanksgiving. Over the past couple decades, the first snowfall seems to be pushing itself into late January, mid-February. Used to be, the harshest part of Winter was Dec-Jan, now it seems firmly seated in February. And why is it every year we see an Indian Summer smack in the middle of Winter? By my reckoning, w

      • Yep... (Score:5, Insightful)

        by msauve (701917) on Monday September 08 2008, @06:42PM (#24927133)
        and if anyone doesn't like leap seconds, all they have to do is use one of the time scales which don't use them, like TAI [wikipedia.org].

        It's exceedingly silly and stupid for people to keep trying to change UTC [wikipedia.org] so it doesn't track solar time. That what it was intended to do. If you made the wrong choice, live with it, or change time scales. If it's being forced on you, quityerbitchin', and convince whoever decided on UTC to change. Stop trying to turn UTC into something it isn't, there are other people out there who made an intelligent decision, and depend on it's characteristics.
      • by Dannkape (1195229) on Monday September 08 2008, @07:29PM (#24927555)
        According to wikipedia, there seems to have been 24 leap seconds in the last 36 years. For solar noon to move a single hour away would take over 5 millenia.

        Of course, they do give the news something harmless to report on every once in a while...
      • by CorporateSuit (1319461) on Monday September 08 2008, @07:50PM (#24927739)

        If we dispense with leap seconds then this relationship will slowly change and noon will eventually be dark.

        In that case, we rename "noon" to "midnight", and "midnight" to "noon"
        then "AM" can mean "After-Meridian" and "PM" can mean "Pre-Meridian"
        I thought of everything. Problem solved forever.

        • Re: (Score:3, Interesting)

          The trouble with that is twofold:

          1. Ordinary people who don't take note of such things can have their clocks be off by a second (or even a few) and still get along in their ordinary lives. That would not be the case if the government announced that there was going to be a leap hour inserted this year and they missed it.

          2. Any semi-periodic event that must be noted and accommodated by the general public that cannot be calendared years in advance is virtually guaranteed to be a snarling mess.

  • Not quite (Score:5, Informative)

    by Deadstick (535032) on Monday September 08 2008, @06:04PM (#24926709)
    there is a demonstrated way to...keep the sun overhead at noon.

    No there isn't, but you can make it culminate at noon.

    rj

    • Yeah, but anyone close enough to give the sun a nooner would get burned up.
      • Re: (Score:3, Informative)

        It's rare for the sun to be directly overhead anywhere, and impossible outside the Tropics. At noon local standard time (assuming the leap-second problem has been taken care of, per the thread topic), it culminates for an observer on the base meridian of the time zone. It always culminates at noon local solar time -- which is a bit of a tautology, because local solar time is computed from the time when it culminates.

        rj

  • by wealthychef (584778) * on Monday September 08 2008, @06:07PM (#24926731)
    I'd be more interested in killing Daylight Savings Time than dealing with Leap Year.
    • DST can be "fixed" by recording time in UCT. No such "fix" exists for leap seconds. With leap seconds, you're getting down to the fundamentals of how time is recorded, not how it is translated to local time.

    • by BitterOldGUy (1330491) on Monday September 08 2008, @06:13PM (#24926839)

      I'd be more interested in killing Daylight Savings Time than dealing with Leap Year.

      My cat wakes me up in the morning. She doesn't adjust. Because of her, I'm a morning person. Unfortunately, 90% of society are night people. Meaning, any social activity is past my bedtime and I become a wet blanket because I start yawning at everything at 20:00.

      • by Anonymous Coward on Monday September 08 2008, @06:21PM (#24926929)

        I think your REAL problems are as follows:

        You have a cat.

        Your cat controls you.

        You characterize and categorize people (90%, society, night people) in terms of what they can give you (social activity).

        You speak in military (24 hour) time unnecessarily.

        You admit your own faults, but rather than fix them, you prefer to revel in your own meekness.

        • by BitterOldGUy (1330491) on Monday September 08 2008, @06:54PM (#24927241)

          I think your REAL problems are as follows:

          You have a cat.

          Your cat controls you.

          You characterize and categorize people (90%, society, night people) in terms of what they can give you (social activity).

          You speak in military (24 hour) time unnecessarily.

          You admit your own faults, but rather than fix them, you prefer to revel in your own meekness.

          Dogs have masters.

          Cats have servants.

          I recognize my overlord and serve her. And as a result, my life is filled with a wondrous furry glory!

          The Egyptians worshiped cats as gods and the cats have never forgotten that.

          Military time is also computer server time. And if you deal with computers across at least one time zone you may want to use Zulu time too. Oooooo, I used another military term. You know why!? Because, I serve in the army of cats!

    • by Kjella (173770) on Monday September 08 2008, @06:32PM (#24927035) Homepage

      Killing it? I want to change them completely, and wintertime too. Now, I live a bit further north than most people (60 degrees latitude) and what happens in the winter is that I, like most people, head to work in the dark and come home in the dark. Maybe you get to see some sun on your lunch break, but unless you got an office with a view you won't see much of it otherwise. If we have like 6 hours of sun, they should be 4PM-10PM so you can do some outdoor activity after work. What happens now is I sit indoors during the day because of work, and I sit indoors in the evenings because it's dark and cold outside. I haven't got any stats to back it up but I'd think most people work indoors these days, the reason to have light == noon so you could run around outside just isn't there. I'd be happy with mornings that suck (some more) and evenings that were bright and nice all year round.

  • by jayveekay (735967) on Monday September 08 2008, @06:18PM (#24926893)

    We don't need even one more second of Bush presidency. :)

  • I know! (Score:5, Funny)

    by tnk1 (899206) on Monday September 08 2008, @06:52PM (#24927225)

    Let's just remove the problem entirely!

    I suggest... the French Republican calendar.

    And a good Tridi, 23 Fructidor, Year 216 to you too.

  • by k1e0x (1040314) on Monday September 08 2008, @06:58PM (#24927283) Homepage

    I don't understand what the DoD has to do with time, standards or measurements.

    Is the DoD trying to say now Muhahaha! Now we control time itself, submit all ye to "civilian time"?

    We need to get the opinion of an expert, not some random poll.. perhaps the DoD should seek the advice of the master of timecube theory Dr. Gene Ray.

    • by John Hasler (414242) on Monday September 08 2008, @08:06PM (#24927875)

      I don't understand what the DoD has to do with time, standards or measurements.

      Navigation depends on time. The Navy is very interested in navigation. That's why they established the Naval Observatory [navy.mil] in 1830.

      We need to get the opinion of an expert, not some random poll..

      USNO employs some of the formost experts on the subject. They are soliciting the opinions of some of the other stakeholders.

  • by PPH (736903) on Monday September 08 2008, @09:21PM (#24928403)
    What significance does this have for people who live in their parents' basement?
    • by klapaucjusz (1167407) on Monday September 08 2008, @06:27PM (#24926991) Homepage

      There should be a planned algorithm that kicks in,

      This assumes that we know when, in the future, we'll need to insert leap seconds. And we don't.

      Leap seconds are introduced in order to compensate for medium-term variations in the earth's rotation speed. We don't have a good understanding of the way the earth rotates -- knowing what UTC time it will be in ten years' time is about as difficult as predicting the weather for next week-end.

        • by techno-vampire (666512) on Monday September 08 2008, @09:19PM (#24928387) Homepage
          More to the point, it appears to average out, so we could be inserting them just to have to remove them a decade later.

          No they don't. If you'll look at the chart in the Wikipedia article, [wikipedia.org] you'll see that since they started using them in 1972, they've never had to subtract a second. Either no change, or +1 second.

        • by Starker_Kull (896770) on Tuesday September 09 2008, @12:11AM (#24929435)

          More to the point, it appears to average out, so we could be inserting them just to have to remove them a decade later.

          No, they don't. The Earth's rotation rate is slowing due to tidal friction (and slowly pushing the moon away in the process, since angular momentum doesn't just vanish). The SI second was set based off of the average solar day back in the 1700's or so, and the Earth's average rotational period has slowed measurably since then. We have only added leap seconds, never subtracted them, and likely never will, despite a significant variation in the rate of slowing.

          The problem is that we want to measure different periodic processes via the same unit - the second. The second was originally based off of the average length of the solar day, but then was redefined in terms of atomic standards. The average solar day, according to atomic standards, has been lengthening somewhat erratically. Either we give up using the second as a fundamental unit in the SI system, suitable for meausring times vast and small, or we give up having our clocks based on the second but choose some other 'variable' unit, synced to the sun (such as UT1 time), or we compromise and stick a leap second in from time to time to assure that UTC and UT1 remain within a second of each other - which is what is currently done. There really isn't an easy way out since the periodic processes of nature that matter to us are not neatly in ratios. Do we really want a 'science' time, and a 'civilian' time?

          As you say, one day, programmers will wrap these difficulties up in libraries nicely and neatly so that it just 'works', but it will be based on an arbitrary table of leap seconds, much like we have an arbitrary table of time zone rules in our zoneinfo files. Part of the problem was due to the POSIX standard for time NOT being done properly. UTC actually specifies that the 'extra' second means that there are 61 seconds in a particular minute - i.e. 23:59:60 is a valid UTC time when a leap second is inserted. Unfortunately, POSIX time 'repeats' a second instead. POSIX time goes.... 23:59:57....23:59:58.... 23:59:59.....(zip! leap second!) 23:59:59.... 00:00:00.... 00:00:01... etc.

          There are some complex tradeoffs associated with this. It simplifies the numerical calculation of traslating POSIX time (since POSIX time really is represented as the integer number of seconds since 1970-Jan-01 00:00:00, and the leap seconds are ignored) to 'clockface' time (i.e. The year, month, date, hour, minute and second). On the other hand, it yields incorrect answers when two POSIX times are naively subtracted to figure out the time delta between the time marks; one has to modify the 'obvious' subtraction algorithm with a somewhat complex lookup table procedure to get an accurate delta. UTC is more complex because the occassional 61 second minute requires that you consult a lookup table to translate UTC seconds to year-month-date-hour-minute-second form, but subtraction easily yields the correct delta between the time marks. If we want to stick with SI seconds and schedule ourselves with the sun, there will always be some messiness!

    • by John Hasler (414242) on Monday September 08 2008, @06:36PM (#24927075)

      > There should be a planned algorithm that kicks in, and the simplest one that actually
      > does the job should be used.

      There is none. The rate of rotation of the Earth is slightly irregular in a not entirely predictable way.

      > I don't think I even own a time keep device where this level of accuracy matters.
      > Perhaps my GPS?

      Definitely your GPS. It cares about nanoseconds.

        • by NF6X (725054) on Monday September 08 2008, @10:30PM (#24928873) Homepage

          Definitely your GPS. It cares about nanoseconds.

          But so long as all the satellites are in sync with their atomic clocks showing the same time, does it matter??? Even without them being in sync, doesn't the GPS use time and rough location to locate the satellites (unitil it's logged on) and then isn't it the round trip time taken by signal that's being measured? Is there any dependancy on leap seconds?

          GPS doesn't use UTC for its measurements; it uses its own system of GPS time for its measurements, and then calculates UTC using a correction value transmitted by the satellites in order to be able to display UTC (or any other UTC-derived time) for the user.

          Also, it doesn't "log in" in any usual sense, as the communication is purely one-way, from the satellite broadcasts to the receiver. Thus, it also doesn't measure round trip time, because there is no round trip. What it does is to receive the signals from multiple satellites, each of which essentially transmits a signal saying "I'm satellite number A, my location is B, and the time is C", and then solve a system of equations to figure out what time it was when it received the signals from each satellite, and thus how long each one-way trip took. Then it can do the geometry to figure out where it must be. The actual mechanism of accomplishing this is a whole lot more complicated, but on a very simple level, that's what's being done.

          The reason it takes at least four visible satellites to produce a 3D fix is because it needs to solve a system of at least four equations with four unknowns: X, Y and Z spatial coordinates, and time. More than four satellites are normally needed for good accuracy, since the each measurement is usually a lot more noisy and less precise than is desired. Additional measurements let the receiver do more math to try and filter out the noise.

    • Re: (Score:3, Insightful)

      Changing the length of a second will end up changing almost everything in our lives. It would be an enormous undertaking, redefining, among many other things, electromagnetic wavelengths and the speed of light. Speed limits would change, computers would have to handle travel time calculations differently, and the length of the workday would change slightly.

      It was hard enough to get the world to change to the metric system (with notable holdouts still remaining). Changing the very definition of one of the

    • by rrohbeck (944847) on Monday September 08 2008, @07:23PM (#24927509)

      That's exactly the point. Changing software in military or even space systems isn't exactly trivial, maybe not even possible, plus you need a method to constantly provide (UT1-UTC) to the systems that rely on UT1 (astronomical time) being equal to UTC by less than a second. Like the radio controlled clock in your home. Or the time signal transmitters would have to be redefined not to transmit UTC but some new time scale, which would be a mess for GPS.

      UTC without leap seconds is basically TAI (international atomic time) - a strictly linear SI second timescale as precise as we can reproduce it.
      Just distribute (TAI-UTC) and (UT1-UTC) together with the usual time signals, leave UTC alone (with leap seconds) and you're all set and can use what you need. There is no one time scale; Einstein told us so. Better accept it.

        • by compro01 (777531) on Monday September 08 2008, @08:55PM (#24928225)

          The problem being, the need for a leap second is not predefinable, unlike a leap day. Leap seconds are needed to compensate for slight (millisecond range) variations in the length of each day, due to the earth's rotation speed not being constant. We currently cannot predict those variations, and as such, the leap seconds are determined based on astronomical observation and applied as needed.

          • Re: (Score:3, Insightful)

            > We currently cannot predict those variations, and as such, the leap seconds are
            > determined based on astronomical observation and applied as needed.

            I know that, but zoneinfo has to be updated frequently anyway to accomodate the whims of princes.

      • It depends on the application. Having one's NFS file server just a second fast will break most Makefiles.

        I think that says more about make than it says about timekeeping.

    • That's cuz our times are valuable, unlike yours, you third-world poor trash!!! Go recycle copper and stuff.
      • by mr_matticus (928346) on Tuesday September 09 2008, @01:47AM (#24929855)

        I think the US should have one time zone, and it should be based on NYC time. -5/-4 UTC for everybody! Who cares if California would have the sunset at 2230 today?

        Fine by me, and I'm a native Californian.

        There's no rule that says business hours need to be 9 to 5. Since you already have to convert what "time" it is in a faraway place you're calling, it's not a big deal. In San Francisco, I can't make any calls after 1pm to East Coast offices and expect to get anything done. What the clocks say over there doesn't really matter. For all intents and purposes, New York business hours are 6am to 2pm from my perspective.

        I'd be content for the entire planet to move past the idea of time zones entirely. It's an outdated idea from a time when you needed physical references to the passing of time, and when it didn't matter that the times didn't line up in faraway places. Just think of all the things it would simplify: flight arrivals/departures, conference calls, news stories--and it would make am/pm an unnecessary distinction, too. 0514 would really be 0514. Everywhere. I'm okay with "business hours" for me being, say 0100 to 0900, and 2200 to 0600 in some other place. They're just numbers.

        Tradition and conditioning, however, are unbeatable--and the idea of "noon" being the middle of the day has undeniable intuitive appeal (even if it's rarely accurate).