It would appear that making adjustments every 10 days is not
often enough, at least in the US, viz:
http://www.nist.gov/pml/div688/grp50/NISTUTC.cfm
http://www.nist.gov/pml/div688/grp50/nistusno.cfm
Even if we abandon the leap second, we have issues at the nanosecond level.
This is what
Alas, 'tis neither normal nor expected by the APIs and the programmers
who are implementing systems that deal with time.
Let me find some good references for you on how the UTC
paper clock actually works. Inter-comparing the clocks from
each national laboratory is in itself a fascinating
On Fri, Jan 14, 2011 at 13:47, Tom Van Baak t...@leapsecond.com wrote:
You really didn't expect 250 diffeent atomic clocks around
the world to all agree at the ns level at all times did you?
tounge-in-cheek
Why not? nano is 10E-9, and I see references to people trying for clocks
with 10E-12
