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 | 4009 |
2 | jiangly | 3773 |
3 | Radewoosh | 3646 |
4 | ecnerwala | 3624 |
5 | jqdai0815 | 3620 |
5 | Benq | 3620 |
7 | orzdevinwang | 3612 |
8 | Geothermal | 3569 |
8 | cnnfls_csy | 3569 |
10 | gyh20 | 3447 |
# | User | Contrib. |
---|---|---|
1 | awoo | 161 |
2 | maomao90 | 160 |
3 | nor | 157 |
4 | atcoder_official | 156 |
4 | cry | 156 |
6 | -is-this-fft- | 155 |
7 | maroonrk | 154 |
8 | adamant | 153 |
9 | Um_nik | 151 |
10 | djm03178 | 146 |
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].