Our librarian has assigned the Library of Congress classification QB213 .R4
2013 to the proceedings of “Requirements for UTC and Civil Timekeeping on
Earth” (ISBN 978-0-87703-603-6, http://futureofutc.org/preprints/). Looking on
the shelf, this is next to the proceedings for IAU Symposium 11,
On Jan 17, 2014, at 5:17 AM, Tony Finch d...@dotat.at wrote:
Note that DST exists because people prefer to set their clocks to sunrise
than to midday, but sunrise is too inconvenient so we use a quantized
approximation.
DST exists for a complex set of sociological and political reasons.
, apparently only in support of some dreary turf battle among special
interests.
Everything not forbidden is compulsory
- Murray Gell-Mann quoting T.H. White
Rob Seaman
National Optical Astronomy Observatory
___
LEAPSECS mailing list
On Jan 19, 2014, at 12:31 AM, Clive D.W. Feather cl...@davros.org wrote:
Rob Seaman said:
Systems, software and civilization depend on both interval time and Earth
orientation time.
In what way does civilization depend on Earth orientation time?
Thanks for acknowledging (through omission
On Jan 20, 2014, at 10:43 AM, Warner Losh i...@bsdimp.com wrote:
[*] An interesting side note about days: The ancient Egyptians regarded light
and night as two separate realms rather than as being two halves of the same
day. The notion of the synodic day thus dates only from the new kingdom,
On Jan 31, 2014, at 10:37 AM, Warner Losh i...@bsdimp.com wrote:
On Jan 31, 2014, at 10:30 AM, Peter Vince wrote:
On 30 January 2014 23:07, Steve Allen s...@ucolick.org wrote:
The revised text for Radio Regulation 2.5 makes no sense. If the time
scale is defined by SI seconds of cesium
I could have sworn that was Nye v Ham, not the State of the Union…
On Feb 5, 2014, at 4:50 PM, Richard Clark rcl...@noao.edu wrote:
I'm surprised that someone on the list hasn't already pointed this out.
Today February 5 2014 (already yesterday in much of the world) marks
the 90th
On Feb 8, 2014, at 5:11 PM, Brooks Harris bro...@edlmax.com wrote:
On 2014-02-07 04:12 AM, Poul-Henning Kamp wrote:
In message 20140206151947.ga25...@ucolick.org, Steve Allen writes:
Taken at face value Google's Site Reliability Team would seem to be
arguing for the return to the bad old
On Feb 9, 2014, at 11:20 AM, Warner Losh i...@bsdimp.com wrote:
On Feb 9, 2014, at 11:13 AM, Rob Seaman wrote:
If anything has prevented leap seconds from death it is the weakness of the
proposal itself. And the real-world distinction between Universal Time and
Atomic Time; Death to leap
On Feb 10, 2014, at 9:57 AM, Warner Losh i...@bsdimp.com wrote:
On Feb 10, 2014, at 9:02 AM, Rob Seaman wrote:
Like I said, it is an attempt to confuse two different concepts.
We disagree here then. Atomic time is adequate for civil needs. The small
divergence can be handled the same way
On Feb 10, 2014, at 4:49 PM, Warner Losh i...@bsdimp.com wrote:
The leap forward or back an hour due to increasing out-of-syncness with the
sun would be a drop in the bucket.
A standard bucket is around 10 liters:
http://www.amazon.com/b/ref=dp_brw_link?ie=UTF8node=2245509011
And a
On Feb 11, 2014, at 9:31 AM, Tony Finch d...@dotat.at wrote:
Warner Losh i...@bsdimp.com wrote:
Perhaps, but leap seconds are a solution to the problem that must die in
the fullness of time. With the quadratic acceleration there will come a
time in a few thousand years when one leap second
, at 10:04 AM, Tony Finch d...@dotat.at wrote:
Rob Seaman sea...@noao.edu wrote:
On Feb 11, 2014, at 9:31 AM, Tony Finch d...@dotat.at wrote:
Yes. And time zone adjustments will be able to keep civil time in sync
with earth rotation for a much longer time than leap seconds :-)
Nonsense
On Feb 12, 2014, at 8:47 AM, Warner Losh i...@bsdimp.com wrote:
The linux kernel has been touted by some of its proponents as the most tested
and verified kernel around. Some may quibble with this characterization, but
if not the most, certainly one of the most. And even so, this problem
, Rob Seaman wrote:
Meanwhile, whatever discussions occur on this list should flow from
documented case studies:
http://www.cacr.caltech.edu/futureofutc/preprints/files/2_AAS%2013-502_Allen.pdf
Not untethered speculation.
Untethered speculation? Sweet! I've never had my direct
On Feb 16, 2014, at 4:30 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message 5300838b.8030...@edlmax.com, Brooks Harris writes:
It seems the meaning of the term Standard time in common-use and in
POSIX is in conflict with the definitions in ISO 8601 and IEC 60050-111.
It seems to
On Feb 16, 2014, at 3:05 PM, Clive D.W. Feather cl...@davros.org wrote:
Brooks Harris said:
Where daylight saving time is used, the term standard time typically
refers to the time without the offset for daylight saving time..
That is consistent with my understanding of Standard time.
For five years running the Chilean government has provided very short notice of
changes to the local daylight saving time rules. This year only 2.5 weeks
advance notice (shifting off DST was scheduled for March 8):
On Feb 24, 2014, at 3:23 PM, Clive D.W. Feather cl...@davros.org wrote:
Rob Seaman said:
Chile's rules are familiar because many observatories are located in that
timezone, but presumably the same shenanigans play out worldwide. It is not
obvious why a couple of weeks notice is acceptable
On Feb 25, 2014, at 12:10 AM, Ian Batten i...@batten.eu.org wrote:
On 24 Feb 2014, at 22:56, Rob Seaman sea...@noao.edu wrote:
Rather, there have to be very close to 86,400 SI-seconds per day, because
that how long a day is.
And this is why engineers and scientists make bad public policy
Pertinent to recent discussions:
http://imgs.xkcd.com/comics/now.png___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
Hi Richard,
The URL in the original email is for embedding. The original page (with that
URL embedded) is:
http://xkcd.com/1335/
and should auto-update (every 15m it looks like) in most browsers. Hover over
the image to see the popup with instructions.
Rob
--
On Feb 26, 2014, at
On Mar 1, 2014, at 1:04 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message 20140301001133.gc12...@ucolick.org, Steve Allen writes:
He says he doesn't know what time it is, but he knows what a second is.
It is again unfortunate that POSIX chose to define the second differently.
The Astronomy Picture of the Day for 2014 May 16 demonstrates that day means
the same thing on Mars as on Earth:
http://apod.nasa.gov/apod/ap140516.html
One supposes that if leap seconds cease and the meaning of day becomes
ambiguous that we could instead start using the word sol as on
Ask Bjørn Hansen writes:
I'd compare it to adding decimal digits to Pi instead of just saying 3 is
accurate enough.
Warner Losh says:
A more proper analogy would be using 3.141593 instead of 3.1415926…
Proper analogies, is it? More like 2.7182818 - the functional forms differ.
To do
On Aug 26, 2014, at 4:43 AM, Tony Finch d...@dotat.at wrote:
Gerard Ashton ashto...@comcast.net wrote:
For example, if one wishes to use the format 2014-08-24, is it mandatory
that the day begin at midnight according to some unspecified local time?
ISO 8601 does not specify the time zone
over the many many
years of this discussion. Only one non-physical non-option has ever been
considered by the ITU. It is the ITU who are being tedious.
Rob Seaman
National Optical Astronomy Observatory
___
LEAPSECS mailing list
LEAPSECS
characteristics would be fair game, including an absence of leap seconds. The
ITU would then simply recommend TI instead of UTC.
Nothing would be renamed. Nothing would be redefined.
Rob Seaman
National Optical Astronomy Observatory
___
LEAPSECS mailing
of the
day. Their actions should aspire to agree with physical reality.
Rob Seaman
National Optical Astronomy Observatory
—
* As the element plutonium was named after the recently discovered planet
Pluto, the element cerium was named for Ceres; the metal was isolated just two
years after
Day is a fundamental physical fact about a planet or moon. Minute is an
artificial concept. Its intuitive role as a fraction of a day takes precedence
over serving as a round number of equally artificial SI seconds. There are two
kinds of time that must be accommodated.
Rob Seaman
NOAO
, and if TAI is
somehow deficient that another time scale be defined with its own new name.
This was the position at the Torino colloquium in 2003.
Rob Seaman
NOAO
--
Steve Allen wrote:
On Thu 2014-10-30T12:18:39 -0700, Rob Seaman hath writ:
Do you have any comments on this question
was sufficient to
prevent a resolution or to prevent forwarding it to the ITU, and the report
was delivered to the IAU Exec in a timely fashion.
Rob Seaman
National Optical Astronomy Observatory
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https
of transition.
• Responsibility for disseminating UT1 information should remain solely
with IERS.
Rob Seaman
National Optical Astronomy Observatory
--
From: Rob Seaman sea...@noao.edu
To: Leap Second Discussion List leapsecs@leapsecond.com
Sent: Thursday, November 6, 2014 10:45 PM
Subject
what a timescale without leap seconds should be called. If it doesn't
function as Universal Time it should not be referred to as a type of Universal
Time.
Rob Seaman
National Optical Astronomy Observatory
___
LEAPSECS mailing list
LEAPSECS
Hi Poul-Henning,
Getting off topic a bit, the comment in leap.py says:
# I chose 0xcf after an exhaustive search for best performance
# on 28 bit messages.
However, crc8() is being called on the entire first three bytes so 24-bits on
encoding and 32-bits on decoding. I’m not
On Jan 24, 2015, at 7:27 AM, Rob Seaman sea...@noao.edu wrote:
As shown, I think we also want to index TAI-UTC after the leap. This is
similar to how the IERS table has it, and remaining aligned with that
resource may be a strong enough argument. (Negative leap seconds would also
be made
On Jan 26, 2015, at 12:21 PM, Warner Losh i...@bsdimp.com wrote:
It all depends on the data that you are using whether the new day starts at
midnight
or noon. If you are talking to astronomers before the 20th century, chances
are good
it is noon.
Big fan of Patrick O'Brian. Frequent
RR?
On Jan 23, 2015, at 2:43 PM, Steffen Nurpmeso sdao...@yandex.com wrote:
Rob Seaman sea...@noao.edu wrote:
|On Jan 23, 2015, at 5:33 AM, Steffen Nurpmeso sdao...@yandex.com wrote:
| This is logical. I indeed have *no* idea on what can happen, \
| which is one of the reasons that i am
I think it’s clear that DNS won’t support all leap second use cases, but that
it may provide a high reliability / low latency method for some specific
purposes. Here is PHK’s specific example:
$ dig +short leap.net-tid.dk a | ./leapdecode.py
248.40.141.250 - OK 2015 7 +35 +1
On Jan 17, 2015, at 1:51 PM, Steffen Nurpmeso sdao...@yandex.com wrote:
Maybe it would be sufficient to start at 2014, which would avoid counting
months of 42 years
However the data are encoded, stored or retrieved, there will be a concept of
operation that supports a variety of timekeeping
On Jan 17, 2015, at 4:12 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
If you need the historical information, you can afford the TCP
connection to IERS.
There's also value in implementing a single ICD for all use cases, but point
taken.
I'm focused on how NTP/PTP clients will be able to
On Jan 16, 2015, at 3:37 AM, Tony Finch d...@dotat.at wrote:
$ dig +short leapsecond.dotat.at | sed 's/:6:/:06:/' | sort
Stupid sed tricks to be compliant both with extended ISO-8601 and with the end
of any month requirement of TF.460:
% dig +short leapsecond.dotat.at | sed -e
On Jan 16, 2015, at 8:57 AM, Warner Losh i...@bsdimp.com wrote:
I’m *loving* this.
It's a bit of a goof...but that doesn't necessarily invalidate the gimmick.
In fact, you could actually make the lookups easier if you leveraged the
domain
system. month.year.lastsec.utc.int would be the
Warner,
Is this what you meant?
% dig +short jun.2009.leapsec.com txt
2009-06-30T23:59:59Z”
I don’t want to invest the time typing two entries per year for the past four
decades into the rather constrained web interface if this isn’t the concept ;-)
(Hmm…looks like I can
On Jan 22, 2015, at 3:27 PM, Steffen Nurpmeso sdao...@yandex.com wrote:
One of them is that the count of months start 2014 not 1972, which
extends the representable range of years until 2099.
Prior leap seconds don’t vanish - nor do prior Bulletins C. There certainly
may be retroactive use
On Jan 22, 2015, at 7:47 AM, Steffen Nurpmeso sdao...@yandex.com wrote:
Rob Seaman sea...@noao.edu wrote:
I think it’s clear that DNS won’t support all leap second use cases, but
that it may provide a high reliability / low latency method for some
specific purposes. Here is PHK’s specific
Zefram zef...@fysh.org wrote:
My Charlottesville paper
https://www.fysh.org/~zefram/time/prog_on_time_scales.pdf gives a
list of desiderata that includes the above, and some others, but without
much rationale.
I've been wondering whether the file format should be textual or
binary.
On Feb 11, 2015, at 7:08 AM, Rob Seaman sea...@noao.edu wrote:
For my current encoding, PHK's CRC keeps the final octet out of harm's way:
255.255.255.47 - OK 2142 8 127 -1 (1, 1)
As shown, the first three 255s would require a negative leap second at the
end of July 2142
On Feb 10, 2015, at 3:43 PM, Clive D.W. Feather cl...@davros.org wrote:
Zefram said:
My concern is more about the risk of colliding with some other protocol.
The answer is to not pervert A (or AAA) records for a purpose they are not
designed for. Either use TXT records or, even better, make
On Feb 15, 2015, at 10:32 AM, Zefram zef...@fysh.org wrote:
OK, have a play with the attached. Comments welcome. Second implementation
especially welcome.
There was a missing perl JD module from the host I first tried. Will try again
later from a different machine.
Man page looks solid.
I realized I hadn't updated the printed header:
Domain Name IPv4 DecodedFlags
bulletin-c.leapsec.com - 250.10.36.152 - OK 2015 7 36 1 (1, 0)
On Jan 28, 2015, at 10:02 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
We each wear multiple hats. Two of mine are 1) to point out that
physical reality trumps standards and software, [...]
And one of my hats is to point out that you have no monopoly on
defining physical reality and
On Jan 28, 2015, at 1:34 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
Derives from is not a physical reality, it's merely a social custom.
So many replies to choose from - and so many that have been posted in the past
- let's go with some (unvetted) quotes on custom:
- Truth always
On Jan 29, 2015, at 1:05 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message bdf1dd12-9e80-4516-91ba-76127dcb9...@noao.edu, Rob Seaman writes:
On Jan 28, 2015, at 1:34 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
Derives from is not a physical reality, it's merely a social custom
On Jan 30, 2015, at 8:41 AM, Warner Losh i...@bsdimp.com wrote:
Rob loves to quote the archives as if they irrefutably prove his point.
My point is that a coherent approach to systems engineering would be the most
efficient and robust way to resolve the issue. Is this controversial? And
with the same
value as the current leap01 but called something like beginning_of_utc or
some such.
Thanks!
Rob
--
On Jan 25, 2015, at 10:00 AM, Michael Deckers via LEAPSECS
leapsecs@leapsecond.com wrote:
On 2015-01-25 14:58, Rob Seaman wrote:
Please let me know about typos
On Jan 25, 2015, at 9:57 PM, Warner Losh i...@bsdimp.com wrote:
On Jan 25, 2015, at 6:15 PM, G Ashton ashto...@comcast.net wrote:
Rob Seaman also wrote:
Leap seconds are introduced at midnight UTC, not when TAI modulo 86400
equals zero.
I would think that midnight UTC is the instant
As with you and Warner, just making sure we’re on the same page.
On Jan 23, 2015, at 2:05 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
There is a separate identity test on the first four bits, so in
relation to the CRC they just modify the initial state.
Yes
The actual message,
On Jan 24, 2015, at 1:29 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message e1yeqbo-0007gl...@www.xplot.org, Tim Shepard writes:
What should next.leapsec.com point at after July 1, 2015 in the few
weeks before Bulletin C number 50 is issued?
It should point to C49 until C50 is
Tom and I seem to keep the same (early) hours...
On Jan 27, 2015, at 4:49 AM, Tom Van Baak t...@leapsecond.com wrote:
But there have been real bugs due to leap indicators remaining set too
long, leading to bogus leaps at the end of July. So in practice there is
less risk in allowing leaps
Hi Tom,
In addition to an interesting systems engineering exercise, it’s great to see
this list working together on something :-) In addition to your kind offer,
Tony Finch should be acknowledged for the original IPv6 notion, and PHK for
settling most of the pragmatic issues with an IPv4
We each wear multiple hats. Two of mine are 1) to point out that physical
reality trumps standards and software, and that 2) that there are precious few
conversations here that haven’t occurred before:
- Warner has explained his use case in the past. There are likely no
engineering use
should be provided in a good format using flexible protocols
implemented on scalable hardware with robust network connections.
Rob Seaman
NOAO
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
On Jan 13, 2015, at 6:10 AM, Brooks Harris bro...@edlmax.com wrote:
On 2015-01-12 06:42 PM, Rob Seaman wrote:
On Jan 12, 2015, at 2:53 PM, Martin Burnicki martin.burni...@meinberg.de
wrote:
I've suggested at various occasions that the IERS should be the
authoritative source for a leap
I'm very much enjoying the dueling perl / python and CRC / SHA competition here
:-)
On Feb 10, 2015, at 9:45 AM, Zefram zef...@fysh.org wrote:
Rob Seaman wrote:
The trouble with encoding dates in the names and interpolating in the
client is that by the time you're done it would have been
Just a reminder that even if future leap seconds cease (Chronos forbid!), they
exist now and will always exist retroactively during these last several
decades. Features and infrastructure improvements such as we are discussing
have value under all scenarios.
Rob
--
On Feb 10, 2015, at 9:46
I read slashdot so you don’t have to (you’re welcome):
NIST Technical Note 1867:
Time-Aware Applications, Computers, and Communication Systems (TAACCS)
http://dx.doi.org/10.6028/NIST.TN.1867
Kind of quiet around here lately; debating the implications of timekeeping in
the IoT
Clive D.W. Feather cl...@davros.org wrote:
Poul-Henning Kamp said:
We have a saying in danish Skoma'r bliv ved din læst which translates
to Cobbler stay at your workbench.
The English word is last: The cobbler should stick to his last. Almost
certainly with the same derivation.
If you
On Mar 11, 2015, at 11:04 AM, Tom Van Baak t...@leapsecond.com wrote:
The entire purpose of UTC is to provide a single timescale for all
human-related activity.
Well… ;-)
Received: from barracuda-1.noao.edu … Wed, 11 Mar 2015 11:05:10 -0700
Received: from six.pairlist.net ... Wed, 11 Mar
) for backwards compatibility. Many other issues are discussed in:
http://www.cacr.caltech.edu/futureofutc/2011/preprints/01_AAS_11-660.pdf
Rob Seaman
National Optical Astronomy Observatory
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https
Från: Steve Allen
Datum:2015-03-02 05:51 (GMT+01:00)
Till: Leap Second Discussion List
Rubrik: [LEAPSECS] prevarication?
An op-ed in GPS World suggest the use of a GNSS simulator
http://gpsworld.com/expert-advice-a-leap-into-the-unknown/
I wonder if attributing prevarication to the
I can load this URL in a browser:
http://hpiers.obspm.fr/iers/bul/bulc/Leap_Second_History.dat
But PHK’s python code (which worked a couple of month’s ago):
def fetch_url(url):
global conn
print(Fetch, url)
if conn == None:
conn =
On Jan 23, 2015, at 5:33 AM, Steffen Nurpmeso sdao...@yandex.com wrote:
Rob Seaman sea...@noao.edu wrote:
It is much cleaner and more robust to support the entire history of leap
seconds.
Ok i'll bite: why this? This service would only track future changes with
the first adjustment
On Jan 25, 2015, at 1:03 PM, Stephen Scott stephensc...@videotron.ca wrote:
Since UTC is defined by the IERS before 1972-01-01 beginning_of_utc is not
appropriate.
This is the beginning of integer leap seconds, not UTC.
Contributors to this list can always count on prompt fact checking ;-)
to suggest that a systems engineering process will produce better
results than politics. But seeking to advance one clock at the expense of the
other will fail just like Canute, and we should be as graceful to accept this
fact as Henry of Huntingdon’s description of Canute.
Rob Seaman
National Optical
Again, these topics are well covered in the archives. By all means talk about
them more, but it would be appropriate to include the top post(s) of prior
thread(s) when restarting a topic.
To summarize some previous talking points: Only a small fraction of the world
observes daylight saving
Thanks for the reminder!
This was announced on the original leapsecs list on 24 Apr 2003:
http://www.ucolick.org/~sla/navyls/0358.html
(So one or the other is likely misdated.) Useful discussion followed:
http://www.ucolick.org/~sla/navyls/0355.html
On May 5, 2015, at 6:16 PM, Warner Losh i...@bsdimp.com wrote:
This is an excellent example of the unintended consequences of leap seconds,
and the ways they insinuate themselves into non-obvious parts of the code.
...and is it somehow impossible that there might be unintended consequences
On May 5, 2015, at 8:37 PM, Warner Losh i...@bsdimp.com wrote:
It is time to look at other solutions to the synchronization problem that can
be implemented correctly.
By all means. That is not what the ITU has been doing. Redefining UTC to
cease leap seconds is the opposite of a solution.
On May 5, 2015, at 6:38 AM, Tom Van Baak t...@leapsecond.com wrote:
But adapting to new requirements, to new possibilities, to new performance is
ok. This is one reason why I sympathize with those who want to abandon leap
seconds.
Discovering new requirements doesn't mean old engineering
The sun sets on two planets: http://apod.nasa.gov/apod/ap150512.html
...and both days were solar (synodic) days.
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
Day means “solar day” on Ceres, too:
http://www.jpl.nasa.gov/news/news.php?feature=4555
http://www.jpl.nasa.gov/news/news.php?feature=4555
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
On May 19, 2015, at 1:39 PM, Joseph M Gwinn gw...@raytheon.com wrote:
In short, POSIX systems have to be able to work in a cave, with no access to
the sky or knowledge of astronomy.
If the cave has access to NTP it has access to the IERS.
And astronomy happens underground as well:
On May 19, 2015, at 10:46 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message 05e65caf-d064-4d4e-aa16-195fe7d15...@noao.edu, Rob Seaman writes:
On the other hand, the one thing we can be sure about POSIX is
that it will ultimately have a finite lifespan. But a day on Earth
On May 20, 2015, at 11:27 AM, G Ashton ashto...@comcast.net wrote:
I think calendars count observed day/night cycles.
They are not arbitrary day/night cycles. What has been observed is Earth has a
sidereal rotation period; during its annual lap around the Sun one of those
rotations is
Others may point out that median and average are different things. (Or that
the tails of a distribution may contribute more than measures of central
tendency.)
But more fundamentally, programming is not a one-dimensional skill. Raw coding
speed is different from debugging or data engineering
On Jun 23, 2015, at 6:00 AM, Kevin Birth kevin.bi...@qc.cuny.edu wrote:
For anyone curious enough to search for information online about the leap
second in Japan, the Japanese term for leap second is:
うるう秒
And indeed Google and Jisho translate that as leap second. For some reason
Bing
On May 30, 2015, at 3:05 PM, Tom Van Baak t...@leapsecond.com wrote:
Oh, you're such an old earth+photon guy. Ask any space probe, neutrino, or
gravitational astronomer if they share your sleep problem. ;-)
As with timekeeping in general it is a question of complex systems-of-systems,
e.g.:
On May 29, 2015, at 10:52 PM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
In message 11BA4A073E104FD29BD9DB1892B7C60F@pc52, Tom Van Baak writes:
And now for something completely different...
http://www.theregister.co.uk/2015/05/29/windows_azure_second_out_of_sync/
The opererative
On Jul 1, 2015, at 1:31 AM, Poul-Henning Kamp p...@phk.freebsd.dk wrote:
it is pretty obvious that John Olivers attention to the leap-second vastly
increased the awareness.
It was the final kick, but the interest level was up broadly already, with many
new voices like:
, 2015 at 3:51 AM, Rob Seaman sea...@noao.edu
mailto:sea...@noao.edu wrote:
Is it too late to get an option E added of simply scheduling “summer leap
seconds on the last Sunday morning in June?
Depending on when on Sunday you do this, it may still after the Sydney Stock
Exchange starts
http://blogs.wsj.com/speakeasy/2015/06/29/john-oliver-really-wants-you-to-enjoy-tomorrows-leap-second/
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs
PHK and others make good points, but I’m still trying to get past the
binary-file equivalent of XML”. I doubt this is worth much more investigation
from this group, but in addition to git:
https://github.com/Matroska-Org/ebml-specification
there are a few links from the wikipedia
What are people’s plans for the day? Aside from reading the usual mishmash of
bad (and some good) news articles, I’m planning to make a shaker of Margaritas
in my rocket ship (http://bit.ly/1HvwlHn http://bit.ly/1HvwlHn) and watch /
listen to the music of the time signals with my perplexed but
Hi Richard,
And I'm still curious how the people in western China deal with it.
This topic has been raised before, here and elsewhere:
http://articles.latimes.com/2009/mar/31/world/fg-china-timezone31
Short answer is that different groups in the same place set their clocks to
Anybody know anything about this? The Economist says:
The Brazilian stock exchange adjusted its clocks on June 28th, a
Sunday, when it was closed.”
(http://www.economist.com/blogs/freeexchange/2015/06/leap-seconds-and-financial-markets
I was going to nominate the one-word headline, “Panic!”, as the most hyperbolic
of the day, but rather will go with:
Universes could be created during Tuesday's leap second”
(http://www.cnet.com/news/universes-could-be-created-in-the-time-it-takes-tuesdays-leap-second-to-pass/
Any thoughts on watching Google’s (or anybody else’s) smear in action? Kind of
like watching paint dry, but still…
For folks without an analog radio handy, what’s the best online (simulated or
realish) WWV (or other time signal) audio, strictly for ambience? Won’t be
like listening in a
Hi Richard,
Matsakis advocates the abolition of the leap second, pointing out that we
already spend so much our time out of sync with the earth’s rotation.”
So what you’re saying is that Demetrios won’t so much be celebrating for
himself? ;-)
“This is what happens in the summertime,” he
, Jun 30, 2015 at 09:42:50PM +0100, Rob Seaman wrote:
Any thoughts on watching Google’s (or anybody else’s) smear in
action? Kind of like watching paint dry, but still…
I did think about fetching it hourly, to see if I could see dirft
in the HTTP timestamps, but didn't get around to scripting
501 - 600 of 646 matches
Mail list logo
