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 <sla_at_ucolick.org> WGS-84 (GPS)
UCO/Lick Observatory Natural Sciences II, Room 165 Lat +36.99858
University of California Voice: +1 831 459 3046 Lng -122.06014
Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
Received on Tue Jan 17 2006 - 09:58:32 PST