freeze.Unfreeze does not check segment number

Case number:699969-2001176
Topic:General
Opened by:LociOiling
Status:Open
Type:Bug
Opened on:Saturday, September 12, 2015 - 18:29
Last modified:Saturday, September 12, 2015 - 18:29

Most foldit function produce an error if the specified segment index is out of range. The error terminates the calling recipe.

freeze.Unfreeze does not seem to check its first argument, the index of the segment to unfreeze. As a result, call like this succeed:

freeze.Unfreeze ( 99999, true, true )
freeze.Unfreeze ( -9999, true, true )

While attempting to unfreeze a non-existent segment seems harmless, this behavior is inconsistent with other foldit functions. For example, structure.DeleteCut produces an error with similar arguments. Deleting a non-existent cut point would also seem harmless.

(Sat, 09/12/2015 - 18:29  |  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, Microsoft, Adobe, RosettaCommons