NTP3: CM5, TimeHat LEA-M8T, NTPSec
One Day - September 24, 2025 04:00 UTC
Report generated: Wed Sep 24 04:01:56 2025 UTC Start Time: Tue Sep 23 04:01:55 2025 UTC
End Time: Wed Sep 24 04:01:55 2025 UTC
Report Period: 1.0 days
Return to It's About Time
NTP3 runs on an RPi Compute Module 5 using a TimeHat prototype with a u-blox LEA-M8T timing receiver. It is used for experimental testing of new GNSS timing configurations.
If graphs don't match report time above, force refresh the browser. The images have been cached.
Local Clock Time/Frequency Offsets
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Time Offset | -19.371 | -3.026 | -1.848 | 0.016 | 1.815 | 3.365 | 8.031 | 3.663 | 6.391 | 1.171 | -0.004 | µs | -0.2717 | 12.67 | ||
| Local Clock Frequency Offset | -5.311 | -5.229 | -5.135 | -4.846 | -4.397 | -4.231 | -4.105 | 0.738 | 0.998 | 0.217 | -4.824 | ppm | 0.6005 | 3.215 | ||
The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.
These are fields 3 (time) and 4 (frequency) from the loopstats log file.
Local RMS Time Jitter
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local RMS Time Jitter | 0.379 | 0.558 | 0.671 | 1.156 | 2.200 | 2.845 | 9.345 | 1.529 | 2.287 | 0.539 | 1.263 | µs | 2.983 | 26.79 | ||
The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.
Lower is better. An ideal system would be a horizontal line at 0μs.
RMS jitter is field 5 in the loopstats log file.
Local RMS Frequency Jitter
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local RMS Frequency Jitter | 3.290 | 4.240 | 4.960 | 7.959 | 14.194 | 18.257 | 54.414 | 9.234 | 14.017 | 3.198 | 8.575 | ppb | 2.86 | 24.32 | ||
The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.
Lower is better. An ideal clock would be a horizontal line at 0ppm.
RMS Frequency Jitter is field 6 in the loopstats log file.
Local Clock Time Offset Histogram
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Offset | -19.371 | -3.026 | -1.848 | 0.016 | 1.815 | 3.365 | 8.031 | 3.663 | 6.391 | 1.171 | -0.004 | µs | -0.2717 | 12.67 | ||
The clock offsets of the local clock as a histogram.
The Local Clock Offset is field 3 from the loopstats log file.
Local Temperatures
Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.
The Local Temperatures are from field 3 from the tempstats log file.
Local Frequency/Temp
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Frequency Offset | -5.311 | -5.229 | -5.135 | -4.846 | -4.397 | -4.231 | -4.105 | 0.738 | 0.998 | 0.217 | -4.824 | ppm | 0.6005 | 3.215 | ||
| Temp CPU | 84.200 | 84.800 | 85.300 | 86.500 | 87.500 | 87.500 | 88.100 | 2.200 | 2.700 | 0.686 | 86.325 | °C | ||||
The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.
These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.
Local GPS
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| nSats | 23.000 | 25.000 | 26.000 | 28.000 | 30.000 | 31.000 | 32.000 | 4.000 | 6.000 | 1.404 | 27.968 | nSat | -0.1733 | 3.066 | ||
| TDOP | 0.440 | 0.460 | 0.480 | 0.550 | 0.660 | 0.690 | 0.740 | 0.180 | 0.230 | 0.053 | 0.553 | 0.6005 | 2.926 | |||
Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.
TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.
TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.
Server Offsets
The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.
Clock Offset is field 5 in the peerstats log file.
Server Offset 10.0.0.240
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 10.0.0.240 | -77.021 | -25.859 | 11.103 | 31.158 | 43.670 | 48.451 | 56.222 | 32.567 | 74.310 | 12.249 | 29.371 | µs | -2.425 | 13.52 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Server Offset 10.0.0.244
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 10.0.0.244 | -51.582 | -38.877 | -28.718 | -8.273 | 1.504 | 4.291 | 24.007 | 30.222 | 43.168 | 9.958 | -10.833 | µs | -0.8142 | 3.367 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Server Offset 10.0.0.246
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 10.0.0.246 | -104.571 | -35.034 | -30.339 | -6.516 | 14.763 | 21.622 | 57.809 | 45.102 | 56.656 | 15.178 | -7.783 | µs | -0.09033 | 2.684 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Server Offset 10.0.50.55
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset 10.0.50.55 | -28.140 | -19.486 | -17.930 | -14.909 | 13.239 | 22.055 | 50.416 | 31.169 | 41.541 | 9.183 | -11.840 | µs | 2.538 | 8.851 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Server Offset SHM(0)
.png?ts=1758686534)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(0) | -322.289 | -298.740 | -289.795 | -268.230 | -254.692 | -248.562 | -232.440 | 35.103 | 50.177 | 10.966 | -269.976 | ms | -0.5521 | 3.21 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Server Offset SHM(1)
.png?ts=1758686534)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Offset SHM(1) | -19.372 | -3.027 | -1.849 | 0.017 | 1.816 | 3.366 | 8.032 | 3.665 | 6.393 | 1.172 | -0.004 | µs | -0.2712 | 12.64 | ||
The offset of a server in seconds. This is useful to see how the measured offset is behaving.
The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.
Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.
Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.
Server Jitters
The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter 10.0.0.240
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 10.0.0.240 | 1.095 | 5.107 | 8.884 | 17.868 | 30.628 | 43.947 | 82.280 | 21.744 | 38.840 | 7.603 | 18.783 | µs | 1.866 | 11.88 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter 10.0.0.244
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 10.0.0.244 | 2.302 | 6.943 | 9.634 | 17.956 | 30.315 | 35.275 | 257.304 | 20.681 | 28.332 | 8.239 | 18.793 | µs | 11.37 | 319 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter 10.0.0.246
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 10.0.0.246 | 1.671 | 3.664 | 5.462 | 17.518 | 39.018 | 109.559 | 567.115 | 33.556 | 105.895 | 42.011 | 22.816 | µs | 10.48 | 121.9 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter 10.0.50.55
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter 10.0.50.55 | 0.001 | 0.002 | 0.003 | 0.010 | 0.365 | 1.221 | 2.041 | 0.362 | 1.219 | 0.198 | 0.064 | ms | 5.244 | 34.45 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter SHM(0)
.png?ts=1758686534)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(0) | 1.194 | 2.502 | 3.474 | 7.541 | 16.587 | 23.021 | 56.259 | 13.113 | 20.518 | 4.280 | 8.441 | ms | 1.735 | 8.93 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Server Jitter SHM(1)
.png?ts=1758686534)
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Server Jitter SHM(1) | 0.071 | 0.313 | 0.450 | 1.197 | 3.093 | 4.494 | 19.673 | 2.643 | 4.181 | 0.908 | 1.405 | µs | 2.764 | 25.2 | ||
The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.
Closer to 0s is better. An ideal system would be a horizontal line at 0s.
RMS Jitter is field 8 in the peerstats log file.
Summary
| Percentiles...... | Ranges...... | Skew- | Kurt- | |||||||||||||
| Name | Min | 1% | 5% | 50% | 95% | 99% | Max | 90% | 98% | StdDev | Mean | Units | ness | osis | ||
| Local Clock Frequency Offset | -5.311 | -5.229 | -5.135 | -4.846 | -4.397 | -4.231 | -4.105 | 0.738 | 0.998 | 0.217 | -4.824 | ppm | 0.6005 | 3.215 | ||
| Local Clock Time Offset | -19.371 | -3.026 | -1.848 | 0.016 | 1.815 | 3.365 | 8.031 | 3.663 | 6.391 | 1.171 | -0.004 | µs | -0.2717 | 12.67 | ||
| Local RMS Frequency Jitter | 3.290 | 4.240 | 4.960 | 7.959 | 14.194 | 18.257 | 54.414 | 9.234 | 14.017 | 3.198 | 8.575 | ppb | 2.86 | 24.32 | ||
| Local RMS Time Jitter | 0.379 | 0.558 | 0.671 | 1.156 | 2.200 | 2.845 | 9.345 | 1.529 | 2.287 | 0.539 | 1.263 | µs | 2.983 | 26.79 | ||
| Server Jitter 10.0.0.240 | 1.095 | 5.107 | 8.884 | 17.868 | 30.628 | 43.947 | 82.280 | 21.744 | 38.840 | 7.603 | 18.783 | µs | 1.866 | 11.88 | ||
| Server Jitter 10.0.0.244 | 2.302 | 6.943 | 9.634 | 17.956 | 30.315 | 35.275 | 257.304 | 20.681 | 28.332 | 8.239 | 18.793 | µs | 11.37 | 319 | ||
| Server Jitter 10.0.0.246 | 1.671 | 3.664 | 5.462 | 17.518 | 39.018 | 109.559 | 567.115 | 33.556 | 105.895 | 42.011 | 22.816 | µs | 10.48 | 121.9 | ||
| Server Jitter 10.0.50.55 | 0.001 | 0.002 | 0.003 | 0.010 | 0.365 | 1.221 | 2.041 | 0.362 | 1.219 | 0.198 | 0.064 | ms | 5.244 | 34.45 | ||
| Server Jitter SHM(0) | 1.194 | 2.502 | 3.474 | 7.541 | 16.587 | 23.021 | 56.259 | 13.113 | 20.518 | 4.280 | 8.441 | ms | 1.735 | 8.93 | ||
| Server Jitter SHM(1) | 0.071 | 0.313 | 0.450 | 1.197 | 3.093 | 4.494 | 19.673 | 2.643 | 4.181 | 0.908 | 1.405 | µs | 2.764 | 25.2 | ||
| Server Offset 10.0.0.240 | -77.021 | -25.859 | 11.103 | 31.158 | 43.670 | 48.451 | 56.222 | 32.567 | 74.310 | 12.249 | 29.371 | µs | -2.425 | 13.52 | ||
| Server Offset 10.0.0.244 | -51.582 | -38.877 | -28.718 | -8.273 | 1.504 | 4.291 | 24.007 | 30.222 | 43.168 | 9.958 | -10.833 | µs | -0.8142 | 3.367 | ||
| Server Offset 10.0.0.246 | -104.571 | -35.034 | -30.339 | -6.516 | 14.763 | 21.622 | 57.809 | 45.102 | 56.656 | 15.178 | -7.783 | µs | -0.09033 | 2.684 | ||
| Server Offset 10.0.50.55 | -28.140 | -19.486 | -17.930 | -14.909 | 13.239 | 22.055 | 50.416 | 31.169 | 41.541 | 9.183 | -11.840 | µs | 2.538 | 8.851 | ||
| Server Offset SHM(0) | -322.289 | -298.740 | -289.795 | -268.230 | -254.692 | -248.562 | -232.440 | 35.103 | 50.177 | 10.966 | -269.976 | ms | -0.5521 | 3.21 | ||
| Server Offset SHM(1) | -19.372 | -3.027 | -1.849 | 0.017 | 1.816 | 3.366 | 8.032 | 3.665 | 6.393 | 1.172 | -0.004 | µs | -0.2712 | 12.64 | ||
| TDOP | 0.440 | 0.460 | 0.480 | 0.550 | 0.660 | 0.690 | 0.740 | 0.180 | 0.230 | 0.053 | 0.553 | 0.6005 | 2.926 | |||
| Temp CPU | 84.200 | 84.800 | 85.300 | 86.500 | 87.500 | 87.500 | 88.100 | 2.200 | 2.700 | 0.686 | 86.325 | °C | ||||
| nSats | 23.000 | 25.000 | 26.000 | 28.000 | 30.000 | 31.000 | 32.000 | 4.000 | 6.000 | 1.404 | 27.968 | nSat | -0.1733 | 3.066 | ||
Our production NTP servers share the same mast-mounted Tallysman Accutenna® TW3972 Triple Band GNSS Antenna + L-band Correction Services antenna using a Tallysman TW164 1-to-4 Port Smart Power GNSS Signal Splitter. No external NTP servers are contacted and all servers, with the exception of NTP6, the LeoNTP 1200, poll each other. Internal NTP clients poll NTP4 or NTP6.
The LeoNTP 1200 is a black-box appliance that doesn't support timing reporting. Its status can be checked by viwing the Server Jitter & Offset from any of the other servers. It can be found at NTP7 or 10.0.50.55. The LeoNTP link above will take you to the Server Jitter between the LeoNTP and the currently selected server.
NTPQ Stats
'GNSS Performance
This server has a u-blox LEA-M8T Timing GNSS Receiver that is configured in Time Mode, using a fixed location, it rejects all fixes calculated to be more than one meter off.
'Glossary:
- frequency offset:
- The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
- jitter, dispersion:
- The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
- ms, millisecond:
- One thousandth of a second = 0.001 seconds, 1e-3 seconds
- mu, mean:
- The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
- ns, nanosecond:
- One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
- percentile:
- The value below which a given percentage of values fall.
- ppb, parts per billion:
- Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
- ppm, parts per million:
- Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
- ‰, parts per thousand:
- Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
- refclock:
- Reference clock, a local GPS module or other local source of time.
- remote clock:
- Any clock reached over the network, LAN or WAN. Also called a peer or server.
- time offset:
- The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
- σ, sigma:
- Sigma denotes the standard deviation (SD) and is centered on the
arithmetic mean of the data set. The SD is simply the square root of
the variance of the data set. Two sigma is simply twice the standard
deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points. - Skewness, Skew:
- The skewness of a random variable X is the third standardized moment
and is a dimension-less ratio. ntpviz uses the FIsher-Pearson moment
of skewness. There are other different ways to calculate Skewness
Wikipedia describes Skewness best: "The qualitative interpretation of
the skew is complicated and unintuitive."
A normal distribution has a skewness of zero. - Kurtosis, Kurt:
- The kurtosis of a random variable X is the fourth standardized
moment and is a dimension-less ratio. ntpviz uses standard
Kurtosis. There are other different ways to calculate Kurtosis.
A normal distribution has a Kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed". - upstream clock:
- Any server or reference clock used as a source of time.
- µs, us, microsecond:
- One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.
