Simplify the qstep.py output

The qstep.py script for latency measurement has somewhat confusing
output currently because it computes the latency with two different
approaches and displays both results.  This CL simply blocks one of the
methods and fixed the units on the remaining one to make the output
easier to read.  Now that people other than myself are running this
script, this should help prevent confusion.

Over several runs the method that remains proved to be much more stable
when using a robot (as our testing lab will) so that one was picked.

BUG=chromium:620090
TEST=manually tested

Change-Id: I88767998b2e713ce1f0656071fca154d32ad0281
Signed-off-by: Charlie Mooney <charliemooney@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/352611
Reviewed-by: Shyh-In Hwang <josephsih@chromium.org>
2 files changed
tree: 176b8e34cf9a327fb7974a444b91fe18eb654a9a
  1. .gitignore
  2. OWNERS
  3. optofidelity/
  4. quickstep/
  5. setup.py
  6. touchbotI/
  7. touchbotII/