Is rating volatility a bug or a feature? [Forked]

[meili_yinhua]

@espoojaram

In general, Glicko-2 is usually implemented by looking at the last 15 games of a player. I’m not sure if this is still how it’s done on OGS, but it’s at least how it was done before 2021.

This has changed to be 1-game ratings periods, and as I understand it (or so I hope) it uses special volatility calculations for games closer or further apart from each other like Lichess does

@espoojaram

Now that I’ve read meili’s comment, I’m wondering if this can be applied more specifically to the Glicko-2 volatility stat in particular, i.e. is there a way to make volatility equally accurate for players that play at vastly different frequencies?

I’d imagine you’d have to write a whole new ratings system, theoretically it should fit to each player for whatever rate they play at (as opposed to glicko-1 which had it as a constant), but the effects of volatility on Ratings Deviation should already be time-dependent as-is (this is one of the things I griped about constantly during the “sliding window” system)