Opened 23 months ago
Closed 23 months ago
#10260 closed defect (fixed)
move command ignores "atoms" option when frames specified
Reported by: | Owned by: | Tom Goddard | |
---|---|---|---|
Priority: | moderate | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
From: "Caroline Stone (JIC) via ChimeraX-users" <chimerax-users@…>
Subject: [chimerax-users] Independent movement of chains in movie
Date: November 30, 2023 at 4:43:40 AM PST
To: "chimerax-users@…" <chimerax-users@…>
Reply-To: "Caroline Stone (JIC)" <>
Dear ChimeraX team and list subscribers,
I am making a little movie to show a complex of two proteins, but am stuck on individual movements of chain /A and /B.
If I use the move command, chain /A and /B both move independently, away from each other:
move x -10 atoms /A; move x 10 atoms /B
However, if I attempt to do the same movement by going -1 or +1 over a series of 10 frames, I no longer get any movement of /A and /B.
move x -1 10 atoms /A; move x 1 10 atoms /B
I can achieve movement over a number of frames, but both chains move although I tried to specify only /A. I did this based on "move axis [ distance [ frames ]]".
move x -1 10 atoms /A
I feel I might be on the right track because when I use turn, I am able to trigger simultaneous independent rotation of /A and /B around their own axes (thank you for this feature by the way, last time I wondered about this it wasn't possible).
cofr /A; turn y -1 90 atoms /A; cofr /B; turn y 1 90 atoms /B
My ultimate goal is to open the binding interface up a bit like opening a book.
I suppose I could achieve a similar effect by setting the centre of rotation for each chain behind, rather than within - if independent movement over a series of frames isn't possible, I might experiment with that.
I updated to version 1.6 and searched the list, but I still see this behaviour with the move command. Perhaps I am missing something basic?
Thank you for any pointers you might be able to share!
Caroline
Fixed in daily build and 1.7.
The code to pass to do the move at each frame did not pass the atoms argument.