Re: Problems with GLONASS Raw Receiver Data at Start of New Year
In message <[EMAIL PROTECTED]>, Rob Seaman writes: >On Jan 14, 2006, at 8:59 AM, Richard Langley wrote: > >> The problem existed for only 2-1/2 minutes, not hours. > >Thanks for the clarification. > >> Might be coincidental with the leap second but I've not noticed >> this problem at other times. > >Would be a significant coincidence. Any simple explanation for the >90 second lag in the issue being triggered? The latency associated >with emergent behavior is of interest in itself. As far as I recall GLONASS was messed up for hours on the previous leapsecond, so there is a good chance it is because of the leap seconds that it fell out this time. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Re: Problems with GLONASS Raw Receiver Data at Start of New Year
On Tue 2006-01-17T18:26:49 +0100, Poul-Henning Kamp hath writ: > As far as I recall GLONASS was messed up for hours on the previous > leapsecond, so there is a good chance it is because of the leap > seconds that it fell out this time. Not according to the Russians: http://www.glonass-center.ru/1999_1e.html There was a NAGU at the time of the mid 1997 leap second http://www.glonass-center.ru/1997_7e.html but the text clearly indicates it was not because of the leap second. Of course the Russian GLONASS operators could be in denial about leap second issues. They wouldn't be the only ones with that condition. -- Steve Allen <[EMAIL PROTECTED]>WGS-84 (GPS) UCO/Lick ObservatoryNatural Sciences II, Room 165Lat +36.99858 University of CaliforniaVoice: +1 831 459 3046 Lng -122.06014 Santa Cruz, CA 95064http://www.ucolick.org/~sla/ Hgt +250 m
Re: Monsters from the id
On Mon 2006/01/16 00:40:28 CDT, John Cowan wrote in a message to: LEAPSECS@ROM.USNO.NAVY.MIL >I realize the ALHP has severe problems with this, but I don't approve >of the ALHP anyhow (save perhaps tactically, as explained). Agreement! But does anyone think that the leap hour proposal is anything other than a political device? If so, please describe in detail how it could/would work. Mark Calabretta ATNF
Re: Monsters from the id
On Sat, Jan 14, 2006 at 02:09:20AM -0700, Rob Seaman wrote: >On Jan 13, 2006, at 12:46 AM, John Cowan wrote: > In the end, it will be impossible to maintain the notion that a solar > day is 24h of 60m of 60s each: we wind up, IIRC, with the solar day > and lunar month both at about 47 current solar days. > >There's a lot of difference between what happens over a billion years >and a million years. Length of day increases only about 20s per million >years. Should we be here to care in a million years, only a 1/4 of 1/10 >of >one percent tweak to the length of the "civil second" would suffice to >allow >our Babylonian clock paradigm to continue in use. Of course, since there is a future time of equilibrium (though a long time off...), the "quadratic" nature of the accumulation of leap seconds will also stop at some point, and eventually we won't need them any more. I hope the 47 day calculation takes the solar tidal influences into effect, and that the moon has to overcome that. It makes me wonder when the maximum rate of change in length of day will come? Not that we need to plan for events that far in the future - just some fun astronomy Neal McBurnett http://bcn.boulder.co.us/~neal/ Signed and/or sealed mail encouraged. GPG/PGP Keyid: 2C9EBA60