From 82369fc387d833c27e0228208a22ea16cc9fbca3 Mon Sep 17 00:00:00 2001
From: Antonio Ospite <ao2@ao2.it>
Date: Thu, 24 Dec 2015 10:42:27 +0100
Subject: [PATCH] measure_call_setup_time.py: don't measure "uncertainty"
anymore
It's not immediately useful to know the uncertainty now that
CallDistanceTransceiver takes minimum and maximum parameters explicitly.
While at it also adjust a print message to be more descriptive.
---
src/measure_call_setup_time.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/measure_call_setup_time.py b/src/measure_call_setup_time.py
index f69bb15..57bf49a 100755
--- a/src/measure_call_setup_time.py
+++ b/src/measure_call_setup_time.py
@@ -47,7 +47,7 @@ def measure_call_setup_time(ingoing_port, outgoing_port, destination_number):
for i in range(5):
print()
- print("Attempt: %s" % (i + 1))
+ print("Call: %s" % (i + 1))
outgoing_modem.send_command("ATDT" + destination_number + ";")
dial_time = time.time()
@@ -66,12 +66,10 @@ def measure_call_setup_time(ingoing_port, outgoing_port, destination_number):
avg_call_setup_time = cumulative_average(avg_call_setup_time,
i + 1,
call_setup_time)
- uncertainty = (max_call_setup_time - min_call_setup_time) / 2.
print("Call setup time: %f" % call_setup_time)
print("Min call setup time: %f" % min_call_setup_time)
print("Max call setup time: %f" % max_call_setup_time)
print("Average call setup time: %f" % avg_call_setup_time)
- print("Call setup time uncertainty: %f" % uncertainty)
print()
call_time = hangup_time - dial_time
--
2.1.4