47
edits
Coot: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| (9 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
[[Image:Coot-with-ATP-vector.png| | [[Image:Coot-with-ATP-vector.png|25%|thumb|right]] | ||
Coot is a graphics program for building, refining and analysing macromolecular models obtained with crystallographic procedures. | Coot is a graphics program for building, refining and analysing macromolecular models obtained with crystallographic procedures. | ||
| Line 32: | Line 32: | ||
==== Example: installing a 64bit nightly CentOS5 binary build on 64bit SL6.1 ==== | ==== Example: installing a 64bit nightly CentOS5 binary build on 64bit SL6.1 ==== | ||
First of all, SL (Scientific Linux) is a derivative of RHEL, as is CentOS. So all three OSs behave exactly the same. | First of all, SL (Scientific Linux) is a derivative of RHEL, as is CentOS. So all three OSs behave exactly the same. | ||
The binaries with "x86_64" binaries are for 64bit systems; the "i386" binaries are for 32bit systems. Since my notebook is 64bits ("uname -a" reports "x86_64" more than once), I download | The binaries with "x86_64" binaries are for 64bit systems; the "i386" binaries are for 32bit systems. Since my notebook is 64bits ("uname -a" reports "x86_64" more than once), I download coot-0.7-pre-1-revision-3999-binary-Linux-x86_64-centos-5-python-gtk2.tar.gz. As root, I "cd /usr/local/src" and un-tar. Next, have to find out which libraries are missing. This can be achieved by (''note the use of LD_LIBRARY_PATH in the second command - do not permanently modify LD_LIBRARY_PATH !''): | ||
[root@localhost]# cd coot-Linux-x86_64-centos-5-gtk2-python | [root@localhost]# cd coot-Linux-x86_64-centos-5-gtk2-python | ||
[root@localhost]# LD_LIBRARY_PATH=lib ldd bin/coot-real | grep found | [root@localhost]# LD_LIBRARY_PATH=lib ldd bin/coot-real | grep found | ||
| Line 75: | Line 75: | ||
and make it executable with | and make it executable with | ||
chmod a+x /usr/local/bin/coot | chmod a+x /usr/local/bin/coot | ||
=== Installation from source code via autobuild scripts === | === Installation from source code via autobuild scripts === | ||
| Line 148: | Line 108: | ||
===Controls=== | ===Controls=== | ||
[[Image:Coot-controls-small.png | [[Image:Coot-controls-small.png]] | ||
| Line 364: | Line 324: | ||
[[morph_residues_gui.py]] | [[morph_residues_gui.py]] | ||
===Example 5: Ensemble GUI=== | |||
GUI to allow navigation through structural ensembles as obtained e.g. from ensemble refinement: | |||
[[ensemble_plugin.py]] | |||
==Python to Scheme and return== | ==Python to Scheme and return== | ||
| Line 483: | Line 449: | ||
A: Well, it's hard to know what's the problem without details - the console should say something. But when handling the output of shelxl, I suggest you read the .res file rather than the pdb, then the subsequent .ins file contains lots of "header" information. | A: Well, it's hard to know what's the problem without details - the console should say something. But when handling the output of shelxl, I suggest you read the .res file rather than the pdb, then the subsequent .ins file contains lots of "header" information. | ||
Another answer to questions 1+2 is to rename the hydrogen atoms in the shelxl res-file to match the mmCIF dictionaries used by Coot. This only needs to be done once as shelxl does not modify these names. Except for a few manual editions, the renaming can be done semi-automatically using regular expressions (replacing A->1, B->2, etc). | |||
Concerning question 3, the Coot -> Extensions -> Module -> SHELXL menu entry works really well now. It reads in all relevant shelxl files and provides a menu highlighting the problematic areas in the model. | |||
==Image quality on NVidia cards== | ==Image quality on NVidia cards== | ||
| Line 554: | Line 524: | ||
A: there are 2 loop fitting tools in Coot | A: there are 2 loop fitting tools in Coot | ||
# C alpha -> Mainchain [http://lmb. | # C alpha -> Mainchain [http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#C_002dalpha-_002d_003e-Mainchain],[http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#Building-Links-and-Loops] | ||
# DB Loop: (No good documentation) [http://lmb. | # DB Loop: (No good documentation) [http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#protein_002ddb_002dloops] Extensions -> Modelling -> DB Loop... | ||
==LSQ superpositions== | ==LSQ superpositions== | ||
| Line 676: | Line 646: | ||
(let ((imol (read-pdb "test.pdb"))) | (let ((imol (read-pdb "test.pdb"))) | ||
(compare-ncs-rotamer imol "A" "B")) | (compare-ncs-rotamer imol "A" "B")) | ||
== make RSR in coot 0.8.1 behave like in earlier versions == | |||
Q: We've noticed a new behavior in real space refinement in coot 0.8.1 whereby dragged atoms are more tightly restrained to their initial positions than in earlier versions. This seems to be described in the release notes by: | |||
o BUG-FIX: The amount that the other atoms ove with moving the picked atom has been reduced (but is configurable) | |||
A: Add e.g. this to your ~/.coot.py file: | |||
set_refinement_drag_elasticity(0.8) | |||
Q: I'm wondering why this was changed. Does the optimum elasticity change with resolution, map quality, or another experimental limitation? Or does it more of a user preference? | |||
A: Because of cis-peptides. My worry was that in the previous regime, it was | |||
too easy to introduce cis-peptides when fitting to low resolution maps. | |||
I believe the current default setting is much less likely to do that. | |||
Q: I've tried various settings of refinement_drag_elasticity and I need to lower it to 0.5 or so before any semblance of earlier behavior appears. | |||
A: It used to be 0.167, I think. | |||
== Molprobity not active in COOT == | |||
Q: I am using COOT 0.8.1 EL that comes with the CCP4 6.5.010 on my Mac OS X 10.10.2. I wanted to run molprobity but the Validate > Probe clashes button in my pull down menu is not active. Is this function available in this COOT version? | |||
A: Reduce and probe are separate programs available from the Richardson’s lab at Duke http://kinemage.biochem.duke.edu/. Download and install on your box. Then coot needs to be told in some instances where it can find these executables. I have the following lines in my ~/.coot file in Linux. | |||
<pre> | |||
;; .coot | |||
;; This file is required. As of coot 0.8pre no other mechanism for | |||
;; enabling probe in coot works | |||
;; | |||
;; This is full pathname of molprobity's probe program | |||
(define *probe-command* "/apps/xray/bin/probe") | |||
;; This is full pathname of molprobity's reduce program | |||
(define *reduce-command* "/apps/xray/bin/reduce") | |||
</pre> | |||
Untried: if you have Phenix installed: it comes with phenix.probe and phenix.reduce - you could insert the paths to these binaries into the above definitions. | |||
== some symmetry mates not shown == | |||
Q: This structure has been solved and refined using phenix in the hexagonal setting of space group R 3. There is one copy per asymmetric unit in R 3. As you can see from the attached image, coot is rendering some but not all of the symmetry mates. | |||
A: Turn up the radius a bit and use (set-symmetry-shift-search-size 3) . I would have thought that 2 is big enough, but maybe not in this case. | |||