Sketchbook: loading secondary structures counts as a "move"
Case number: | 699969-2004001 |
Topic: | General |
Opened by: | LociOiling |
Status: | Open |
Type: | Bug |
Opened on: | Thursday, August 3, 2017 - 00:40 |
Last modified: | Saturday, February 20, 2021 - 01:53 |
Check out move tester 1.0 for a semi-automated way to verify the impact of various functions.
Still an issue in 20180725-d14dae34c3-win_x86-devprev, see also partial duplicate https://fold.it/portal/node/2005475
Still an issue in 20191029-32048a6a12-win_x86-devprev, bumping due to renewed outbreak of sketchbookitis.
Another year, another sketchbook puzzle.
On 20210208-41263fb5e3-win_x86-devprev, save.LoadSecondaryStructure now costs two moves. It should not cost any moves.
Not strictly on-topic for this feedback, but rotamer.SetRotamer costs also two moves, where it should cost only one.
Also OT but perhaps related is how the move tool works. Moving the entire protein with the move tool doesn't cost anything. Opening a cutpoint doesn't seem to cost anything. But moving a cut section initially costs two moves. After the first move, additional moves are free. Formula350 speculates that some of this accounting magic is related to dojo mode.
Thanks LociOiling! I'm sorry we haven't responded to any of these comments. I could have sworn we fixed some of these bugs previously, but I was mistaken. We shouldn't have any problem tracking these down.
Please continue to post here if you run into more move count weirdness, in addition to the issues you've already listed:
save.LoadSecondaryStructure
rotamer.SetRotamer
Move tool
Insert Cut + Move tool
Calling save.LoadSecondaryStructure from a recipe or using the keyboard equivalent control+shift+9 counts as a move. This happens regardless of whether the saved structure is different from the current structure.