5 Other Features
> latency_tester_receiver --out-file mydata.txt
Starting capture thread succeeded.
Receiver setup. Listening to incoming packets.
File 'mydata.txt' exists, skipping sequence.
File 'mydata.txt' exists, skipping sequence.
Opened file 'mydata.txt' for writing.
Starting recording sequence...
seq=99 diff=410
seq=199 diff=410
seq=299 diff=410
seq=399 diff=410
seq=499 diff=410
seq=599 diff=410
...
seq=9899 diff=420
seq=9999 diff=410
Recording sequence finished.
Problems detected: no
File 'mydata.txt' closed.
File 'mydata.txt' exists, skipping sequence.
File 'mydata.txt' exists, skipping sequence.
The file mydata.txt was deleted shortly after the receiver was started. The file was then created again
and opened for writing. The host program picked up the next sequence of test packets and wrote them
to mydata.txt. The sequences after that are skipped because mydata.txt still exists. (It will log two skip
messages per sequence, because it encounters a first packet from both paths.) The idea behind this
behavior is that tests can be repeated without much interaction, simply by renaming the output file (maybe
giving it a more descriptive name), without the danger of accidentally overwriting files.
The output file simply contains the differences in receive timestamps in nanoseconds, with 10 ns resolu-
tion:
Example Output File (Partial)
22
