News for hackers. Stuff that matters.
Re:Time.is by roryokane on Sunday March 11, 2012 @03:22PM (#3691018)
I'm wondering how atomic clocks in general get set in the first place. Did, at some point, scientists calculate when the sun was exactly overhead Greenwich and call that noon? Because I would think that that calculation would have a multi-second error, so setting your clock to the second would be pointless.

Or maybe there is no such thing as "actual physical time" and there is only what people have agreed to call the standard. But in that case why do time sources, such as time.gov and time.windows.com, still give different times? I would think Microsoft would have fixed any bugs in their NTP implementation by now, so it's not that. If it's just politics about nobody wanting to move to someone else's time, then there's no way to tell which source is the real standard, so your most practical choice is to synchronize your clock to the times you deal with. That is, set your clock to your clock at work, or an average of your friends clocks, or whatever source they get their time from. I don't mind the existence of central time sources, because they are better than having to go out and find someone else's clock, but they shouldn't call themselves official if they aren't actually official.

So, does anybody know how the starting time for central time sources is chosen, and if any source is worthy of being called "the real time"?

Re:Time.is by dfc on Sunday March 11, 2012 @03:36PM (#3691052)
UTC is a "paper clock." The calculation of UTC has nanosecond error, not multisecond error. The most recent data for the calculation of UTC:

ftp://ftp2.bipm.org/pub/tai/publication/cirt.290

Time is a really tricky and interesting topic. I would start with:

"From Sundials to Atomic Clocks: Understanding Time and Frequency"

http://www.nist.gov/timefreq/general/pdf/1796.pdf

"Originally published in 1977, this full-length book provides a comprehensive, easy-to-understand introduction to the field of time and frequency. Readers of nearly all ages and educational backgrounds should find it enjoyable. 306 pages."

Re:Time.is by phillmv on Sunday March 11, 2012 @03:37PM (#3691055)
Well… it's an arbitrary standard. We just call a day one full rotation of the earth, and we just happen to divide it into 24hr periods with 60 subdivisions.

Theoretically, you could measure the rotation of the earth and call that a day, but I have no idea how you would measure that down to the millisecond.

As to "Real Time", I don't know about the specific legalities, but the standard goes as follows: everyone uses UTC http://en.wikipedia.org/wiki/Coordinated_Universal_Time which is based off the International Atomic Time http://en.wikipedia.org/wiki/International_Atomic_Time

I too would be interested in how they picked the beginning epoch, i.e. "this moment right here is midnight from which all other seconds shall be referenced against" but in the grand scheme of things it doesn't matter - the only thing that matters is the standard we agreed to measure against.

Re:Time.is by dfc on Sunday March 11, 2012 @03:54PM (#3691103)
"Theoretically, you could measure the rotation of the earth and call that a day"

This is not theoretical; this is known as sidereal time and is measured to the nanosecond...

http://en.wikipedia.org/wiki/Sidereal_time

Re:Time.is by mceachen on Sunday March 11, 2012 @04:10PM (#3691146)
Except that "…due to nutation, an actual sidereal day is not quite so constant."

Yeah. Nutation.

Nutation "…is a rocking, swaying, or nodding motion in the axis of rotation of a largely axially symmetric object, such as a gyroscope, planet, or bullet in flight…"

http://en.wikipedia.org/wiki/Nutation

Re:Time.is by troels on Sunday March 11, 2012 @04:00PM (#3691117)
The rotation of Earth is actually not as stable a thing as one might expect. See for example http://en.wikipedia.org/wiki/Leap_second
Re:Time.is by dfc on Sunday March 11, 2012 @04:13PM (#3691155)
NIST recently published the new ntp.leap file and it looks like we will have one this July...

  3550089600	35	# 1 Jul 2012 [1]
Re:Time.is by apaprocki on Sunday March 11, 2012 @10:13PM (#3692072)
You also need to make sure your IANA tzdata is updated to account for this. I think this leap second was first added in tzdata2012a, but I'd have to check:

ftp://ftp.iana.org/tz/data/leapseconds

Re:Time.is by acqq on Monday March 12, 2012 @07:03AM (#3692992)
If you use Unix time, you don't have to care:

http://en.wikipedia.org/wiki/Unix_time

"Unix time, (...) is (...) defined as the number of seconds elapsed since midnight Coordinated Universal Time (UTC) of Thursday, January 1, 1970 (...) not counting leap seconds"

Re:Time.is by apaprocki on Monday March 12, 2012 @09:32AM (#3693411)
You might not be able to ignore leap seconds if you are interacting with an external system (software or hardware) / API that expects actual UTC. General rule applies to everything.. know your system, know what systems you are connected to, know what standards you need to adhere to.

Microsoft apparently rejected the idea of using leap seconds because Windows just isn't accurate enough:

  The W32Time service uses the Network Time Protocol (NTP) in
  Microsoft Windows Server 2003, in Windows Server 2003 R2,
  in Windows Server 2008, and in Windows Server 2008 R2.
  ...
  The W32Time service cannot reliably maintain sync time to 
  the range of 1 to 2 seconds. Such tolerances are outside 
  the design specification of the W32Time service.
http://support.microsoft.com/kb/939322
Re:Time.is by acqq on Monday March 12, 2012 @11:28AM (#3693856)
Do you happen to know "an external system (software or hardware) / API that expects actual UTC"?

Unix/Linux computers don't, Windows computers don't, GPS doesn't:

http://en.wikipedia.org/wiki/Global_Positioning_System#Timek...

Re:Time.is by apaprocki on Monday March 12, 2012 @12:05PM (#3694046)
GPS doesn't, but GLONASS does:

  GPS Time is designated as being coincident with UTC 
  (USNO) at the start date of January 6, 1980 (00 hours). 
  GPS Time does not count leap seconds, and therefore an 
  offset exists between UTC (USNO) and GPS Time (at this 
  date in April 2007: 14 seconds).

  Unlike GPS, the GLONASS time scale is not continuous and 
  must be adjusted for periodic leap seconds. Leap seconds
  are applied to all UTC time references as specified by 
  the International Earth Rotation and Reference System
  Service (IERS). Leap seconds are used to keep UTC close
  to mean solar time. Mean solar time, based on the spin of 
  the Earth on its axis, is not uniform and its rate is 
  gradually changing due to tidal friction and other 
  factors such as motions of the Earth's fluid core.
http://webone.novatel.ca/assets/Documents/Papers/GLONASSOver...

This is the best overview I've seen of all the pros/cons with regard to UTC and whether leap seconds should be abolished:

http://www.agi.com/downloads/resources/user-resources/downlo...

Basically, much in the same way that we all despise DST (or date differences between Julian/Gregorian calendars), a certain part of me wants to know, if we humans last on this planet long enough, that our descendants thousands of years from now won't look back and curse at us for being idiots and deviating from celestial time.

Re:Time.is by dfc on Monday March 12, 2012 @12:36PM (#3694214)
A lot of RFCs, the first that comes to mind is the timezone seconds offset in DHCP replies and time fields in openpgp standard.

Google probably knows a lot more:

  UTC site:rfc-editor.org