From Seth's Blog post: "We imagine that low and medium power wiggle will be most useful at the beginning of a puzzle to explore different structure possibilities. If a structure is already ideal, low power wiggle may be the fastest way to get a good idea of how well it can score."
If this is the case, wouldn't it be better to have low power as the default? (Every unecessary click puts unneeded stress on the brachial, ulnar and radial nerves.)
Or just make the client remember its previous setting.
Disabled Cut Bands and LOW has a better yield per unit of time than Medium. High has a ridiculous yield. See first results (on a big protein) here:
http://fold.it/portal/recipe/46929
(+ Wiggle backbone crashes on a big protein)
Selecting both ends of a cutpoint and then calling wiggle (from selection interface) with cutpoints pull enabled does only work well on low wiggle. WHY?
I agree, make it remember.
Medium is the default because many of the other tools can actually lead to unideality in the pose. For example - rebuild, local wiggle, and tweak all use cutpoints internally and attempt to close them automatically, but they dont always get it perfect. So we wanted the default to be a version of wiggle which would smooth out these imperfect cut resolutions and re-idealize the pose.
I still don't see need for medium to be the default. Why can't it be remembered per track? Dealing with the client crashes alone is annoying enough, but finding out that you forgot to change the wiggle power back to the setting you had it on prior to a crash is doubly so. I'm not even playing the De-novo now, too many crashes. It's a shame too, because I was actually happy with the design.
So jflat, firstly, if that is the case, then why have low at all since it will lead us astray? Or is low OK for wiggle all and shake etc. So secondly, if that is the case, then since W and S are the basic tools we are using to stabilize (maybe even before tweaking, local wiggle, or rebuild), shouldn't low still be the default then?
I also agree with gitwut regarding forgetting to change the medium default which leads to wasted time and effort, overheating especially on big puzzles, and the dreaded crashing. I have even crashed on medium just doing a wiggle sidechains.
First of all, the client should NEVER change the setting when not asked for. So no change when changinge puzzles, tracks, loading a solution or whatever.
And the program (read devs) should not guess what it best for the players, if we want Low we should get Low and that should be remembered.
The behavior menu switching Clash Importance and Wiggle power on puzzle changes (or when selecting Enable Cut Bands) has been reproduced and is currently being looked at.