The Future of Time: UTC and the Leap Second 235
rlseaman writes "UTC ("Coordinated Universal Time") is very close to being redefined to no longer track Earth rotation. Clocks everywhere — on your wall, wrist, phone or computer — would stop keeping Solar time. 'American Scientist' says: 'Before atomic timekeeping, clocks were set to the skies. But starting in 1972, radio signals began broadcasting atomic seconds and leap seconds have occasionally been added to that stream of atomic seconds to keep the signals synchronized with the actual rotation of Earth. Such adjustments were considered necessary because Earth's rotation is less regular than atomic timekeeping. In January 2012, a United Nations-affiliated organization could permanently break this link by redefining Coordinated Universal Time.'"
Copypasta (Score:2, Insightful)
Taco, all you did is quote the article summary. I can spin up an RSS reader to do that.
Re: (Score:3)
Re: (Score:2)
You actually read the articles?
Re: (Score:3)
Only if they're on playboy.com
Re: (Score:2, Funny)
Are you sure he didn't replace himself with a shell script? :-)
That's what I would do if it was my site
Re:Copypasta (Score:5, Funny)
Re: (Score:2)
I'm getting hungry.
Re: (Score:2)
Re: (Score:2)
Hhhmmmm, a taco shell? What might you put in a taco shell? A script??? What kind of sauce do you put on that?
Re: (Score:2)
Re:Copypasta (Score:5, Insightful)
Do you normally read all American Scientist articles? I don't, so I appreciate this article being brought to my attention (though I'm not planning to pay to read it). The purpose of /. is to point out interesting information so that we can read it further. The summary is supposed to be an accurate summary of the article; since an abstract is already provided, why shouldn't it be used?
Re: (Score:3)
The summary is supposed to be an accurate summary of the article; since an abstract is already provided, why shouldn't it be used?
Because we can't read the actual article unless we're a paid subscriber to the journal/magazine - that's why.
Re: (Score:2, Informative)
Because we can't read the actual article unless we're a paid subscriber to the journal/magazine - that's why.
As others have mentioned, it is available - follow the first link and look for a link to the article PDF in the right sidebar. I agree that the /. summary could've mentioned that.
Re: (Score:2)
That's not a solution. You still have to purchase the article.
Re: (Score:3)
Taco, all you did is quote the article summary. I can spin up an RSS reader to do that.
So then why are you on /.? Don't bitch, go sign up for your feed and you've fixed _your_ problem.
Re: (Score:2)
Yeah, and then you can't even RTFA if you want to, because it's behind a paywall.
Well done, Taco. Well done.
PDF version (Score:5, Informative)
Metric Time (Score:2, Interesting)
base-12 >> base-10 (Score:3)
10 is an arbitrary base and works poorly for time. Earth time works very well in Base-12, which is what we have now.
If you want to think of the children, the Egyptians and Babylonians taught their children to count on the knuckles of their four non-thumb fingers. The 10-finger-number system is just an unfortunate thing that came along with arabic numerals, which are very useful.
I saw we adopt something from the UNICODE set to mean eleven and twelve. Say, they're not 1-teen and 2-teen, are they?
Re:base-12 base-10 (Score:2)
Why would it work more poorly for time than for distance or anything else?
Although one thing I do find amusing about the whole metric vs. traditional units is that one of the primary arguments for moving to metric units is that it makes conversion between units easier. The only problem is that about the only units that I convert between on a regular basis is ... time, which is not handled in
Re: (Score:3)
The ease of conversion is more when converting compound units. A newton is a kg m/second^2. A Joule is a Newton applied over a meter = kg m^2/second^2. A Watt is a Joule used every second = kg m^2/second^3.
American units have the pound, which is a slug foot /second^2. Except no one uses the slug, so it has to be pound-force = pound mass * 32.2 ft/second ^2. Energy? Sometimes they use foot-pound which is easy enough, but other areas we use kilowatt-hour, or BTU (defined from the heat capacity of water). Powe
Re: (Score:2)
Oh, I understand the principle. The thing is that I haven't had any reason to do those types of unit conversions since I got out of school, and I'm willing to bet that goes for almost everyone else. Those who do (scientists and engineers, mostly), ought to be using metric in their work, no argument there
Re: (Score:2)
Re: (Score:3)
Um ... don't you ever use the phases "half past ten" or "quarter to six"?
Re: (Score:3)
You don't need fractions though? That's the point of metric?
A day is 100 centidays long.
Go to work at 37.5cd (375millidays) aka 9h... high noon at .5d / 5dd / 50cd. So take your half hour lunch ( 2 centiday lunch). Come back to the office at 52cd Leave work at 71cd (17h). supper at 75cd (18h). etc. The 11oclock news is now on at 958md. They'd probably make it a nice number like .95day. "Late news nine five".
Realistically these would end up being aligned with rounder numbers. Just like no one has an official
Re:base-12 base-10 (Score:2)
I'm one of the biggest advocates for the base 12 (or 16) number system, but if we have to keep with base 10 for now, then it would obviously make sense to have time as base 10 also to keep things standard.
Re:base-12 base-10 (Score:2)
I agree, 10 doesn't work so well, but 1 works great for time if you consider one rotation of Earth. At .500000 Greenwich would be through one half rotation. If you told someone to meet up in 2 and a half days you know how many time units it is already... (hint: 2.5)
I actually wrote a JavaScript clock for my desktop that uses UTC time converted to decimal for Earth rotations.
I will disagree that 12 is a reasonable number though. Sixteen I can see, but twelve does not evenly halve out to a round number. 1
Re: (Score:2)
Re: (Score:2)
But what's the point of dividing a day into three or six parts? I can see 2 and 4 (half and quarter day) but I don't know many people who think in third or sixth of days.
Re: (Score:2)
Shift workers think 8 hours, not 1/3 days. I'd even argue that a majority of those don't even account for those as 8 hour days but as start and end times. It's a subtle distinction, but I think a very important one. Using any arbitrary timescale you can still come up with a set of time that you have to work. For the start/end timers all they need is a time to start. For the hourly, all they are looking for is a number of time units to meet.
Re: (Score:2)
The current time values are hard to use in calculations. Calculations for pay, calculations for project times, calculations for just about anything with direct ties to time. At their level it's easy to deal with but converting the number to another level requires that you remember a set of numbers that have no other meaning but that. (ie: 1440 for minutes in a day)
In our current system: it's 24 units, then 12, then 60, then 60, then 1000. There's no consistency. If you wanted to find the hours in a day
base 60 (Score:2)
The next step would add 7 as a factor, and we sure wouldn't want to try to base our technological civilization on that! (do the math, be, um, enlightened...)
Re:base-12 base-10 (Score:2)
"We know that the human race is not sufficiently advanced because they have not yet converted to a base-6 system of enumeration."
Re:base-12 base-10 (Score:2)
Re:Metric Time (Score:5, Informative)
The metric system is originally based upon an earth derived measurement called the meter. 1m ~ 1/10,000 the distance from the equator to the poles, 1g = the weight of 1cc of pure water at STP, etc. That all the measurements are base 10 is not what makes it "metric", it's that they're derived from the (originally) earth centric meter. Our time system is also derived from earth centric measurements, called day and year.
Base 10 time would be a huge adjustment for society. While using a 100,000 "MetSec" day and a 100 "MetSec" "MetMin" would produce units fairly close to the existing second and minute measurements, a "MetHour" would be much longer or much shorter than an hour, either 14.4 minutes (100 MetHours/day), or 2.4 hours (10 MetHours/day). And that doesn't do anything to address the leap second issue, nor does it alter the ~ 365.25 MSD year.
The bottom line is that as long as we maintain the concept of a day and year and all the associated stuff (seasons, equinoxes, solstices, etc.), all of which are critical to agriculture and survival, there has been no system of time keeping proposed that is significantly better than what we have. The universe is not going to arbitrarily adapt it's cycles to make it easy for our minds and computers to keep track of time.
And that's without considering relativistic time dilation. While most people never have to worry about time dilation effects, the atomic clocks that create UT1 and GPS satellites have to compensate for relativistic differences caused by differences in local gravity and speed, both of which are affected by altitude.
Perhaps Douglas Adams said it best, "Time is an illusion, lunchtime doubly so."
Re: (Score:2)
Captain's Log.... (Score:2, Offtopic)
<Kirk Voice> Stardate.....65500...My...solar TIME, clock...seems to be...malFUNCTIONing...perhaps Coordinated....UniversalTime...is finally...UPON us. <\Kirk Voice>
Relativistic Reference Frames? (Score:4, Interesting)
In 2012, a new definition of time that is only relative to the Earth's reference frame falls short.
The point is? (Score:2)
Re: (Score:2)
So what we need to do is leave it as is for now and when we start real space travel, we can have Space Time.
Space Time, a fusion between the concepts of space and time, brought forward into one four dimensional continuum. Yeah man. I love that shit right there.
While we're at it (Score:5, Insightful)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Of course not. Studies utilizing questionable methodologies say it saves energy.
Besides, not having to run in circles every time Congress decides to twiddle the dates would put people out of work and that's the last thing we need in this economy.
Re: (Score:3)
Congratulations, you've just won a contract valued at 4 weeks of "running in circles" paying $100 per hour next time Congress twiddles the dates. This will spare you having to take out a second mortgage for the expanded deck and hot tub. Hope your spouse is the patient type and accepts that you'll be in good coin any day now for the big splur
Re: (Score:2)
No, leave the daylight savings time. Get rid of the standard one. I like the extra daylight in the evening hours. ;)
Re: (Score:3)
How long is year anyway? (Score:4, Informative)
We say 365 days.
We observe 365.25.
The tropical year (equinoxes+solstices) is closer to 365 solar days, 5 hours 49 minutes 19 seconds
The sidereal year is 1.0000385 tropical years (365.256363004 ) (20m24.5128s longer than tropical year)
So may times...
Re: (Score:2)
A year is a year long.
Your numerical estimates of it are conveniences for your daily use, but, as you can see, can only be reconciled to the year by defining context and accounting for variability.
If UTC stops adjusting for variability, then we'll just go back to using GMT as our human-readable clock standard timebase.
Aw, jeezus (Score:3)
This has been *progressing*?
This is possibly the stupidest idea in history. Their stated goal: taking complexity out of time handling code -- *cannot happen*: it will *still* have to account for all the years we did this.
And it will break *lots* of stuff.
Re: (Score:2)
It will have to account for all the years this was done, but there will be no unpredictable changes in the future. The difference between atomic time and current time will be a constant from now on. This is a lot easier, because you can write a self-contained program to do 100% of the conversion right now, rather than having to write a program that can update the conversion from an outside source.
Re: (Score:2)
Arghhh! (Score:2)
Re: (Score:2)
i would guess all of it does, because we've always assumed UTC=UTC=UTC=UTC.
luckily, the fix could be very simple.
you just point your time server for those systems at a master time server that is still giving out UTC, instead of at whatever standards' organization's time server that's been changed over to the new standard.
i suspect you'll be able to find (or construct) such UTC servers indefinitely.
the math will then be done at one place, and everywhere else can just go on as their original specifications, u
Re: (Score:2)
Oh... (Score:2)
and TFA is apparently only available to Sigma Xi members. Great work there, Slashdot editor.
Re: (Score:2)
You should have just eaten the dog food and taken the paddling, and you'd have a login.
Wall clocks (Score:5, Insightful)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
In general, people will want clocks that pretty much point to the minute at which the next television show will appear. They should therefore synced instead to the broadcast signal time. Keeping your DVR and wall clock in sync with the broadcasting stations reduces the possibility of DVR drift, where you miss the first or last few seconds of a show, or reality drift where you turn the tv on a few seconds late.
Re: (Score:2)
But it doesn't have to be at the nearest second. Where I live, the sun reached zenith at 1:43pm today. Even if we stop counting the leap seconds, it will take long before that number reaches 2pm. At that time, we can start considering adding a leap hour, or something similar.
Re: (Score:2)
I will ignore both and continue to claim "my watch is a little fast" when showing up my customary 160+-5 seconds late for meetings.
What would be the point of UTC, then? (Score:4, Informative)
If UTC would be redefined to no longer be adjusted to Earth's rotation, then what would be the point of having UTC at all? We already have a time scale that counts seconds without adjusting to Earth's rotation: TAI [wikipedia.org]
Re: (Score:2)
If UTC would be redefined to no longer be adjusted to Earth's rotation, then what would be the point of having UTC at all? We already have a time scale that counts seconds without adjusting to Earth's rotation: TAI [wikipedia.org]
Yeah, this really makes no sense. We will always have the need for a time that will tell us when the Sun will rise and whatnot, and that time will always need leap seconds or something like them.
A better solution might be to redefine UTC to be independent of any notion of "seconds" as a datum. Give each UTC year a TAI start-second (floating point, of course) as a datum and be done with it, rather than counting UTC seconds from a one datum, TAI seconds from another datum, and adding an adjustment between t
Re: (Score:2)
It would be a good timebase for when we're not on Earth. I.e., it would become "universal".
So, while I think changing what UTC means is pretty dumb, now, I think that if we had /. back when they decided to make the first adjustment to it to keep to the Earth's clock that I would have thought that changing what UTC meant then was really fucking dumb. Since I think now that's what I think having done it then was.
So here's my solution: Leave UTC alone, don't make anyone have to change anything they've based
three pictures to explain it, and a solution (Score:2, Informative)
The situation can be explained in three pictures [ucolick.org].
Using already-deployed code, here is one way to solve the problems [ucolick.org].
so this what the mayan ment by end of time (Score:2)
The old system will end and all new one will start up at the same time with big changes.
what about NIST (Score:2)
itsabouttime (Score:3)
Oh groan, best use of that tag on /. so far.
Seems like a silly thing to do (Score:2)
I know that we can keep time much more accurate using atomic time.
My questions is, why on earth would we want to? I mean that literally. We live on earth. The earths travel rotation around the sun and the rotation the earth does each day is what is relevant to our lives.
We plant our crops according to the seasons. We wake up because the sun shines. Why should our system of time directly reflect the way we live our lives?
Re: (Score:2)
The best use of atomic timebases is the same as the best use of clocks used to be: navigation.
We started out needing accurate clocks so we could tell from the angles of celestial bodies and the horizon where we were on the planet relative to home, to within a few hundred meters.
Now we need accurate atomic timebases to measure the frequencies of radio waves from satellites to triangulate between them so we can tell where we are on the planet even if we're at home, to within a few meters.
PDF Link and the Real Threat Is Not Real (Score:2)
If you want to read it for yourself: http://arxiv.org/pdf/1106.3141v1 [arxiv.org]
Quoting the last line: "Will deliberations at the ITU-R Radiocommunication Assembly in January 2012 resolve or cloud these issues?"
This is a committee to review the standard. Nothing is going to change without proposals. Those come long AFTER the review. Then there's the discussion process. Eventually it may make it to being a standard. Then people have time to implement it.
Cheers,
Ehud
Re: (Score:2)
Why do we need them?
They should submit the standard to us and we'll figure out whether anything needs to be done.
Re: (Score:3)
We can't have this! Think of the children! They'll learn that Noon is when the Sun is high in the sky only to see it pitch black!
By then, children will no longer venture outside. Thanks to Facebook. And Slashdot.
Think of the Humans (Score:2)
If time is kept by atomic clocks that's not synchronized with the Earth's rotation then one day, Midnight could be when the Sun is high in the sky!
We can't have this! Think of the children! They'll learn that Noon is when the Sun is high in the sky only to see it pitch black!
You're right, even if accidentally. Time keeping that is meaningful for most humans is much more important than time that is meaningful for just a handful of computer operators and nuclear scientists. They need to stop being so ego-ce
Re: (Score:3)
Yes, think of the humans. The ones wasting millions of dollars a year keeping databases up to date with the leap seconds which, unlike leap years, are not algorithmically predictable, and ensuring that all critical time-dependent software is properly tested and verified.
Leap seconds happen at most twice a year, and typically once every few years. If they happen at their maximum permitted frequency, then in 1000 years the difference between midday and noon will be 2000 seconds, or just over half an hour.
Re:Think of the Humans (Score:4, Interesting)
Leap seconds happen at most twice a year, and typically once every few years. If they happen at their maximum permitted frequency, then in 1000 years the difference between midday and noon will be 2000 seconds, or just over half an hour. In other words, for me the drift due to not living exactly on a time zone boundary line will still be more than the difference due to ignoring leap seconds.
It's impossible to predict ahead of time how many leap seconds are necessary. Just because it's been historically ±1 second doesn't mean it will always stay like that in the future. As T increases quadratically, we will eventually see leap minutes and leap hours.
That's not even taking into account of the fact that doomsday style meteor impacts could necessitate adding or removing a whole day every year. That pretty much breaks half of the time-related code that I've written.
Note that this is a wildly pessimistic prediction. It's more likely that we will drift about 5 minutes over the next thousand years. In 1,000 years, if the position of the sun over Greenwich at 12:00 is still of importance to a significant fraction of the human race, then I'll be very surprised.
It's not pessimistic at all. T between the 1000AD and 2000AD was 1600 seconds.
In fact, I'd say that's a very optimistic prediction, since T is monotonically increasing, T for the next 1000 years will be much larger than T for the previous 1000 years.
Re: (Score:2)
If you're basing your critical time-dependent software on year:day:month:hour:minute:second time formats, you're a dope.
Your computer could care less, and the things you schedule in that format are about as critical as snooze alarms.
Re: (Score:2)
But only the handful of computer operators and nuclear scientists use UTC; the rest can use UT1 or more accurately continue to use EST, or MST, or GMT, which will likely track UT1 which will continue to take into account leap seconds.
From the article:
Reprogramming of operational software that already presumes UT1 and UTC are always within a second of
each other would be required, and some space operations and astronomical applications would need to
distinguish between the UTC without leap seconds and UT1.
Re: (Score:2)
Re: (Score:2)
Speak for yourself, timezone-off-center dweller.
Re: (Score:2)
Oh the horrors. My grandkids will mock me thusly "Sonny, back when I was a kid, we would have had to wait until 04:17:43, a whole 20 seconds longer, for the sun to rise on July 4th."
Re:Membership Required (Score:5, Informative)
The Download: PDF Only link on the right hand side of the first linked page (Cornell) gives you a PDF of the same article [arxiv.org].
Re: (Score:2)
Yeah, no kidding. Here I am thinking, "maybe I should stop my regular pattern of opening my big mouth in the comments without bothering to read the article first, and go RTFA first!" And then I find that I can't! What a crock.
Re: (Score:2)
I really don't care about coordinated universal time or time that has to be regular. I care about the real rotation of the Earth and the Earth's orbit around the sun. So, what we see in the sky is always gonna matter most to me and not what humans create :) It doesn't matter to me if it's irregular.
And you're going to notice a small number of seconds difference?
Re:It's about time (Score:5, Informative)
Seriously this has been an issue for along time - GPS time does not include leap seconds and I am tired of having to write software that let's user adjust for the variable amount of leap seconds - nobody really cares if the earths rotation is synchronized with " UTC"
Those who doesn't care about synchronisation already have the option to use TAI. They should use that instead of redefining UTC.
Re: (Score:2)
No, we don't have this option. See CCTF/09-27 [bipm.org] which was submitted to ITU-R SG7A in 2007-09 and which said
That's not their call. TAI a well known and well-defined time scale. Unless and until we become subject to the Digital Millennium Timekeeping Act or some similar insanity, we have the option to use it however we please.
Re: (Score:3)
Leap seconds is already included in the GPS stream. So, with the GPS stream you get GPS time, and UTC time. Most GPS receivers output GPS time until they've received the NAV or other message that has the leapseconds count in it, and then correctly updates to UTC time. It seems like a simple, solved problem. Am I missing something with respect to your leap year stuff?
Re: (Score:3)
You're doing it wrong.
No it's pointless. (Score:2)
Time conversion is complicated because the universe is complicated. The time it takes to orbit around the sun isn't a nice even multiple of the amount of time it takes for the earth rotate, or any subdivision of that day. It isn't even constant as the drag of the moon and the shifting of the tectonic plates all affect the rate at which the earth rotates.
Over time we have developed many different ways of measuring time, each of which have their own advantages and disadvantages depending on the application. T
Re: (Score:2)
Um, GPS sends the GPStime/UTC offset.
http://en.wikipedia.org/wiki/GPS#Timekeeping_and_leap_seconds [wikipedia.org]
It's been done. (Score:5, Informative)
(GMT hasn't been in use for a long time, although most people use the term interchangeably with UTC).
Re: (Score:2)
> GMT hasn't been in use for a long time
Au contraire - it is the official time of GB and Ireland. As such it is subject to Daylight Saving Time (called BST), and very different from UTC. So using GMT could cause never ending confusion...
Funny enough gruve.com made exactly that mistake: it does not support DST for GMT. And support is unable to help.
Anyway, the C in UTC stands for coordinated, so I cannot see how they could redefine it without turning it into a lie.
Re: (Score:3)
Re: (Score:2)
Re: (Score:2)
Redefining UTC is just plain stupid - it was created to track sol.
Actual sol or relativistically delayed sol?
Re: (Score:2)
Re: (Score:2)
Protip: It's after the "U".
Re: (Score:2)