-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestions for the residue stepper command #14
Comments
Hi Guillawme, These are good suggestions! I’m on holiday until the middle of the month, but will look into it after that. In the meantime, the “isolde step” command does have a few optional arguments that might help. Each is persistent - use the argument once and it will remember your setting for the duration of the session or until you change it again.
I don’t have an option to not reset the orientation, but that certainly seems like a reasonable addition. |
Wonderful, this is helpful already! Thank you. |
These days I am working on a model with many cofactors, so I got a new idea for the residue stepper command: could it also step through cofactors? They are not polymers, but they have a chain ID and a residue number, so it seems like stepping through them should work the same way. At the moment (ChimeraX 1.7.1 and corresponding version of ISOLDE), when I do |
Try including the argument "polymericOnly false" (or just "pol f"). I'm
afraid there's currently no option to step through *just* cofactors, though.
…On Tue, May 28, 2024 at 3:42 PM Guillaume Gaullier ***@***.***> wrote:
These days I am working on a model with many cofactors, so I got a new
idea for the residue stepper command: could it also step through cofactors?
They are not polymers, but they have a chain ID and a residue number, so it
seems like stepping through them should work the same way.
At the moment (ChimeraX 1.7.1 and corresponding version of ISOLDE), when I
do isolde step /a:401 (residue /a:401 is a cofactor and chain /a contains
more cofactors with increasing residue numbers), I am taken to the
cofactor, no problem. But then, isolde step next skips all cofactors and
takes me to the next protein residue (in the next chain). So I simply edit
the first command and go through the residue numbers manually, but this is
a bit slow.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFM54YDFES3XL4OIDIQJXL3ZESJTRAVCNFSM6AAAAAA4NQZCUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVGQYDOOBZHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Altos Labs UK Limited | England | Company reg 13484917
Registered
address: 3rd Floor 1 Ashley Road, Altrincham, Cheshire, United Kingdom,
WA14 2DT
|
Great, thank you! This is sufficient because the numbering is always such that all cofactors come after protein residues (at least in the models I have seen). Impressive how every time I have an idea for a feature, it already exists in some way. 👍 |
Hello,
I happily use the residue stepper command (
isolde step
or shorthandst
) all the time, it's very convenient. I have two suggestions that could make its use even nicer when using it repeatedly with no arguments to browse through a model:I understand why it's doing both zoom and rotation: to present the next residue with its C-alpha centered and side-chain pointing up. This is useful if you intend to start a simulation and tug on the side-chain.
But sometimes it's helpful to look at a region from a bit further away than a single-residue close-up, while still wanting to step through the region. Or say you simply wanted to browse through a model quickly, then it would be easier on the eyes to simply have a smooth translation from one C-alpha to the next, with no rotation and no change in zoom level (smooth translation between C-alphas would also help when skipping over missing residues; as it is now, I need to zoom out and rotate to understand where the step took me). Then the user could use the mouse to zoom/rotate exactly as they want between steps to follow the main chain in the way that they find most comfortable (been going through many chains lately, and the rotation eventually makes me dizzy 😵💫 ).
Of course, this alternative behavior doesn't need to become the default. It could be optional, as long as there is a way to toggle it easily (so one could switch between browsing and working modes when needed in the same session).
The text was updated successfully, but these errors were encountered: