This has been around for a long time…I keep forgetting it. I just spent an hour trying to moves something with bands and then realized I had the tab window up. So I finally made a test case.
Basically, the Tab info window causes Lua global wiggle (and maybe other wiggles) to stop after one mini-iteration. This makes the protein look frozen when it really isn't.
Test case: (2012-05-17-48987M-win_x86)
573b Reset Score 5484.534
Clash Importance 1.0
Run Script with no Tab window up, final score 9429.549
Run Script with Tab window up (I hit 31 Aspartate at random), final score 5503.663
Script:
puzzle.StartOver()
structure.WiggleAll(1)
Nice catch brow42!
this script will do the same, final scores the same:
select_all()
do_global_wiggle_all(1)
Hmmm I had looked into this before - under the assumption that it was banding to center of the protein that was causing the issue. It just so happens that I would find the center of the protein by tabbing over residues…
If it turns out the tab window is at fault, this should make it a lot easier to debug! Thanks!
This m might sound stupid - but what is the "Tab Window" ?
This should be fixed in the next update.
It would appear this was one source of "wiggle lock". If you had the tab window up while wiggling, the protein would somehow get stuck in a low score state, and even after closing the tab window, it would still remain stuck. The only way to get rid of it was to reset the puzzle.
…and even after closing the tab window, it would still remain stuck. The only way to get rid of it was to reset the puzzle.
Wow! It does explain some problems.
It's the little "Segment Information" window that appears when you hit the tabulator key on your keyboard while mouse-hovering over a segment.
Ah. OK. I almost never use that so it didn't even sound familiar.
I would agree except that I've observed that once the tab window was closed, wiggle behaved normally. But if you've found the problem, great!
It depends on how long you let wiggle run for. If you close it right away it seems to recover, but if you let it run until it starts really getting stuck, it would appear that it cant recover without a reset. I'm still not totally sure how the tab window was affecting wiggle behavior, but at least it should be fixed now.
