↵
↵
<spoiler summary="UPD 2 Sep 2018">↵
I've deployed an update today. If you face any issues with CF-Predictor, please let me know :) ↵
</spoiler>↵
↵
Hi guys! As I mentioned on previous contest I'm working on tool that predicts rating changes. I'm happy to present it now!↵
↵
↵
↵
A huge amount of your nerve cells die every time when you wait for a rating update on Codeforces. Stop this! From now you could use this service, it calculates approximate rating changes for every contestant.↵
↵
The most interested thing for you is extension. It partly modifies the contest standings page and shows approximate rating changes for every contestant. It is available for three browsers: ↵
↵
[](https://chrome.google.com/webstore/detail/rating-predictor-for-code/ocfloejijfhhkkdmheodbaanephbnfhn)↵
[](https://addons.opera.com/en/extensions/details/cf-predictor/)↵
[](https://addons.mozilla.org/en-US/firefox/addon/cf-predictor/)↵
↵
Extension in work:↵
↵
↵
↵
Also you could find more detailed information (seed, rank, expected delta, etc.) [here](http://cf-predictor.us-west-2.elasticbeanstalk.com/).↵
↵
↵
A project still in beta, so predictions are not very accurate. Average mistake around 5 points, but for the contestants at the back of standings it could be greater up to a few hundreds.↵
↵
<spoiler summary="Tech details">↵
[Project](https://github.com/WslF/CF-rating-prediction) consist of 3 main parts. ↵
↵
↵
| № | assignment | path | language |↵
|:---- | :------ | :------ | :-------|↵
| 1 | compute role | CF-PredictorBackEnd | Java8, Tomcat |↵
| 2 | web role | CF-PredictorFrontEnd | Java8, Tomcat |↵
| 3 | chrome extension | CF-Predictor-Extension | JavaScript (with using jQuerry) |↵
↵
↵
**Compute role** send requests to codeforces, compute approximate rating changes and store some of them in the cache. Every cached value recomputes once a few minutes.↵
↵
**Web role** just get rating prediction from compute role and show it in human readable view.↵
↵
Currently compute & web roles runs on aws Elastic Beanstalk. Servers run only in the contest's days to prevent overusing free tier resources.↵
↵
**Chrome extension** send request to web role, get JSON response and partly modify the contest standings page.↵
↵
If you want to contribute to the project or have any questions, you could reach me by codeforces profile ([user:Wsl_F,2017-02-13]) or email: [email protected]↵
↵
</spoiler>↵
↵
I'd like to thank [user:Rubanenko,2017-02-13] and all other members of NBHEXT developers team for your shared [sources](https://github.com/Rubanenko/NBHEXT) and [user:MikeMirzayanov,2017-02-13] for the great Codeforces platforms with shared API & ratings formulas.↵
↵
**AWESOME UPD** ↵
↵
Prediction for todays contest (cf #399) is absolutely matching real rating changes! Thanks for [user:AlexDmitriev,2017-02-20]! He was close to find my bug in rating calculation:) ↵
↵
↵
**UPD**↵
↵
Thanking [user:KieranHorgan,2017-10-20] now CF-Predictor has a new design. Check [it](https://wslf.github.io/CF-Predictor/) out:)↵
↵
↵
<spoiler summary="UPD 2 Sep 2018">↵
I've deployed an update today. If you face any issues with CF-Predictor, please let me know :) ↵
</spoiler>↵
↵
Hi guys! As I mentioned on previous contest I'm working on tool that predicts rating changes. I'm happy to present it now!↵
↵
↵
↵
A huge amount of your nerve cells die every time when you wait for a rating update on Codeforces. Stop this! From now you could use this service, it calculates approximate rating changes for every contestant.↵
↵
The most interested thing for you is extension. It partly modifies the contest standings page and shows approximate rating changes for every contestant. It is available for three browsers: ↵
↵
[](https://chrome.google.com/webstore/detail/rating-predictor-for-code/ocfloejijfhhkkdmheodbaanephbnfhn)↵
[](https://addons.opera.com/en/extensions/details/cf-predictor/)↵
[](https://addons.mozilla.org/en-US/firefox/addon/cf-predictor/)↵
↵
Extension in work:↵
↵
↵
↵
Also you could find more detailed information (seed, rank, expected delta, etc.) [here](http://cf-predictor.us-west-2.elasticbeanstalk.com/).↵
↵
↵
A project still in beta, so predictions are not very accurate. Average mistake around 5 points, but for the contestants at the back of standings it could be greater up to a few hundreds.↵
↵
<spoiler summary="Tech details">↵
[Project](https://github.com/WslF/CF-rating-prediction) consist of 3 main parts. ↵
↵
↵
| № | assignment | path | language |↵
|:---- | :------ | :------ | :-------|↵
| 1 | compute role | CF-PredictorBackEnd | Java8, Tomcat |↵
| 2 | web role | CF-PredictorFrontEnd | Java8, Tomcat |↵
| 3 | chrome extension | CF-Predictor-Extension | JavaScript (with using jQuerry) |↵
↵
↵
**Compute role** send requests to codeforces, compute approximate rating changes and store some of them in the cache. Every cached value recomputes once a few minutes.↵
↵
**Web role** just get rating prediction from compute role and show it in human readable view.↵
↵
Currently compute & web roles runs on aws Elastic Beanstalk. Servers run only in the contest's days to prevent overusing free tier resources.↵
↵
**Chrome extension** send request to web role, get JSON response and partly modify the contest standings page.↵
↵
If you want to contribute to the project or have any questions, you could reach me by codeforces profile ([user:Wsl_F,2017-02-13]) or email: [email protected]↵
↵
</spoiler>↵
↵
I'd like to thank [user:Rubanenko,2017-02-13] and all other members of NBHEXT developers team for your shared [sources](https://github.com/Rubanenko/NBHEXT) and [user:MikeMirzayanov,2017-02-13] for the great Codeforces platforms with shared API & ratings formulas.↵
↵
**AWESOME UPD** ↵
↵
Prediction for todays contest (cf #399) is absolutely matching real rating changes! Thanks for [user:AlexDmitriev,2017-02-20]! He was close to find my bug in rating calculation:) ↵
↵
↵
**UPD**↵
↵
Thanking [user:KieranHorgan,2017-10-20] now CF-Predictor has a new design. Check [it](https://wslf.github.io/CF-Predictor/) out:)↵
↵
