[Chimera-users] ImportError: No module named Chimera
meng at cgl.ucsf.edu
Wed May 4 10:18:01 PDT 2016
In agreement with Conrad, just a note that there is a similar “MD Movie” per-frame scripting example in the trajectory tutorial, part 1:
The main example is a per-frame script in Chimera commands, but it also links to a python example:
You shouldn’t have to do anything other than run Chimera (no other installation stuff).
On May 4, 2016, at 9:47 AM, Conrad Huang <conrad at cgl.ucsf.edu> wrote:
> Hi, Juan.
> Try using the all lower case module name: "chimera".
> According to Python PEP 235 (https://www.python.org/dev/peps/pep-0235/), imports are case sensitive, even on platforms whose file systems are case insensitive.
> On 5/4/2016 4:04 AM, Eiros Zamora, Juan wrote:
>> I’m running a per-frame script to display the time in a MD movie. I used
>> to run it without problems until I downloaded the new Mac OS X 64-bit
>> 1.11 version. (I erased the old app, also tried to re-download the old
>> version with no success).
>> More specifically, I load the MD movie, and in the command line I
>> write: 2dlabels create timer text "0 ns" color white ypos .9 xpos .9 size 50
>> then I open a per-frame script with the following commands:
>>> from Chimera import runCommand
>>> runCommand("2dlabels change timer text '%.1f ns'" %
>> and get the error:
>>> Problem in per-frame script:
>>> ImportError: No module named Chimera
>> I’ve googled it and found this reply:
>> [Chimera-users] How to install chimera as a python module
>> ** http://www.cgl.ucsf.edu/pipermail/chimera-users/2014-July/010120.html
>> I’ve tried setting the $CHIMERA_PATH environment variable
>> to /Applications/Chimera.app/Contents/Resources/share but I still run
>> into the same problem.
>> Now, I don’t want to run the script directly from the command line, as
>> it’s a per-frame script I have to run after I load the MD movie and
>> create the 2dlabel object.
>> Anything obvious I’m missing here?
More information about the Chimera-users