strange things on 1115 (scoring, autosave)
|Opened on:||Thursday, July 23, 2015 - 08:12|
|Last modified:||Tuesday, July 31, 2018 - 20:48|
Puzzle 1115 seems to have a scoring problem.
After a client crash due to "asymmetry introduced by ActionLocalMinimize" while Acid Tweeking (yes I verified that debug.txt was updated at the time of the crash), my evolver score showed as 13621. Actually, it had been 13621 for a while, but the recipes were not seeing it.
There was an autosaved credit best showing 13621, but when I opened it, it loaded as 13606. I then did a "restore credit best", which set the score to 13616, which was the last thing reported by my recipe before the crash.
Maybe it's to be expected, but the Manage Solutions window is no longer showing the 13621 credit best autosave. The credit best autosave is now 13616, with a recent best autosave of 13617. Both these load at the same score, 13616.791.
This seems like a new wrinkle on a familiar problem. The client is now smart enough to eliminate the evidence. Next it will get a good lawyer.