1,330
edits
Coot: Difference between revisions
Jump to navigation
Jump to search
→Installing Coot on Windows
| (62 intermediate revisions by 13 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. | ||
There is a [http:// | There is a [http://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/ homepage] with extensive [http://www2.mrc-lmb.cam.ac.uk/Personal/pemsley/coot/web/docs/ documentation]. The program may there be [http://www2.mrc-lmb.cam.ac.uk/Personal/pemsley/coot/binaries/release downloaded] for Linux and Windows. There's also Paul Emsley's [https://pemsley.github.io/coot/ coot blog]. The license of Coot is GNU GPL. | ||
=Installing Coot= | =Installing Coot= | ||
==Installing Coot on OS X== | ==Installing Coot on OS X== | ||
OS X install packages for nightly builds that work on 10.8.X and 10.9.X are available here: [http://scottlab.ucsc.edu/~wgscott/xtal/wiki/index.php/Stand-Alone_Coot Coot OS X package installers] | |||
Please refer to the [http://sage.ucsc.edu/xtal/wiki/index.php/Installing_Coot_on_OS_X Installing Coot on OS X] page | Please refer to the [http://sage.ucsc.edu/xtal/wiki/index.php/Installing_Coot_on_OS_X Installing Coot on OS X] page | ||
==Installing Coot on Windows== | ==Installing Coot on Windows== | ||
Please refer to | Please refer to [http://bernhardcl.github.io/coot/ Bernhard Lohkamp's WinCoot download] page. Or check manually on | ||
[https://github.com/bernhardcl/coot/releases GitHub]. | |||
==Installing Coot on Linux== | ==Installing Coot on Linux== | ||
| Line 16: | Line 20: | ||
=== Installation from a distributed binary tarball package === | === Installation from a distributed binary tarball package === | ||
This is the recommended way for those who do not want to delve into the mysteries of compiling and linking a great but complex piece of software. Read the | This is the recommended way for those who do not want to delve into the mysteries of compiling and linking a great but complex piece of software. Read the [https://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/ Coot documentation] to find out about the details. | ||
In short, just go to | In short, just go to https://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/binaries/release/ and pick a suitable binary, e.g. | ||
coot-0. | coot-0.9.4.1-binary-Linux-x86_64-scientific-linux-7.6-python-gtk2.tar.gz for a Red Hat Enterprise Linux 7 (or CentOS-7) or newer system. | ||
Then un-tar it under /usr/local/src (or in your $HOME), and establish a symlink (ln -s) between /usr/local/bin/coot and the bin/coot of the freshly unpacked distribution. | Then un-tar it under /usr/local/src (or in your $HOME), and establish a symlink (ln -s) between /usr/local/bin/coot and the bin/coot of the freshly unpacked distribution. | ||
| Line 27: | Line 31: | ||
and install the library, again using yum (assuming yum is available in your distribution, otherwise use apt or whatever is there for this purpose). | and install the library, again using yum (assuming yum is available in your distribution, otherwise use apt or whatever is there for this purpose). | ||
=== | ==== Example: installing a 64bit nightly CentOS5 binary build on 64bit SL6.1 ==== | ||
As | 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 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]# LD_LIBRARY_PATH=lib ldd bin/coot-real | grep found | |||
libssl.so.6 => not found | |||
libcrypto.so.6 => not found | |||
libssl.so.6 => not found | |||
libcrypto.so.6 => not found | |||
So only two libraries are missing! Either they can be installed using yum, or they are already available, but have a higher version. | |||
* First possibility: find out about installable RPM packages (preferred way): | |||
[root@localhost src]# yum provides libssl.so.6 libcrypto.so.6 | |||
Loaded plugins: refresh-packagekit | |||
openssl098e-0.9.8e-17.el6.i686 : A compatibility version of a general | |||
: cryptography and TLS library | |||
Repo : sl | |||
Matched from: | |||
Other : libssl.so.6 | |||
... (the package is repeated, and libcrypto.so.6 is also mentioned) | |||
: Now don't just install the openssl098e-0.9.8e-17.el6.i686 and its dependencies - it is a 32bit library (the name ends with ".i686")! Installing it does not solve the problem - we need a 64bit library. Unfortunately "yum provides" does not tell us about the 64bit library (is that a yum bug?). By specifying just the package name (openssl098e.x86_64 would also work, and would avoid any 32bit package) | |||
yum install openssl098e | |||
: we install both libssl.so.6 and libcrypto.so.6 in their 64bit versions - done! | |||
* Second possibility: find out if the system already has a higher version of the two libraries: | |||
[root@localhost locate libssl.so | |||
/usr/lib64/.libssl.so.1.0.0.hmac | |||
/usr/lib64/.libssl.so.10.hmac | |||
/usr/lib64/libssl.so | |||
/usr/lib64/libssl.so.1.0.0 | |||
/usr/lib64/libssl.so.10 | |||
: So the answer is: there is /usr/lib64/libssl.so which is at version 10, which is compatible with the version we need (6). For libcrypto.so the same is true. So just | |||
cd coot-Linux-x86_64-centos-5-gtk2-python/lib/ | |||
ln -s /usr/lib64/libssl.so libssl.so.6 | |||
ln -s /usr/lib64/libcrypto.so libcrypto.so.6 | |||
: The way these symlinks are made they would even work if RHEL upgrades libssl or libcrypto to higher versions. Works for me. | |||
Final step (this does not need to be repeated for a new coot version): create /usr/local/bin/coot with | |||
#!/bin/csh -f | |||
setenv LANG C | |||
exec /usr/local/src/coot-Linux-x86_64-centos-5-gtk2-python/bin/coot $* | |||
and make it executable with | |||
chmod a+x /usr/local/bin/coot | |||
=== Installation from source code via autobuild scripts === | === Installation from source code via autobuild scripts === | ||
Go to https://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/build-install-coot-from-scratch.html | |||
=Running Coot= | =Running Coot= | ||
| Line 72: | Line 87: | ||
===Controls=== | ===Controls=== | ||
[[Image:Coot-controls-small.png | [[Image:Coot-controls-small.png]] | ||
| Line 88: | Line 103: | ||
Similarly, hardware stereo can be invoked (assuming you have the CRT, correct graphics card, emitter, etc) using the same menu item, by selecting "Hardware Stereo". | Similarly, hardware stereo can be invoked (assuming you have the CRT, correct graphics card, emitter, etc) using the same menu item, by selecting "Hardware Stereo". | ||
[[Image:a_zalman_zm_m220w__2d_35_pic.jpg|150px|thumb|right|3d lcd]] | |||
Control stereo separation / depth in coot 0.9: the transformation between the eyes is no longer a rotation and is now a shear. Which means that now we don't get part of the map showing up in the left eye but not the right (or vice versa). | |||
This is documented in Section 3.4.1, e.g. | |||
set_hardware_stereo_angle_factor(0.5) # for the Python fans | |||
Hardware stereo failure: try the line | |||
(set-display-lists-for-maps 0) | |||
in ~/.coot for coot 0.9 - see https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind2002&L=COOT&P=R312 and https://www.jiscmail.ac.uk/cgi-bin/wa-jisc.exe?A2=COOT;49fa8d15.2006 | |||
==== Zalman Stereo ==== | ==== Zalman Stereo ==== | ||
| Line 95: | Line 123: | ||
The attributes for this monitor have been tested and [http://pymol.org/zalman/ described rather extensively by Warren DeLano] on the PyMOL site. Please read it for important details and suggested purchasing sources. | The attributes for this monitor have been tested and [http://pymol.org/zalman/ described rather extensively by Warren DeLano] on the PyMOL site. Please read it for important details and suggested purchasing sources. | ||
[[ | The [[coot zalman]] page describes specifically how to get this to work with coot on Mac OS X, but the instructions should be generalizable to linux and Windoze. | ||
Note that the stereo effect is very sensitive to the vertical position of your eyes relative to the screen: if you don't see stereo, try tilting the screen. | |||
=== Stereo: left/right (and front/back) interchanged? === | |||
Establish an additional toolbutton "swap stereo": | |||
Main Toolbar -> right mouse click-> Manage buttons-> select Swap Stereo | |||
Or for the script minded: | |||
switch_stereo_sides() | |||
This will toggle the stereo images left and right. | |||
===External Links=== | ===External Links=== | ||
====[ | ====[https://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html On-line User Manual]==== | ||
====[ | ====[https://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/ Coot's home page]==== | ||
====[http://www.mail-archive.com/coot@jiscmail.ac.uk/ Current mailing list archives]==== | ====[http://www.mail-archive.com/coot@jiscmail.ac.uk/ Current mailing list archives]==== | ||
==Scheme Scripts== | ==Scheme Scripts== | ||
| Line 173: | Line 209: | ||
The Powermate dial can be used with coot. One could just assign the rotations to +/-y keys and be done with it, but this script gives you a way of having positive and negative rotations in all three cartesian directions. The F1 key is mapped to positive rotation, the F2 key to negative rotation, and the F3 key permits you to toggle through x, y, and z, on successive key presses. I then map F1 and F2 into the ordinary rotations on the powermate (using send key equivalents) and then I map F3 into the single click on the dial, making it easy to toggle through x, y and z. The press-and-rotate options remain available; I map these into scroll up and down, and put them on the slowest response setting, which makes contouring density easier to control than it is from my mouse scroll wheel. | The Powermate dial can be used with coot. One could just assign the rotations to +/-y keys and be done with it, but this script gives you a way of having positive and negative rotations in all three cartesian directions. The F1 key is mapped to positive rotation, the F2 key to negative rotation, and the F3 key permits you to toggle through x, y, and z, on successive key presses. I then map F1 and F2 into the ordinary rotations on the powermate (using send key equivalents) and then I map F3 into the single click on the dial, making it easy to toggle through x, y and z. The press-and-rotate options remain available; I map these into scroll up and down, and put them on the slowest response setting, which makes contouring density easier to control than it is from my mouse scroll wheel. | ||
[ | [http://code.google.com/p/zsh-templates-osx/source/browse/trunk/Library/init/zsh/zshrc.d/local-functions/etc/dotfiles/cootrc_powermate_and_keybindings.scm powermate-coot.scm] | ||
===Example Scheme Script 7: Applying arbitrary value to "B" factor column === | ===Example Scheme Script 7: Applying arbitrary value to "B" factor column === | ||
| Line 257: | Line 293: | ||
For (re-)colouring maps blue: | For (re-)colouring maps blue: | ||
[[blueify_map_keys.py]] | |||
To (re-)colour coordinate molecules yellow: | |||
To ( | [[yellowify_molecule_keys.py]] | ||
===Example 3: NCS Rotamer differences=== | |||
To show NCS where NCS-related side-chains have different rotamers: | |||
[[ncs_rotamer_differences.py]] | |||
===Example 4: Morphing GUI=== | |||
GUI to easily access jiggle fit and morphing (currently pre-release Coot required, may be moved into trunk): | |||
[[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]] | |||
===Example 6: some basic scripting=== | |||
Q: I want to prepare scripts to run coot functions like water picking or rotamer fitting in command line. Therefore I am looking for some examples of simple coot scripts, e.g. load ref.pdb, load ref.mtz, fft create map. | |||
Answer: | |||
<pre> | |||
imol = read_pdb("6vw1.pdb") | |||
imol_map = make_and_draw_map("6vw1/6vw1_refine.mtz", "2FOFCWT", "PH2FOFCWT", "", 0, 0) | |||
find_waters(imol_map, imol, 0, 1.4, 1) | |||
</pre> | |||
==Python to Scheme and return== | ==Python to Scheme and return== | ||
| Line 311: | Line 339: | ||
Here some simple rules how to translate from Scheme to Python. To translate the other way around, i.e. Python to Scheme, just turn the rules around: | Here some simple rules how to translate from Scheme to Python. To translate the other way around, i.e. Python to Scheme, just turn the rules around: | ||
# | # Replace all '-' with '_' (except in equation when you need arithmetic '-' minus signs) | ||
# | # Move the brackets around the argument(s) | ||
# | # Separate multiple arguments by commas rather than spaces | ||
# | # Replace 'define' with 'def' for functions and with '=' for assignments | ||
# Make sure to use indentation for the function content [Python is indentation sensitive] and a ':' after the function definition. | # Make sure to use indentation for the function content [Python is indentation sensitive] and a ':' after the function definition. | ||
| Line 348: | Line 376: | ||
run_scheme_command("(scheme-command arg1 arg2 ...)") [from python] | run_scheme_command("(scheme-command arg1 arg2 ...)") [from python] | ||
= | =Assorted questions and answers (from the mailinglist)= | ||
It should be noted that the answers ("A") are from Paul Emsley himself (and were maybe slightly edited). | |||
== | ==Coot development== | ||
Q: How can I get involved with Coot development? | |||
A: Join the [[Coot Janitors]] project. This is a project to get new people involved in improving Coot, by acting as a clearing house for simple tasks which need doing, and providing documentation for doing them. | |||
== Get rid of the "fix nomenclature" check == | |||
Q: Is it possible to deactivate the nomenclature errors check? Sometimes this check is not very useful and it becomes rather annoying when one has several molecules loaded only wants to look at the structures... | |||
A: The [https://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#set_002dnomenclature_002derrors_002don_002dread Coot manual] should help: Add to your startup script ~/.coot : | |||
(set-nomenclature-errors-on-read "ignore") | |||
In case you are using the python file ~/.coot.py , use | |||
set_nomenclature_errors_on_read("ignore") | |||
On Windows, this line should go into X:\YourWinCootDirectory\.coot-preferences\coot.py . | |||
Alternatively put ".coot.py" in X:\YourWinCootDirectory. | |||
Alternatively | |||
==NCS edits== | ==NCS edits== | ||
| Line 403: | Line 424: | ||
A: Yes this fails. Hydrogens are named differently to SHELX hydrogens. In principal this could be made to work if the dictionary was reworked to use SHELX hydrogen names. This would also fix the chi angles problem too of course. | A: Yes this fails. Hydrogens are named differently to SHELX hydrogens. In principal this could be made to work if the dictionary was reworked to use SHELX hydrogen names. This would also fix the chi angles problem too of course. | ||
Specific Q3: I am unable to open the output pdb file from ShelXL in Coot. | |||
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 456: | Line 485: | ||
(apply density-at-point (imol-refinement-map) (rotation-centre)) | (apply density-at-point (imol-refinement-map) (rotation-centre)) | ||
There is no user access to the peak integration code of coot as yet. | There is no user access to the peak integration code of coot as yet. | ||
==Disulfide bond across crystallographic axis== | |||
Q: I have a pair of disulfide bonds which link two monomers in separate asymmetric units. There is a single monomer in the asymmetric unit, and two monomers come together to form disulfides between Cys 26-Cys45, and Cys45-Cys26. When I real-space-refine these residues, they do not form a nice disulfide, and Coot does not seem to recognize them as a disulfide. | |||
A: For the record, you can't refine symmetry-related disulfides in Coot (as of Nov 3, 2009). | |||
==Macros in COOT== | |||
Q: How to use macros in COOT? Do they need to be written in Python or another language that I had not heard of before? Where can I find a low level description of how to write macros with some examples (I know nothing about Python, except that it is fashionable)? | |||
A: The other language is a form of Lisp, called [http://en.wikipedia.org/wiki/Scheme_(programming_language) Scheme]. You can learn about programming python in many ways of course (not least the [http://docs.python.org/tutorial/ python tutorial], which is what I read first). The coot python extensions are described in the documentation. There is a standard trivial formatting change that has to be made to get the syntax right for python, see "Python Scripting" [[http://www.ysbl.york.ac.uk/~lohkamp/coot/wincoot-faq.html|here]]. There is a growing collection of coot scripts in this Wiki article. | |||
== building loops == | |||
Q: Is there any similar function in COOT as lego_auto_mainchain command in O program? | |||
A: there are 2 loop fitting tools in Coot | |||
# 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://www2.mrc-lmb.cam.ac.uk/personal/pemsley/coot/web/docs/coot.html#protein_002ddb_002dloops] Extensions -> Modelling -> DB Loop... | |||
==LSQ superpositions== | |||
Q: Do an LSQ superposition using specified residues in multiple chains (superposing one oligomer on another). | |||
A: Something like this then? | |||
clear_lsq_matches() | |||
# specs for reference then moving | |||
add_lsq_match(20, 90, "A", 20, 90, "A", 1) | |||
add_lsq_match(20, 90, "B", 20, 90, "B", 1) | |||
add_lsq_match(15, 75, "D", 15, 75, "D", 1) | |||
apply_lsq_matches(1, 2) | |||
which presumes that the reference molecule is in 1 and the moving molecule 2. | |||
Q: How to do a LSQ superposition of a homologous structure onto my working structure using ± N residues about the current position, where N is a variable (not essential, could be fixed) and the current position is the last residue that I clicked on. | |||
A: That is more involved - and more useful because it can be dynamic. Something like the following perhaps (in Scheme, just for amusement (not tested)). You will need to set imol-ref, perhaps by reading in the reference pdb, as demonstrated below. The function is bound to Shift-Y. | |||
(define dynamic-lsq-range-extent 2) ;; ± 2 residues either side of centre residue | |||
(define imol-ref (read-pdb "reference.pdb")) | |||
;; convert between the input reference chain id and the chain id of | |||
;; the moving molecule that corresponds to that chain | |||
;; | |||
(define (mov-match-chain ref-chain-id) | |||
ref-chain-id) | |||
(define (dynamic-lsq-match) | |||
;; get the current residue and use that to make residue ranges for | |||
;; an LSQ fit | |||
;; | |||
(using-active-atom | |||
(clear-lsq-matches) | |||
(add-lsq-match (- aa-res-no dynamic-lsq-range-extent) | |||
(+ aa-res-no dynamic-lsq-range-extent) | |||
aa-chain-id | |||
(- aa-res-no dynamic-lsq-range-extent) | |||
(+ aa-res-no dynamic-lsq-range-extent) | |||
(mov-match-chain aa-chain-id) | |||
1) | |||
(apply-lsq-matches aa-imol imol-ref))) | |||
(add-key-binding "Dynamic LSQ overlay" "Y" dynamic-lsq-match) | |||
== reading MTZ file with experimental PHI and FOM using --auto == | |||
Q: There is the --auto <filename> commandline option for auto-reading mtz files (mtz file has the default labels FWT, PHWT). Can this be made to work with a SHELXE .phs output file after converting with convert2mtz ? - the resulting MTZ file has labels F PHI FOM. | |||
A: use: coot --python -c 'make_and_draw_map("sad.mtz", "F", "PHI", "FOM", "/HKL_base/HKL_base/FOM",1, 0)' | |||
== NCS Rotamer differences == | |||
Show me where NCS-related side-chains have different rotamers | |||
(define (compare-ncs-rotamer imol chain-A chain-B) | |||
(let ((n-residues (chain-n-residues chain-A imol)) | |||
(mismatched-rotamers '())) | |||
(for-each | |||
(lambda (serial-number) | |||
(let ((res-name-A (resname-from-serial-number imol chain-A serial-number)) | |||
(res-no-A (seqnum-from-serial-number imol chain-A serial-number)) | |||
(ins-code-A (insertion-code-from-serial-number imol chain-A serial-number)) | |||
(res-name-B (resname-from-serial-number imol chain-A serial-number)) | |||
(res-no-B (seqnum-from-serial-number imol chain-A serial-number)) | |||
(ins-code-B (insertion-code-from-serial-number imol chain-A serial-number))) | |||
(if (not (= res-no-A res-no-B)) | |||
(begin | |||
(format #t "sequence number for ~s do not match~%" res-no-A)) | |||
(if (not (string=? res-name-A res-name-B)) | |||
(begin | |||
(format #t "residue names for ~s do not match~%" res-no-A)) | |||
(let ((rot-name-A (get-rotamer-name imol chain-A res-no-A ins-code-A)) | |||
(rot-name-B (get-rotamer-name imol chain-B res-no-B ins-code-B))) | |||
(if (not (string=? rot-name-A rot-name-B)) | |||
(begin | |||
(set! mismatched-rotamers | |||
(cons (list imol chain-A res-no-A ins-code-A | |||
res-name-A | |||
(if (string=? rot-name-A "") "-" rot-name-A) | |||
(if (string=? rot-name-B "") "-" rot-name-B)) | |||
mismatched-rotamers)))) | |||
))))) | |||
(range n-residues)) | |||
(dialog-box-of-buttons "Mismatched Rotamers" | |||
(cons 300 300) | |||
(map (lambda(rotamer) | |||
(let ((label (string-append " " | |||
(list-ref rotamer 1) | |||
" " | |||
(number->string (list-ref rotamer 2)) | |||
(list-ref rotamer 3) | |||
" " | |||
(list-ref rotamer 4) ;; res-name | |||
": " | |||
(list-ref rotamer 5) | |||
" vs. " | |||
(list-ref rotamer 6))) | |||
(thunk (lambda () | |||
(set-go-to-atom-molecule imol) | |||
(set-go-to-atom-chain-residue-atom-name | |||
(list-ref rotamer 1) | |||
(list-ref rotamer 2) " CA ")))) | |||
(list label thunk))) | |||
mismatched-rotamers) | |||
" Close "))) | |||
And one would use this something like: | |||
;; example usage: | |||
(let ((imol (read-pdb "test.pdb"))) | |||
(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. | |||
== specify Coot download directory, like specifying backup dir by COOT_BACKUP_DIR? == | |||
here is my working startup.py (of course replace src folder with your preferred location): | |||
import os | |||
try: | |||
os.symlink('/ccp4/xray/tmp/', 'coot-download') | |||
except: | |||
pass | |||
(Eugene Osipov on 22/04/2020) | |||
== how to enable the interactive dots during RS refinement and the Ramachandran polyeders? == | |||
(asked by Clemens Grimm on 08/10/2020 ) | |||
A: | |||
set_show_intermediate_atoms_rota_markup(1) | |||
set_show_intermediate_atoms_rama_markup(1) | |||
set_do_coot_probe_dots_during_refine(1) | |||
=See also= | |||
[https://www.youtube.com/watch?v=Xhonm4K1y0c This video] is one of what will be a series of videos showcasing Coot 1 - and this one starts at the beginning. | |||