Hey MikeMirzayanov why rating of codeforces problems are getting updated so late? Please look into it, as it helps during upslolving.
# | User | Rating |
---|---|---|
1 | jiangly | 3640 |
2 | Benq | 3593 |
3 | tourist | 3572 |
4 | orzdevinwang | 3561 |
5 | cnnfls_csy | 3539 |
6 | ecnerwala | 3534 |
7 | Radewoosh | 3532 |
8 | gyh20 | 3447 |
9 | Rebelz | 3409 |
10 | Geothermal | 3408 |
# | User | Contrib. |
---|---|---|
1 | maomao90 | 173 |
2 | adamant | 164 |
3 | awoo | 161 |
4 | TheScrasse | 160 |
5 | nor | 159 |
6 | maroonrk | 156 |
7 | SecondThread | 152 |
8 | pajenegod | 146 |
9 | BledDest | 144 |
10 | Um_nik | 143 |
Hey MikeMirzayanov why rating of codeforces problems are getting updated so late? Please look into it, as it helps during upslolving.
Name |
---|
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.)