The Future of Leap Seconds
@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."
I can't see why they hate leap second. I'll be damned if I am going to eat lunch at what is called 8:00 in the morning because they don't want to keep leap second. Grow up, we have leap years and human time keeping is not an exact science as the Earth tends to spin the way IT wants not the way we want.
Visit www.seriouslythough.com
Time is an Illusion. Lunchtime doubly so.
Me: Wanna go have sex?
Hot Girl: OK! When?
Me: I'm on lunch break in 3 Maxtors and a Tape.
Hot Girl: I'll pay for the Hotel room.
This site may be more helpful, especially in clearing up some of the problems with leap seconds (and their ultimate creation of an offset from both TAI and GPS time)
I propose we keep the earth spinning at a constant rate by detonating thousands of nukes at certain places once every four years. This will produce a Catherine Wheel effect and the earth will speed back to its original spin rate.
I am going to patent this idea but I fear itll be 500 years before I get it processed.
This is the link to a summary of the issues involved, written at a slightly less technical level.
(don't have to pay, don't have to register, etc.)
http://www.cl.cam.ac.uk/~mgk25/c-time/metrologia-
If I understand what I read correctly, essentially the problem they're trying to solve is this: the Earth's rotation is slowing, but they can't predict exactly how much it's going to slow at any given time. It is a real, physical thing, and while they can model its orbit with extreme and unchanging accuracy (things are widely separated enough that the mathematical abstractions work fine), modeling its rotation isn't really possible. There's all sorts of liquid sloshing around everywhere, both liquid water on the surface and molten rock in the center. All they can do is measure it, and every once in awhile, determine that sunrise is happening just a little late.
:-)
There are two major timekeeping systems: TAI, which is "absolute time" and is never adjusted, and UTC, which is "civilian time". Because UTC is used by normal people, they try to keep it synced to the Earth's rotation, which in theory at least makes it more useful for us mere mortals. (knowing that the sun will rise at exactly X time on X date at sea level, for instance.). So, gradually, UTC diverges from TAI, because one rotation of the Earth is just a little longer than 24 hours, and over time this divergence adds up to be greater than a second. When it's getting close, they add a leap second. These additions are not at regular intervals, because they can't predict exactly when any given second should be added.
There are occasional problems when they add the leap seconds (programs that don't expect 61 seconds in a minute, for example), or programs that don't realize that there are X number of seconds (15 or so?) that simply didn't exist since 1970. (sometimes this stuff matters).
Thus, they're debating about doing away with leap seconds altogether. One possible substitute is a 'leap hour' every thousand years.
It seems like a rather anal-retentive thing to argue about, but these people are paid to be precise to a degree we can't even imagine.
A worthy slashdot story. This is serious geekery.
And why do we care?
Read the article!
It's important for systems programmers, and lots of folks here are at least systems programming fanboys.
It's important for navigation. Yeah, that includes your GPS toys.
It's important for a number of scientific disciplines, including a number of subdisciplines of radio astronomy.
It's also really interesting that the change in the Earth's rotation can't yet be predicted with enough accuracy to set a schedule in advance for adding leap seconds, but must be measured. This is relatively prosaic stuff that's nonetheless at the limits of our current understanding. Doesn't anyone get excited or curious about science anymore?
And just think, if no leap seconds were added since 1972, you'd be having your Noon Lunch at 11:59:38!
:)
Oh the horror...
Accuracy isn't everything...
"Can of worms? The can is open... the worms are everywhere."
first of all, I think it's important to keep on track with time, it's not like we don't have the technology to keep it up. Isn't it amazing that we can even develop the concepts in the first place? Leap years have been incorporated for awhile now, it keeps the seasons from drifting to some "other" part of the calendar. (Winter in July anyone?) Daylight savings wasn't invented to annoy people or make people appreciate the season by forcing you to be awake earlier. It saves energy by having people awake during the daylight hours. This means you're more likely to open a window than cut on a light, and go to bed while it's dark out. While leap seconds are comparatively minute, it's just maintence. (Y2k is an example of what happens when we don't think far enough ahead). I think modern-day timekeeping is the result of centuries of work. It started with us observing the sun, then the stars, and now the earth itself. Needless to say, timekeeping ought to be an exact science. Until we find something more reliable of deserving to serve as a time reference, we ought to keep our ears to the ground. We do happen to live here, and I think the Earth deserves to set the pace.
Why can't all fpga/microcontroller manufacturers just release free optimizing compilers???
requires a lookup table and regular (like every
two weeks) network connections to the Navy's
leap second table server to detect updates,
and the software needs to parse the table and
account for the update if and when it occurs.
Since we have not had a leap second update since
1999, it has meant there has been lots of time
for folks to get complacent and ignore the update
checks, so most recent code that handles leap
seconds is trouble waiting to happen.
I will be very happy when leap seconds are put
to bed.
Leap years work like this:
;-)
One year = the time it takes for the Earth to revolve around the Sun.
One day = the time it takes for the Earth to rotate on its axis.
The problem is, there are really about 365-1/4 days in a year - it doesn't work out evenly to 365 days. So, every four years we add an extra day (Feb. 29), and then it all averages out. Otherwise, if we only had 365 days in a year, over many years seasons would start getting earlier and earlier on the calendar.
One day = the time it takes for the Earth to rotate on its axis
One second = the time it takes for Cesium 133 to oscilate about 9.19 billion times (because it's something constant we can measure)
The problem, again, is that there aren't exactly 86400* seconds in a day. So, we add leap seconds periodically to account for it. As I understand it, this isn't necessarily done at fixed intervals, but rather whenever it's decided that it needs to be done. The Network Time Protocol used to synchronize clocks over the Internet supports leap seconds; they can be announced over NTP in advance, so everybody adds them at the correct moment.
Why is it important? It's not important to most people, but computers like things to be precise and accurate for various reasons, and that means we have to agree on exactly what time it is.
* BIND now lets you write "1d" in a zone file, but how many of you still have this number memorized?
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
A slashdot reader having sex with a hot girl????????
Either the poster's definition of hot, girl or sex is seriously out of whack.
I like my beverages with warning labels!
The stated problem with leap seconds is that some software gets confused by them. Guess what? That same software probably gets confused if the time zone changes, or when it moves into daylight savings time.
The Right Way to solve this problem is for computers to work with TAI internally, and treat the difference introduced by leap seconds as part of the time zone, for human consumption only. Instead of defining PST to be UTC - 08:00, define PST = TAI - 08:00:22.
Computers can keep their straightforward time system, humans can keep our astronomically synchronized system. No need to lose either of those qualities.
Tarsnap: Online backups for the truly paranoid
Hmmm..
"matter of international significance"
Hmmm... I know!
echo "matter of international significance" | perl -p -e 's/t..n[^s]+//';
Ahh. Now *THATS* more like it.
A bird, a plane, No SUPERMAN
When he messed around with the Earth's rotation to save Lois Lane, he got lazy and messed it up by a tiny bit. Now look whats happened, we're off by a couple seconds now.
This is what happens when you get an alien to do a human's job.
It's about time someone did something to correct these errors.
(it's funny, go ahead and laugh, willya?)
Need a Linux consultant in New Orleans?
seriously, i did! during one of my scientific experiments (I believe it was in Jun-93), they added leap second in the middle of my experiment. The data taken from various places could not be combined together, since they didn't know at what time, leap second was adjusted at which place. So we had a 24 hours experiment on 300 million dollar equipment failed and 100's of manhours were lost in the process.
It seems to me that we should get rid of the concept of seconds altogether. The second was devised in the Sumerian culture, along with such bizarre ideas as a circle having 360 degrees.
The French of course stole the concept of decimalization from Thomas Jefferson and applied it to a variety of measurements, but failed to carry it to a good conclusion by decimalizing time (it seems everything French starts off well but is never really completed).
It seems to me that real progress should be made by dividing the day up into decimal units of time, and the circle into decimal units of arc, thus eliminating the second as a unit of measure.
With a manned mission to Mars possibly less than 20 years away, shouldn't we start looking at timekeeping systems that aren't tied to this rock?
There used to be a time that a second was something that would fit 24 x 60 x 60 times in one day -- no matter how long the day was. Nowadays a second is something like this-and-that many vibrations of some atomic particle thingy.
:-)
So maybe we should just stretch the number of vibrations of the particle thingy a little, instead of adding extra seconds to days
"We can confirm that Debian does *not* ship the version with the trojan horse. Our version predates it." [CA-2002-28]
OK, we can slashdot a webiste, surely we can fix this. Ok, on 3 let's all start running west. 1...2...3...
running though is not so popular among this crowd...
It looks like the day is getting an average of 2ms longer per century, but it fluctuates 4-5ms away from that on a decade timescale plus some shorter-term noise.
A really interesting guy on this topic is Tom Van Baak, the fellow that runs leapsecond.com. As a measure of the level of obsession a person can obtain, this guy has multiple cesium frequency standards, but he had to go out and buy a crazy russian hydrogen maser so he could get better than a microsecond a year accuracy. He's also got some interesting information about the leapsecond debate on his website.
Me, I'm a simple guy, I just need to keep NTP locked to a couple of microseconds to sleep well.
jeff
Here's an idea, why not fix it on those wierd years, without leap years. For example, 2100 is not a leap year, even though it is divisible by 4 (because it is divisible by 400 and 100). Since many computer programs won't handle that correctly, on those days, adjust for the missing seconds (a few minute change).
Kill two birds with one stone, so to speak.
-Sean
On the one side, I don't like the idea of time being shifted around like that because it could upset my schedule, what with a tenth of a microsecond popping up like that every year, but on the other hand, if we wait until there is a full second accumulated, it could be really hard to decide what to do with it...
I mean, do I go on vacation, read a book, learn a new language? What to do with the extra time is just too huge a responsibility.
I don't know the meaning of the word 'don't' - J
Leap year, leap seconds, leap minutes, daylight savings time ... change all of this stuff so that it cuts a year/seconds/minute/hour out of my workday, and you'll get my vote. Losing an hour of sleep overnight on a Tuesday does nothing for me, but skipping that mid-Monday meeting would be a God-send.
America is to blame! We are only 5% of the Earth's population, but we use 80% of the angular momentum. Scientists have warned us for years about global slowing, but big business Republicans, and Democrats with large angular momentum consuming projects in their districts refuse to address the issue. The only viable solution is to make papier mache puppets and parade them down Pennsylvania Avenue.
For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
The amount of time it takes is not constant. All we can do is mesure the rotation and let everyone know when it's changed.
autopr0n is like, down and stuff.
Right. The real problem is that lots of people who write code dealing with times and dates do a really crappy job. Some piece of software breaks every leap year, every time we change to daylight savings time, every time the dates of daylight savings time change, every time there's a leap second, every time you move your computer across time zones, every time a year divisible by 4 isn't a leap year... Just last month I reported a bug in a library function in a well-known software product, and had to explain to the developer that no, we weren't on DST yet, but Australia was.
So this leap second debate is really just a cunningly disguised way of talking about the crisis of software quality. The fact that a lot of software can't deal with 23:59:60 is the same problem that causes a lot of software to fall over when there's a February 29th.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
leap seconds are only evil when you try to commingle UTC and TAI. If your system operates on a straight TAI, then leap seconds become a presentation issue right along with time zones and daylight savings.
-russ
Don't piss off The Angry Economist
> SPEED UP THE EARTH!
I wholeheartedly agree. We can shed some mass temporarily and help the earth spin faster by "leaping for leaps." Every few months or so everyone on a given continent will jump up at the same time. I'm sure it'll all work out just fine. Organize a "leaps for leaps" chapter in your town today.
I think that the removal of the leap second is a big mistake. Sure any noticeable changes will be extremely gradual, keeping time has more purposes than just knowing what time to leave for lunch. If we read about cowboys fighting at high noon, we know what it is. If we read about Paul Revere's midnight ride, we know that it did indeed happen at night.
Removing the leap second makes most history recorded with reference to time of day pretty useless. Noon is defined by most people as the time that the sun is in the middle of the sky. Let's keep it that way. If method of keeping time based on exact seconds from one point in time to another (which is actually pretty useless for most things that happen within timeframes longer than a couple of minutes) then let a separate system be designed for it. Start reading off an atomic clock and never account for leap seconds, but don't screw up the rest of the world to please a few.
I wouldn't be so quick to suggest tampering with the earth's rotation. I recently saw a very intellectual documentary about what can happen if the earth's core ever stops rotating. Birds would fall from the sky, people with pacemakers would keel over dead, and entire football stadiums would be electrocuted by superstorms. All sorts of crazy shit that you wouldn't expect happens when crazy scientists start messing around with the earth's rotation.
GMD
watch this
No! If they get rid of leap seconds, that'll cut my sex time in half!
All this techno mumbo-jumbo is just an overly verbose representation of an old saw:
A man with a watch always knows what time it is. A man with two watches is never quite sure...
I have no problem with your religion until you decide it's reason to deprive others of the truth.
Is France a member?
Do they take requests? ("I'd like an extra long sunset this Friday night... I have a date!")
There are several timescales. There is already one that does not have leap seconds, and one that does. What is important for the average person is that when the beep, beep, beeeeeeeeep goes beeeeeeeep it's the same for *all* people. While 22 seconds isn't a big deal for most people, it's a huge difference in a lot of other areas from financial trading to shipping. There's a hint of the fact that a USBN (submarine) hit something because a leap second got inserted in to a clock that no one was prepared to handle and they went a second to far.
.9 seconds of cosmic time.
The leap second reconizes the fact that the "second" is defined in terms of particle physics (a quantity of state changes) which is very stable (it's always going to take the same amount of time for the same quantity of state changes), where as the idea of time really comes from the cosmos. When the sun is directly overhead it's 12:00.
Where the earths orbit around the sun is very stable, 265.24 days, the rotation of the earth is very unstable. In fact, there's a provision (though never used) to remove a second from the day! The speed of the rotation is constantly changing. Over the long term it's pretty stable with a stable decay, but in the short it could be necessary to add a second rather quickly to keep the civil time within
The long term average is that we need to add a second to the day about every 18 months, but we haven't needed a leap second since the end of 1998 (over four years!) so in the short term the stability of the earths rotation is low compared to the order of magnitude we measure.
In order to handle this a desicion is made every six months as to a new leap second at the end of June or December (or to remove a second). This is a problem because some systems can't handle the addition of a second on six months notice such as the submarine!
One proposed solution is to allow UT1 (cosmic time) and UTC (civil time) to be out of sync by as many as 10 seconds. This would allow for ample time for warnings to be produced and everyone to know exactly what is going to happen and how to handle it. I don't know if the protocol would add 10 seconds at once, or warn everyone a few years in advance that a second is going to be added at several different points in time.
One interesting side note. Most computer systems don't handle leap seconds. Time keeping software slows the computers clock down (since it's important not to have events which have happened (past) in the future (future). This means that if your measuring anything else based on time that measurement is going to be wrong. The theory being that the accuracy in what time it *is* is more important than what time it *was*. The reason I bring this up is that time is something that can be measured with amazing percision, where as other things can't be measured as well. If you can convert one measurement to time you can measure it more percisely. For example, how fast does the ISS move? If you know it's altitude by measuring how long it takes to bounce a light off of it, and you know how long it takes to get from A to B (or from A to A again), you know how far it moved and how long it took to move and voila, speed, all by measuring time. If a leap second got thrown in while you weren't paying attetion during your measurement, your speed will be wrong.
Darthtuttle
Thought Architect
This is the best news I've heard in a very long time! I'm sure I'm not the only one who thinks that both day and night are way too short. How long do we have to wait until the day will be 25 hours? Aaaahh... I'm looking forward to that extra hour of sleep!
Posters seem to broadly agree that we use time in 2 ways: 1, as humans, to "tell the time of day", ie relating the position of the sun in the sky to a time of day, which should not change, and 2, to measure a time difference between 2 events, which may have nothing to do with the sun or times of day. Clearly, for the first application, leap seconds etc. are important to eliminate drift. However for the second use of clocks leap seconds don't matter. So why not use Julian dates (number of metric seconds since some datum) for stuff like GPS, atomic clocks etc. and keep normal times with all the quirky leap seconds for "human-interface" use? After all, we don't find out the time of day from a GPS so why does it need to use minutes, hours or days? Julian timekeeping is already in widespread use in astronomy for "interval between 2 events" uses so I don't see why it couldn't be used in other such applications. We could even have a nice standards-based libtime to convert between the two.