Odd 'mutate' behaviour, or did something change?

Case number:699969-991284
Opened by:CharlieFortsCon...
Opened on:Saturday, December 10, 2011 - 21:26
Last modified:Sunday, December 11, 2011 - 11:43

Evening FoldCentral

Working 487 tonight, and mistakenly ran a 'BlueFuze' variant that has a 'do_mutate ()' step instead of a 'do_shake ()' - to my surprise, it actually did something. Previously, on non-mutable puzzles, the do_mutate would just skip to the next line of code, and produce a white bar on the Undo graph. So, did something get changed?

Curiosity tweaked, I ran a single line, 'do_mutate (1)' on 487, and it did a shake, but produced a light blue bar (mutate) on the Undo graph. When I run a 'select_all (), do_mutate (1), deselect_all ()' it does a shake, but produces the dark blue bar (shake) on the Undo graph.

It's well known that mutate has a shake in-built to it, but this is the first time I've actually seen it function in non-mutable puzzles. I'm happy to be shot down, but I've not seen this behaviour before.


(Sat, 12/10/2011 - 21:26  |  1 comment)

Joined: 06/17/2010

Maybe it is because it was not found better mutation only better ss position? Thats why it produces shake not mutate undo?


Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, Boehringer Ingelheim, RosettaCommons