Re: [chrony-dev] [GIT] chrony/chrony.git branch, master, updated. 2.4-9-g6cd5583

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-dev Archives ]


Another question is what one takes as the "no-assymmetry" delay ( ie the
minimum delay). The lowest delay? Ovr what time period? Can one imagine weird
situations in which the minimum is a bad estimate? Over how long a period does
one take the minimum? It would be a mistake to take 0 for that minimum.

William G. Unruh   |  Canadian Institute for|     Tel: +1(604)822-3273
Physics&Astronomy  |     Advanced Research  |     Fax: +1(604)822-5324
UBC, Vancouver,BC  |   Program in Cosmology |     unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1     |      and Gravity       |  www.theory.physics.ubc.ca/

On Thu, 30 Jun 2016, Miroslav Lichvar wrote:

On Wed, Jun 29, 2016 at 08:04:44AM -0700, Bill Unruh wrote:
On Wed, 29 Jun 2016, Miroslav Lichvar wrote:
I'm very interested in implementing some estimation of the asymmetry
to chrony. I'd like to allow any slope between -0.5 and 0.5, not just
one of the three values (-0.5, 0.0, +0.5). One idea I had was to
search for a value which minimizes the variance in the linear
regression when all points have a constant weight. With each new
sample, the asymmetry would be estimated first and then the offsets
would be adjusted for the weighted regression which is currently used
to estimate the offset. Basically I'm looking for a constant A between
-0.5 and 0.5 which minimizes the variance in linear regression of
points (x, y + A * d), where x is time, y is the symmetric offset and
d is the increase in delay over the minimum. Can A be calculated
directly from (x, y, d) samples? I suspect it would have to be an
iterative approach and this might be expensive.

No, that would just be a two, instead of one, variable linear regression,
One would just minimize (y-C(x-x0)+Ad)^2 over C, x0 and A. Still linear
equations.

Oh, that's great. Thanks. I'll try that. I suspect we will need to use
a long-term average of the slope to prevent adding more noise when the
number of samples is small. If this works well, there will probably be
other interesting problems with "asymmetric" offset that will need to
be addresses. For instance the error interval used in the source
selection would shift, which could be a problem for detection of
falsetickers. The code will likely have to work with both offsets
depending on the context. There is also a question how they should be
reported in chronyc and the logs, and how much confusion this will
create.

--
Miroslav Lichvar

--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/