|Opened by:||Timo van der Laan|
|Opened on:||Saturday, September 7, 2013 - 11:20|
|Last modified:||Saturday, September 7, 2013 - 11:20|
I have shared with the scientists just an example of the following problem that is occuring a lot on 773.
Running a script containing just WiggleAll(2), less precize wiggle, the score almost does not change.
Then set CI on 0.5 run the same script and move CI back to 1 when the score has dropped about 10 pts. Then wiggle does a lot more. In the starting position there are a few bad backbone scores that are not affected the first time. In the example I shared seg 33 -100, seg 34 -200.
It looks like wiggle is not really targeting bad backbone scores like it used to.