[or-cvs] r20543: {torflow} I think we want ALPHA at 0 when BETA is at 0. (torflow/branches/stable/NetworkScanners/BwAuthority)

[mikeperry@xxxxxxxx]

Author: mikeperry
Date: 2009-09-13 01:30:10 -0400 (Sun, 13 Sep 2009)
New Revision: 20543

Modified:
   torflow/branches/stable/NetworkScanners/BwAuthority/aggregate.py
Log:

I think we want ALPHA at 0 when BETA is at 0.



Modified: torflow/branches/stable/NetworkScanners/BwAuthority/aggregate.py
===================================================================
--- torflow/branches/stable/NetworkScanners/BwAuthority/aggregate.py	2009-09-13 05:12:49 UTC (rev 20542)
+++ torflow/branches/stable/NetworkScanners/BwAuthority/aggregate.py	2009-09-13 05:30:10 UTC (rev 20543)
@@ -16,7 +16,11 @@
 nodes = {}
 prev_consensus = {}
 
-ALPHA = 0.3333 # Prev consensus values count for 1/3 of the avg 
+# ALPHA is the parameter that measures how much previous consensus 
+# values count for. With a high BETA value, this should be higher
+# to avoid quick changes. But with 0 BETA, it is probably best to
+# also leave it 0.
+ALPHA = 0 
 
 # BETA is the parameter that governs the proportion that we use previous 
 # consensus values in creating new bandwitdhs versus descriptor values.
@@ -26,7 +30,6 @@
 # necessary since the descriptors values should rise as more traffic
 # is directed at nodes. Also, there are cases where our updates may
 # not cause node traffic to quickly relocate, such as Guard-only nodes.
-
 BETA = 0
 
 NODE_CAP = 0.05