New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
glicko_rating_period
is probably supposed to imply decay_deviation
#3
Comments
Hi, thanks for the bug report! I think you are right, this seems to be an oversight. If you want to submit a PR to fix this yourself, you are welcome to. Otherwise I will do so sometime later this weekend. I think it would make sense to run the same calculation in the normal |
Trying to fix this now. I wanted to put step 1 calculation into |
Yes, I think that would make the most sense. The calculated RD from step 1 also would be needed in the |
Also, I assume this will break the |
We could either pass in a value that will equal the same RD after calculation (seems to be `~190) and round the outcome, or just change the outcome of the test. I think I would prefer solution 1 but either is fine. Edit: So I with solution 1 I meant setting the RD like this should yield the same results, maybe with a slight rounding error: let player = GlickoRating {
rating: 1500.0,
deviation: (200.0_f64.powi(2) - 62.3_f64.powi(2)).sqrt(),
}; |
I'll do the first solution for |
I think just changing the outcome is the best option there, since it is not based off of any official example. |
As far as I understand it, Glicko paper requires to increase RD at the beginning of every rating period in Step 1 before changing it again in Step 2, regardless of whether the player played games in previous rating period or not, since it is said that Step 1 should be done for each player and Step 2 specifies RD as a rating deviation from Step 1:
Which I believe means that
glicko_rating_period
needs to run step 1 as well, the same equation thatdecay_deviation
uses. This would be similar to Glicko-2 where Step 6 is ran in bothglicko2
andglicko2_rating_period
.The text was updated successfully, but these errors were encountered: