[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7241 [Analysis]: Visualize how quickly the Tor network changes



#7241: Visualize how quickly the Tor network changes
----------------------+-----------------------------------------------------
 Reporter:  asn       |          Owner:                
     Type:  task      |         Status:  needs_revision
 Priority:  normal    |      Milestone:                
Component:  Analysis  |        Version:                
 Keywords:            |         Parent:  #2681         
   Points:            |   Actualpoints:                
----------------------+-----------------------------------------------------

Comment(by karsten):

 Neat analysis!

 2012_frac_relays.png looks correct.  I like how the fraction goes down at
 12 and 36 hours and back up at 24 and 48 hours.  But it makes sense: there
 are quite a few relays on a 24-hour cycle, and even if they're offline 12
 hours later, they can be back online 24 hours later.

 2012_frac_cw.png looks wrong though.  The definition should be: "frac_cw
 is the sum of consensus weights of routers in Y that are also in X based
 on fingerprint, divided by the total sum of consensus weights of all
 routers in Y."  The result should be a graph similar to
 2012_frac_relays.png, so distributions from `[0..1]`, with fractions
 dropping more slowly; based on the assumption that most of the fast relays
 are 24/7.

 Do you mind if we add your code, possibly after making the changes that
 gsathya suggests, to metrics-tasks.git?  Do you want to clone that
 repository, commit your code, and let me know from where to pull?  It
 would be good to have all analysis code in a single repository for others
 who want to run similar analyses.

 To answer your question about missing hourly consensuses: it happens from
 time to time that the 9 directory authorities fail to generate a
 consensus, and it's also possible that the descriptor-fetching service
 fails temporarily.  Your approach, to ignore cases when a consensus is
 missing, is perfectly reasonable.

 Also, the decision not to look at routers that are missing between `]now-
 hours, now[` is perfectly fine.  That would be a different research
 question, so please leave this as is.

 Thanks!

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7241#comment:4>
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