Tom Van Baak wrote:
How about making the second hand variable length. Have it
grow like Pinocchio's nose during a positive leap second.
Although I really like the nose, the jumps are ugly. What about an
adaptive dial made of rubber sheet with a slit at the 12 o'clock position.
There, the two
Rob Seaman said:
Exactly. The search space is a lot larger than explored so far. Consider a
leap second modification to the Chronophage for instance:
http://www.wired.com/culture/design/magazine/17-02/st_chronophage
Bear in mind that this is a clock that only shows the correct time
Rob Seaman sea...@noao.edu wrote:
The way to deal with multi-location metings is to choose a primary
location, then it it obvious what will happen when TZ rules change.
Interesting. Immediately after that I said:
Whatever our individual positions on the issues, they will be better
On 1/25/2012 8:40 AM, Tony Finch explained it would be desirable to store
information about events that are to be observed in local civil time as a
local time and a location, so that the time zone could be looked up close
to the time of the event, and thereby avoid reliance on stale time zone
Gerard Ashton ashto...@comcast.net wrote:
This suggest a desire for an algorithm that accepts as input a latitude
and longitude of a point of interest, and a set of boundaries, and
determines which of the regions the point of interest falls in. Does
anyone know of such an algorithm?
I
Tom Van Baak t...@leapsecond.com wrote:
And again, this is an example of what I meant by a collection of best
practices documents. I think it is much better for the community to
document the idea of smoothed leap seconds and then describe the dozen
ways it has been proposed or actually
Tony Finch wrote:
There's also the railway clock genre, where each clock's second hand ticks or
sweeps slightly fast, and the clock waits at the top of the minute for a
synchronization pulse. Handles leap seconds easily, if the master clock does
:-)
Rob Seaman wrote:
Might I suggest that real is a poor descriptor here (no philosophy intended)?
linear.
-zefram
___
LEAPSECS mailing list
LEAPSECS@leapsecond.com
http://six.pairlist.net/mailman/listinfo/leapsecs
Tom Van Baak wrote:
How about making the second hand variable length.
If we're going for cartoonish variability of the clock face structure,
I'd rather have the seconds marks on the dial move, gradually changing
the number of seconds around the dial from 60 to 61, while the second
hand sticks at
Poul-Henning Kamp wrote:
The name refers to the data type.
Indeed, but real time already means something completely different in
computing. I had a boss who named a server data (after the Star Trek
character). The resulting confusion was monumental.
The data type is more properly termed
In message 43238110-5070-4223-a687-abb760759...@noao.edu, Rob Seaman writes:
Indeed, but real time already means something completely different
in computing. I had a boss who named a server data (after the
Star Trek character). The resulting confusion was monumental.
If you really want fun,
Damn! Yet another joke I'll never be able to explain to my family.
On Jan 25, 2012, at 11:50 AM, Steve Allen wrote:
On Wed 2012-01-25T18:48:28 +, Poul-Henning Kamp hath writ:
I really don't think the name is as important as the semantics.
Stop the presses! We should forward this to
On Jan 25, 2012, at 11:48 AM, Poul-Henning Kamp wrote:
In message 43238110-5070-4223-a687-abb760759...@noao.edu, Rob Seaman writes:
Indeed, but real time already means something completely different
in computing. I had a boss who named a server data (after the
Star Trek character). The
Tony Finch wrote:
You'll have to explain why you think videoconferencing breaks the Olson
timezone database to me, because I don't get it.
I don't recall saying any such thing. The original reply was to this comment
from Daniel R. Tobias:
Usually such events are only fixed relative to
Tony Finch d...@dotat.at wrote:
Have there really been that many? Any refs to ones other than Markus's and
Google's?
There is also my UTR scheme:
http://ifctfvax.Harhan.ORG/timekeeping/draft-utrspec.txt
http://ifctfvax.Harhan.ORG/timekeeping/draft-utrdef.txt
MS
On 25 Jan 2012, at 19:05, Rob Seaman sea...@noao.edu wrote:
Tony Finch wrote:
You'll have to explain why you think videoconferencing breaks the Olson
timezone database to me, because I don't get it.
I don't recall saying any such thing.
I said:
Displaying the time correctly for
Ian Batten wrote:
You've imposed the additional requirement that you can't have a primary
timezone, for political reasons.
Requirements are discovered, not imposed.
That's not an engineering requirement, or at least, it's a constraint more
easily solved by sacking people than dreaming up
Just to expand on this rather obscure exchange, from
http://en.wikipedia.org/wiki/Corpus_Clock :
'The clock is entirely accurate only once every five minutes. The rest
of the time, the pendulum may seem to catch or stop, and the lights may lag or,
then, race to get ahead. According to
On Jan 25, 2012, at 1:05, Michael Sokolov wrote:
I vigorously advocate only the general idea of rubberization. The
exact mode of rubberization is up to each individual implementor in
practice.
Why do we even try coordinating our clock-ticking if that's okay?
Alice and Bob may choose two
Rob Seaman found this
http://www.youtube.com/watch?v=C-2UqYW9SEs
--
Steve Allen s...@ucolick.orgWGS-84 (GPS)
UCO/Lick Observatory--ISB Natural Sciences II, Room 165Lat +36.99855
1156 High StreetVoice: +1 831 459 3046 Lng -122.06015
http://www.youtube.com/watch?v=C-2UqYW9SEs
The pertinent phraseology:
We return this draft revision of recommendation four-six-zero to Study
Group 7 for further work leading to the development of a continuous standard
taking into account all technical options that may be available and
On 25 Jan 2012, at 21:29, Rob Seaman sea...@noao.edu wrote:
Just to expand on this rather obscure exchange, from
http://en.wikipedia.org/wiki/Corpus_Clock :
'The clock is entirely accurate only once every five minutes. The rest of
the time, the pendulum may seem to catch or stop, and
On Thu, Jan 26, 2012 at 06:54, Ask Bjørn Hansen a...@develooper.com wrote:
On Jan 25, 2012, at 1:05, Michael Sokolov wrote:
I vigorously advocate only the general idea of rubberization. The
exact mode of rubberization is up to each individual implementor in
practice.
Why do we even
On 1/21/2012 4:44 AM, Poul-Henning Kamp wrote:
I think it is important that the unit of the representation is a
second rather than a day, simply because most of the stuff computers
do are in the second domain, not in the day domain. (See code example
above)
There's a lot of business
24 matches
Mail list logo
