We have posted a puzzle in the developer preview to solicit feedback on which starting model will be most useful to you for future puzzles.
More info (including how to try out the Foldit Developer Preview) here:
http://fold.it/portal/node/992750
Also note that Puzzle 562, the first CASP10 puzzle with symmetry, closes on May 29th. We hope you enjoy it!
It's called:
"Help us pick the best starting model!"
Using lowest start.
So start1 has Lysine 43 wiggle locked?
Are start2 and start3 ok?
It is connection between #43 and #44 residue.
It is not locked entirely (bands are working) but when wiggle it stays red, need local wiggle (selected 3-4 residues) to solve.
It is possible to move that "wiggle hook point" to another place? First or last residue? Best scoring residue? It is puzzle config or wiggle function itself?
One of the things we are trying to determine with this BETA puzzle is if relaxing these server models actually solves this issue.
If start2 and start3 do not have this problem, or any other issues, then we can do this for all future server puzzles.
If all three multi-starts have the same problem, then this "wiggle hook point" is the problem.
If I reset to model 1, then shake out the sidechains, then wiggle all, and repeat this procedure a couple of times, the score rises to 9387 and the whole protein looks fine. The loop containing seg 43 is green with segments showing normal scores of 22pts+.
Seg 43 is locked in 3D space when using global wiggle, but there has always been one segment like this in every puzzle I have ever seen. The fact that it is locked in space has always seemed irrelevant, as I guess the programme is normalising to this segment's configuration before rendering the display i.e. seg 43 is moving relative to the rest of the protein, even though it appears to be static to the observer.
Can't see a problem with this puzzle.
On the subject of which segment in the puzzle displays this property, then it would be highly advantageuos to be able to move the property onto a user selected segment. 'Static' segments on loops are much harder to work with from a visual point of view than static segments on helices/sheets. For some psychological reason, when I wiggle all, I expect the sheets to remain stationary and the loops to move, and when the opposite happens it is difficult to grasp in your mind.
Models 1,2 and 3 behave in exactly the same way
I used a start 3 at low ci to play around with it, and no matter what you do, that seg or connection stays exactly in place during wiggle while the whole rest of the protein moves around freely. Perhaps I just don't notice that during other puzzles, but it does seem pronounced since it's in an area that is crying for a rebuild :-)
Side note… I had downloaded the devprev just to test this puzzle, so have only opened devprev twice. As I tried to open another puzzle in this client, it evaporated with no notice. Here's the error message:
ERROR: boinc::Puzzle::current_env_puzzle_okay(metadata_->get_puzzle_id())
ERROR:: Exit from: /Users/jflat06/foldit/mini-interactive-main/rosetta_source/xcode/../src/game/application/novice/Solution.cc line: 643
I ran the same 3 scripts (fusy type and two rebuilders which are not lossy) after restarting the 3 models each time - I did not touch the protein at all manually, scores after each script:
1 start .504 >9401,9501,9800
2 start 6873 >9416,9576,9772
3 start 9035 >9559,9581,9636