recentbest ignores residue count penalty
|Opened on:||Tuesday, May 30, 2017 - 03:08|
|Last modified:||Tuesday, July 31, 2018 - 20:43|
As shared (just now) with scientists on puzzle 1373, a solution with a score of 10690 shows a recentbest score of 10805, but recentbest.Restore does not change the score.
The solution has 100 residues, incurring a penalty of 5 * -23 = -115 points. So the recentbest score is incorrectly ignoring this penalty.
I've also noticed this problem on other design puzzles, including the current 1383, but I haven't been able to reproduce it reliably.