Changing project.

Yeah -- I've lost a couple of my top solutions this way. It's annoying.

Would you prefer another button, or to just replace the existing restore very best with this behavior?

Hello Seth,

I would recommend a "set very best" new button to solve this problem, for the following reasons :

1) when the foldit algorithms are wiggling a puzzle with conditions not met(cnm), occasionaly the protein will distort into a shape where the conditions are met, just for a fraction of a second. If you are eagle eyed you see the red line flash on and off across the score. If the "set very best" was automatic then you could have the bizarre situation of starting with a structure at 9000pts(cnm), ending with a structure at 9500pts(cnm) but with a "restore very best" at an arbitrary point somewhere between the two.

2) the problem also applies to "quest to the native" puzzles. Often, whilst distorting the backbone of the protein to match the ghost image, the closeness of the protien to the ghost is much better than previously, but the score is significantly lower. It would be usefull at this point to "set best score" to what is displyed on the screen. The benefit of this is that currently the "set recent best" functionality of the programme is unavailable for use as a development tool if it is being used to store the best matching shape (which is the only way to use the programme at present).

Obviously if you implement a "set very best" button its going to need a warning sign the size of a small planet,

Rgds

SteveB

I would prefer another button.

Another button,too.

Still waiting

A fix for this will be coming up soon!

May I also suggest a lua function for this new feature. If it isn't implemented now it will just be another feedback suggestion later. Might as well get it out of the way on the first shot. I'm sure the script writers will appreciate it

Yes...a button and a lua function, please!

The newest update has a button and lua function for restoring the "credit best", the best solution that satisfies all the conditions and therefore gets credit.

Nice job, but we still need a "set very best" function.
An example:
If you do a rebuild, it often creates more than one result in the undo bar.
Most times, the first rebuild results are better than the last ones, but you can only get the very last rebuild result by script, as no other script commands are executed, when a tool is running.
Setting the "very best" state before rebuilding and getting the very best result at the end of rebuild would fish out the very best of all rebuild states which were generated by the rebuild command.

Kind regards,
Alex

Thanks to the developers for addressing this issue, but the implemented solution, restore_credit_best(), simply doesn't work as far as scripting is concerned. The main issue is that the user will be forced, for many scripts, to start at the best solution rather a lower-scoring one of their own choosing, making exploration of alternate structures more difficult. There are other problems too.

Preferable would be a function such as is_condition_met() which would return a boolean value. Much more flexible and hopefully easy to implement.

Just as spvincent said, scratching at the top the whole time doesn't help.
We definitely need a possibility to change the "very best" state.

There needs to be two functions:

1) are_conditions_met()

2) get_credit_best_score()

While you are implementing that last one, can we get

3) get_recent_best_score()

4) get_absolute_best_score()

as well. These should all return negative scores or have the argument that allows negative scores.

the requested functions should have gone out in Lua V2