Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Migrate ratings to Codeforces #811

Closed
xiaowuc1 opened this issue Nov 25, 2018 · 1 comment
Closed

Migrate ratings to Codeforces #811

xiaowuc1 opened this issue Nov 25, 2018 · 1 comment

Comments

@xiaowuc1
Copy link
Contributor

DMOJ currently uses TopCoder ratings. TopCoder ratings are unique in that they have a volatility metric which bounds the rating changes that an individual has (individuals with lower volatility change rating less than individuals with higher volatility).

This issue is a proposal to migrate the rating system to that used by Codeforces, which does away with the notion of volatility. In reality, this issue is asking for volatility to be removed from the rating system, and migrating to Codeforces is a convenient way to achieve this.

Although there is nothing inherently wrong with TopCoder's rating system, it does not feel well-suited to DMOJ. The main reason for this is that the community is small and volatility will result in rating differences going to zero over time as volatility converges to zero, which punishes individuals who stay on DMOJ for a long time and markedly improve. By comparison, on TopCoder, volatility does not appear to converge to zero which is why rating changes are not affected by this.

qazokm pushed a commit to uwapcs/DMOJ-site that referenced this issue Dec 28, 2018
outloudvi pushed a commit to SchOJ/site that referenced this issue Jan 12, 2019
SchrodingerZhu pushed a commit to SchOJ/site that referenced this issue Feb 6, 2019
Ninjaclasher pushed a commit to Ninjaclasher/site that referenced this issue Mar 3, 2019
@xiaowuc1
Copy link
Contributor Author

It turns out that TopCoder ratings can be manipulated adversarially (see https://codeforces.com/blog/entry/87848).

It is unlikely that this matters in practice.

malbareda pushed a commit to malbareda/JOEL-web that referenced this issue Jan 4, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants