Timo van der Laan Lv 1
Very good analysis Loc. Now I get why my DRW reports ligands in some cases, and behaves accordingly. I was really puzzled why this happened.
Very good analysis Loc. Now I get why my DRW reports ligands in some cases, and behaves accordingly. I was really puzzled why this happened.
This one could use a new title, like "auto structures tool creates spurious ligand".
Fixed :)
My tests on release 20150819-e47db4cb4b-win_x86 show this bug has indeed been fixed.
My tests included two semi-related issues:
the auto structures tool no longer changes the last segment to a ligand when all segments are selected
type "molecule" – codes "m" and "M" – as argument 2 to structure.SetSecondary no longer terminate the recipe
The valid secondary structure are now 'e', 'h', 'l', 'm', 'E', 'H', 'L', and 'M'. The codes 'm' and 'M' don't seem to have any effect on a non-ligand puzzle. Other codes still terminate the recipe.
I'm marking this feedback closed. I'll see if there was a separate feedback on the "molecule" issue.
Changing the status back to "open", this bug has been back for a while (http://fold.it/portal/node/2001300) and is still with us in 20151218-b5ec35b633-win_x86-devprev.
Old problem, got fixed a while back, closing.