This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] [NTP measurements] Minimum offset if negative
- Previous message (by thread): [atlas] [NTP measurements] Minimum offset if negative
- Next message (by thread): [atlas] [NTP measurements] Minimum offset if negative
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Povl Ole Haarlev Olsen
ripe-atlas at stderr.dk
Fri Jun 28 12:22:45 CEST 2024
On Fri, 28 Jun 2024, Stephane Bortzmeyer wrote: > Measurement #74488034 says on > <https://atlas.ripe.net/measurements/74488034>: "Min Offset: > -1 173,799". Since offsets can be positive or negative, I suggest it > is not a good idea to take the minimum without first removing the > sign. Here, the real minimum offset was -0.000345 (the closest from > the server) and the maximum -1.173799 (the farthest from the server). min( abs( value_1 ) , abs( value_2 ) ) would be the minimum difference, not the minimum offset. Both minimum difference and minimum offset can be useful, but they're not the same thing. -- Povl Ole
- Previous message (by thread): [atlas] [NTP measurements] Minimum offset if negative
- Next message (by thread): [atlas] [NTP measurements] Minimum offset if negative
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]