Re: [phenixbb] Molecule and maps will not load into coot from Phenix 1.7.1-743
Dear Nat,
Any progress in this matter. To add, do you have any version of Phenix
which is working perfectly (the communication of Phenix with pymol and
coot) in ubuntu system in you lab?
Jobi
On Tue, Nov 1, 2011 at 5:08 PM, Jobichen Chacko
Dear Nat, Just to add when I try open the files in pymol, it doesnot open up and show this output.
/usr/local/phenix-1.7.1-743/build/intel-linux-2.6-x86_64/base/bin/python2.7: No module named pymol
Jobi
On Tue, Nov 1, 2011 at 10:58 AM, Jobichen Chacko
wrote: Dear Nat, I installed the the coot version you sent to me. Still not working. jobi
On Tue, Nov 1, 2011 at 10:43 AM, Nathaniel Echols
wrote: On Mon, Oct 31, 2011 at 7:34 PM, Jobichen Chacko
wrote: Dear Nat, Thank you for your help. Please see the attached output after running coot_test.py I will also try to install the coot version you send to me. Jobi ... 'import site' failed; use -v for traceback
Wow, that's way more broken than I was expecting. I think this means a library conflict, but I've only come across this error on Mac. Can you try one more thing?
export PYTHONVERBOSE=1 coot --script coot_test.py
(If you're using csh or tcsh as your shell, the first line should be "setenv PYTHONVERBOSE 1" instead.)
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
On Thu, Nov 3, 2011 at 12:10 AM, Jobichen Chacko
Any progress in this matter. To add, do you have any version of Phenix which is working perfectly (the communication of Phenix with pymol and coot) in ubuntu system in you lab?
Sorry, I'm completely stumped. It's working perfectly on my computer - if the same Coot build is not working elsewhere, I think the problem is something specific to the way your OS is set up. All I can tell for sure is that the interaction with all of the Python modules is completely corrupted. It's extremely difficult to debug this kind of problem without direct access to the computer in question, but I'll do a little more digging when I get to lab and see if there are some other things you can check. As a start, find the file in the Coot installation named "coot-real" and run this command: ldd coot-real and send me the output (off-list, probably). -Nat
participants (2)
-
Jobichen Chacko
-
Nathaniel Echols