Update plot defaults for current conditions.

Stock maximum peer count has increased, so peer counts can be easily
twice as high. The default probe rate is higher than it was initially,
so less of a time span is required to get enough information for a
reasonable-looking plot.

README.md

@@ -103,6 +103,8 @@ Can perform analysis of gathered probe data:
 * Uptime distribution (using that included with `identifier`)
 * Bulk reject percentage distribution
 
+The time spans used are manually specified (with defaults) but might be better as a function of probe rate and type distribution for more consistent results at the cost of more unusual time spans.
+
 For documentation on using it run `analyze` with `--help`.
 
 ## Database Schema

analyze.py

@@ -21,10 +21,16 @@
 # Options.
 parser.add_argument('-d', dest="databaseFile", default="database.sql",
                     help="Path to database file. Default \"database.sql\"")
-parser.add_argument('-T', '--recentHours', dest="recentHours", default=168, type=int,
-                    help="Number of hours for which a probe is considered recent. Used for peer count histogram and link lengths. Default 168 - one week.")
-parser.add_argument('--histogram-max', dest="histogramMax", default=50, type=int,
-                    help="Maximum number of peers to consider for histogram generation; anything more than that is included in the maximum. Default 50.")
+parser.add_argument('-T', '--recentHours', dest="recentHours", default=24,
+                    type=int,
+                    help="Number of hours for which a probe is considered "
+                         "recent. Used for peer count histogram and link "
+                         "lengths. Default 24.")
+parser.add_argument('--histogram-max', dest="histogramMax", default=110,
+                    type=int,
+                    help="Maximum number of peers to consider for histogram "
+                         "generation; anything more than that is included in "
+                         "the maximum. Default 110.")
 parser.add_argument('-q', dest='quiet', default=False, action='store_true',
                     help='Do not print status updates.')
 parser.add_argument('--round-robin', dest='rrd', default='size.rrd',

index.md

@@ -84,7 +84,7 @@ Errors are:
 * Unrecognized Type: a remote node did not recognize the requested probe type.
 * Cannot Forward: a remote node understood the request but failed to forward it to another node.
 
-Link length, peer count, bulk reject percentages, and uptime are from the past 7 days of results. All peer counts above 50 count towards 50. Reported uptime can exceed 100% due to the added random noise. Bulk reject percentages are restricted to between 0% and 100%.
+Link length, peer count, bulk reject percentages, and uptime are from the past day of results. All peer counts above 110 count towards 110. Reported uptime can exceed 100% due to the added random noise. Bulk reject percentages are restricted to between 0% and 100%.
 
 The bulk queue (therefore not realtime queue) reject percentages are an indicator of network health. My understanding is that a node will reject a request if it does not have sufficient bandwidth available to take on the commitment. This would mean that high reject percentages might indicate low bandwidth limits and problems with routing. I am currently collecting information on bandwidth limits, but I am not yet plotting that information.