Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

@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.

I don't get why being that anal about time keeping is so important anyway. I guess with all the high dollar electronic transactions that go on these days there and what not, but for the average chump going about day to day... if the sun is in the sky it's day time, if it's not, it's night. If it looks like it's in the middle of the sky it's time for lunch.

First of all, whether or not an observer can tell how many matches are in a matchbox is immaterial--nay, completely unrelated to the fact that there is a particular number of matches in the box, a precise number that can be determined.

Secondly, time needs not be exact for most people most of the time, but perhaps you can recognize that there are certain applications, especially scientific and technological, for which a measure of exactitude is quite necessary.

One word: Longitude. Generally speaking, you determine your longitude by comparing what the local solar time is (determined by looking at the position of the sun in the sky) and comparing it to the time in some reference point (say, the Prime Meridian). Every hour's difference is 15 degrees of longitude.

Obviously, there have been all sorts of tweaks and modifications to this formula in the past 200+ years or so, but the basics are the same: You need to know what time it is to know where you are. Your precious little GPS receivers wouldn't work if they could get as accurate a time measurement as possible from the US Naval Observatory.

(Some historians have suggested that the US won the war in the Pacific because US ships had more accurate clocks.)

Your precious little GPS receivers wouldn't work if they could [not] get as accurate a time measurement as possible from the US Naval Observatory.

Not true. GPS receivers get all the information they need directly from the GPS satellites - which track their own "GPS Time" that dispenses with the leap-seconds.

You're right that having an accurate astronomically-relevant time is important for navigation - if you are determining your position with a sextant. It's the decreasing relevance of sextants to the world of navigation, and the increasing need to keep electronic equipment of all sorts in lock-step, that is driving this movement away from the leap-seconds.

See a summary of the issues from one of the US Naval Observatory scientists in charge of this stuff: PDF [navy.mil], Postscript [navy.mil].

The fundamental root of the problem is that time is one of those concepts that we all THINK we understand, but frequently we are talking at crossed purposes. Here the problem is a tension between those who use time to measure the duration between two events and those who use it in its more historically traditional role as a metric describing the orientation of the Earth.

Initially the precise measurement of time was the province of astronomers and ship navigators. Time was fundamentally the measurement of the orientation of the Earth. Time was a function of location. Noon was when the sun was at zenith. If you could know the difference in time measurements at two locations, you could determine the difference in longitudes of the two locations. In order to determine the differences in time systems, mankind developed precise mechanical time measuring systems. The new time measuring systems allowed man to measure the durations between events very precisely.

Eventually man developed atomic clocks that could use the decay of atoms to provide an incredibly stable time reference. However, some time ago, we reached a point where the mechanical time measuring systems became more stable than the Earth's rotation. So the atomic clocks which were counting down seconds very accurately were now getting out of synch with the Earth's rotation which was slowing down (and not smoothly slowing down, either).

Since no one who was concerned with the durations between events wanted seconds that varied in length, which is what would happen if you fixed the varying length of the day at 86400 seconds, the concept of using seconds of fixed duration (based on an atomic standard) was developed. The ever accumulating count of these seconds is TAI (Time Atomique Internationale aka International Atomic Time). The time which represents the orientation of the Earth is Universal Time (UT). (This is a simplification, there are a number of subtle variations on UT that I'm not going to go into, but which aren't important for the purposes of this discussion.)

If left alone, the difference between UT and TAI would grow. So, many years ago the concept of UTC (Universal Time Coordinated) was invented. This time standard uses the standard TAI second, but at irregular intervals, an additional second may be added (on either June 30th or Dec. 31st) to always keep UTC and UT to within half a second of each other.

The bottom line is that for people who have to deal with durations, especially long durations, having those irregular additional seconds is a bookkeeping pain and for those who need to be very concerned about the orientation of the Earth, a half second isn't nearly accurate enough. The latter group are undoubtedly using much higher resolution correction data that is produced by the IERS (International Earth Rotation Service). For most civilians, the fact that noon is shifting off by a second every couple of years just doesn't matter. (Especially since the railroads introduced the concept of time zones a little over a hundred years ago, which means that the sun is rarely at zenith when the clock says its noon.)

A lot of people in the field have questioned for some time whether in the era of modern computers where using the higher resolution IERS corrections is trivial, the leap second has any use. Now it may finally be going away.

Now if you want to get really esoteric, here is something to ponder: For astronomy and celestial mechanics, time is defined as the independent variable in the equations of motion of the universe. For physicists and those who use atomic time standards, time is defined as the independent variable in the decay of atomic particles. Noone, to my knowledge, has ever been able to detect a difference in these two independent variables, but it is not a given that they are the same.

For those who'ld like to know more, the University of Texas teaches a graduate level course in the Aerospace Eng. Dept. on the "Determination of Time".

Because while the day is 86400.002 seconds long (on average) it's getting longer. About 170 years ago the day averaged 86400.000 seconds long. In 170 years it shoudl be about 86400.004, though the slowing down is caused by the moon, which is moving away from us, so it's effect will get less and less (though probably not that fast) but it could be as little as 86400.003. The point is, the second is defined by one measure and the day another, and we are trying to cram the two measures together when they don't have a linear relationship.

I wondered this too, and you have to dig a little bit to find the answer. It seems most people don't like it because the software they use is often a pain in the butt to adjust for the leap second. Check out the survey here [obspm.fr] that seems to give some decent answers to why leap seconds suck for some folks.

Here's an example of a complaint:

Answer:Because time discontinuity causes a number of problems in handling time-stamped geophysical data such as seismic.

The problem with leap days has nothing to do with the Roman calendar. It is because the time it takes the Earth to revolve around the Sun is not an integer multiple of the time it takes the Earth to rotate on its axis. The Lunar calendars you mention have leap-months.

I don't think that is accurate. the concept of leap years is because the roman calendar sucks.

The concept of leap years is because the ratio of the length of a year divided by the length of an earth day is not an iteger. No calendar can get around that fact. You either add intercalation days whenever the remainders of your divisions exceed 1, or you keep track of huge numbers and cycles that greatly complicate your timekeeping.

The Julian roman calendar did suck because they didn't get the ratios quite right and it drifted. (The Gregorian calendar fixed this for all practical purposes.) However, prior to Julius Caesar, it sucked even more because there was no mathematical formula. Instead, priests were supposed to observe the sun each year and decide when leap days were needed.

The priests were also involved in politics, so they chose to shorten political terms more often than not by omitting leap days. IIRC, by the time the Julian calendar was instituted, the Romans were off by several months due to these partisan shenanigans.

There is time as used by humans vs other measures. Its purpose was to define the time that the trains ran on and is very convenient and has only passing relationshipt to the position of the sun -- those at the edges of timezones can be off by an hour or two or more.

Considering that some programmers (of commercial software, no less) have no idea HOW TO CHECK IF A YEAR IS A LEAR YEAR, I fear this is going to be no less catastrophic than Y2K, perhaps even a cataclysm of Y2038 proportions!

2. I'm actually rather smart, but sometimes instead of a word's last letter I type the next word's last letter. You may classify it as mild dyslexia; it's mostly not a problem since most people can understand what I meant from context.

3. The person sitting next to me right now has been using excessive amounts of glue for the last few minutes; I'm not sure what its purpose was, but some of you CSI fans can no doubt explain how certain types of industrial-strength glue can cause synapses to misfire.

4. Again, I apologize for any inconveniece. As a token of good will, please accept this coupon, good for ignoring one (1) typo or grammar error in any future slashdot posting. Expires 6/18/2003.

With the increasing amount of precision in today's timekeepers these problems seem to be cropping up more and more. I don't believe it really matters, except the whole world needs to agree on a standard. With our global economy (weather we like it or not) times need to be synced across the world.

Although if there are going to be changes to the time standards I can always add converters [webcalc.net] to my calculator site for people to use.

"With the increasing amount of precision in today's timekeepers these problems seem to be cropping up more and more."

What's this "today's precision" bullshit? We've been having this problem for thousands of years.

For centuries, peoples dickered back and forth about how many 28-day lunar cycles ("months") were in a year. Some said 12, some said 13. The concept of fractions apparently escaped these simple folk.

Then the Romans came along. Not to be daunted by silly things like "reality," they declared that the lunar cycle was really 30 days, and that there were exactly 10 of those months in a year. While they were at it, they delcared pi to be exactly 3.125. To make things work out a little better, they threw in some extra days between a few months whenver they felt the need. The Latin names for these periods translates roughly to "Not really a month."

That got real old real fast so they threw in two more "real" months, and juggled around the lengths of the months just because they could (They're Romans, they ruled the world, yadda yadda yadda).

That one actually lasted a few centuries, at which point they started to admit that things were still screwy (in the sweltering heat of January), which was also the same time when some guy named after a salad was thinking he was Alexander the Great. The Senate told saladm boy to go fix things (apparently smacking cheese-eating surrender monkeys around qualifies one to make a calendar). Lo and behold he did, declaring that a year was 365.25 days long (ie. every fourth year had a full extra day). Ever humble, he took the time to re-name a month after himself. Feeling insufficient in some department, he also shifted around some days so that his own personal month was longer than most.

For a group of people that had no concept of zero, this system worked pretty well for a millenium or so, when it became obvious that things were getting screwy again. This time, the folks in Rome asked some guy with a funny white hat named Greg to help sort things out. Apparently not as experienced in invading France as salad boy was, he decided he had to plagiarize somebody else's work. He found some insane scribblings from some Poloc kook who figured out that a year was "really" 365.2425. Because the Poloc was loony (he said the earth went around the sun, of all things!), Greg felt comfortable with taking that number without admitting where he found it.

The system work, but the folks Greg worked with had a bit of a bad reputation at the time. To the west, there were a bunch of political crackpots who called themselves "Complainers" or something like that, and to the east there were a bunch of people in even funnier hats than Greg's who all spoke Greek. So it took a little bit of time for "Greg's Nifty Calendar" (why name a month after yourself when you can rename the whole damned calendar?) to catch on, which is why nobody can figure out when Washington's birthday is and why the October Revolution took place in September.

And even now there are all sorts of people from Newton to Einstein that say that even that calendar is screwed up! Greg's plagiarized number was off by 0.0003 days! That's almost 26 seconds! Heck, after a few thousand years that's a hole big enough to drive a Mack truck through, and then where will we be?

"With our global economy (weather we like it or not) times need to be synced across the world."

Between the Greek-speaking folks still thinking Greg was the anti-Christ and two groups of people blowing themselves up in the Middle East still trying to make the whole lunar cycle thing work out, we can't even agree on what day it is!

Actually, you do use daylight savings time in Indiana [mccsc.edu]. There are eleven counties that are on central time and use DST, five counties that are eastern time and use DST and 76 counties that are eastern time and don't use DST. So Indiana has no less than three different time zones. At least they don't have multiple timezones per county.

Given Indiana's history with keeping time, probably half the counties will participate and half won't. And some will just switch to the Mayan calander and be done with it.

I think it's great that we don't use DST here. Everyone curses it, and I know from experience (having moved elsewhere for a while) how it screws up your circadian rhythms. I felt like I had jet lag for a month.

A few years ago somebody was running radio commercials here to support a bill that would have put us on DST. The tug-your-heartstrings appeal was that "there are two states that don't use DST: Arizona because of the heat, and Indiana because of special interest groups" (always the Bad Guys here in Indiana.) who want our kids to wait for the school bus in the dark.

Funny because DST makes it darker at any given hour of the morning, and everybody knows that the "special interest groups" who came up with DST in the first place are commerical interests who wanted to extend their business hours. Either the writers of that commercial were really, really stupid, or it was a brilliant piece of social engineering. Either way, I don't think Indiana will be adopting DST any time in the near future.

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.

Why? Energy released from nukes can change angular momentum. The only problem is directing the nukes (doing at ground level = pushing the air attached to the earth = friction). You'd have to attach the nukes to long poles sticking up into vacuum.

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 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.

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.

> Thus, they're debating about doing away with leap seconds altogether. One possible substitute is a 'leap hour' every thousand years.

Why not?

Asshats from the Industrial Revolution days make us do a frickin' "leap hour" twice a year anyways, one of which violates causality.
Fuckin' Daylight Savings Time.

What drooling asshat decided that it'd be a good idea if, every year, there was one day when everyone's heart/respiration rates slowed down to one beat/breath per hour, and about six months later, these same people should be able to start a 20 minute download that finishes 40 minutes before it started?

Fine if you've got a black hole nearby for the former, and fine if you can travel faster than light for the latter.

The day we have those technologies, fine. Until then, no, no, no, no, no, these are bad, bad, bad, bad, bad ideas.

In college we had the tradition of the 'Negative time Tommy's run'. Tommy's was a hamburger joint open all night. We'd leave at, say, 2:30 AM, go eat supfast (or whatever a meal eaten at that time is called) and return to campus before we left, at 2:20 AM.

Might as well make an event out of our nonsensical system of labelling the current time.

A few years back, I was working at a software firm that dealt with satellite radar imagery. The software calculated the satellite's lat/long position by extrapolating from a known time and position right after launch, to the time when the data was captured. Some of these satellites had been in operation for over ten years.

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).

I think that the present UTC compromise is quite reasonable. In almost all civilian systems, including non-real-time computers (like the one you are using right now), you really don't need perfectly constant real time and they are proba

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?

This is relatively prosaic stuff that's nonetheless at the limits of our current understanding.

So we don't know why the Earths rotation is slowing? I'll bet we do. It's probably the net result of several factors, most if not all of which are understood. The problem is that we have no way to collect enough data to predict the amount of slowing.

The orbit of our Moon is slowing growing larger also. Something to think about; which is more difficult? Speeding up the Earths rotation or stopping the Moon f

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 du

requires a lookup table and regular (like everytwo weeks) network connections to the Navy'sleap second table server to detect updates,and the software needs to parse the table andaccount for the update if and when it occurs.

Since we have not had a leap second update since1999, it has meant there has been lots of timefor folks to get complacent and ignore the updatechecks, so most recent code that handles leapseconds is trouble waiting to happen.

Leap seconds are evil. As someone who has spent way too many hours programming high precision time distribution systems to deal with leap seconds, I'd say 'good riddance, don't let the door hit you on the way out. Sites that have to deal with them typically shut down near leap seconds to avoid any glitches. The amount of time wasted on this problem boggles the mind.

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

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 axisOne 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?;-)

So why not redefine one second to equal 1/86400 the time it takes for the Earth to rotate on its axis? Or alternatively, change the number of oscilations of Cesium 133? It seems like a much more elegant solution than these crazy leap seconds.

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.

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

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.

no i didn't design one bit of the equipment. the equipement belongs one of the national labs and the only lab of its type in the world. the equipment was newly designed with lots of new hardware and real time software. have you heard of 350 GByes of uncompressed data on a single tape? well there were 11 of them in the experiment a decade ago! they obsoleted them more than a year ago! these data on each tapes are marked using time stamp (since the tape drives are located from east coast to hawaii). in order for the experiment to succeed, each block of data recorded at the same time must be combined. there is no independent way to say that the data tracks on two tapes are aligned other than the time stamp. you get meaningful data only if close to all the data are aligned perfectly (to within few microseconds). processing of these data is too expensive too. so trial and error is ruled out. basically, the committee felt that it wasn't worth salvaging the data and I got one more day to use this equipment.

one way to look at this experiment is like this. you have a very faint object that you are photographing. you also want 360 degree view and are using 10 cameras at different angles. Due to shaky-ness, you can't use long exposures. So you use multiple photos which you later combine in your computer. Assume that the object was moving randomly but you know the exact motion. Now if you forget to remember what time, each frame was taken, there is no way to do motion compensation and hence no way to superimpose the frames. now if your computer was too slow to superimpose the images, it may not be worth doing trial and error.

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?

Actually, it's been done. In Kim Stanley Robinson's Red Mars, a Martian colony did adopt a clock customized for the local conditions.

The Martian day is twenty-four hours, forty minutes long, roughly. Mars kept a twenty-four hour clock, with hours, minutes, and seconds remaining the same length. The colony then added a forty minute period (the 'timeslip', if I

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:-)

Check out this presentation. [ucalgary.ca] It describes the methods currently used to accurately determine the rate of the earth's rotation, and how they've been able to use historical accounts to get earth rotation data points- if they have a record, for example, that there was a total eclipse in a certain city in Babylon at local noon on January 1, 1000 BC, they can use the orbits of the earth and moon (which are well-modeled over that time frame) to figure out when in UTC that eclipse must have happened, and compare the two.

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 [leapsecond.com]. As a measure of the level of obsession a person can obtain, this guy has multiple [leapsecond.com] cesium frequency standards, but he had to go out and buy a crazy russian hydrogen maser [leapsecond.com] 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.

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.

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.

America is to blame! We are only 5% of the Earth's population, but we use 80% of the angular momentum.

It's the failure of the world's industrialized nations to use renewable power sources. By drilling for oil, millions of tons of heavy crude are removed from the the depths of the earth and brought to ground level. Since angular momentum is conserved, the earth's rotation slows slightly to compensate for the now-larger moment of inertia. Extraction of metals from mines also contributes to the problem.

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.

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.

Too late. In most places, local solar noon hasn't been used as a time standard for more than a century [greenwichmeantime.com]. Depending upon where you live within your time zone, the local solar noon can be different from standard time by a half hour or worse--and I'm not going to mention the impact of Daylight Saving Time.

Correcting--or not correcting--the time through use of leap seconds makes a difference of less than half a minute per century. The leap second correction is too coarse for almost any scientific work, and much too fine for the average person on the street.

Why not have a leap minute, where necessary, once every two or three centuries? It will still be dark at midnight, and we reduce the hassle of dealing with time discontinuities by a couple orders of magnitude.

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.

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.9 seconds of cosmic time.

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.

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!

In a few millenia when noon has actually shifted to what could be today's quarter 'til 10, they will hopefully have a different concept of morning/first daylight at somewhere between 6 and 8

People, in general, don't seem to give much of a damn about when noon happens. They would prefer noon to happen at 6 in the afternoon if they don't have to change their watch too often when they travel to the next town.

In Europe, it can really be strange. Except for the UK (and possibly Ireland, don't remember), it i