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] Actual measurement interval much larger than planned
- Previous message (by thread): [atlas] Actual measurement interval much larger than planned
- Next message (by thread): [atlas] Actual measurement interval much larger than planned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Sep 2 09:53:18 CEST 2016
On 2016-09-01 19:14, Wenqin SHAO wrote: > 1470055259 > 1470055499 > 1470055978 > 1470056216 > > Four measurements are retrieved within the given time range. I noticed that > time interval between the 2nd and the 3rd measurement is 479s much larger > than the planned value 240s. > How come? 479 is almost exactly twice the frequency (240), so it's basically one result skipped. Most likely the probe just didn't execute that measurement (was powered down? rebooting? was refreshing its set of tasks just at the worst time?) Regards, Robert
- Previous message (by thread): [atlas] Actual measurement interval much larger than planned
- Next message (by thread): [atlas] Actual measurement interval much larger than planned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]