Adds a chart to the home page, showing how much coverage there is in the best case.
Here's an example from a real census run on my machine a few days ago:
The basic approach is to split the keyspace into 256 1-byte buckets. Then show how many nodes fully cover that keyspace, and how much partial coverage there is of those buckets.
This mostly reuses the existing data from the node radius chart, plus a bit more precision in the radius calculation sent by the server.
Also, I added a tooltip to help you see which bucket is showing which data, and the precise value of coverage. I am a little unsatisfied with the method of identifying the bucket prefix (back-calculating from the x-value), but I couldn't find a better solution after digging a bit. I'm open to suggestions.
Note: there are a few little fix-up commits working on the logs and readme. It may be easier to review by commit.
TODO:
[x] remove TODO comments, they should be fully captured in #267 now
[x] squash comment removal and tooltip into the "add chart" commit
Fix #261
Adds a chart to the home page, showing how much coverage there is in the best case.
Here's an example from a real census run on my machine a few days ago:
The basic approach is to split the keyspace into 256 1-byte buckets. Then show how many nodes fully cover that keyspace, and how much partial coverage there is of those buckets.
This mostly reuses the existing data from the node radius chart, plus a bit more precision in the radius calculation sent by the server.
Also, I added a tooltip to help you see which bucket is showing which data, and the precise value of coverage. I am a little unsatisfied with the method of identifying the bucket prefix (back-calculating from the x-value), but I couldn't find a better solution after digging a bit. I'm open to suggestions.
Note: there are a few little fix-up commits working on the logs and readme. It may be easier to review by commit.
TODO: