Find some way to get interesting reports out of routeCompare()
Current state: We have two versions of routeCompare at the moment, routeCompare() and newRouteCompare(). The former saves all possible route variations and compares them to determine how normal a hop is, but it also does a lot of other weird things. It's basically just a big mess. newRouteCompare() establishes the normal more elegantly, using something like https://en.wikipedia.org/wiki/D%27Hondt_method creating an "average hop" based on the distribution of IPs and stars. It also tries to distinguish between reports which are warnings and reports which are complete, similar to the errorCheck() routine. We're still unable to get interesting results out from either of these.
-
Keep tweaking and experimenting with the routine to get a reasonable amount of reports which are interesting.