Glicko rating system
The Glicko rating system and Glicko-2 rating system are methods of assessing a player's strength in zero-sum two-player games. The Glicko rating system was invented by Mark Glickman in 1995 as an improvement on the Elo rating system and initially intended for the primary use as a chess rating system. Glickman's principal contribution to measurement is "ratings reliability", called RD, for ratings deviation.
Overview
[edit]Mark Glickman created the Glicko rating system in 1995 as an improvement on the Elo rating system.[1]
Both the Glicko and Glicko-2 rating systems are under public domain and have been implemented on game servers online like Counter-Strike: Global Offensive, Team Fortress 2,[2] Dota 2,[3] Guild Wars 2,[4] Splatoon 2,[5] Lichess and chess.com.[6]
The Reliability Deviation (RD) measures the accuracy of a player's rating, where the RD is equal to one standard deviation. For example, a player with a rating of 1500 and an RD of 50 has a real strength between 1400 and 1600 (two standard deviations from 1500) with 95% confidence. Twice (exact: 1.96) the RD is added and subtracted from their rating to calculate this range. After a game, the amount the rating changes depends on the RD: the change is smaller when the player's RD is low (since their rating is already considered accurate), and also when their opponent's RD is high (since the opponent's true rating is not well known, so little information is being gained). The RD itself decreases after playing a game, but it will increase slowly over time of inactivity.
The Glicko-2 rating system improves upon the Glicko rating system and further introduces the rating volatility σ.[7] A very slightly modified version of the Glicko-2 rating system is implemented by the Australian Chess Federation.[8]
The algorithm of Glicko
[edit]Step 1: Determine ratings deviation
[edit]The new Ratings Deviation () is found using the old Ratings Deviation ():
where is the amount of time (rating periods) since the last competition and '350' is assumed to be the RD of an unrated player. If several games have occurred within one rating period, the method treats them as having happened simultaneously. The rating period may be as long as several months or as short as a few minutes, according to how frequently games are arranged. The constant is based on the uncertainty of a player's skill over a certain amount of time. It can be derived from thorough data analysis, or estimated by considering the length of time that would have to pass before a player's rating deviation would grow to that of an unrated player. If it is assumed that it would take 100 rating periods for a player's rating deviation to return to an initial uncertainty of 350, and a typical player has a rating deviation of 50 then the constant can be found by solving for .[9]
Or
Step 2: Determine new rating
[edit]The new ratings, after a series of m games, are determined by the following equation:
where:
represents the ratings of the individual opponents.
represents the rating deviations of the individual opponents.
represents the outcome of the individual games. A win is 1, a draw is , and a loss is 0.
Step 3: Determine new ratings deviation
[edit]The function of the prior RD calculation was to increase the RD appropriately to account for the increasing uncertainty in a player's skill level during a period of non-observation by the model. Now, the RD is updated (decreased) after the series of games:
Glicko-2 algorithm
[edit]Glicko-2 works in a similar way to the original Glicko algorithm, with the addition of a rating volatility which measures the degree of expected fluctuation in a player’s rating, based on how erratic the player's performances are. For instance, a player's rating volatility would be low when they performed at a consistent level, and would increase if they had exceptionally strong results after that period of consistency. A simplified explanation of the Glicko-2 algorithm is presented below:[7]
Step 1: Compute ancillary quantities
[edit]Across one rating period, a player with a current rating and ratings deviation plays against opponents, with ratings and RDs , resulting in scores . We first need to compute the ancillary quantities and :
where
Step 2: Determine new rating volatility
[edit]We then need to choose a small constant which constrains the volatility over time, for instance (smaller values of prevent dramatic rating changes after upset results). Then, for
we need to find the value which satisfies . An efficient way of solving this would be to use the Illinois algorithm, a modified version of the regula falsi procedure (see Regula falsi § The Illinois algorithm for details on how this would be done). Once this iterative procedure is complete, we set the new rating volatility as
Step 3: Determine new ratings deviation and rating
[edit]We then get the new RD
and new rating
These ratings and RDs are on a different scale than in the original Glicko algorithm, and would need to be converted to properly compare the two.[7]
See also
[edit]References
[edit]- ^ Glickman, Mark. "The Glicko System" (PDF). Archived (PDF) from the original on November 3, 2022. Retrieved October 13, 2022.
- ^ Valve. "Team Fortress 2 Update Released". Archived from the original on 29 June 2021. Retrieved 29 June 2021.
- ^ "The New Frontiers Update - Gameplay Update 7.33". Archived from the original on 20 April 2023. Retrieved 20 April 2023.
- ^ Justin, O'Dell. "Finding the perfect match". Archived from the original on 11 November 2020. Retrieved 16 January 2015.
- ^ Oatmealdome. "An In-Depth Look at the Splatoon 2 Ranking System". Archived from the original on 24 March 2024. Retrieved 24 March 2024.
- ^ Johnson, Ben (26 October 2023). Perpetual Chess Improvement: Practical Chess Advice from World-Class Players and Dedicated Amateurs. Continental Sales, Inc.
- ^ a b c Glickman, Mark E. (November 30, 2013). "Example of the Glicko-2 system" (PDF). Glicko.net. Archived (PDF) from the original on February 11, 2020. Retrieved January 27, 2020.
- ^ "Australian Chess Federation Ratings By-Law" (PDF). Archived (PDF) from the original on 11 March 2020. Retrieved 17 January 2019.
- ^ "Welcome to Glicko ratings". Archived from the original on 2020-12-12. Retrieved 2010-02-11.
External links
[edit]- Professor Glickman's Glicko-Website Archived 2020-12-12 at the Wayback Machine
- TrueSkill [1] Archived 2019-10-16 at the Wayback Machine rating system by Microsoft borrows many ideas from Glicko.
- forwardloop/glicko2s Archived 2020-11-12 at the Wayback Machine Glicko-2 implementation for the JVM
- RobKohr/glicko Archived 2019-10-16 at the Wayback Machine JavaScript Glicko-2 implementation.
- mmai/glicko2js Archived 2020-12-12 at the Wayback Machine Client side javascript and node.js Glicko-2 implementation
- deepy/glicko2 Archived 2020-09-12 at the Wayback Machine Python Glicko-2 implementation.
- sublee/glicko2 Archived 2021-01-06 at the Wayback Machine Python Glicko-2 implementation.
- PlayerRatings Archived 2020-05-14 at the Wayback Machine R Glicko implementation by Alec Stephenson and Jeff Sonas.
- scala-glicko2 Archived 2019-10-16 at the Wayback Machine Scala Glicko-2 implementation.
- dimos/glicko2 Archived 2022-02-16 at the Wayback Machine Glicko-2 implementation for Scala and Scala.js