[time-nuts] June 30 2015 leap second

Henry Hallam henry at pericynthion.org
Fri Jan 9 19:57:55 EST 2015

Such slewing solutions are OK for Google.  They wouldn't work well for
one of the systems I work with, which uses system time to calculate
the position of a LEO satellite for purpose of pointing a 7.6 meter
X-band dish.  Half a second of error corresponds to a pointing error
of 0.5 degrees, well outside the main lobe of the antenna beam.

Anecdotally yours,

On Fri, Jan 9, 2015 at 2:30 PM, Hal Murray <hmurray at megapathdsl.net> wrote:
> time at patoka.org said:
>> 1s/24h = 1/86400 which is approximately 12ppm. That means that Aging  Offset
>> could slow down my clock for 1 second if I'll apply the maximum  value one
>> day ahead (roughly). I need to do some experiments first. ;-)  Its looks too
>> unreliable for me.
> If you do it that way, your clock will be off by a whole second just before
> midnight when the leap-second brings it back into sync.  If you tweak your
> clock from noon-noon, it will only be off by 1/2 second at midnight when the
> sign-bit of the error flips.
> --
> These are my opinions.  I hate spam.
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.

More information about the time-nuts mailing list