After starting a new track in the latest DevPrev release (in my case, 20210927-14624118e3-win_x86-devprev), I noticed that Wiggle does not behave as before.
It feels a bit like a gearbox where the oil has been replaced with a handful of sand: it just does not m o ve .
I copied the track to my Main folder (20210913-39cb7ecfb1-win_x86), and there it behaves as I would expect. I have not done a lot of experimenting, but when Main reaches 5000 points more than DevPrev (both at Medium Wiggle Power and CI 0.3), that seems like a significant difference to me.
Uploaded the track for scientists (Puzzle 2047, 90 residue C4 Tetramer, 0 (-1822) points).
Thank you for letting us know about this, HuubR!
Anyone using a different OS getting this as well?
Thanks again for testing out devprev and finding this!
yes, I also noticed something strange, wiggle's execution time is bit short and it passed in middle of optimizing.
and I've tested it as score benchmark with my recipe and compare it to latest one.
https://fold.it/portal/recipe/105209
attached is a comparison of wiggle possible scores.
this was small test just to clarify that different, so cannot guarantee it as accurate value.
by 20210913-8a73606462-linux_x64-devprev vs 20210927-14624118e3-linux_x64-devprev
okay, I confirmed hot fix.
rerun it again to make sure it was bug fixed.
it has same configuration as previous attachment.
by 20211002-e0f71ff1ca-linux_x64-devprev
Thank you, Nicm25, for for letting me know about the hotfix in DevPrev. I have been using Main since last week, so I did not notice.
I can confirm that the problem is now gone (using 20211004-c10476c737-win_x86-devprev). It wiggles as before :-)
Thanks, beta_helix and devs, for fixing this!
