[tor-commits] [torspec/main] Clarify tiebreaker rules when computing X_m

[nickm@xxxxxxxxxxxxxx]

commit 788fa527836e2fbacbb02671ba37de62e1c3940d
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date:   Tue Aug 17 09:33:12 2021 -0400

    Clarify tiebreaker rules when computing X_m
---
 path-spec.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/path-spec.txt b/path-spec.txt
index f02bee6..65d56c4 100644
--- a/path-spec.txt
+++ b/path-spec.txt
@@ -433,6 +433,8 @@ of their choices.
    Instead of using the mode of discrete build times directly, Tor clients
    compute the Xm parameter using the weighted average of the the midpoints
    of the 'cbtnummodes' (10) most frequently occurring 10ms histogram bins.
+   Ties are broken in favor of earlier bins.
+
    (The use of 10 modes was found to minimize error from the selected
    cbtquantile, with 10ms bins for quantiles 60-80, compared to many other
    heuristics).

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits