On Tue, 19 Nov 2019 at 21:20, Ian Gregory <[email protected]> wrote: > I can > confirm that change resolved the precision issue described in the > linked thread, but it also seems to have resulted in much improved > clock stability (4 steps in 24hr, 1.0s, 1.0s, 0.5s, 0.5s).
Correction - there were actually 3 instances of 1.0s time steps (clock lags real time by 3.0s) Ian
