If there will be 3 or 4 rounds before rating update on problems, we'll have full empty page. Is it like a challenge that codeforces is trying?
# | User | Rating |
---|---|---|
1 | tourist | 3751 |
2 | Benq | 3727 |
3 | cnnfls_csy | 3691 |
4 | Radewoosh | 3651 |
5 | jiangly | 3632 |
6 | orzdevinwang | 3559 |
7 | -0.5 | 3545 |
8 | inaFSTream | 3478 |
9 | fantasy | 3468 |
10 | Rebelz | 3415 |
# | User | Contrib. |
---|---|---|
1 | adamant | 178 |
2 | awoo | 167 |
3 | BledDest | 165 |
4 | Um_nik | 163 |
5 | maroonrk | 162 |
6 | SecondThread | 160 |
7 | nor | 158 |
8 | -is-this-fft- | 154 |
9 | kostka | 146 |
10 | TheScrasse | 144 |
If there will be 3 or 4 rounds before rating update on problems, we'll have full empty page. Is it like a challenge that codeforces is trying?
Name |
---|
clist publishes problem ratings immediately after each contest. Subjectively, I've found these ratings more helpful than the ones provided by Codeforces; they seem to be influenced less by extreme outliers (e.g. D1Fs solved by rainboy) and avoid the artificial constraint of using only ratings in [800, 3500].