Constraints & the Contact Map

Case number:699969-991197
Opened by:tristanlbailey
Opened on:Thursday, December 1, 2011 - 07:18
Last modified:Thursday, December 1, 2011 - 17:19

While doing puzzle 486 (Exploration puzzle 457 with constraints), I noticed there were several constraints that have been assigned to the puzzle. I only found out just how many, and where they were, when I pulled the starting model apart. These particular constraints are different to the ones used in the Intro levels, as they only appear when the constrained segments are apart from each other. If we are supposed to stick to these constraints to achieve higher scores, there should be a better way of showing where these constraints are. I also noticed that changing the "Show Constraints" option under the "View" menu doesn't do anything to these kinds of constraints.

I would like to suggest that the Contact Map is changed to display constraints, so that they are easier to track, especially when there are several constraints present. I have attached an image of one way of doing this. You will notice that I have changed the colour of the contacts in the map, so that the constraints can use red. The pink blocks on the key at the side have also been removed, as they don't serve any clear purpose. When doing an Exploration puzzle without constraints, the "Excellent!" and "Constraints" labels and squares in the key, disappear.

I would also like to suggest that the name of the Contact Map is changed to "Exploration Map", and the Exploration Map name changed to something else (or perhaps even remove the map, since it doesn't appear to do anything at the moment), as the names can confuse people. I accidentally discussed the wrong one with a new player about a week ago, when they asked about it, and didn't realise my mistake until quite some time later.

My Contact Map.png34.43 KB
(Thu, 12/01/2011 - 07:18  |  1 comment)

beta_helix's picture
User offline. Last seen 16 hours 37 min ago. Offline
Joined: 05/09/2008
Groups: None

good suggestion, assigning....


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, Boehringer Ingelheim, RosettaCommons