Approximate ELO
This is the thread's initial revision.
I have been mulling around ways to approximate ELO for awhile. Since originally it was used for ranking (2000 club, etc), however the rankings have drifted considerably and with the advent of APS there is no real need for it. However the number is still nice, even if the methods for calculating it have problems.
So I figured we could get our nice number without a lot of number crunching with way of a simple equation. At least that was the original theory. However APS doesn't map very well to ELO, which is not at all linear, and the data set required for calculating such an equation is incomplete.
However here are my token efforts at doing just that. The dataset I used was the 2009 Glinko-2 and APS, as it was likely the most similar to the old ELO rankings. I would ahve used those, but they lacked an APS column, and the common bots between them don't exactly line up very well (plus that decimates my data set even more).
public static final double calculateElo(double x) {
double a = 169.1;
double b = 0.02369;
double c = 334.2;
return a*Math.cosh(b*x)+c*Math.log(x);
}
public static final double calculateEloFast(double x) {
double a = 0.7082e-03;
double b = -0.3340e-05;
double c = 0.3992e-02;
return 1.0/(a+b*x+c/x);
}
The first is a bit more accurate. 0 is negative infinity, and 100 is around 2450 (it should be positive infinity, but I did what I could). However with a logarithm and a cosh, it is a bit heavy to be called 700+ times every a page loads (I think at least). The second is a slightly less accurate system, 0 is 0 and 100 is about 2415. With mostly simple math it is much easier to execute.
So thoughts, concerns, scorn?