Cutpoints incorrectly placed in 501?

Case number:671071-991481
Topic:Game: Other
Opened by:tokens
Opened on:Thursday, January 5, 2012 - 20:32
Last modified:Thursday, July 19, 2012 - 12:09

After resetting the puzzle (puzzle 501) to get to the start where segment 29-60 were unfrozen, the cutpoints weren't placed at the ends of the unfrozen segments. Instead they were placed between segment 56-57 and between segment 70-71 (possibly the ends of the unfrozen segments of another start?).

(Thu, 01/05/2012 - 20:32  |  8 comments)

Joined: 04/19/2009

Kicking priority up and adding link to picture that tokens posted in global:

I was unable to reproduce this.

Thanks for reporting, tokens!

spdenne's picture
User offline. Last seen 2 weeks 2 days ago. Offline
Joined: 10/01/2011
Groups: Void Crushers

I've had this too, by going through each starting point, and saving it as an undo track. When going from a higher scoring starting position to a lower scoring starting position, and restoring best score, the cut points from the previous starting point were applied.

Joined: 06/24/2008
Groups: Void Crushers

I think it would be helpful if there was a way to label each start. Most of us are messing with several starts in different tracks and working with several starts on our screens at once - its easy to lose track of which you are looking at.

Joined: 04/19/2009
Topic: General » Game: Other

Bump so that the devs will see this when they return from holidays

jflat06's picture
User offline. Last seen 6 hours 41 min ago. Offline
Joined: 09/29/2010
Groups: Window Group

It looks like the competitive solutions are still making use of this bug, so we'll have to take it down until we can resolve the situation. Any details on reproducing this bug would be welcome (I haven't been able to reproduce it yet).

Joined: 04/19/2009

glaciall had just jumped in score and posted this as you pulled the puzzle:

Same area of the puzzle, but the cutpoint in a totally different place.

jflat06's picture
User offline. Last seen 6 hours 41 min ago. Offline
Joined: 09/29/2010
Groups: Window Group

I have posted a version of this puzzle into the developer preview.

I am having trouble reproducing this bug on my computer; if you have some time, it would be greatly appreciated if you could play with it and see if you can reproduce the bug (making sure to keep track of what steps you took to get the bug).

Joined: 06/17/2010
Status: Open » Closed

Threading tool fixed, we can cut where we want.


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