Extracting Quantitative Information with Lua

Started by brow42

brow42 Lv 1

I have written scripts to force sidechain angles in disulfide bridges, measure dihedral angles, twist sheets, make perfect (pi!) helices. I've done this because the tweak/rebuild tool is too violent, or I can't intuit WHY a segment is scoring poorly. A lot of other discussion has been going on among the scriptors about doing similar things themselves. Clever scripting and a lot of trig can get you pretty far.

Quantitative information has been intentionally hidden from the players. Being able to make measurements allows the creation of scripts that converge to a particular conformation, be it a superior evolved foldit solution or a pdb extract.

What information is the foldit team willing to provide? What limits should we impose upon ourselves in using that information? There are lots of stakeholders in this:

The science team wants novel solutions, not copies of other servers.

The players want a fair competition with integrity of the solo / evolved ranking system

The games team wants to compare humans to computers and study crowdsourcing and gamification.

The dev team has to implement it.

I think some guidelines need to be laid out so that everybody gets what they want out of Foldit. For example, from a scripting folder's point of view, http://fold.it/portal/node/991316 really should be implemented, we're doing crazy work-arounds to emulate it, yet it is ultimately a very powerful function in regards to the information it provides.

beta_helix Staff Lv 1

I promise to bring this up at our next Foldit meeting, but please don't change the priority of this one to High. That is reserved for when something in the game is broken, thanks!

ComputerMage Lv 1

Okay. Thanks for bringing it up. And I promise I won't push it to highest priority.
May be only to the second to the highest ;)

brow42 Lv 1

No explicit guidelines have been given, but steps have been taken to discourage/prevent outright copying of structures, which is something of a statement. Closing.