Huge scoring difference between 681 devprev and 681 main
| Case number: | 954892-994609 |
| Topic: | Developer Preview |
| Opened by: | Hanto_FZ140E_4G |
| Status: | Closed |
| Type: | Bug |
| Opened on: | Friday, March 1, 2013 - 03:25 |
| Last modified: | Tuesday, December 29, 2020 - 11:40 |
I'm seeing a 400 pt increase in scoring between 681 devprev and 681 main with devprev coming out the winner. That means all people playing this puzzle who are on main will be suffering a point and possibly a rank reduction due to the observed difference. So far only using a first recipe on all 681 clients with all clients being pretty close to equal as far as where the recipe is in each client.
| Status: Open » Open |
Thanks for reporting this!
We'll figure out what is going on and resolve this ASAP.
(don't worry, this wasn't a ploy by us to try to get more players beta-testing the devprev client ;-)
Did some research on this.
The difference is caused by a difference in computing the other score.
See my tmp1 shared with myself. Segment 53 gives -11 in main on other, -9 in devprev on other. The rest of the score components seem to be the same.
Some more research: the difference in score can be totally explained by the difference in other score.
There was an update in how Rosetta calculates the score function for electron density. Sorry, I didn't list it in the update news. This will be out into main shortly.
| Status: Open » Closed |
outdated
I saw this and also heard team members complaining about high differences in what was needed for evos.
I saved my score and saved to myself in Main, which is what I was working in - then loaded that into a devprev client - and had an instant increase on loading of 290 points.