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:
On Jan 13, 2006, at 7:51 AM, Richard Langley wrote:
The International GNSS Service (IGS) includes a sub-network of
continuously
operating GLONASS monitor stations (about 50) including one at the
University
of New Brunswick (UNB1). At UNB1 we lost C1 (coarse code on L1
frequencies),
P1
Rob Seaman scripsit:
But there are also risks associated with *not* having
leap seconds, with allowing DUT1 to increase beyond 0.9s, for
instance. And events triggered by those risks would not draw
worldwide scrutiny - they could occur year-round and the media circus
would have moved on.
The International GNSS Service (IGS) includes a sub-network of continuously
operating GLONASS monitor stations (about 50) including one at the University
of New Brunswick (UNB1). At UNB1 we lost C1 (coarse code on L1 frequencies),
P1 (precision code on L1), and P2 (precision code on L2)
