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.
Signed-off-by: Charlie Mooney <firstname.lastname@example.org>
Reviewed-by: Shyh-In Hwang <email@example.com>
diff --git a/quickstep/latency_measurement.py b/quickstep/latency_measurement.py
index c8af55d..e216a6d 100644
@@ -282,6 +282,8 @@
# Display the results
print 'Average', 'Maximum', 'Minimum'
print np.average(latencies), max(latencies), min(latencies)
+ print 'Latency result: %f ms' % (np.average(latencies) * 1000.0)
if __name__ == '__main__':
diff --git a/quickstep/qstep.py b/quickstep/qstep.py
index 9f43fc5..a9ee6fc 100644
@@ -221,5 +221,4 @@
print "\nProcessing data, may take a minute or two..."
- minimization.minimize(evtest_file_name, laser_file_name)