Re: [tor-bugs] #6232 [Analysis]: Make entropy-over-time graph

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#6232: Make entropy-over-time graph
-------------------------+--------------------------------------------------
 Reporter:  arma         |          Owner:                   
     Type:  enhancement  |         Status:  needs_information
 Priority:  normal       |      Milestone:                   
Component:  Analysis     |        Version:                   
 Keywords:               |         Parent:                   
   Points:               |   Actualpoints:                   
-------------------------+--------------------------------------------------

Comment(by karsten):

 Replying to [comment:41 gsathya]:
 > Yeah, this looks good. Thanks for the fixes!

 Great!  Merging.

 > Is there a next step to this ticket? From my notes from the Tor dev
 meeting, we still need to -
 >
 >  1. Make this runnable every 3 hours

 Right.  The goal here would be to add graphs to the metrics website.  The
 script would first rsync consensuses and server descriptors from metrics
 and then process only the new consensuses to update the local .csv file.
 metrics-web would then use the .csv file to generate graphs based on user
 input.

 >  1. Make it read files in subdirs

 That's for consensus files, right?  We don't really need that feature
 anymore.

 But I'm not sure if my file system will like me anymore if I move a few
 years of server descriptors into a single directory without sub
 directories.  I'll try to find out.

 >  1. Find different metrics-
 >    1. Legislative diversity - based on countries
 >    1. Organizational diversity - based on Family
 >    1. Financial diversity - ??
 >    1. Physical location diversity - ??
 >    1. Network diversity - Subnets

 Right.  We already have legislative and network diversity, and
 organizational diversity is doable.  I don't see how we would come up with
 financial or physical diversity metrics.  I'd say it's safe to ignore
 those.

 But let's step back: all our metrics consist of three components:

  - (1a) based on consensus weights vs. (1b) based on advertised bandwidth
  - weighting bandwidth values by (2a) guard or (2b) exit position, or (2c)
 considering unweighted bandwidth
  - aggregating nodes by (3a) country, (3b) AS, (3c) family, or (3d)
 comparing single nodes

 That's 2 * 3 * 4 = 24 possible combinations.  We have implemented five of
 them.  For example, in arma's first comment on #6443 he's asking for
 advertised bandwidths in the exit position for single relays.  We don't
 have those numbers yet.  Want to add the remaining 19 combinations, each
 of them with entropy and max entropy?

 (Note that we don't have a single metric based on advertised bandwidth
 yet.)

 >  1. Give weights to every metric

 What does that mean?

 > Looks like #6443 is done(?), are there other things that arma might find
 interesting?

 #6443 is not done yet, because we should implement the metric in comment
 1.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6232#comment:42>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs