<p dir="ltr">Thanks. I got it.</p>
<div class="gmail_quote">On 06-Feb-2015 9:47 pm, "Elaine Meng" <<a href="mailto:meng@cgl.ucsf.edu">meng@cgl.ucsf.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ankit,<br>
You would just use the “close” Chimera command to close the new axes model each time, e.g. “close #2” if the axes model is #2. You can see which one it is in the Model Panel (under Favorites in the menu). I would expect it to be the next unused number.<br>
<br>
Before actually running a script for a whole trajectory you should generally work out the necessary commands “by hand” (interactively) for one or two frames first.<br>
<br>
I hope this helps,<br>
Elaine<br>
-----<br>
Elaine C. Meng, Ph.D.<br>
UCSF Computer Graphics Lab (Chimera team) and Babbitt Lab<br>
Department of Pharmaceutical Chemistry<br>
University of California, San Francisco<br>
<br>
On Feb 5, 2015, at 8:53 PM, Ankit Agrawal <<a href="mailto:aka895@gmail.com">aka895@gmail.com</a>> wrote:<br>
<br>
> Hi<br>
> I am doing trajectory analysis which has 40000 frames. So for all frames I wanted to calculate the all three inertia axes. That I did. But problem is that when I run the python code it starts making all the three axes for each frames that becomes messy. So I want a little change in my code so that during trajectory analysis it should create axes but should delete or hide the previous axes also. So during run I will see only the axes which are related to that frame.<br>
><br>
> Here is the python code in per-frame analysis.<br>
><br>
> from chimera import runCommand<br>
> frame = mdInfo['frame']<br>
> runCommand("measure inertia #1:0-120 color yellow")<br>
> runCommand("measure inertia #1:120-237 color green")<br>
><br>
> Thanks.<br>
> Ankit<br>
<br>
</blockquote></div>