Hi Tom,
Your nixie clock got to 23:59:60 and then started counting backwards!
It still is, and it counts backwards through 60 in the seconds field,
skipping 01 - currently at 2015.06.30 23:49:60. See the video clip I
sent you last time. Maybe it's a southern hemisphere thing.
Regards,
Mark
the SOFA home page where the
latest release is dated 2014-10-07.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
On Tue 2012/01/24 07:18:36 -0800, Steve Allen wrote
in a message to: Leap Second Discussion List leapsecs@leapsecond.com
The ones with WWVB
receivers in them do a little dance every night when nobody is
watching and the signal is strong, and that dance looks a lot
like the handling of a leap
On Tue 2012/01/24 08:22:41 -, Poul-Henning Kamp wrote
in a message to: Mark Calabretta mcala...@atnf.csiro.au
and copied to: Leap Second Discussion List leapsecs@leapsecond.com
int tmdiff(const struct tm *tm1, const struct tm *tm2, double *diff);
Return the time interval, *tm2 - *tm1
On Tue 2012/01/24 16:23:17 PDT, Warner Losh wrote
in a message to: Leap Second Discussion List leapsecs@leapsecond.com
In the latter, the second hand would move continuously past 60 to 01
second and immediately flick back to 60, thus making it possible to
reckon time during a leap second.
Or
On Tue 2012/01/24 16:53:37 PDT, Rob Seaman wrote
in a message to: Leap Second Discussion List leapsecs@leapsecond.com
Might I suggest that real is a poor descriptor here (no
philosophy intended)? There is a vast prior art of real time
that means something entirely different.
In addition, there
On Mon 2012/01/23 08:05:15 -, Poul-Henning Kamp wrote
in a message to: Mark Calabretta mcala...@atnf.csiro.au
and copied to: Leap Second Discussion List leapsecs@leapsecond.com,
Keith Winstein kei...@mit.edu
So effectively what is needed is a function to subtract two tm structs.
You
On Fri 2012/01/20 07:50:47 -, michael.deckers wrote
in a message to: Leap Second Discussion List leapsecs@leapsecond.com
existence. Is it any wonder that leap seconds may not have been
implemented properly?
Can you point us to an implementation that does it properly?
Try Tom's
On Fri 2012/01/20 11:29:18 -, Poul-Henning Kamp wrote
in a message to: Leap Second Discussion List leapsecs@leapsecond.com
I would like your comments on this API proposal, if we can agree
that it workable, I am willing to push it, hard, in the UNIX world.
This ticks all the right boxes for
picked up that glaring error.
Approximately one hour after 600 years is the canonical figure.
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
to know better, seem
not to be aware of it.
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
be a bit better explored.
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
.
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
On Thu 2012/01/19 20:54:52 -0800, Tom Van Baak wrote
in a message to: Leap Second Discussion List leapsecs@leapsecond.com
Welcome back to the list. It's been a while.
I have to admit to lurking, though usually take shelter during
the cyclone season, except this season was too hard to ignore
for
seconds.
If anyone were to make that argument.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
including deceleration), which seems much preferable to letting it
grow without limit.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
, it is
a specious argument that should be rejected. The solution, in the
distant future when it does start to bite, will be to measure the
length of day properly - finally admit that there are more than 86400
SI seconds in it.
Regards,
Mark Calabretta
effect of Special Relativity.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
or the sidereal day of 23 hours, 56 minutes.
Heartfelt thanks to the Association for Biblical Astronomy for a
light-hearted interlude.
...I wonder what they make of the CMB dipole anisotropy?
Or Foucault's pendulum.
Regards,
Mark Calabretta
___
LEAPSECS mailing
/Proper_time as well as Rob's references.
I think someone already mentioned that GPS satellites correct for
time dilation, though their orbital velocities make for a much
larger correction.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS
seconds
would seem to be asking for trouble so far as interpreting
historical timestamps is concerned.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
attitude at the refinery or oil rig.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
round.
Whatever the timezone in London is in July, one thing it certainly
_isn't_ is GMT. They mean clock on the wall time in places where
the civil time is UTC or UT1 during the winter. Extra fun will
Microsoft gets it wrong? Never! Surely it must be user error.
Regards,
Mark Calabretta
for immediately changing UTC, would it be too much to
expect that its replacement actually solve the problem rather
than simply delay it?
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo
level of chaos, one that will eventually lead to multi-hour offsets
that continue to grow over time.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
.
Not if the timestamps are properly labelled with the timezone,
preferably specified as an offset, which distinguishes between
DST and non-DST.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
the equation of time (and the
obliquity of the ecliptic).
http://apod.nasa.gov/apod/ap101231.html
http://apod.nasa.gov/apod/ap061230.html (Mars)
http://apod.nasa.gov/apod/ap050713.html (Moon)
Check out the last two particularly.
Regards,
Mark Calabretta
if you correctly predict the date of the next leap second, and
you give me $850 if I predict the date of the next leap day.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
.
And anyone who cannot see a pythonesque dialogue in this needs a
humour-transplantation:
Would you care to speculate on what the Pythons might have made of
the long-term unpredictability of the Gregorian calendar itself?
Regards,
Mark Calabretta
face is another
problem, again not fundamental - solutions can be found.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
calendar will no longer accurately
reflect the ratio between the length of the year and the length of the
day.
Agreed. Which is to say that that the quadratic blow out in leap
seconds is a specious argument which should be rejected.
Regards,
Mark Calabretta
, as we used to say, this is just an implementation
detail. Someone does it, and everyone else uses it.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
reductio ad
absurdum result of a leap-second-per-day, should hopefully cause
a re-examination of this convenient untruth.
However, it is a very distant horizon.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http
of calendar date to Julian Date.
The fundamental problem is that there is no formula for determining
when leap seconds occur.
Regards,
Mark Calabretta
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
than what ITU-R
are offering - though it wouldn't have the political clout to
implement it.
Mark Calabretta
ATNF
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
--- Forwarded Message
Date: Mon 2008/03/31 14:28:15 +1100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Client Notification: Daylight Savings Issues
Client Notification: Daylight Savings Issues
IMT wish to advise that a number of Daylight Savings issues are
currently being
37 matches
Mail list logo
