You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The page on the Lichess accuracy metric talks about Win% and Accuracy% as a move by move metric, but doesn't discuss the gameAccuracy function defined in the source code below. In the game review section, the "information" button near the Accuracy % for the game links to the page without any discussion of the comprehensive game accuracy.
Just sharing this picture as an example. The blue "i" made me think the page I was going to would explain Game Accuracy.
I think this page would be improved if there is a more clear explanation of converting the move by move Accuracy% to game accuracy. For example, why was volatility weighted and harmonic means chosen? Why are they averaged? Why is the volatility clamped to 0.5 - 12? I'd find this information interesting, I think others would as well.
For example, why was volatility weighted and harmonic means chosen? Why are they averaged? Why is the volatility clamped to 0.5 - 12?
As far as I remember, these were just heuristics tweaked manually until it matched the most with what a human would feel about accuracy. It is not a scientific metric.
The page on the Lichess accuracy metric talks about Win% and Accuracy% as a move by move metric, but doesn't discuss the gameAccuracy function defined in the source code below. In the game review section, the "information" button near the Accuracy % for the game links to the page without any discussion of the comprehensive game accuracy.
Just sharing this picture as an example. The blue "i" made me think the page I was going to would explain Game Accuracy.
I think this page would be improved if there is a more clear explanation of converting the move by move Accuracy% to game accuracy. For example, why was volatility weighted and harmonic means chosen? Why are they averaged? Why is the volatility clamped to 0.5 - 12? I'd find this information interesting, I think others would as well.
lila/modules/analyse/src/main/AccuracyPercent.scala
Lines 77 to 111 in d816175
The text was updated successfully, but these errors were encountered: