US DoD Poll On Leap Seconds 314
@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."
Are leap seconds really all that important? (Score:5, Insightful)
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)
Re:Are leap seconds really all that important? (Score:5, Funny)
Compare absolute time vs relative time vs elapsed time vs hammer time...
Re:Are leap seconds really all that important? (Score:5, Funny)
I dunno. When it's Miller Time all those other times kinda look alike.
Re: (Score:2)
I dunno. When it's Miller Time all those other times kinda look alike.
4:20 would be all over the place. Interesting concept.
Re: (Score:3, Funny)
Just make sure to take her home to her house...so when you wake up hungover and see her...you can leave quickly...
Re: (Score:3, Insightful)
I want to solve: There is no such thing as absolute 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).
Leap seconds fix a diferent problem (Score:5, Informative)
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.
Re: (Score:3)
I suppose I'd know that if I'd R'd TFA... :P
Or played with GPS etc (Score:3, Insightful)
Re:Or played with GPS etc (Score:4, Interesting)
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
Re: (Score:3, Insightful)
Re:Or played with GPS etc (Score:5, Informative)
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, Informative)
Not every day (i.e., from one solar crossing of the meridian to the next) is exactly the same length. (Ptolemy knew about this.) Furthermore, because of drag/perturbation/molten core/etc., not every terrestrial trip around the sun is exactly the same length. I think these latter factors contribute to the need for ad hoc leap seconds.
Re:Leap seconds fix a diferent problem (Score:5, Interesting)
Yeah. an hour is meant to be 1/24 of a day. but unfortunatly, every day has a different length. You can have a look at the length of the days for each day the past 2 years here: http://hpiers.obspm.fr/eop-pc/ [obspm.fr]
Yep, that means that meanwhile, our clocks are far more precise than the earth rotation itself.
Re:Leap seconds fix a diferent problem (Score:4, Insightful)
so our clocks are more precise at measuring how fast the earth does a twirl than the earth is at twirling?
wait, what?
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
Re: (Score:2)
has any one noticed that this has failed over the last 20 years or so?
No. Labor Day was as cold in the valley as it usually is in the mountains this year, and trick or treating has consistently required coats for my family for the past 20 years.
Re: (Score:2)
Well, Labor Day is late Summer, and at elevation weather is always more extreme. Over recent history, haven't you noticed that the snows come later and linger longer? There was a snow storm late March 2 years ago... that just doesn't sit right with me that the biggest storms are arriving post-January rather than early December.
Re: (Score:2)
Well , my grandma told me, that once, they had snow in mid-June. I guess we need more and more exact data...
Re: (Score:2)
source? Pretty sure the latest recorded freeze in the DFW area has been april 14th for something like that for more than 30 years. when 80% of the US has only had scientifically accurate weather data for the last 100 year or so. pull up weather records for your area and post them, i'd be interested to see factual evidence support your theory.
Re: (Score:3, Informative)
The start of winter is the shortest day of the year, the start of summer the longest. Weather is only a secondary effect.
Actually, that's only in the US. In most of the rest of the world, the MIDDLE of Winter is the shortest day and the MIDDLE of summer is the longest day.
Not that it matters - the seasons are just names for some various times of year anyway, so it doesn't make any difference when you start/finish them, or even whether you have them at all or not.
You're of course right that weather has nothing to do with it though.
Yep... (Score:5, Insightful)
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.
Re: (Score:3, Insightful)
If they really have to, UNIX could define their own epoch with a zero offset to UTC as of right now. Then timestamps made in the past few years won't have to jump in the changeover. This would give exactly the same benefit as no longer applying leap seconds to UTC without removing UTC's ability
Re: (Score:2)
My God your signature:
And then this quote:
Does slowly equal 20 years, or 20,000 years before we're dark? I mean really?!?
Re:Leap seconds fix a diferent problem (Score:4, Interesting)
Around 43,200 years, actually.
Re: (Score:2, Funny)
Re:Leap seconds fix a diferent problem (Score:5, Informative)
Of course, they do give the news something harmless to report on every once in a while...
Re:Leap seconds fix a diferent problem (Score:5, Funny)
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, Funny)
That's a great idea! Actually, let's do one better, and we'll change the names of the times whenever it drifts by six hours: we'll call noon "six o'clock", and whatnot. Actually, gosh, let's go all the way and do it for every hour. So, if we drift by an hour, then we'll rename "one o'clock" "two o'clock", and whatnot. That'll keep it all about right. No, wait, actually, we should do it for every minute -- no, let's do it for seconds! So, every time it gets off by a second, we'll add a second to the middle o
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.
Re: (Score:2)
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
We seem to get along just fine with the idiotic Daylight Savings Time and changing clocks twice a year. True those who are paying attention actually know which days those are. But the same could be done with a leap hour as those could be scheduled and known years in advance. Not that I agree with the concept of a leap hour, I think the very idea is moronic as I agree more with your first statement. People don't care or notice if their clocks are off by a few seconds or even a few minutes. If they happe
Re: (Score:2)
Did you miss the part where I talked about events that can be calendared years in advance? Leap hours can't be so easily predicted. Remember the gnashing of teeth the last time they changed the DST rules, for example?
Re: (Score:3, Interesting)
Averages are wonderful things. Over time they account for variations in, well, just about everything. So, yeah, I'll assume that the average rate over millennia is predictable once we've measured it for the few millennia between the needs for a leap hour. A large enough data set and all that.
Doesn't a leap second smack of someone looking overhead at "high noon" each day and re-setting their watch? I mean, really. Next people will want time zones sliced into second increments so that everyone has the sun di
Re:Slightly OT: Earth Rotations? (Score:5, Funny)
... does anyone know if the rotation of the earth around the sun mean that we actually rotate 366.25 times per revolution, or 364.25?
Yes, of course someone does.
Re: (Score:3, Informative)
If you have ever
Not quite (Score:5, Informative)
No there isn't, but you can make it culminate at noon.
rj
Re: (Score:3, Funny)
Re: (Score:2)
<PARIS-HILTON>
That's Hot!
</PARIS-HILTON>
Re: (Score:2)
No there isn't, but you can make it culminate at noon.
It depends where you are in your time zone. It's rare for the sun to be directly overhead at noon.
Re: (Score:3, Informative)
rj
Re: (Score:2)
No there isn't, but you can make it culminate at noon.
Yes there is: Move to the equator.
Kill DST instead!!!! (Score:5, Insightful)
Re: (Score:3, Insightful)
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.
Re: (Score:2)
Why don't you try to get everyone you interact with to use UTC, then?
The gp obviously wasn't talking about recording timestamps, which should be in UTC.
Re: (Score:3, Interesting)
Re: (Score:2)
Because it doesn't give you enough time during the day to sufficiently explain yourself on /.?
You and me both! (Score:5, Funny)
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.
Re:You and me both! (Score:5, Funny)
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.
Re:You and me both! (Score:5, Funny)
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!
Re:You and me both! (Score:5, Funny)
I, for one, welcome our feline overlords. (I'd better, I have one watching me type this, ready to sink his claws into my leg if I type the wrong thing.)
Re: (Score:2)
And in fact people who work with animals are the biggest opponents of DST. Their livestock refuses to change its habits just because clock time has changed.
What, you say you don't work with animals? Yes you do. You're a cat servant.
Re: (Score:3, Informative)
If I may say so, Oz has a weird attitude towards time. Its the only country where the central region uses a time zone that's one half hour behind the eastern region. (Sign near the border: "Turn your clock back 30 minutes and your calendar back 30 years.") Then there's Western Australia, which tries to put things back in sync by making the whole huge state 2 hours behind the east coast. Doesn't quite work, because there's a tiny area near the border with South Australia that has its own unofficial time zone
Re:Kill DST instead!!!! (Score:5, Insightful)
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.
Re: (Score:2)
Why not see if you could get to work at (say) midnight, so that when you get home it is morning?
How about instead of redefining time, you change what the times mean?
That is my complaint about DST: instead of leaving it up to businesses to start work at 9 instead of 8, they have to mandate that the whole concept of local time changes.
Re: (Score:2)
Why not see if you could get to work at (say) midnight, so that when you get home it is morning?
It's not the "getting to work" part, it's the "staying employed" part. Very few jobs, even with flexible hours will accept that you're never around during normal business hours. And the whole bit about social events which would then happen at "nighttime" for you.
That is my complaint about DST: instead of leaving it up to businesses to start work at 9 instead of 8, they have to mandate that the whole concept of local time changes.
It's not like they're warping the time stream or anything, it's just digits on a watch and there's no law saying businesses can't "un-DST" their business hours. Can it be that what you really have a problem with is being an hour out of synch with ev
Re: (Score:2)
But think of the children!
No, really.
How the hell am I going to go to sleep and wake up in time?
3PM-9PM, with the sun completely down at 10PM would be pretty sweet. I mean, I'm in school all day, and they're leaving the lights on anyway, so why not? I finish school and it's bright out, it's so great to go outside! It would encourage us to get off our fat asses too. No more excuses. It's now sunny outside when you don't have work.
Re: (Score:2)
Yes, indeed. I was hoping to find an explanation in comments... I don't have TIME to read the articles... sigh
Re:Kill DST instead!!!! (Score:5, Funny)
Re: (Score:2, Interesting)
Why would you want to get rid daylight savings time?
Because it is like cutting a foot off of one end of a blanket and sewing it on the other end and expecting to get a blanket that is a foot longer. Kind of dumb. If you want to get up when it is light, get up earlier. When should we all have to move the clock back and forth? Split the difference between DST and normal time and leave it. Who cares if the sun isn't overhead at exactly noon.
Re: (Score:2)
Not only that the blanket keep shrinking in the wash anyway, so moving the end around doesn't matter as the blanket will be too short in any direction in a few weeks anyway.
http://www.gaisma.com/en/dir/001-continent.html [gaisma.com]
Re: (Score:2)
My thoughts *exactly*. That whole DST idea was broken from the very beginning and I wonder what could actually break if we just got rid of it right now?
I guess there would be some confusion in the first few years because millions of clocks and watches would still auto-adjust (and have to be fixed or replaced anyhow) but that's not so different to what we have today, twice every year.
Is there anything serious relying on DST that would break if DST suddenly went away?
Either way I think it's a safe bet that th
Re: (Score:2)
Nonsense! In the beginning it served an important purpose - it allowed the pubs to stay open after people got off work and before the blackout went into effect in the evening during WW1.
Anyone who can say that keeping the pubs open an extra hour was "broken from the very beginning" is a sick, depraved individual....
Re: (Score:2)
Re: (Score:2)
Why don't you ask if you can come into work earlier so that you can leave earlier, rather than messing with my clock?
Re: (Score:2)
Because maybe he's a bus driver and flex time wouldn't work very well.
Re: (Score:2)
Think of how many lives daylight savings saves regarding traffic
Um, if you extend DST longer, then you're going to lose all those lives you save by having the morning commute occur in darkness.
They tried this during WWII. It was called "War Time," and yes, the accident rate went up in the mornings during the winter.
Automated and consistent leap seconds (Score:2)
This adding of leap seconds based on decisions by panels of experts or authoritative bodies is a nonsense.
If you're going to do this sort of thing - adding seconds to the clock here or there - it shouldn't be decided upon by some review committee. There should be a planned algorithm that kicks in, and the simplest one that actually does the job should be used. The bottom line is that a watch should be able to do it. If you do this, you're able to program devices to account for leap seconds instead of having
Re:Automated and consistent leap seconds (Score:5, Insightful)
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.
Re:Automated and consistent leap seconds (Score:5, Informative)
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.
Re:Automated and consistent leap seconds (Score:4, Informative)
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!
Re: (Score:2)
The Earth's rotation varies somewhat unpredictably and thus there's no simple way of automatically adding/subtracting leap seconds without observation first.
Communications, such as cellular phone networks, often depend on very precise syncronized timing.
Ron
Re: (Score:2, Interesting)
If you're going to do this sort of thing - adding seconds to the clock here or there - it shouldn't be decided upon by some review committee. There should be a planned algorithm that kicks in, and the simplest one that actually does the job should be used. The bottom line is that a watch should be able to do it. If you do this, you're able to program devices to account for leap seconds instead of having to manually put in fudges which is an error prone process. You also get the possibility of adding leap milli-seconds or micro-seconds so fine grained adjustments are possible where required, whereas it would be much harder (though not impossible) to do that if you're manually correcting.
It cannot be done. Leap seconds are dependent on unpredictable, chaotic natural events -- namely the fact that one day in not exactly 24 hours in length. The daily error is not constant, so the only way to determine when a leap second is required is through astronomical observations.
Re:Automated and consistent leap seconds (Score:5, Informative)
> 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.
Re:Automated and consistent leap seconds (Score:5, Informative)
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.
No leap seconds prior to Jan. 20, 2009 please (Score:4, Funny)
We don't need even one more second of Bush presidency. :)
Re: (Score:2)
Re: (Score:2)
Why not just change time pieces to include the (Score:2)
Yeah, I guess the clocks would have to take into account the increases in orbits and whatnot mentioned, but so what? Computation has become dirt cheap. So the Naval Observatory does an extra calculation for GPS and things that require that kind of accuracy.
And as far as I'm concerned, my clocks are all within 10 minutes of each other - in other words, I don't give a shit about 10 minutes either way.
Re: (Score:2)
I don't give a shit about 10 minutes either way.
It depends on the application. Having one's NFS file server just a second fast will break most Makefiles.
Re: (Score:3, Funny)
I think that says more about make than it says about timekeeping.
Re: (Score:2)
Nah. It just gets bitchy. "Blah blah has modification time in the future!"
You might wind up generating a couple of .o files more than you need to, but I wouldn't call that breakage.
Now, an NFS server that's running SLOW, OTOH....
Re:Why not just change time pieces to include the (Score:5, Informative)
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.
Re: (Score:2)
Just distribute TAI, publish zoneinfo with leap seconds included, and calculate whatever you need for local use or display as needed.
Re:Why not just change time pieces to include the (Score:5, Informative)
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.
I know! (Score:5, Funny)
Let's just remove the problem entirely!
I suggest... the French Republican calendar.
And a good Tridi, 23 Fructidor, Year 216 to you too.
superman could help (Score:2, Funny)
Why is this the DoD's responsibility? (Score:3, Funny)
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.
Re: (Score:2)
I think you've got the wrong DoD here.
The Denizens of Doom are trying to control time, because indirectly, time controls doppler RADAR.
Re:Why is this the DoD's responsibility? (Score:5, Informative)
Navigation depends on time. The Navy is very interested in navigation. That's why they established the Naval Observatory [navy.mil] in 1830.
USNO employs some of the formost experts on the subject. They are soliciting the opinions of some of the other stakeholders.
Who cares about all this timezone crap? (Score:2, Interesting)
Who gives a damn about the sun being overhead at 12PM? China operates in a single timezone, despite spanning something like five, and they do just fine.
Give us GMT. Let noon drift where noon drifts. Just keep the seasons in line with the longest and shortest days and forget the rest.
Re:Who cares about all this timezone crap? (Score:5, Insightful)
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).
There is no problem here. (Score:2)
The problem isn't with UTC or TAI or any other timekeeping system used by the world.
The problem is with the cheap crap you have in your home which assumes every day is 86400 seconds long and every year is 365 days.
You bought it, you adjust it. I got better problems to solve.
Sun Overhead? (Score:4, Funny)
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
Re: (Score:3, Informative)
http://en.wikipedia.org/wiki/Circadian_rhythm#The_myth_of_the_25-hour_day [wikipedia.org]
Re: (Score:2)
http://www.newearthcalendar.com/ [newearthcalendar.com]
13 Months of 28 days, with a leap week occasionally.
The problem is if you want weeks and months, there aren't many ways to split up the 365.24 days in a year.
Having a time notation that is based on fractional days would be cool, with .0 being midnight and .5 being noon would be nice.
Re: (Score:3, Funny)