restore best forgets history

Case number:954892-972940
Topic:Developer Preview
Opened by:Brad Taylor
Opened on:Saturday, February 7, 2009 - 18:46
Last modified:Monday, February 9, 2009 - 17:50

In the beta, restore deletes the history. It should leave the history when used.

(Sat, 02/07/2009 - 18:46  |  3 comments)

xiando's picture
User offline. Last seen 6 years 37 weeks ago. Offline
Joined: 10/19/2008
Groups: Oma Gawd

Yes, the history should not be cleared....but I don't see that on my PC. It seems to keep the history just fine (minus any subsequent action and it's own associated contribution via resetting the score to the "rcnt best" marker previously defined)...Are you on Linux or Mac O/S?

However, if I hit ctrl-v (restore very best score) after setting (ctrl-shift-n) or even restoring (ctrl-n) a recent (or new) best, and since a peak hold detector is supposed to store the best value after a reference point is set (technically a floating reset or "set-to-current-value" function), the "recent best" will increment accordingly, so it will now point to that score, and overwriting the recent best originally's a caveat that can't be overcome automatically...

If you need a restore point that is static or immovable, then use ctrl-shift 1/2/3 and and ctrl-1/2/3 to set and restore those points. the set Rcnt Best can then be applied to start from that location.

Joined: 11/10/2007
Groups: Window Group
Status: Open » Closed

I agree as well. This will not be fixed in the current developer preview, but should be in the feedback tracker for future releases.

Joined: 11/10/2007
Groups: Window Group
Status: Closed » Closed

Mark as duplicate.


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