How should Wiggle be changed?

Case number:699969-996878
Topic:General
Opened by:bob1928
Status:Open
Type:Suggestion
Opened on:Saturday, February 8, 2014 - 22:33
Last modified:Saturday, February 8, 2014 - 22:33

The latest front page blog invites feedback about the user tools. This thread is intended to collect player comments on Wiggle.

My input for Wiggle:

At the top of my list: Wiggle controls (whatever from they take) should be set-able from scripts (GUI and Lua).

My personal preference for such controls is continuous rather than discrete (low, med, high). At present I am frustrated that Wiggle-Med doesn’t do enough and Wiggle-High does too much).

In its present form puzzles reach a well settled point where Wiggle seems to totally give up and slip into a mode of doing about 10 iterations per second. It’s like not even looking for work rather than completing some ‘unit of work’ (whatever that is). I’m thinking maybe we could have two variables: one setting how hard Wiggle looks for things to do (aggressive-ness...for want of better term) and a second control for how long it works on things (‘persistence’) which might be based on time or score change.

(Sat, 02/08/2014 - 22:33  |  0 comments)


Sitemap

Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, RosettaCommons