Hey MikeMirzayanov why rating of codeforces problems are getting updated so late? Please look into it, as it helps during upslolving.
# | 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 | Um_nik | 3396 |
# | User | Contrib. |
---|---|---|
1 | Um_nik | 163 |
2 | cry | 161 |
3 | maomao90 | 160 |
4 | -is-this-fft- | 159 |
5 | awoo | 158 |
6 | atcoder_official | 157 |
7 | adamant | 155 |
8 | nor | 154 |
9 | maroonrk | 152 |
10 | Dominater069 | 148 |
Hey MikeMirzayanov why rating of codeforces problems are getting updated so late? Please look into it, as it helps during upslolving.
Name |
---|
Yeah it's taking time more than usually expected.
If you didn't know you can actually find approximations of the ratings on clist (which I learned from Ritwin iirc). It's usually pretty accurate, except for ratings below 800 and above 3500 which are of course bounded to those ratings.
Alternately, if you're in a server with the TLE bot, use
;probrat contestID
to get an approximation for the ratings of the problems in any contest.Here are the outputs from the TLE bot on the recent contests:
Note: This was taken before the CF API was temporarily shut down (as is usual for a brief period right after contests), so they be slightly off
(The predicted ratings are not necessarily multiples of $$$100$$$ in the range $$$[800, 3500]$$$; they reflect what the problem would be rated if it had any integer rating, given only the solves in-contest.)