Yo All!
New data for poll=8 (256 Sec). Like before, all data is 90% bounds,
run over 24 hours or more. Looks like 8 is clearly too high for
either of these PPS hosts. So this is the end of this test series.
Xeon:
Local Clock Local Clock Local ClockPPS PPS
Poll Freq Of
> Since the data is computed in ntpviz, not in gnuplot, would it make sense to
> put the computed data just in the html, instead of in the plot?
It would be neat if you could put the data someplace (file?) where a script
can easily get at it. The idea is to automate collecting the data that go
Quoting "Gary E. Miller" :
Yo All!
Hal has brought up a good point about ntpviz. Some stats are calculated
in ntpviz, like the 90% range of offset, then plotted over the data in
the gnuplot output.
Sometimes the curves overlay the data block and it is hard to read.
Since the data is computed
Yo All!
Hal has brought up a good point about ntpviz. Some stats are calculated
in ntpviz, like the 90% range of offset, then plotted over the data in
the gnuplot output.
Sometimes the curves overlay the data block and it is hard to read.
Since the data is computed in ntpviz, not in gnuplot, wo
Yo Hal!
On Wed, 21 Sep 2016 23:05:02 -0700
Hal Murray wrote:
> >> Notes on the system config, and links to the ntp.conf are on those
> >> pages.
> > GPS; GlobalSat MR-350P
>
> Are all the PPS pulses getting through? The MR-350P has a very
> narrow pulse.
Yes. every one.
> If you don't ha
