<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://biomolmd.org/mw/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Admin</id>
	<title>biowiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://biomolmd.org/mw/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Admin"/>
	<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php/Special:Contributions/Admin"/>
	<updated>2026-11-16T02:10:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2161</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2161"/>
		<updated>2026-02-12T17:33:41Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Latest tool for system set up for Tinker and AMOEBA */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebabio18.prm &lt;br /&gt;
                                      &#039;&#039;# use the latest prm from GitHub&#039;&#039;&lt;br /&gt;
 # verbose                            &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 integrator            respa          &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 a-axis                62.23          &#039;&#039;# add b and c-axis if not cubic&#039;&#039;&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 neighbor-list                &#039;&#039;# this below requires your box is twice the cutoff plus 2 or 3 Ang.&#039;&#039;&lt;br /&gt;
                              &#039;&#039;#&#039;&#039; &#039;&#039;If your box is too small for vdw but OK for Ewald, you can&#039;&#039; &#039;&#039;use &amp;quot;mpole-list&amp;quot;&#039;&#039;&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0    &#039;&#039;# small cutoff because dipole/quadrupole die off &amp;gt; charge.&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 polar-eps             0.01    &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 &lt;br /&gt;
 #polarization         OPT3    &#039;&#039;#For improving polarization. OPT4 is more accurate but OPT3 is faster&#039;&#039;&lt;br /&gt;
 #openmp-threads       16      &#039;&#039;# CPU only. how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN              #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be &#039;&#039;                                                                      &lt;br /&gt;
                              #&#039;&#039;Kinetics will  be affected            &#039;&#039;&lt;br /&gt;
                                                &lt;br /&gt;
 # pme-grid  64 64 64       &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 &lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files =&lt;br /&gt;
&lt;br /&gt;
== CHARMM-GUI ==&lt;br /&gt;
charmm-gui can now output simulation files in Tinker format, but only fixed-charge force fields for now.&lt;br /&gt;
&lt;br /&gt;
== Latest tool for system set up for Tinker and AMOEBA ==&lt;br /&gt;
https://github.com/prenlab/Tinker-GUI&lt;br /&gt;
&lt;br /&gt;
Tools developed by Dr. Chengwen Liu for complex systems such as protein-membrane system: https://github.com/leucinw/TIPTOP&lt;br /&gt;
&lt;br /&gt;
Once built, before running production, see below [[#Check your xyz/key files and common errors]]&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check. The CPU version &amp;quot;analyze&amp;quot; has many more options.&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key eL&amp;quot; &lt;br /&gt;
  will print out large interactions, for example large ele or vdw interactions of two atoms that are too close&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2160</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2160"/>
		<updated>2026-02-12T17:27:29Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Check your xyz/key files and common errors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebabio18.prm &lt;br /&gt;
                                      &#039;&#039;# use the latest prm from GitHub&#039;&#039;&lt;br /&gt;
 # verbose                            &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 integrator            respa          &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 a-axis                62.23          &#039;&#039;# add b and c-axis if not cubic&#039;&#039;&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 neighbor-list                &#039;&#039;# this below requires your box is twice the cutoff plus 2 or 3 Ang.&#039;&#039;&lt;br /&gt;
                              &#039;&#039;#&#039;&#039; &#039;&#039;If your box is too small for vdw but OK for Ewald, you can&#039;&#039; &#039;&#039;use &amp;quot;mpole-list&amp;quot;&#039;&#039;&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0    &#039;&#039;# small cutoff because dipole/quadrupole die off &amp;gt; charge.&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 polar-eps             0.01    &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 &lt;br /&gt;
 #polarization         OPT3    &#039;&#039;#For improving polarization. OPT4 is more accurate but OPT3 is faster&#039;&#039;&lt;br /&gt;
 #openmp-threads       16      &#039;&#039;# CPU only. how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN              #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be &#039;&#039;                                                                      &lt;br /&gt;
                              #&#039;&#039;Kinetics will  be affected            &#039;&#039;&lt;br /&gt;
                                                &lt;br /&gt;
 # pme-grid  64 64 64       &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 &lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files =&lt;br /&gt;
&lt;br /&gt;
== CHARMM-GUI ==&lt;br /&gt;
charmm-gui can now output simulation files in Tinker format, but only fixed-charge force fields for now.&lt;br /&gt;
&lt;br /&gt;
== Latest tool for system set up for Tinker and AMOEBA ==&lt;br /&gt;
https://github.com/prenlab/Tinker-GUI&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check. The CPU version &amp;quot;analyze&amp;quot; has many more options.&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key eL&amp;quot; &lt;br /&gt;
  will print out large interactions, for example large ele or vdw interactions of two atoms that are too close&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2159</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2159"/>
		<updated>2026-02-05T20:44:48Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* *.key file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebabio18.prm &lt;br /&gt;
                                      &#039;&#039;# use the latest prm from GitHub&#039;&#039;&lt;br /&gt;
 # verbose                            &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 integrator            respa          &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 a-axis                62.23          &#039;&#039;# add b and c-axis if not cubic&#039;&#039;&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 neighbor-list                &#039;&#039;# this below requires your box is twice the cutoff plus 2 or 3 Ang.&#039;&#039;&lt;br /&gt;
                              &#039;&#039;#&#039;&#039; &#039;&#039;If your box is too small for vdw but OK for Ewald, you can&#039;&#039; &#039;&#039;use &amp;quot;mpole-list&amp;quot;&#039;&#039;&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0    &#039;&#039;# small cutoff because dipole/quadrupole die off &amp;gt; charge.&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 polar-eps             0.01    &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 &lt;br /&gt;
 #polarization         OPT3    &#039;&#039;#For improving polarization. OPT4 is more accurate but OPT3 is faster&#039;&#039;&lt;br /&gt;
 #openmp-threads       16      &#039;&#039;# CPU only. how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN              #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be &#039;&#039;                                                                      &lt;br /&gt;
                              #&#039;&#039;Kinetics will  be affected            &#039;&#039;&lt;br /&gt;
                                                &lt;br /&gt;
 # pme-grid  64 64 64       &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 &lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files =&lt;br /&gt;
&lt;br /&gt;
== CHARMM-GUI ==&lt;br /&gt;
charmm-gui can now output simulation files in Tinker format, but only fixed-charge force fields for now.&lt;br /&gt;
&lt;br /&gt;
== Latest tool for system set up for Tinker and AMOEBA ==&lt;br /&gt;
https://github.com/prenlab/Tinker-GUI&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2158</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2158"/>
		<updated>2026-02-05T20:41:02Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* *.key file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebabio18.prm&lt;br /&gt;
 # &lt;br /&gt;
 # use the latest prm from GitHub&lt;br /&gt;
 &lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 a-axis                62.23 # add b and c if not cubic&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
    &#039;&#039;&lt;br /&gt;
 neighbor-list                # this below requires your box is twice the cutoff plus 2 or 3 Ang.&#039;&#039;&lt;br /&gt;
                              # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can&#039;&#039;         &lt;br /&gt;
                                              &#039;&#039;use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# small cutoff because dipole/quadrupole die off &amp;gt; charge.&#039;&#039;&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #polarization OPT3                         #OPT4 is more accurate but OPT3 is faster&lt;br /&gt;
 polar-eps             0.01    &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 &lt;br /&gt;
 #openmp-threads    16          &#039;&#039;# CPU only. how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #HEAVY-HYDROGEN              #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be &#039;&#039;                                                                      &lt;br /&gt;
                              #&#039;&#039;Kinetics will  be affected            &lt;br /&gt;
                                                &lt;br /&gt;
 # pme-grid  64 64 64       &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files =&lt;br /&gt;
&lt;br /&gt;
== CHARMM-GUI ==&lt;br /&gt;
charmm-gui can now output simulation files in Tinker format, but only fixed-charge force fields for now.&lt;br /&gt;
&lt;br /&gt;
== Latest tool for system set up for Tinker and AMOEBA ==&lt;br /&gt;
https://github.com/prenlab/Tinker-GUI&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2157</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2157"/>
		<updated>2026-02-05T20:35:52Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* *.key file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can&#039;&#039;         &lt;br /&gt;
                                              &#039;&#039;use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23 # add b and c if not cubic&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# small cutoff because dipole/quadrupole die off &amp;gt; charge.&#039;&#039;&lt;br /&gt;
                                                &lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&lt;br /&gt;
 polar-eps             0.01                &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files =&lt;br /&gt;
&lt;br /&gt;
== CHARMM-GUI ==&lt;br /&gt;
charmm-gui can now output simulation files in Tinker format, but only fixed-charge force fields for now.&lt;br /&gt;
&lt;br /&gt;
== Latest tool for system set up for Tinker and AMOEBA ==&lt;br /&gt;
https://github.com/prenlab/Tinker-GUI&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2156</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2156"/>
		<updated>2026-02-05T20:29:43Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to generate input files of your own */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&lt;br /&gt;
&lt;br /&gt;
 polar-eps             0.01                &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files =&lt;br /&gt;
&lt;br /&gt;
== CHARMM-GUI ==&lt;br /&gt;
charmm-gui can now output simulation files in Tinker format, but only fixed-charge force fields for now.&lt;br /&gt;
&lt;br /&gt;
== Latest tool for system set up for Tinker and AMOEBA ==&lt;br /&gt;
https://github.com/prenlab/Tinker-GUI&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2155</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2155"/>
		<updated>2026-01-28T16:13:27Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Induced dipole not converging error */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&lt;br /&gt;
&lt;br /&gt;
 polar-eps             0.01                &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.1&amp;quot; or 0.01 during system setup and 0.01 (0.001) for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2154</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2154"/>
		<updated>2026-01-28T16:11:58Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Induced dipole not converging error */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&lt;br /&gt;
&lt;br /&gt;
 polar-eps             0.01                &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOESN&#039;T mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2153</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2153"/>
		<updated>2026-01-28T16:09:45Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* *.key file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&lt;br /&gt;
&lt;br /&gt;
 polar-eps             0.01                &#039;&#039;# the induced dipole convergence threshold, 0.001 is better but slower.&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multipoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Ammm:Md_tp&amp;diff=2152</id>
		<title>Ammm:Md tp</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Ammm:Md_tp&amp;diff=2152"/>
		<updated>2026-01-22T19:24:21Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Langevin */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Ensemble==&lt;br /&gt;
Typical microscopic ensembles &lt;br /&gt;
&lt;br /&gt;
* Microcanonical: &amp;lt;math&amp;gt;\; \Omega(E,V,N) = e^{S/k} &amp;lt;/math&amp;gt; &lt;br /&gt;
** Constant energy; the probability density is proportional to &amp;lt;math&amp;gt;\delta = \aleph(q,p)-E\,&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----------------------&lt;br /&gt;
&lt;br /&gt;
* Canonical: &amp;lt;math&amp;gt;\; Z(T,V,N) = e^{- \aleph/kT} &amp;lt;/math&amp;gt;&lt;br /&gt;
** the probability density is proportional to &amp;lt;math&amp;gt; exp\left(-\frac{\aleph}{kT}\right)&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
---------------------------&lt;br /&gt;
&lt;br /&gt;
* Grand canonical:  &amp;lt;math&amp;gt;\; \Xi(T,V,\mu) = \sum_{N}^{}e^{(\mu N/kT)}{Z}_{NVT} = e^{\beta P V} &amp;lt;/math&amp;gt;&lt;br /&gt;
** th density is proportional to  &amp;lt;math&amp;gt; exp\left(-\frac{\aleph-\mu N}{kT}\right)&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----------------------------&lt;br /&gt;
* isothermal-isobaric: &amp;lt;math&amp;gt;\Delta(N, P, T) = \int  Z(N, V, T) \exp(-\beta  PV ) C dV. \,\;&amp;lt;/math&amp;gt;&lt;br /&gt;
** the density is proportional to  &amp;lt;math&amp;gt; exp\left(-\frac{\aleph+PV}{kT}\right)&amp;lt;/math&amp;gt;&lt;br /&gt;
** Note that  &amp;lt;math&amp;gt; H=&amp;lt;\aleph&amp;gt;+ P&amp;lt;V&amp;gt;\,&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In different situations, different ensembles shall be applied in MD simulations:&lt;br /&gt;
&lt;br /&gt;
*phase equilibrium; absorption where particle number N is a variable: Grand canonical&lt;br /&gt;
&lt;br /&gt;
*free energy: NPT or NVT. Note that free energy calculated from NPT or NVT is the same but the enthalpy and entropy components aren&#039;t necessary the same. &lt;br /&gt;
&lt;br /&gt;
[[File:Lvey1997-nvt-npt.pdf | 380px‎|388x388px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;It should be noted that the choice of the ensemble (canonical or isobaric) in eq 1 is somewhat arbitrary. In a constant volume ensemble, eq 1 would correspond to the change in Helmholtz free energy at a specific volume. Not considering finite size effects, this Helmholtz free energy change would be equal to the corresponding Gibbs free energy change at the pressure determined by the equation of state of the system. Both quantities correspond to the change in chemical potential of the solute.19&#039;&#039;&#039;&lt;br /&gt;
&#039;&#039;&#039;The choice of the ensemble is, however, critical when considering the entropy and enthalpy changes.20&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[File:npt-nvt.pdf | 380px]] &lt;br /&gt;
[[File:nvt-npt-2002.pdf|380px]]&lt;br /&gt;
&lt;br /&gt;
*NPT resembles the experimental condition (open container) most closely; but the converge is slow.&lt;br /&gt;
&lt;br /&gt;
[[File:Sun_jp980939v.pdf|380px]]&lt;br /&gt;
&lt;br /&gt;
[[File:Npt-nvt-corr.png|380px]]&lt;br /&gt;
&lt;br /&gt;
How does it affect the error of sampling?&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;\sigma = \sqrt{\frac{1}{N} \sum_{i=1}^N (x_i - \mu)^2},&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
where N is the number of independent samples.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;{{N}_{true}}={{N}_{record}}\frac{{{t}_{{interval}}}}{t{}_{{correlation}}}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Comparing Ensemble==&lt;br /&gt;
The averages of any quantity calculated in, say, the constant-NVE ensemble and the constant-NVT ensemble, will be equal in the thermodynamic limit, as long as we choose E and Г consistently so that &amp;lt;math&amp;gt;E = &amp;lt;E&amp;gt;_{NVT}&amp;lt;/math&amp;gt;. In fact, there are some restrictions on the kinds of functions for which this principle holds. The average should be a sum of single-particle functions &lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;A=\sum_{i=1}^NA_i&amp;lt;/math&amp;gt; for example: K, U, P, V, T....&lt;br /&gt;
&lt;br /&gt;
The fluctuation is however, ensemble dependent!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;\delta^2 (A)=&amp;lt;\delta A^2&amp;gt;=&amp;lt;A^2&amp;gt;-&amp;lt;A&amp;gt;^2\,&amp;lt;/math&amp;gt; &lt;br /&gt;
----------------------------&lt;br /&gt;
&#039;&#039;&#039;For example, the heat capacity:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In NVT, &amp;lt;math&amp;gt;kT^2 C_V=&amp;lt;\delta \aleph^2&amp;gt;_{NVT}=&amp;lt;\delta K^2&amp;gt;_{NVT}+&amp;lt;\delta U^2&amp;gt;_{NVT}&amp;lt;/math&amp;gt; &lt;br /&gt;
&lt;br /&gt;
and for a system of N partciles,  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;&amp;lt;\delta K^2&amp;gt;_{NVT}=\frac{3N}{2}(kT)^2&amp;lt;/math&amp;gt; so that &lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;kT^2(C_V-3/2Nk)=&amp;lt;\delta U^2&amp;gt;_{NVT}\,&amp;lt;/math&amp;gt;&lt;br /&gt;
----------------------------------&lt;br /&gt;
In NPT, &amp;lt;math&amp;gt;kT^2 C_P=&amp;lt;\delta (\aleph+PV)^2&amp;gt;_{NPT}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
---------------------------------&lt;br /&gt;
In NVE, the potential energy component of Cv &amp;lt;ref&amp;gt; Ren and Ponder, J. Phys. Chem. B 2003, 107, 5933-5947&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:Cv-nve.png|400px]]&lt;br /&gt;
------------------------&lt;br /&gt;
In weak-coupling (when Berendsen thermostat is used) [[File:Weak_coupling_fluc.pdf|380px]]&lt;br /&gt;
&lt;br /&gt;
[[File:Cv-berendsen.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Mor examples of fluctuation, structure and correlation properties in Allen and Tildesley book.&lt;br /&gt;
&lt;br /&gt;
== Temperature control ==&lt;br /&gt;
&#039;&#039;&#039;In Tinker, recommended thermostat is Bussi, used with RESPA integrator, 2fs time step. Recommended pressure control for homogeneous systems (protein in water is OK) is Monte Carlo, used with RESPA integrator, 2fs time step. For inhomogeneous system like lipids, use Langevin piston for pressure/temperature control and its own integrator. See [https://biomolmd.org/mw/index.php/Tutorial:tinkertut#Recommended_NVT_and_NPT_combinations Using Tinker&amp;amp;AMOEBA] for details.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the NVT, NPT, or &amp;lt;math&amp;gt;\mu&amp;lt;/math&amp;gt;VT ensemble simulations, the temperature is controlled by scaling atomic velocity in certain frequency. &lt;br /&gt;
There are several ways to scale the velocity and maintain the T at desired value, however, not all produce a true ensemble (fluctuation).&lt;br /&gt;
&lt;br /&gt;
Reference reading: &amp;lt;ref&amp;gt;Forcefield-Based Simulations/September 1998, MSI&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Direct velocity scaling===&lt;br /&gt;
[[Image:Md_vscale.png|200px]]&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
[[Image:Md_vscale2.PNG|200px]]&lt;br /&gt;
&lt;br /&gt;
===Berendsen method of temperature-bath coupling===&lt;br /&gt;
[[Image:Md_berendsen.png|280px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----------------------&lt;br /&gt;
&#039;&#039;&#039;The following methods ensure a correct ensemble fluctuation:&#039;&#039;&#039; &lt;br /&gt;
-----------------------&lt;br /&gt;
&lt;br /&gt;
===Bussi Parrilleno===&lt;br /&gt;
[[File:VelocityRescaling_JCP_2007_126_014101.pdf‎ |300px]]&lt;br /&gt;
&lt;br /&gt;
[[File:Md_bussi.png|300px]]&lt;br /&gt;
&lt;br /&gt;
===Nosé and Nosé–Hoover dynamics===&lt;br /&gt;
The extended system (model plus a fictitious for temperature) Hamiltonian is  &lt;br /&gt;
&lt;br /&gt;
[[Image:Md_nosehoover.png|400px]]&lt;br /&gt;
*The choice of the fictitious mass Q of that additional degree of freedom is arbitrary but is critical to the success of a run. If Q is too small, the frequency of the harmonic motion of the extended degree of frequency is too high. This forces a smaller timestep to be used in integration. However, if Q is too large, the thermalization process is not efficient—as Q approaches infinity, there is no energy exchange between the heat bath and the model.&lt;br /&gt;
*Q should be different for different models—Nosé (1991) suggests that Q should be proportional to gkBT, where g is the number of degrees of freedom in the model, kB is the Boltzmann constant, and T is the temperature.&lt;br /&gt;
*To determine the proportionality constant, studies were done with a model consisting of a box of liquid argon containing 343 atoms at 87 K. Setting Q to 2.5 10-5 kcal mol-1 fs-2 for this model yielded good results. This proportionality constant, together with the gkBT term, was then used to generate Q for a box of water and an amorphous cell of polypropylene, which also yielded satisfactory results.&lt;br /&gt;
*For the Nosé–Hoover method, the smaller the timestep, the closer it approaches the target temperature.&lt;br /&gt;
*For energy to be conserved, the Nosé–Hoover method requires an accurate integrator. such as 0.5 fs as the timestep should be used.&lt;br /&gt;
&lt;br /&gt;
===Andersen method===&lt;br /&gt;
&lt;br /&gt;
One version of the Andersen method of temperature control involves randomizing the velocities of all atoms at a predefined “collision frequency”. (The other version involves choosing one atom at each timestep and changing its velocity according to the Boltzmann distribution.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;&lt;br /&gt;
f (v) = 4 \pi &lt;br /&gt;
\left(\frac{m}{2 \pi kT}\right)^{3/2}\!\!v^2&lt;br /&gt;
\exp \left[&lt;br /&gt;
\frac{-mv^2}{2kT}&lt;br /&gt;
\right]&lt;br /&gt;
\qquad &amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==pressure control==&lt;br /&gt;
Pressure is another state variable of the system. It is defined as the force per unit area. Standard atmospheric pressure is 1.013 bar, where 1 bar = 105 Pa (roughly 1 atm). Pressure is actually a tensor:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;P=\begin{pmatrix}&lt;br /&gt;
Pxx &amp;amp;Pxy  &amp;amp; Pxz\\ &lt;br /&gt;
Pyx &amp;amp;Pyy  &amp;amp; Pyz \\ &lt;br /&gt;
Pzx &amp;amp;Pzy  &amp;amp; Pzz&lt;br /&gt;
\end{pmatrix}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In an isotropic situation, where forces are the same in all directions and there is no viscous force, the pressure tensor becomes&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;P=p\begin{pmatrix}&lt;br /&gt;
1 &amp;amp;0  &amp;amp; 0\\ &lt;br /&gt;
0 &amp;amp;1  &amp;amp; 0 \\ &lt;br /&gt;
0 &amp;amp;0  &amp;amp; 1&lt;br /&gt;
\end{pmatrix}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
where p is the scalar pressure we are familiar with.&lt;br /&gt;
&lt;br /&gt;
The thermodynamic pressure is defined by:&lt;br /&gt;
&amp;lt;math&amp;gt;PV=Nk_{b}T + \frac {2}{3}&amp;lt;W&amp;gt;&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
where W is the virial&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt; W = \frac{1}{2}\sum_{i=1}^{N}{r}_{i}.{f}_{i}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The instantaneous pressure of a system is then &lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;P =\frac{2}{3V}(K+W)=\frac{1}{V}\begin{pmatrix}&lt;br /&gt;
\sum_{i}^{N}miVi.{Vi}^{T}+\sum_{i}^{N}ri.{fi}^{T}&lt;br /&gt;
\end{pmatrix}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;P=\frac{1}{V}\left[ \begin{matrix}&lt;br /&gt;
   \sum_{i}{{{m}_{i}}{{v}_{ix}}{{v}_{ix}}} &amp;amp; \sum_{i}{{{m}_{i}}{{v}_{ix}}{{v}_{iy}}} &amp;amp; \sum_{i}{{{m}_{i}}{{v}_{ix}}{{v}_{iz}}}  \\&lt;br /&gt;
   \sum_{i}{{{m}_{i}}{{v}_{iy}}{{v}_{ix}}} &amp;amp; \sum_{i}{{{m}_{i}}{{v}_{iy}}{{v}_{iy}}} &amp;amp; \sum_{i}{{{m}_{i}}{{v}_{iy}}{{v}_{iz}}}  \\&lt;br /&gt;
   \sum_{i}{{{m}_{i}}{{v}_{iz}}{{v}_{ix}}} &amp;amp; \sum_{i}{{{m}_{i}}{{v}_{iz}}{{v}_{iy}}} &amp;amp; \sum_{i}{{{m}_{i}}{{v}_{iz}}{{v}_{iz}}}  \\&lt;br /&gt;
\end{matrix} \right]+\frac{1}{V}\left[ \begin{matrix}&lt;br /&gt;
   \sum_{i}{{{r}_{ix}}{{f}_{ix}}} &amp;amp; \sum_{i}{{{r}_{ix}}{{f}_{iy}}} &amp;amp; \sum_{i}{{{r}_{ix}}{{f}_{iz}}}  \\&lt;br /&gt;
   \sum_{i}{{{r}_{iy}}{{f}_{ix}}} &amp;amp; \sum_{i}{{{r}_{iy}}{{f}_{iy}}} &amp;amp; \sum_{i}{{{r}_{iy}}{{f}_{iz}}}  \\&lt;br /&gt;
   \sum_{i}{{{r}_{iz}}{{f}_{ix}}} &amp;amp; \sum_{i}{{{r}_{iz}}{{f}_{iy}}} &amp;amp; \sum_{i}{{{r}_{iz}}{{f}_{iz}}}  \\&lt;br /&gt;
\end{matrix} \right]&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The scalar pressure is the average of the trace:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;math&amp;gt;p=\frac{1}{3}\left(Pxx+Pyy+Pzz\right)&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Berendsen method===&lt;br /&gt;
At each step, the x, y, and z coordinates of each atom are scaled by the factor:&lt;br /&gt;
&lt;br /&gt;
[[File:pressure3.png|300px]]&lt;br /&gt;
&lt;br /&gt;
*Note that this method (as implemented) changes the cell uniformly,so that the size of the cell is changed, but not its shape. Therefore, for simulations such as crystal phase transitions, where both the cell size and shape are expected to change, this method is not appropriate. &lt;br /&gt;
*The pressure fluctuation has been observed to be large during test runs with the Discover program and in studies in the literature (Brown and Clark 1984). Negative pressures sometimes occur because the virial can be negative, even though this defies the usual sense that pressure is a positive number. The calculated pressure depends on the cutoff distances used in the simulation.&lt;br /&gt;
&lt;br /&gt;
===Parrinello–Rahman method of pressure and stress control===&lt;br /&gt;
*Both size and shape of cell can change under the stress tensor.&lt;br /&gt;
*The Lagrangians of the system are modified such that a term representing the kinetic energy of the cell depends on a user-defined mass-like parameter W. An elastic energy term pΩ is related to the pressure and volume or the stress and strain of the system. The equations of motion for the atoms and cell vectors can be derived from this Lagrangian. The motion of the cell vectors, which determines the cell shape and size, is driven by the difference between the target and internal stress.&lt;br /&gt;
&lt;br /&gt;
[[File:press_parr.png|300px]]&lt;br /&gt;
&lt;br /&gt;
[[File:press_parr2.png|300px]]&lt;br /&gt;
&lt;br /&gt;
*Note the user-defined variable W, which determines the rate of change of the volume/shape matrix. A large W means a heavy, slow cell. In the limiting case, infinite W reverts to constant-volume dynamics. A small W means fast motion of the cell vectors. Although that may mean that the target stress can be reached faster, there may not be enough time for equilibration.&lt;br /&gt;
&lt;br /&gt;
==Types of MD==&lt;br /&gt;
=== Langevin ===&lt;br /&gt;
&lt;br /&gt;
The Langevin dynamics method (McCammon et al. 1976, Levy et al. 1979) approximates a full molecular dynamics simulation of a system by eliminating unimportant degrees of freedom (e.g. solvent). The effects of the eliminated degrees of freedom are simulated by mean and stochastic forces. Friction coefficients must be assigned to selected atoms before starting the dynamics run. Langevin dynamics includes a constant-temperature bath. &lt;br /&gt;
&lt;br /&gt;
For a system of &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;&#039;&#039;N&#039;&#039;&amp;lt;/span&amp;gt; particles with masses &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;&#039;&#039;M&#039;&#039;&amp;lt;/span&amp;gt;, with coordinates &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;&#039;&#039;X&#039;&#039; = &#039;&#039;X&#039;&#039;(&#039;&#039;t&#039;&#039;)&amp;lt;/span&amp;gt; the resulting Langevin equation is &amp;lt;ref&amp;gt;{{cite bookfckLR| first=Tamar | last=Schlick | year=2002 | title=Molecular Modeling and Simulation | publisher=Springer | isbn=0-387-95404-X |  pages = 435–438fckLRfckLR}}&amp;lt;/ref&amp;gt; &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt;M\ddot{X} = - \nabla U(X) - \gamma M \dot{X} + \sqrt{2 \gamma k_B T M} R(t)\,,&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;&#039;&#039;U&#039;&#039;(&#039;&#039;X&#039;&#039;)&amp;lt;/span&amp;gt; is the potential energy;&amp;amp;nbsp;is the friction coefficent or damping factor; the dot is a time derivative such that &amp;lt;math&amp;gt;\dot{X}&amp;lt;/math&amp;gt; is the velocity and &amp;lt;math&amp;gt;\ddot{X}&amp;lt;/math&amp;gt; is the acceleration; and &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;&#039;&#039;R&#039;&#039;(&#039;&#039;t&#039;&#039;)&amp;lt;/span&amp;gt; is a random (Gaussian) force with zero-mean, satisfying &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt;\left\langle R(t) \right\rangle =0&amp;lt;/math&amp;gt; &lt;br /&gt;
:&amp;lt;math&amp;gt;\left\langle R(t)R(t&#039;) \right\rangle = \delta(t-t&#039;)&amp;lt;/math&amp;gt; &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* As &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;γ&amp;lt;/span&amp;gt; grows, it spans the inertial all the way to the diffusive (Brownian) regime. The limit of non-inertia is commonly described as Brownian dynamics, or overdamped, creeping motion.&lt;br /&gt;
&lt;br /&gt;
* The Hamiltonian of a generalized LE is&lt;br /&gt;
&lt;br /&gt;
[[File:gle_5-1.PNG|480px]]&lt;br /&gt;
&lt;br /&gt;
===Brownian dynamics  ===&lt;br /&gt;
In Brownian dynamics, no acceleration is assumed to take place. Thus, the &amp;lt;math&amp;gt;M\ddot{X}(t)&amp;lt;/math&amp;gt; term is neglected, and the sum of these terms is zero. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;0 = - \nabla U(X) - \gamma M\dot{X}+ \sqrt{2 \gamma k_B T M} R(t)&amp;lt;/math&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Defining &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;ζ = γ&#039;&#039;M&#039;&#039;&amp;lt;/span&amp;gt;, and using the Einstein relation, &amp;lt;span class=&amp;quot;texhtml&amp;quot;&amp;gt;&#039;&#039;D&#039;&#039; = &#039;&#039;k&#039;&#039;&amp;lt;sub&amp;gt;&#039;&#039;B&#039;&#039;&amp;lt;/sub&amp;gt;&#039;&#039;T&#039;&#039; / ζ&amp;lt;/span&amp;gt;, it is often convenient to write the equation as, &lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;\dot{X}(t) = - \nabla U(X)/\zeta + \sqrt{2 D} R(t)&amp;lt;/math&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 A free program for Brownian dynamics: http://adrik.bchs.uh.edu/uhbd.html &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===More reading===&lt;br /&gt;
* The Langevin equation can be reformulated as a Fokker–Planck equation (http://en.wikipedia.org/wiki/Fokker%E2%80%93Planck_equation) that governs the Probability distribution of the random variable &#039;&#039;X&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Read me more about generalized Langevin, FPE, and GE here [[File:gle.pdf|300px]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2150</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2150"/>
		<updated>2025-11-10T19:52:25Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Recommended NVT and NPT combinations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT for anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2149</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2149"/>
		<updated>2025-11-10T19:51:07Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Recommended NVT and NPT combinations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2148</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2148"/>
		<updated>2025-11-10T19:45:51Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* MD setup-initial equilibration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equilibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g. for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to speed up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error.&lt;br /&gt;
**Use &amp;quot;polar-eps 0.01&amp;quot; and &amp;quot;polar-predict&amp;quot; for equilibration for speed. For production use &amp;quot;polar-eps 0.001&amp;quot; or &amp;quot;0.0001&amp;quot;.&lt;br /&gt;
**use &amp;quot;neighbor-list&amp;quot;&lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be. Water/ions are relaxed after this step.&lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run 1-2 ns NPT. Add/use &#039;&#039;&#039;&amp;quot;barostat MonteCarlo&amp;quot; in key.&#039;&#039;&#039;&lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
**use 2 fs with RESPA&lt;br /&gt;
**polar-eps 0.001 &lt;br /&gt;
**polar-predict&lt;br /&gt;
**neighbor-list&lt;br /&gt;
**&#039;&#039;&#039;barostat MonteCarlo&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Lab:newuser&amp;diff=2147</id>
		<title>Lab:newuser</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Lab:newuser&amp;diff=2147"/>
		<updated>2025-10-17T14:59:49Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Lab cluster usage monitoring and signup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= How to use lab cluster =&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
If you are new to Linux: [https://ryanstutorials.net/linuxtutorial/ https://ryanstutorials.net/linuxtutorial/]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Lab cluster ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;login&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
You need an account to login to lab cluster to use various software and perform calculations. We can no longer log in remotely using password. SSH key is required. &#039;&#039;&#039;&#039;&#039;You have to come to the lab to do the below in person. If not, ask admin to do it for you.&#039;&#039;&#039;&#039;&#039;&amp;amp;nbsp;Once you receivd an account and temp password, log in at any workstation &#039;&#039;&#039;in the lab&#039;&#039;&#039;, and set up your ssh key:&lt;br /&gt;
&lt;br /&gt;
These steps should have been done for you by admin. &lt;br /&gt;
 cd ~&lt;br /&gt;
 ssh-keygen -t rsa -b 4096 (then hit enter all the way)&lt;br /&gt;
 cd .ssh &lt;br /&gt;
 cat id_rsa.pub &amp;gt;&amp;gt; authorized_keys&lt;br /&gt;
 chmod 600  authorized_keys&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note the key exist in pairs, one is public (id_rsa_pub) and another is private.&lt;br /&gt;
&lt;br /&gt;
Then &amp;quot;ssh bme-uranus”. Use &amp;quot;passwd&amp;quot; to update your password to something very secure. The bare command is sufficient; prompts will open up for old and new passwords. Your changes will be propagated to all nodes automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
After you have logged into uranus, obtain a list of all known nodes (hostnames, [https://github.com/bdw2292/Ren-Lab-Daemon/blob/main/nodes.txt https://github.com/bdw2292/Ren-Lab-Daemon/blob/main/nodes.txt]) and ssh from uranus to each node. There will be a prompt that opens asking if you would like to add that hostname to list of known hosts, just type yes for each prompt.&lt;br /&gt;
&lt;br /&gt;
There is a Google spreadsheet for signing up to use different CPUs and GPUs.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;login from your laptop on and off campus&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
You will need a ssh client to remote log into our computer cluster.&lt;br /&gt;
&lt;br /&gt;
You also need UT VPN to connect from off campus. On campus, you don&#039;t need this.&lt;br /&gt;
&lt;br /&gt;
If you use Mac or Linux, ssh client is built-in (via terminal). If you use Windows, you can install ssh clients like mobaxterm [https://mobaxterm.mobatek.net/ https://mobaxterm.mobatek.net/], Windows subsystem for linux (ubutu/Debian etc), or cygwin. You need to create ssh keys (&#039;&#039;&#039;private and public pair&#039;&#039;&#039;) on your own computer (e.g. laptop).Mobaxterm has tool for this (Tools/mobakeygen). If you use WSL or Mac, the instruction is the same as above (ssh-keygen). &#039;&#039;&#039;Once you generate the key pairs, save them somewhere you know.&#039;&#039;&#039; Then append the pub key from your laptop (client) to &amp;quot;authorized_keys&amp;quot; on lab computer (remote server) in your .ssh folder. On your laptop, you will need specify the matching private key if you use mobaxterm (otherwise it will be found in ~/.ssh if you use Mac or linux). Again, if you cannot come to lab in person, send me the public key (via link to clound drive, not explicitly in email)&amp;amp;nbsp;and we will append for you.&lt;br /&gt;
&lt;br /&gt;
Remotely, you can log into &#039;&#039;&#039;bme-jupiter.bme.utexas.edu&#039;&#039;&#039; or &#039;&#039;&#039;bme-sugar.bme.utexas.edu or &#039;&#039;&#039;All the other nodes/server are blocked. From there, you can ssh into uranus and nodes behind uranus (see cluster structure at the bottom of this page). If the username you have on your device does not match your cluster username, you will have to preface this address &amp;lt;span style=&amp;quot;background-color:#f1c40f;&amp;quot;&amp;gt;with your username &amp;lt;/span&amp;gt;(&#039;&#039;e.g.&#039;&#039; &amp;lt;span style=&amp;quot;background-color:#f39c12;&amp;quot;&amp;gt;longhorn42@bme-jupiter.bme.utexas.edu&amp;lt;/span&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
From off campus, you need to use UT VPN to ssh into jupiter or sugar.&lt;br /&gt;
https://wikis.utexas.edu/display/engritgpublic/Connecting+to+the+University+of+Texas+VPN&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;More instructions if you are using mobaxterm:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* make sure connected via VPN&lt;br /&gt;
* Start mobxterm and use Tools/mobakeygen to generate a pair of public and private keys. Save both.&lt;br /&gt;
* Append your public key to .ssh/authprized_keys (you can ask for help if you are remote)&lt;br /&gt;
* Create a new session in mobaxterm, under Advanced ssh setting, host: bme-jupiter.bme.utexas.edu, username: xxx, &#039;&#039;&#039;and specify your private key&#039;&#039;&#039; you saved above.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;your home dir is on uranus&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
uranus is now obsolete. Uranus replaced uranus as the header node.&lt;br /&gt;
&lt;br /&gt;
bme-uranus.bme.utexas.edu (node199, 10.0.0.199) is the header node of our computer cluster where all your home directory and files are stored. Your home directory (echo $HOME) is located either in /home or /users which is physically located on uranus . It can be accessed from any nodes and workstations in the lab. From uranus, you can start your job by doing &amp;quot;ssh node120 xxx” where xxx is your simulation script. You can write your own script to submit a bunch of job to these nodes (check the availability and skip if the node is busy). Your home directory is shared among uranus and all nodes vis NFS.&lt;br /&gt;
&lt;br /&gt;
(More about lab cluster structure at the end of page)&lt;br /&gt;
&lt;br /&gt;
Your home directory has a limit (quota) on space and file number and you won&#039;t be able to create new files once it is reached.&lt;br /&gt;
&lt;br /&gt;
Even you see your home folder on all WS/nodes in the lab but they are actually doing so remotely (hence use /scratch that is local on each node for serious jobs).&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;where to run simulations &amp;amp; analysis&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
The home dir on uranus is accessible on all nodes. But when you perform calculations on the nodes/WS in your home directory, it is actually accessing the files on uranus through network. It is convenient to run relatively short simulations, store the output files and perform quick analysis directly in your home directory. But because all members in the lab share home dir on uranus, it could stress out the system if several demanding simulations/trajectory analyses are performed at the same time on files in your home dir on uranus.&lt;br /&gt;
&lt;br /&gt;
So for demanding calculations, please use &#039;&#039;&#039;/work (mounted from sun.bme.utexas.edu) and /work2 (from uranus.bme.utexas.edu) &#039;&#039;&#039;as working directories. &amp;quot;sun and uranus&amp;quot; are also shared among all nodes like uranus. But this way we spread out the burden among 3 servers. If you ahve an active projecta nd expect to produce sunstaitnal amount files, let me know and I will created folder for you on /work and /work2. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#f39c12&amp;quot;&amp;gt;Keep uranus(your home directory) clean and efficient for everyone including yourself.&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For QM and highly disk intensive tasks, we also use local &amp;quot;&#039;&#039;&#039;/scratch&#039;&#039;&#039;&amp;quot; disk. This space is large (100s GB) but is &amp;quot;local&amp;quot; meaning only accessible on specific node (after you ssh into it).&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;pre&amp;gt;When submitting a command, use the following. This will run it in the background and redirect output that would print to the screen to a file &amp;quot;nohup.out&amp;quot;. This prevents it from terminating when you logout or close the terminal.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nohup your_command &amp;amp;&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;quot;less +F file_name&amp;quot; to have constantly updated end of file on screen&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Lab cluster usage monitoring and signup ==&lt;br /&gt;
&lt;br /&gt;
The node activities can be monitored here:&lt;br /&gt;
&lt;br /&gt;
 https://biomolmd.org/pren/nodes.html&lt;br /&gt;
 https://biomolmd.org/liuchw/jobs.txt&lt;br /&gt;
 &lt;br /&gt;
 &#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff33;&amp;quot;&amp;gt;Complete CPU/GPU usage &amp;amp; sign up spreadsheet&amp;lt;/span&amp;gt; &#039;&#039;&#039;(email pren to request permission to edit): [https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Utilities and Consideration when set up jobs ==&lt;br /&gt;
&lt;br /&gt;
We don’t have a job queuing system (yet) so you just log into a node to run your job.&lt;br /&gt;
&lt;br /&gt;
Be considerate and coordinate with lab mates using the spreadsheet and Slack.&lt;br /&gt;
&lt;br /&gt;
for each node you can check the resourses available and make sure DO NOT OVERLOAD&lt;br /&gt;
&lt;br /&gt;
DO NOT use more than 80% of total CPUs or memory on each node.&lt;br /&gt;
&lt;br /&gt;
 Use &amp;quot;top&amp;quot; to check the load on a node. 600% means 6 cores are fully loaded.&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;lscpu&amp;quot; to check how many CPU/threads on each node&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
 Or &amp;quot;less /proc/cpuinfo&amp;quot; to check how many CPU cores/threads on a node&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
 &amp;quot;free -g&amp;quot; to check free memory (esp. for QM jobs). The line &amp;quot;-/+ buffers/cache:&amp;quot; has the real number for free space;&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
 &amp;quot;echo &amp;gt; large_file_name&amp;quot; to empty a large file quickly. rm can be slow&lt;br /&gt;
 &amp;quot;df -h&amp;quot; to check available storage (disk space)&lt;br /&gt;
&lt;br /&gt;
== Backups ==&lt;br /&gt;
&lt;br /&gt;
All home directories (/home, /users, /opt, /work, /work2) are backed up twice a week for ~ 2 weeks on bigdata.bme.utexas.edu. If you need to recover any files from last couple of&amp;amp;nbsp;weeks, you should be able to find them there. Log into bigdata, cd /bigdata/renlab/.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Cluster structure ==&lt;br /&gt;
&lt;br /&gt;
uranus.bme.utexas.edu is the header node for all computing nodes (nodexxx) that can only be accessed from uranus. The /home, /users, /opt folders are all part of uranus file system. The computing nodes have private IP address so can not be seen from outside including your WS or laptop. Each mode has a large local /scratch&amp;quot; folder that writable by everyone. &amp;quot;sun and uranus&amp;quot; are another two large servers mounted as /work and /work2 on each WS and computing node. You can use them just like the home dir. bigdata is the backup server.&lt;br /&gt;
&lt;br /&gt;
Read the pdf below for an illustration (replace NOVA with uranus)&lt;br /&gt;
&lt;br /&gt;
Current login nodes are bme-jupiter and bme-sugar and UT VPN is required&lt;br /&gt;
&lt;br /&gt;
[[File:LabCluster.pdf|200px|thumb|left|alt text]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Lab:newuser&amp;diff=2146</id>
		<title>Lab:newuser</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Lab:newuser&amp;diff=2146"/>
		<updated>2025-10-17T14:54:57Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* your home dir is on uranus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= How to use lab cluster =&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
If you are new to Linux: [https://ryanstutorials.net/linuxtutorial/ https://ryanstutorials.net/linuxtutorial/]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Lab cluster ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;login&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
You need an account to login to lab cluster to use various software and perform calculations. We can no longer log in remotely using password. SSH key is required. &#039;&#039;&#039;&#039;&#039;You have to come to the lab to do the below in person. If not, ask admin to do it for you.&#039;&#039;&#039;&#039;&#039;&amp;amp;nbsp;Once you receivd an account and temp password, log in at any workstation &#039;&#039;&#039;in the lab&#039;&#039;&#039;, and set up your ssh key:&lt;br /&gt;
&lt;br /&gt;
These steps should have been done for you by admin. &lt;br /&gt;
 cd ~&lt;br /&gt;
 ssh-keygen -t rsa -b 4096 (then hit enter all the way)&lt;br /&gt;
 cd .ssh &lt;br /&gt;
 cat id_rsa.pub &amp;gt;&amp;gt; authorized_keys&lt;br /&gt;
 chmod 600  authorized_keys&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note the key exist in pairs, one is public (id_rsa_pub) and another is private.&lt;br /&gt;
&lt;br /&gt;
Then &amp;quot;ssh bme-uranus”. Use &amp;quot;passwd&amp;quot; to update your password to something very secure. The bare command is sufficient; prompts will open up for old and new passwords. Your changes will be propagated to all nodes automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
After you have logged into uranus, obtain a list of all known nodes (hostnames, [https://github.com/bdw2292/Ren-Lab-Daemon/blob/main/nodes.txt https://github.com/bdw2292/Ren-Lab-Daemon/blob/main/nodes.txt]) and ssh from uranus to each node. There will be a prompt that opens asking if you would like to add that hostname to list of known hosts, just type yes for each prompt.&lt;br /&gt;
&lt;br /&gt;
There is a Google spreadsheet for signing up to use different CPUs and GPUs.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;login from your laptop on and off campus&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
You will need a ssh client to remote log into our computer cluster.&lt;br /&gt;
&lt;br /&gt;
You also need UT VPN to connect from off campus. On campus, you don&#039;t need this.&lt;br /&gt;
&lt;br /&gt;
If you use Mac or Linux, ssh client is built-in (via terminal). If you use Windows, you can install ssh clients like mobaxterm [https://mobaxterm.mobatek.net/ https://mobaxterm.mobatek.net/], Windows subsystem for linux (ubutu/Debian etc), or cygwin. You need to create ssh keys (&#039;&#039;&#039;private and public pair&#039;&#039;&#039;) on your own computer (e.g. laptop).Mobaxterm has tool for this (Tools/mobakeygen). If you use WSL or Mac, the instruction is the same as above (ssh-keygen). &#039;&#039;&#039;Once you generate the key pairs, save them somewhere you know.&#039;&#039;&#039; Then append the pub key from your laptop (client) to &amp;quot;authorized_keys&amp;quot; on lab computer (remote server) in your .ssh folder. On your laptop, you will need specify the matching private key if you use mobaxterm (otherwise it will be found in ~/.ssh if you use Mac or linux). Again, if you cannot come to lab in person, send me the public key (via link to clound drive, not explicitly in email)&amp;amp;nbsp;and we will append for you.&lt;br /&gt;
&lt;br /&gt;
Remotely, you can log into &#039;&#039;&#039;bme-jupiter.bme.utexas.edu&#039;&#039;&#039; or &#039;&#039;&#039;bme-sugar.bme.utexas.edu or &#039;&#039;&#039;All the other nodes/server are blocked. From there, you can ssh into uranus and nodes behind uranus (see cluster structure at the bottom of this page). If the username you have on your device does not match your cluster username, you will have to preface this address &amp;lt;span style=&amp;quot;background-color:#f1c40f;&amp;quot;&amp;gt;with your username &amp;lt;/span&amp;gt;(&#039;&#039;e.g.&#039;&#039; &amp;lt;span style=&amp;quot;background-color:#f39c12;&amp;quot;&amp;gt;longhorn42@bme-jupiter.bme.utexas.edu&amp;lt;/span&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
From off campus, you need to use UT VPN to ssh into jupiter or sugar.&lt;br /&gt;
https://wikis.utexas.edu/display/engritgpublic/Connecting+to+the+University+of+Texas+VPN&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;More instructions if you are using mobaxterm:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* make sure connected via VPN&lt;br /&gt;
* Start mobxterm and use Tools/mobakeygen to generate a pair of public and private keys. Save both.&lt;br /&gt;
* Append your public key to .ssh/authprized_keys (you can ask for help if you are remote)&lt;br /&gt;
* Create a new session in mobaxterm, under Advanced ssh setting, host: bme-jupiter.bme.utexas.edu, username: xxx, &#039;&#039;&#039;and specify your private key&#039;&#039;&#039; you saved above.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;your home dir is on uranus&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
uranus is now obsolete. Uranus replaced uranus as the header node.&lt;br /&gt;
&lt;br /&gt;
bme-uranus.bme.utexas.edu (node199, 10.0.0.199) is the header node of our computer cluster where all your home directory and files are stored. Your home directory (echo $HOME) is located either in /home or /users which is physically located on uranus . It can be accessed from any nodes and workstations in the lab. From uranus, you can start your job by doing &amp;quot;ssh node120 xxx” where xxx is your simulation script. You can write your own script to submit a bunch of job to these nodes (check the availability and skip if the node is busy). Your home directory is shared among uranus and all nodes vis NFS.&lt;br /&gt;
&lt;br /&gt;
(More about lab cluster structure at the end of page)&lt;br /&gt;
&lt;br /&gt;
Your home directory has a limit (quota) on space and file number and you won&#039;t be able to create new files once it is reached.&lt;br /&gt;
&lt;br /&gt;
Even you see your home folder on all WS/nodes in the lab but they are actually doing so remotely (hence use /scratch that is local on each node for serious jobs).&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;where to run simulations &amp;amp; analysis&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
The home dir on uranus is accessible on all nodes. But when you perform calculations on the nodes/WS in your home directory, it is actually accessing the files on uranus through network. It is convenient to run relatively short simulations, store the output files and perform quick analysis directly in your home directory. But because all members in the lab share home dir on uranus, it could stress out the system if several demanding simulations/trajectory analyses are performed at the same time on files in your home dir on uranus.&lt;br /&gt;
&lt;br /&gt;
So for demanding calculations, please use &#039;&#039;&#039;/work (mounted from sun.bme.utexas.edu) and /work2 (from uranus.bme.utexas.edu) &#039;&#039;&#039;as working directories. &amp;quot;sun and uranus&amp;quot; are also shared among all nodes like uranus. But this way we spread out the burden among 3 servers. If you ahve an active projecta nd expect to produce sunstaitnal amount files, let me know and I will created folder for you on /work and /work2. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#f39c12&amp;quot;&amp;gt;Keep uranus(your home directory) clean and efficient for everyone including yourself.&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For QM and highly disk intensive tasks, we also use local &amp;quot;&#039;&#039;&#039;/scratch&#039;&#039;&#039;&amp;quot; disk. This space is large (100s GB) but is &amp;quot;local&amp;quot; meaning only accessible on specific node (after you ssh into it).&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;pre&amp;gt;When submitting a command, use the following. This will run it in the background and redirect output that would print to the screen to a file &amp;quot;nohup.out&amp;quot;. This prevents it from terminating when you logout or close the terminal.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nohup your_command &amp;amp;&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;quot;less +F file_name&amp;quot; to have constantly updated end of file on screen&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Lab cluster usage monitoring and signup ==&lt;br /&gt;
&lt;br /&gt;
The node activities can be monitored here:&lt;br /&gt;
&lt;br /&gt;
 https://biomolmd.org/pren/nodes.html&lt;br /&gt;
 https://biomolmd.org/liuchw/jobs.txt&lt;br /&gt;
 &lt;br /&gt;
 &#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff33;&amp;quot;&amp;gt;Complete CPU/GPU usage &amp;amp; sign up spreadsheet&amp;lt;/span&amp;gt; &#039;&#039;&#039;(email pren to request permission to edit): [https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Utilities ==&lt;br /&gt;
&lt;br /&gt;
We don’t have a job queuing system (yet) so you just log into a node to run your job.&lt;br /&gt;
&lt;br /&gt;
 Use &amp;quot;top&amp;quot; to check the load on a node. 600% means 6 cores are fully loaded.&lt;br /&gt;
 &amp;quot;less /proc/cpuinfo&amp;quot; to check how many CPU cores/threads on a node&lt;br /&gt;
 &amp;quot;free -g&amp;quot; to check free memory (esp. for QM jobs). The line &amp;quot;-/+ buffers/cache:&amp;quot; has the real number for free space&lt;br /&gt;
 &amp;quot;echo &amp;gt; large_file_name&amp;quot; to empty a large file quickly. rm can be slow&lt;br /&gt;
 &amp;quot;df -h&amp;quot; to check available storage (disk space)&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
More tips about Lnux commands and uitlies:&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit?usp=sharing https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit?usp=sharing]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Backups ==&lt;br /&gt;
&lt;br /&gt;
All home directories (/home, /users, /opt, /work, /work2) are backed up twice a week for ~ 2 weeks on bigdata.bme.utexas.edu. If you need to recover any files from last couple of&amp;amp;nbsp;weeks, you should be able to find them there. Log into bigdata, cd /bigdata/renlab/.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Cluster structure ==&lt;br /&gt;
&lt;br /&gt;
uranus.bme.utexas.edu is the header node for all computing nodes (nodexxx) that can only be accessed from uranus. The /home, /users, /opt folders are all part of uranus file system. The computing nodes have private IP address so can not be seen from outside including your WS or laptop. Each mode has a large local /scratch&amp;quot; folder that writable by everyone. &amp;quot;sun and uranus&amp;quot; are another two large servers mounted as /work and /work2 on each WS and computing node. You can use them just like the home dir. bigdata is the backup server.&lt;br /&gt;
&lt;br /&gt;
Read the pdf below for an illustration (replace NOVA with uranus)&lt;br /&gt;
&lt;br /&gt;
Current login nodes are bme-jupiter and bme-sugar and UT VPN is required&lt;br /&gt;
&lt;br /&gt;
[[File:LabCluster.pdf|200px|thumb|left|alt text]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Lab:newuser&amp;diff=2145</id>
		<title>Lab:newuser</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Lab:newuser&amp;diff=2145"/>
		<updated>2025-10-17T14:54:35Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* your home dir is on uranus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= How to use lab cluster =&lt;br /&gt;
&lt;br /&gt;
== Preparation ==&lt;br /&gt;
&lt;br /&gt;
If you are new to Linux: [https://ryanstutorials.net/linuxtutorial/ https://ryanstutorials.net/linuxtutorial/]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Lab cluster ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;login&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
You need an account to login to lab cluster to use various software and perform calculations. We can no longer log in remotely using password. SSH key is required. &#039;&#039;&#039;&#039;&#039;You have to come to the lab to do the below in person. If not, ask admin to do it for you.&#039;&#039;&#039;&#039;&#039;&amp;amp;nbsp;Once you receivd an account and temp password, log in at any workstation &#039;&#039;&#039;in the lab&#039;&#039;&#039;, and set up your ssh key:&lt;br /&gt;
&lt;br /&gt;
These steps should have been done for you by admin. &lt;br /&gt;
 cd ~&lt;br /&gt;
 ssh-keygen -t rsa -b 4096 (then hit enter all the way)&lt;br /&gt;
 cd .ssh &lt;br /&gt;
 cat id_rsa.pub &amp;gt;&amp;gt; authorized_keys&lt;br /&gt;
 chmod 600  authorized_keys&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note the key exist in pairs, one is public (id_rsa_pub) and another is private.&lt;br /&gt;
&lt;br /&gt;
Then &amp;quot;ssh bme-uranus”. Use &amp;quot;passwd&amp;quot; to update your password to something very secure. The bare command is sufficient; prompts will open up for old and new passwords. Your changes will be propagated to all nodes automatically.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
After you have logged into uranus, obtain a list of all known nodes (hostnames, [https://github.com/bdw2292/Ren-Lab-Daemon/blob/main/nodes.txt https://github.com/bdw2292/Ren-Lab-Daemon/blob/main/nodes.txt]) and ssh from uranus to each node. There will be a prompt that opens asking if you would like to add that hostname to list of known hosts, just type yes for each prompt.&lt;br /&gt;
&lt;br /&gt;
There is a Google spreadsheet for signing up to use different CPUs and GPUs.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;login from your laptop on and off campus&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
You will need a ssh client to remote log into our computer cluster.&lt;br /&gt;
&lt;br /&gt;
You also need UT VPN to connect from off campus. On campus, you don&#039;t need this.&lt;br /&gt;
&lt;br /&gt;
If you use Mac or Linux, ssh client is built-in (via terminal). If you use Windows, you can install ssh clients like mobaxterm [https://mobaxterm.mobatek.net/ https://mobaxterm.mobatek.net/], Windows subsystem for linux (ubutu/Debian etc), or cygwin. You need to create ssh keys (&#039;&#039;&#039;private and public pair&#039;&#039;&#039;) on your own computer (e.g. laptop).Mobaxterm has tool for this (Tools/mobakeygen). If you use WSL or Mac, the instruction is the same as above (ssh-keygen). &#039;&#039;&#039;Once you generate the key pairs, save them somewhere you know.&#039;&#039;&#039; Then append the pub key from your laptop (client) to &amp;quot;authorized_keys&amp;quot; on lab computer (remote server) in your .ssh folder. On your laptop, you will need specify the matching private key if you use mobaxterm (otherwise it will be found in ~/.ssh if you use Mac or linux). Again, if you cannot come to lab in person, send me the public key (via link to clound drive, not explicitly in email)&amp;amp;nbsp;and we will append for you.&lt;br /&gt;
&lt;br /&gt;
Remotely, you can log into &#039;&#039;&#039;bme-jupiter.bme.utexas.edu&#039;&#039;&#039; or &#039;&#039;&#039;bme-sugar.bme.utexas.edu or &#039;&#039;&#039;All the other nodes/server are blocked. From there, you can ssh into uranus and nodes behind uranus (see cluster structure at the bottom of this page). If the username you have on your device does not match your cluster username, you will have to preface this address &amp;lt;span style=&amp;quot;background-color:#f1c40f;&amp;quot;&amp;gt;with your username &amp;lt;/span&amp;gt;(&#039;&#039;e.g.&#039;&#039; &amp;lt;span style=&amp;quot;background-color:#f39c12;&amp;quot;&amp;gt;longhorn42@bme-jupiter.bme.utexas.edu&amp;lt;/span&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
From off campus, you need to use UT VPN to ssh into jupiter or sugar.&lt;br /&gt;
https://wikis.utexas.edu/display/engritgpublic/Connecting+to+the+University+of+Texas+VPN&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;More instructions if you are using mobaxterm:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* make sure connected via VPN&lt;br /&gt;
* Start mobxterm and use Tools/mobakeygen to generate a pair of public and private keys. Save both.&lt;br /&gt;
* Append your public key to .ssh/authprized_keys (you can ask for help if you are remote)&lt;br /&gt;
* Create a new session in mobaxterm, under Advanced ssh setting, host: bme-jupiter.bme.utexas.edu, username: xxx, &#039;&#039;&#039;and specify your private key&#039;&#039;&#039; you saved above.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;your home dir is on uranus&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
uranus is now obsolete. Uranus replaced uranus as the header node.&lt;br /&gt;
&lt;br /&gt;
bme-uranus.bme.utexas.edu (node199, 10.0.0.199) is the header node of our computer cluster where all your home directory and files are stored. Your home directory (echo $HOME) is located either in /home or /users which is physically located on uranus . It can be accessed from any nodes and workstations in the lab. From uranus, you can start your job by doing &amp;quot;ssh node120 xxx” where xxx is your simulation script. You can write your own script to submit a bunch of job to these nodes (check the availability and skip if the node is busy). Your home directory is shared among uranus and all nodes vis NFS.&lt;br /&gt;
&lt;br /&gt;
(More about lab cluster structure at the end of page)&lt;br /&gt;
&lt;br /&gt;
Your home directory has a limit (quota) on space and file number and you won&#039;t be able to create new files once it is reached.&lt;br /&gt;
&lt;br /&gt;
Even you see your home folder on all WS/nodes in the lab but they are actually doing so remotely (hence use /scratch that is local on each node for serious jobs).&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;where to run simulations &amp;amp; analysis&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
The home dir on uranus is accessible on all nodes. But when you perform calculations on the nodes/WS in your home directory, it is actually accessing the files on uranus through network. It is convenient to run relatively short simulations, store the output files and perform quick analysis directly in your home directory. But because all members in the lab share home dir on uranus, it could stress out the system if several demanding simulations/trajectory analyses are performed at the same time on files in your home dir on uranus.&lt;br /&gt;
&lt;br /&gt;
So for demanding calculations, please use &#039;&#039;&#039;/work (mounted from sun.bme.utexas.edu) and /work2 (from uranus.bme.utexas.edu) &#039;&#039;&#039;as working directories. &amp;quot;sun and uranus&amp;quot; are also shared among all nodes like uranus. But this way we spread out the burden among 3 servers. If you ahve an active projecta nd expect to produce sunstaitnal amount files, let me know and I will created folder for you on /work and /work2. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#f39c12&amp;quot;&amp;gt;Keep uranus(your home directory) clean and efficient for everyone including yourself.&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
For QM and highly disk intensive tasks, we also use local &amp;quot;&#039;&#039;&#039;/scratch&#039;&#039;&#039;&amp;quot; disk. This space is large (100s GB) but is &amp;quot;local&amp;quot; meaning only accessible on specific node (after you ssh into it).&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;pre&amp;gt;When submitting a command, use the following. This will run it in the background and redirect output that would print to the screen to a file &amp;quot;nohup.out&amp;quot;. This prevents it from terminating when you logout or close the terminal.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nohup your_command &amp;amp;&amp;quot;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;quot;less +F file_name&amp;quot; to have constantly updated end of file on screen&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Lab cluster usage monitoring and signup ==&lt;br /&gt;
&lt;br /&gt;
The node activities can be monitored here:&lt;br /&gt;
&lt;br /&gt;
 https://biomolmd.org/pren/nodes.html&lt;br /&gt;
 https://biomolmd.org/liuchw/jobs.txt&lt;br /&gt;
 &lt;br /&gt;
 &#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff33;&amp;quot;&amp;gt;Complete CPU/GPU usage &amp;amp; sign up spreadsheet&amp;lt;/span&amp;gt; &#039;&#039;&#039;(email pren to request permission to edit): [https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Utilities ==&lt;br /&gt;
&lt;br /&gt;
We don’t have a job queuing system (yet) so you just log into a node to run your job.&lt;br /&gt;
&lt;br /&gt;
 Use &amp;quot;top&amp;quot; to check the load on a node. 600% means 6 cores are fully loaded.&lt;br /&gt;
 &amp;quot;less /proc/cpuinfo&amp;quot; to check how many CPU cores/threads on a node&lt;br /&gt;
 &amp;quot;free -g&amp;quot; to check free memory (esp. for QM jobs). The line &amp;quot;-/+ buffers/cache:&amp;quot; has the real number for free space&lt;br /&gt;
 &amp;quot;echo &amp;gt; large_file_name&amp;quot; to empty a large file quickly. rm can be slow&lt;br /&gt;
 &amp;quot;df -h&amp;quot; to check available storage (disk space)&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
More tips about Lnux commands and uitlies:&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit?usp=sharing https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit?usp=sharing]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Backups ==&lt;br /&gt;
&lt;br /&gt;
All home directories (/home, /users, /opt, /work, /work2) are backed up twice a week for ~ 2 weeks on bigdata.bme.utexas.edu. If you need to recover any files from last couple of&amp;amp;nbsp;weeks, you should be able to find them there. Log into bigdata, cd /bigdata/renlab/.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Cluster structure ==&lt;br /&gt;
&lt;br /&gt;
uranus.bme.utexas.edu is the header node for all computing nodes (nodexxx) that can only be accessed from uranus. The /home, /users, /opt folders are all part of uranus file system. The computing nodes have private IP address so can not be seen from outside including your WS or laptop. Each mode has a large local /scratch&amp;quot; folder that writable by everyone. &amp;quot;sun and uranus&amp;quot; are another two large servers mounted as /work and /work2 on each WS and computing node. You can use them just like the home dir. bigdata is the backup server.&lt;br /&gt;
&lt;br /&gt;
Read the pdf below for an illustration (replace NOVA with uranus)&lt;br /&gt;
&lt;br /&gt;
Current login nodes are bme-jupiter and bme-sugar and UT VPN is required&lt;br /&gt;
&lt;br /&gt;
[[File:LabCluster.pdf|200px|thumb|left|alt text]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2144</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2144"/>
		<updated>2025-10-15T14:50:05Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Purposes */ links&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker source from https://github.com/TinkerTools/tinker&amp;lt;nowiki/&amp;gt;and executables from https://github.com/TinkerTools/tinker-ffe/releases/tag/v25.5 or  [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. Linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the opportunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
If you want to build a peptide from a sequence, you can use tinker &amp;quot;protein.x&amp;quot; command, for example, ACE-ALA-NME, while create/use a tinker.key to specify which force field (with one line as below).&lt;br /&gt;
 parameters /path/to/amoebabio18.prm&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equlibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to spede up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error. &lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be.&amp;amp;nbsp;Water/ions are&amp;amp;nbsp;relaxed after this step. &lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run&amp;amp;nbsp;1.5&amp;amp;nbsp;ns NPT to compute the average density/box size (ignore the first 300ps). &#039;&#039;&#039;For GPU, only &amp;quot;barostat MonteCarlo&amp;quot; is available.&#039;&#039;&#039;&amp;amp;nbsp; &lt;br /&gt;
**NVT MD for ~2ns with box fixed at the average lengths from above. &lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Fundamental theory of AMOEBA multipoles:&#039;&#039;&#039; ===&lt;br /&gt;
[[Tutorial:amm#Molecular Mechanics and Force Fields (AMOEBA, AMOEBA+)]]&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
&lt;br /&gt;
=== Suggested Tinker Key File for AMOEBA+ Condensed Phase Simulations ===&lt;br /&gt;
 EWALD&lt;br /&gt;
 EWALD-CUTOFF      9.0 # for real space Ewald and charge penetration&lt;br /&gt;
 &lt;br /&gt;
 NEIGHBOR-LIST&lt;br /&gt;
 &lt;br /&gt;
 VDW-CUTOFF        12.0 # for vdw term&lt;br /&gt;
 CHGTRN-CUTOFF     12.0 # for charge transfer term&lt;br /&gt;
 VDW-CORRECTION&lt;br /&gt;
 &lt;br /&gt;
 INTEGRATOR  RESPA&lt;br /&gt;
 THERMOSTAT  BUSSI&lt;br /&gt;
 BAROSTAT    MONTECARLO&lt;br /&gt;
 &lt;br /&gt;
 POLAR-PREDICT&lt;br /&gt;
 POLAR-EPS 0.00001&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2072</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2072"/>
		<updated>2025-01-16T15:20:39Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Tutorials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker executables from [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the oppurtunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomolmd.org/pren/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equlibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to spede up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error. &lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be.&amp;amp;nbsp;Water/ions are&amp;amp;nbsp;relaxed after this step. &lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run&amp;amp;nbsp;1.5&amp;amp;nbsp;ns NPT to compute the average density/box size (ignore the first 300ps). &#039;&#039;&#039;For GPU, only &amp;quot;barostat MonteCarlo&amp;quot; is available.&#039;&#039;&#039;&amp;amp;nbsp; &lt;br /&gt;
**NVT MD for ~2ns with box fixed at the average lengths from above. &lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
	&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2071</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2071"/>
		<updated>2025-01-16T15:19:40Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Tutorials */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker executables from [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the oppurtunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomolmd.org/pren/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equlibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to spede up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error. &lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be.&amp;amp;nbsp;Water/ions are&amp;amp;nbsp;relaxed after this step. &lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run&amp;amp;nbsp;1.5&amp;amp;nbsp;ns NPT to compute the average density/box size (ignore the first 300ps). &#039;&#039;&#039;For GPU, only &amp;quot;barostat MonteCarlo&amp;quot; is available.&#039;&#039;&#039;&amp;amp;nbsp; &lt;br /&gt;
**NVT MD for ~2ns with box fixed at the average lengths from above. &lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
	&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Lab:labinfo&amp;diff=2070</id>
		<title>Lab:labinfo</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Lab:labinfo&amp;diff=2070"/>
		<updated>2024-12-19T17:01:28Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Graduate students fellowships */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Welcome, Ren Lab Members! =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== General&amp;amp;nbsp;Information ==&lt;br /&gt;
&lt;br /&gt;
=== Lab Website ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/ https://biomol.bme.utexas.edu/] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Lab Office Number ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;BME 3.516&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
=== How to Find Lab ===&lt;br /&gt;
&lt;br /&gt;
* Go to the 3rd floor of BME (ground floor on Dean Keeton side, next floor up on the South side)&lt;br /&gt;
* There is a hallway on the west side of the building that runs north-south&lt;br /&gt;
* if you come in from the lobby it is on the right side of the building running straight back&lt;br /&gt;
* the last door at the end of the hallway (located near Stair 3)&lt;br /&gt;
&lt;br /&gt;
=== Dr. Ren&#039;s Office Number ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;BME 5.202M&#039;&#039;&#039; (located in 5th floor faculty suite)&lt;br /&gt;
&lt;br /&gt;
== Communication and File Sharing ==&lt;br /&gt;
&lt;br /&gt;
=== Slack ===&lt;br /&gt;
&lt;br /&gt;
*utren.slack.com &lt;br /&gt;
*accounts will be created for new lab members/rotation students &lt;br /&gt;
*noteworthy channels&lt;br /&gt;
*##software for discussing various lab software + issues&lt;br /&gt;
*##cat for sending cat pics&lt;br /&gt;
*##paper-literature for sharing helpful papers + interesting new general papers&lt;br /&gt;
*##amoebaplus&lt;br /&gt;
*##poltype&lt;br /&gt;
*##general - general Ren lab stuff&lt;br /&gt;
*##allinclude - basically general but including some Schnieders lab members&lt;br /&gt;
&lt;br /&gt;
=== Lab Contacts ===&lt;br /&gt;
https://docs.google.com/spreadsheets/d/1Lea3_EAsVyOcMja7Ox_mNfj8ZNzj6Dupd8w5dNuFr4I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Lab Meetings ===&lt;br /&gt;
&lt;br /&gt;
https://docs.google.com/spreadsheets/d/133vg99syg17xPR-H-UH0B2gLlC9469AFAwMQx2LGn4s/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Individual Meetings ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1yLw5xenlOgIdsylFVk4fDnu7s5juZvgFgU8ztYvMfQE/edit?pli=1#gid=0 https://docs.google.com/spreadsheets/d/1yLw5xenlOgIdsylFVk4fDnu7s5juZvgFgU8ztYvMfQE/edit?pli=1#gid=0] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Cluster Sign-Up Sheet ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?pli=1#gid=0 https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?pli=1#gid=0]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== AMMM Meeting Sign-Up Sheet (Summer) ===&lt;br /&gt;
https://docs.google.com/document/d/1Pn2ZhHBQ82miVhl6CGG0zj2rMQxTLvTznrGColcNYhQ/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Suggested Literature (in Box) ===&lt;br /&gt;
&lt;br /&gt;
[https://utexas.app.box.com/folder/103794407727 https://utexas.app.box.com/folder/103794407727] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Learning and reading ==&lt;br /&gt;
You are expected to learn from your labmates and by reading literature regularly. Most learnings in grad school/postdoc training are not from classroom!&lt;br /&gt;
&lt;br /&gt;
You will run MD simulations and free energy calculations, using polarizable force field AMOEBA. These are expertise our lab has developed over past two decades so anyone to graduate from this lab should understand how and why on the following relevant subjects. You all should spend time read papers and documents I have been sharing. If you don&#039;t understand what you do and only run others&#039; scripts to get numbers, you won&#039;t go far.&lt;br /&gt;
* Polarizable multipole force field AMOEBA. why and how&lt;br /&gt;
** Understand AMOEBA model (read slides and latest review paper Jing et al)&lt;br /&gt;
** Using POLTYPE to get parameters and understand what POLTYPE is doing (read POLTYPE papers)&lt;br /&gt;
* Hydration free energy. Salt effect and charge correction (if solute has net charge)&lt;br /&gt;
** FEP and BAR&lt;br /&gt;
** Other methods including TI and WHAM (PMF)&lt;br /&gt;
&lt;br /&gt;
* Binding free energy calculations&lt;br /&gt;
** restraint and standard state correction&lt;br /&gt;
** Neutralizing counter ion and background salt; what to do when ligand has net charge&lt;br /&gt;
** It is OK to use other&#039;s script (Brandon, CW) to set thing up and learn. But you need to know what the program is doing, how and why again.&lt;br /&gt;
* How to compile Tinker CPU and GPU code&lt;br /&gt;
&lt;br /&gt;
* Advanced models/enhanced sampling methods&lt;br /&gt;
** AMOEBA+&lt;br /&gt;
** AI based models&lt;br /&gt;
** Adaptive biasing force (ABF)&lt;br /&gt;
** Metadynamics (well tempered)&lt;br /&gt;
** OSRW&lt;br /&gt;
** few years ago our lab members did a seminar course together and covered a wide range of topics: https://biomol.bme.utexas.edu/wiki/index.php?title=Course:ABS&lt;br /&gt;
&lt;br /&gt;
Many topics above found on lab wiki (https://biomol.bme.utexas.edu/tinkergpu) and a BOX folder I shared with lab members (for example AMOEBA folder has slides and papers introducing AMOEBA). If you don&#039;t have/see anything or have question, contact asap. &lt;br /&gt;
It is important to establish a routine, setting aside time to read regularly (daily, weekly). I would start from basic and whatever relevant to what you are doing now and gradually cover more and more.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Lab policy &amp;amp; resource =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Financial support ===&lt;br /&gt;
&lt;br /&gt;
PhD students are typically fully supported via either GRA ot TA. However funding is not always guaranteed. Studenst and postdocs are expected to work deligently and be productive, which in turn will help us to secure the funding to support your stipend, fringe, tuition and other expense.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Work schedule ===&lt;br /&gt;
&lt;br /&gt;
Postdocs are required to fill in time sheet per university policy. While we don&#039;t require everyone follow a fixed schedule, everyone is expected to follow &amp;quot;reasonable&amp;quot; working hours (e.g. 9am - 5pm). People who show chronic tardiness and fail to comply after multiple warnings will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
=== Vocation and leave  ===&lt;br /&gt;
Graduate students and postdocs are supported by either state or federal funds (including TA and RA ship). You are considered employees (hence the benefit etc.). We typically observe the university official holiday and vacation policy (http://www.utexas.edu/hr/holiday/ and http://www.utexas.edu/hr/current/leave/annual.html). You are allowed to take 4 weeks off for vacation each year, holidays and sick days not included. &#039;&#039;&#039;Please consult with PI in advance to plan on a vacation.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Please note&#039;&#039;&#039;Winter, spring and summer breaks are NOT vacation time&#039;&#039;&#039;. These are breaks for classes and undergraduate students, not for staff and employees. You can certainly take vacations during the breaks (use against the 4-week a year vacation time).&lt;br /&gt;
&lt;br /&gt;
You need to consult with PI for longer/extended leave. You may not expect financial support for the extended leave. &lt;br /&gt;
&lt;br /&gt;
We expect students to respect the rules and work diligently, which is essential for us to to receive funding to support everyone in the lab.&lt;br /&gt;
&lt;br /&gt;
=== Lab Resource ===&lt;br /&gt;
&lt;br /&gt;
When use the cluster, be considerate. Don&#039;t spread your job all over the nodes (use all the processors on one node before using other nodes), so that others that need the multiprocessors can utilize them.&lt;br /&gt;
&lt;br /&gt;
CPU &amp;amp; GPU resources in the lab (email Dr. Ren if you need write permission) https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit#gid=0&lt;br /&gt;
&lt;br /&gt;
More about using the cluster: https://biomolmd.org/mw/index.php/Lab:newuser&lt;br /&gt;
&lt;br /&gt;
=== Lab Responsibility ===&lt;br /&gt;
&lt;br /&gt;
Each of you will share some lab responsibility, such as maintenance, purchasing, organizing group meeting etc. Senior lab members are expected to advise and help out new lab members on research.&lt;br /&gt;
&lt;br /&gt;
=== Lab security  ===&lt;br /&gt;
&lt;br /&gt;
* Do not use university resource for personal use.&lt;br /&gt;
&lt;br /&gt;
* Do not install or alter operating system and software, change system setting or have root privileges (including sudo) on lab computers/workstations/laptops, unless with explicit permission from PI.&lt;br /&gt;
&lt;br /&gt;
* You are responsible to make sure your workstation and user account (password) are secure. &lt;br /&gt;
&lt;br /&gt;
* The university monitors the internet activity of every network port. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;Always lock the door when you are the last one to leave.&lt;br /&gt;
&lt;br /&gt;
=== Meetings and Conference  ===&lt;br /&gt;
&lt;br /&gt;
*Funding&lt;br /&gt;
&lt;br /&gt;
The lab provides support for each of you to go to meetings and conferences to present your work in orals or posters. The amount ($500 - $1000 a year) depends on funding availability and your presentation (oral has higher priority) etc. You are also strongly encouraged to seek for support from department, college and society etc, many in the format of award. &lt;br /&gt;
&lt;br /&gt;
Oral presentations receives a higher priority for support than posters.&lt;br /&gt;
&lt;br /&gt;
*Save all your receipts and program documents etc.&lt;br /&gt;
*Send me the following in electronic format (word doc, PDF) &lt;br /&gt;
**Your abstract before submission for me to check &lt;br /&gt;
**Published abstract (web print or scanned pdf)&lt;br /&gt;
**Official program page that has your presentation or poster title and author names (web print or scanned pdf is fine).&lt;br /&gt;
**The final powerpoint files for presentation or poster&lt;br /&gt;
===Graduate students fellowships===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NSF https://www.nsfgrfp.org/ NSF&lt;br /&gt;
&lt;br /&gt;
NDSEG https://ndseg.sysplus.com/ &lt;br /&gt;
&lt;br /&gt;
NIH  https://researchtraining.nih.gov/programs/fellowships &lt;br /&gt;
&lt;br /&gt;
American heart https://professional.heart.org/en/research-programs/aha-funding-opportunities/predoctoral-fellowship &lt;br /&gt;
&lt;br /&gt;
MSU resource: https://libguides.lib.msu.edu/c.php?g=96743&amp;amp;p=622546&lt;br /&gt;
&lt;br /&gt;
SMART: https://www.smartscholarship.org/smart/en&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Fellowship Databases: ==&lt;br /&gt;
&lt;br /&gt;
[http://www.grad.nd.edu/gfd/ https://gradschool.cornell.edu/fellowships]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.lib.msu.edu/harris23/grants/3gradinf.htm#a https://awardsdatabase.usc.edu/]&lt;br /&gt;
&lt;br /&gt;
[http://grad.berkeley.edu/news/headlines/guide-to-fellowships-grants/ http://grad.berkeley.edu/news/headlines/guide-to-fellowships-grants/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Technical reading materials =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Molecular Modeling ==&lt;br /&gt;
&lt;br /&gt;
 Book: Molecular Modelling, Principles and Pllications, Andrew Leach&lt;br /&gt;
 Computer simulations of liquids, Allen &amp;amp; Tildesley&lt;br /&gt;
 Book: Molecular Simulations, Frenkel and Smit&lt;br /&gt;
&lt;br /&gt;
You can use Google to find these books online.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Free energy ==&lt;br /&gt;
&lt;br /&gt;
Book:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;Free energy Calculations, Theory and Applications in Chemistry and Biology&#039;&#039;&#039;, Chipot and Pophorille, Springer&lt;br /&gt;
&lt;br /&gt;
Review by Simonson &amp;amp; Roux (charge correction/solution-gas-phase): Concepts and protocols for electrostatic free energies&lt;br /&gt;
&lt;br /&gt;
 [https://utexas.box.com/s/fx8ixqhz9zj9i5ebv3rzrgclwiighnd6 https://utexas.box.com/s/fx8ixqhz9zj9i5ebv3rzrgclwiighnd6]&lt;br /&gt;
&lt;br /&gt;
More about charge corrections when system/ligand being disappeared is not neutral&lt;br /&gt;
&lt;br /&gt;
 [https://utexas.box.com/s/nj6jcufmms5hs1xqu5pywkwp3kax3y6k https://utexas.box.com/s/nj6jcufmms5hs1xqu5pywkwp3kax3y6k]&lt;br /&gt;
&lt;br /&gt;
== Force Fields ==&lt;br /&gt;
&lt;br /&gt;
MSI force field handbook:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;[https://utexas.box.com/s/ge7f4q6svq5ammy736c7d729ms6jxzzw https://utexas.box.com/s/ge7f4q6svq5ammy736c7d729ms6jxzzw]&lt;br /&gt;
&lt;br /&gt;
== Molecular binding termodynamics &amp;amp; simlations ==&lt;br /&gt;
&lt;br /&gt;
Gilson &amp;amp; Zhou&lt;br /&gt;
&lt;br /&gt;
  [https://utexas.box.com/s/esttb5govnir7mvnvydcid4ukv7nxmnc https://utexas.box.com/s/esttb5govnir7mvnvydcid4ukv7nxmnc]&lt;br /&gt;
  [https://utexas.box.com/s/dugh8ba95gf8v0fnsnzf6a63beu47qee https://utexas.box.com/s/dugh8ba95gf8v0fnsnzf6a63beu47qee]&lt;br /&gt;
  [https://utexas.box.com/s/p2fcjdzdssuxicopv5mkl843grrjinoh https://utexas.box.com/s/p2fcjdzdssuxicopv5mkl843grrjinoh] &lt;br /&gt;
&lt;br /&gt;
Hamelberg &amp;amp; McCammon&lt;br /&gt;
&lt;br /&gt;
  [https://utexas.box.com/s/bsayz0jmfgd7o8ibx0pqtkoqwuk108tm https://utexas.box.com/s/bsayz0jmfgd7o8ibx0pqtkoqwuk108tm]&lt;br /&gt;
&lt;br /&gt;
Ren lab:&lt;br /&gt;
&lt;br /&gt;
  [http://www.pnas.org/content/pnas/105/17/6290.full.pdf http://www.pnas.org/content/pnas/105/17/6290.full.pdf]&lt;br /&gt;
&lt;br /&gt;
== Data analysis ==&lt;br /&gt;
&lt;br /&gt;
 R for Data Science: [http://r4ds.had.co.nz/ http://r4ds.had.co.nz/]&lt;br /&gt;
&lt;br /&gt;
= Writing =&lt;br /&gt;
&lt;br /&gt;
== Writing a scientific paper, step by painful step by Kevin D. Lafferty ==&lt;br /&gt;
&lt;br /&gt;
  [http://trophiccascades.forestry.oregonstate.edu/sites/trophic/files/Lafferty_WritingScientificPaper.pdf http://trophiccascades.forestry.oregonstate.edu/sites/trophic/files/Lafferty_WritingScientificPaper.pdf] &lt;br /&gt;
&lt;br /&gt;
== Recipe for a Quality Scientific Paper: Fulfill Readers&amp;amp;nbsp;and Reviewers&amp;amp;nbsp;Expectations ==&lt;br /&gt;
&lt;br /&gt;
 Prof Yaoqi Zhou [https://utexas.box.com/s/m93b92gwzcxgi1iw8qw7gdf6z7duzmm1 https://utexas.box.com/s/m93b92gwzcxgi1iw8qw7gdf6z7duzmm1] &lt;br /&gt;
&lt;br /&gt;
== Making better figures ==&lt;br /&gt;
&lt;br /&gt;
  [http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003833 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003833]&lt;br /&gt;
&lt;br /&gt;
== 21 suggestions ==&lt;br /&gt;
&lt;br /&gt;
 [https://www.scitechedit.com/images/21_writing_tips.pdf https://www.scitechedit.com/images/21_writing_tips.pdf] &lt;br /&gt;
&lt;br /&gt;
== Ten simple rules for structuring papers ==&lt;br /&gt;
&lt;br /&gt;
 [http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Literature search =&lt;br /&gt;
&lt;br /&gt;
pubmed:&amp;amp;nbsp;[https://www.ncbi.nlm.nih.gov/pubmed/ https://www.ncbi.nlm.nih.gov/pubmed/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Web of science (use UT eid when off campus):&amp;amp;nbsp;[https://guides.lib.utexas.edu/az.php?a=w https://guides.lib.utexas.edu/az.php?a=w]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hot paper search&amp;amp;nbsp;[https://www.oligotherapeutics.org/hot-papers-search/ https://www.oligotherapeutics.org/hot-papers-search/]&lt;br /&gt;
&lt;br /&gt;
Off campus access&amp;amp;nbsp;to paper download&amp;amp;nbsp;via ezproxy:&amp;amp;nbsp;[https://legacy.lib.utexas.edu/help/proxy.html#subscription https://legacy.lib.utexas.edu/help/proxy.html#subscription]&lt;br /&gt;
&lt;br /&gt;
Check out resources (including classes) offered by university library&lt;br /&gt;
&lt;br /&gt;
= Presentation =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#1f497d&amp;quot;&amp;gt;[http://blogs.nature.com/naturejobs/2017/01/11/scientific-presentations-a-cheat-sheet/ http://blogs.nature.com/naturejobs/2017/01/11/scientific-presentations-a-cheat-sheet/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#1f497d&amp;quot;&amp;gt;[http://www.nextscientist.com/improve-presentation-skills-of-phd-students/ http://www.nextscientist.com/improve-presentation-skills-of-phd-students/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Career Development =&lt;br /&gt;
&lt;br /&gt;
== The Professor Is In: The Essential Guide To Turning Your Ph.D. Into a Job==&lt;br /&gt;
&lt;br /&gt;
 [https://www.amazon.com/Professor-Essential-Guide-Turning-Ph-D/dp/0553419420 https://www.amazon.com/Professor-Essential-Guide-Turning-Ph-D/dp/0553419420]&lt;br /&gt;
&lt;br /&gt;
 Some contents are inspired by&amp;amp;nbsp;[https://twitter.com/thehauer/status/1021179403680862218?s=19 https://twitter.com/thehauer/status/1021179403680862218?s=19] &lt;br /&gt;
== Communication kit ==&lt;br /&gt;
&lt;br /&gt;
nstructions on writing cover letters, formatting CVs, writing abstracts, personal statements, etc.&lt;br /&gt;
&lt;br /&gt;
[http://mitcommlab.mit.edu/be/use-the-commkit/ http://mitcommlab.mit.edu/be/use-the-commkit/]&lt;br /&gt;
&lt;br /&gt;
== Lab Resources ==&lt;br /&gt;
&lt;br /&gt;
===Disk spaces ===&lt;br /&gt;
Your home dir is in /home/YOURUSERNAME, which is physically on Nova and space is limited. But each of you have space in /work/YOURUSERNAME (physically on SUN), which is at least 2 TB (more if needed). You can access home and work dir similarly on all computers in the lab. If you have MD jobs producing large trajectories and you wan to keep them for analysis (until paper pub), please use /work. You can check your space and quota limits in /opt/quota.* Once you reach quota you can not log in or execute commands.&lt;br /&gt;
===Using Lab Cluster===&lt;br /&gt;
[[Lab:newuser| new user set up to access lab cluster]]&lt;br /&gt;
&lt;br /&gt;
=== Cluster Monitoring ===&lt;br /&gt;
https://biomol.bme.utexas.edu/~pren/nodes.html &lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing CPU &amp;amp; GPU resource sign up]&lt;br /&gt;
&lt;br /&gt;
=== GPU Monitoring ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/~rq875/checkgpu.log https://biomol.bme.utexas.edu/~rq875/checkgpu.log] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Tinker Tutorials ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut] &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Poltype Github ===&lt;br /&gt;
&lt;br /&gt;
https://github.com/TinkerTools/poltype2&lt;br /&gt;
&lt;br /&gt;
=== Linux Utilities ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Lab Guide for Grad Students ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1PKyWNTntusPeRrOiGaLAkUvJbuuc4cVBfE4Lo9ZMt2I/edit https://docs.google.com/document/d/1PKyWNTntusPeRrOiGaLAkUvJbuuc4cVBfE4Lo9ZMt2I/edit] &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== UT Resources ==&lt;br /&gt;
&lt;br /&gt;
=== Ombuds ===&lt;br /&gt;
&lt;br /&gt;
*[https://ombuds.utexas.edu/student/about-us https://ombuds.utexas.edu/student/about-us] &lt;br /&gt;
*Can listen to your concerns, give advice, and direct you to resources &lt;br /&gt;
&lt;br /&gt;
=== Employee Assistance Program ===&lt;br /&gt;
&lt;br /&gt;
Counseling&lt;br /&gt;
&lt;br /&gt;
*[https://eap.utexas.edu/counseling-consultations https://eap.utexas.edu/counseling-consultations]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Wellness (sometimes has fitness videos)&lt;br /&gt;
&lt;br /&gt;
*[https://healthpoint.utexas.edu/ https://healthpoint.utexas.edu/]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Night rides (Lyft discount) ===&lt;br /&gt;
&lt;br /&gt;
*[https://parking.utexas.edu/night https://parking.utexas.edu/night]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== University Health Services ===&lt;br /&gt;
&lt;br /&gt;
*List of services [https://www.healthyhorns.utexas.edu/appointments.html#services https://www.healthyhorns.utexas.edu/appointments.html#services]&amp;amp;nbsp; &lt;br /&gt;
*As employees, a lot of care is free. Sometimes there is a copay, but it is very affordable usually &lt;br /&gt;
&lt;br /&gt;
COVID testing&lt;br /&gt;
&lt;br /&gt;
*[https://www.healthyhorns.utexas.edu/coronavirus_testing.html https://www.healthyhorns.utexas.edu/coronavirus_testing.html]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Women’s Health&lt;br /&gt;
&lt;br /&gt;
*[https://www.healthyhorns.utexas.edu/womenshealth.html https://www.healthyhorns.utexas.edu/womenshealth.html]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Free nurse advice line&lt;br /&gt;
&lt;br /&gt;
*[https://healthpoint.utexas.edu/247-nurse-line https://healthpoint.utexas.edu/247-nurse-line]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Student Emergency Services ===&lt;br /&gt;
&lt;br /&gt;
Services offered [https://deanofstudents.utexas.edu/emergency/howwecanhelp.php https://deanofstudents.utexas.edu/emergency/howwecanhelp.php]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Student Emergency Fund&lt;br /&gt;
&lt;br /&gt;
*[https://deanofstudents.utexas.edu/emergency/studentemergencyfund.php https://deanofstudents.utexas.edu/emergency/studentemergencyfund.php]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Services for Students with Disabilities ===&lt;br /&gt;
&lt;br /&gt;
*[https://diversity.utexas.edu/disability/about/ https://diversity.utexas.edu/disability/about/]&amp;amp;nbsp; &lt;br /&gt;
*The process is a bit difficult sometimes, be aware &lt;br /&gt;
&lt;br /&gt;
== Life in Austin ==&lt;br /&gt;
&lt;br /&gt;
=== Coffee Shops ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/4nDa3AMZDFoTA9FTA https://goo.gl/maps/4nDa3AMZDFoTA9FTA] &lt;br /&gt;
&lt;br /&gt;
=== Food ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/v4fQHJ4YhYtMrNh29 https://goo.gl/maps/v4fQHJ4YhYtMrNh29]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Essential Stores ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/iTLRvaAf4anVkm7j6 https://goo.gl/maps/iTLRvaAf4anVkm7j6]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Outdoor Landmarks / Hiking ===&lt;br /&gt;
&lt;br /&gt;
Highest point in Austin, not much of an actual hike&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/nd2aAXqoyVPivADH6 https://goo.gl/maps/nd2aAXqoyVPivADH6]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Pennybacker Bridge (park on side of road, can go up either side of road)&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/zfYHwUkRTYwTQfu69 https://goo.gl/maps/zfYHwUkRTYwTQfu69]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Overlook&amp;amp;nbsp;Trail (3ish miles each way, nice overlook part way, decent elevation change)&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/Cx9YdkuQWWmKBGAe9 https://goo.gl/maps/Cx9YdkuQWWmKBGAe9]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Bat Observation&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/ZHfnn54qKY6icEq3A https://goo.gl/maps/ZHfnn54qKY6icEq3A] &lt;br /&gt;
*Austin has a bat colony. The bats migrate but they like to hang out under the Congress bridge. &lt;br /&gt;
*You can park in a paid lot or take the bus&amp;amp;nbsp;and watch the bats fly sometime around sunset. You can also watch the bats from the river or on top of the bridge. &lt;br /&gt;
*It’s really neat and an Austin staple.&amp;amp;nbsp;Sometimes there are a lot of people. &lt;br /&gt;
&lt;br /&gt;
Parks to wander around near campus&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/fRs2w2LCX7emZNuWA https://goo.gl/maps/fRs2w2LCX7emZNuWA] &lt;br /&gt;
*[https://goo.gl/maps/Vu7L1DZDevn1FXNG6 https://goo.gl/maps/Vu7L1DZDevn1FXNG6] &lt;br /&gt;
*[https://goo.gl/maps/2qn9a8U1w3ZZY72u9 https://goo.gl/maps/2qn9a8U1w3ZZY72u9]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Pet Care Resources ===&lt;br /&gt;
&lt;br /&gt;
*Sometimes you can get pet supplies at the APA thrift stores &lt;br /&gt;
*Austin is very dog friendly and has many dog parks &lt;br /&gt;
&lt;br /&gt;
Great web resources&lt;br /&gt;
&lt;br /&gt;
*[https://www.austinpetdoctor.com/pet-education-center/ https://www.austinpetdoctor.com/pet-education-center/]&amp;amp;nbsp; &lt;br /&gt;
*[https://goo.gl/maps/SHm6N2Xgrdptcfsx7 https://goo.gl/maps/SHm6N2Xgrdptcfsx7] &lt;br /&gt;
*[https://goo.gl/maps/A4qmGfa6VQqomRFq9 https://goo.gl/maps/A4qmGfa6VQqomRFq9]&amp;amp;nbsp;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Lab:labinfo&amp;diff=2069</id>
		<title>Lab:labinfo</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Lab:labinfo&amp;diff=2069"/>
		<updated>2024-12-19T16:58:42Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Graduate students fellowships */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Welcome, Ren Lab Members! =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== General&amp;amp;nbsp;Information ==&lt;br /&gt;
&lt;br /&gt;
=== Lab Website ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/ https://biomol.bme.utexas.edu/] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Lab Office Number ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;BME 3.516&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
=== How to Find Lab ===&lt;br /&gt;
&lt;br /&gt;
* Go to the 3rd floor of BME (ground floor on Dean Keeton side, next floor up on the South side)&lt;br /&gt;
* There is a hallway on the west side of the building that runs north-south&lt;br /&gt;
* if you come in from the lobby it is on the right side of the building running straight back&lt;br /&gt;
* the last door at the end of the hallway (located near Stair 3)&lt;br /&gt;
&lt;br /&gt;
=== Dr. Ren&#039;s Office Number ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;BME 5.202M&#039;&#039;&#039; (located in 5th floor faculty suite)&lt;br /&gt;
&lt;br /&gt;
== Communication and File Sharing ==&lt;br /&gt;
&lt;br /&gt;
=== Slack ===&lt;br /&gt;
&lt;br /&gt;
*utren.slack.com &lt;br /&gt;
*accounts will be created for new lab members/rotation students &lt;br /&gt;
*noteworthy channels&lt;br /&gt;
*##software for discussing various lab software + issues&lt;br /&gt;
*##cat for sending cat pics&lt;br /&gt;
*##paper-literature for sharing helpful papers + interesting new general papers&lt;br /&gt;
*##amoebaplus&lt;br /&gt;
*##poltype&lt;br /&gt;
*##general - general Ren lab stuff&lt;br /&gt;
*##allinclude - basically general but including some Schnieders lab members&lt;br /&gt;
&lt;br /&gt;
=== Lab Contacts ===&lt;br /&gt;
https://docs.google.com/spreadsheets/d/1Lea3_EAsVyOcMja7Ox_mNfj8ZNzj6Dupd8w5dNuFr4I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Lab Meetings ===&lt;br /&gt;
&lt;br /&gt;
https://docs.google.com/spreadsheets/d/133vg99syg17xPR-H-UH0B2gLlC9469AFAwMQx2LGn4s/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Individual Meetings ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1yLw5xenlOgIdsylFVk4fDnu7s5juZvgFgU8ztYvMfQE/edit?pli=1#gid=0 https://docs.google.com/spreadsheets/d/1yLw5xenlOgIdsylFVk4fDnu7s5juZvgFgU8ztYvMfQE/edit?pli=1#gid=0] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Cluster Sign-Up Sheet ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?pli=1#gid=0 https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?pli=1#gid=0]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== AMMM Meeting Sign-Up Sheet (Summer) ===&lt;br /&gt;
https://docs.google.com/document/d/1Pn2ZhHBQ82miVhl6CGG0zj2rMQxTLvTznrGColcNYhQ/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Suggested Literature (in Box) ===&lt;br /&gt;
&lt;br /&gt;
[https://utexas.app.box.com/folder/103794407727 https://utexas.app.box.com/folder/103794407727] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Learning and reading ==&lt;br /&gt;
You are expected to learn from your labmates and by reading literature regularly. Most learnings in grad school/postdoc training are not from classroom!&lt;br /&gt;
&lt;br /&gt;
You will run MD simulations and free energy calculations, using polarizable force field AMOEBA. These are expertise our lab has developed over past two decades so anyone to graduate from this lab should understand how and why on the following relevant subjects. You all should spend time read papers and documents I have been sharing. If you don&#039;t understand what you do and only run others&#039; scripts to get numbers, you won&#039;t go far.&lt;br /&gt;
* Polarizable multipole force field AMOEBA. why and how&lt;br /&gt;
** Understand AMOEBA model (read slides and latest review paper Jing et al)&lt;br /&gt;
** Using POLTYPE to get parameters and understand what POLTYPE is doing (read POLTYPE papers)&lt;br /&gt;
* Hydration free energy. Salt effect and charge correction (if solute has net charge)&lt;br /&gt;
** FEP and BAR&lt;br /&gt;
** Other methods including TI and WHAM (PMF)&lt;br /&gt;
&lt;br /&gt;
* Binding free energy calculations&lt;br /&gt;
** restraint and standard state correction&lt;br /&gt;
** Neutralizing counter ion and background salt; what to do when ligand has net charge&lt;br /&gt;
** It is OK to use other&#039;s script (Brandon, CW) to set thing up and learn. But you need to know what the program is doing, how and why again.&lt;br /&gt;
* How to compile Tinker CPU and GPU code&lt;br /&gt;
&lt;br /&gt;
* Advanced models/enhanced sampling methods&lt;br /&gt;
** AMOEBA+&lt;br /&gt;
** AI based models&lt;br /&gt;
** Adaptive biasing force (ABF)&lt;br /&gt;
** Metadynamics (well tempered)&lt;br /&gt;
** OSRW&lt;br /&gt;
** few years ago our lab members did a seminar course together and covered a wide range of topics: https://biomol.bme.utexas.edu/wiki/index.php?title=Course:ABS&lt;br /&gt;
&lt;br /&gt;
Many topics above found on lab wiki (https://biomol.bme.utexas.edu/tinkergpu) and a BOX folder I shared with lab members (for example AMOEBA folder has slides and papers introducing AMOEBA). If you don&#039;t have/see anything or have question, contact asap. &lt;br /&gt;
It is important to establish a routine, setting aside time to read regularly (daily, weekly). I would start from basic and whatever relevant to what you are doing now and gradually cover more and more.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Lab policy &amp;amp; resource =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Financial support ===&lt;br /&gt;
&lt;br /&gt;
PhD students are typically fully supported via either GRA ot TA. However funding is not always guaranteed. Studenst and postdocs are expected to work deligently and be productive, which in turn will help us to secure the funding to support your stipend, fringe, tuition and other expense.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Work schedule ===&lt;br /&gt;
&lt;br /&gt;
Postdocs are required to fill in time sheet per university policy. While we don&#039;t require everyone follow a fixed schedule, everyone is expected to follow &amp;quot;reasonable&amp;quot; working hours (e.g. 9am - 5pm). People who show chronic tardiness and fail to comply after multiple warnings will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
=== Vocation and leave  ===&lt;br /&gt;
Graduate students and postdocs are supported by either state or federal funds (including TA and RA ship). You are considered employees (hence the benefit etc.). We typically observe the university official holiday and vacation policy (http://www.utexas.edu/hr/holiday/ and http://www.utexas.edu/hr/current/leave/annual.html). You are allowed to take 4 weeks off for vacation each year, holidays and sick days not included. &#039;&#039;&#039;Please consult with PI in advance to plan on a vacation.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Please note&#039;&#039;&#039;Winter, spring and summer breaks are NOT vacation time&#039;&#039;&#039;. These are breaks for classes and undergraduate students, not for staff and employees. You can certainly take vacations during the breaks (use against the 4-week a year vacation time).&lt;br /&gt;
&lt;br /&gt;
You need to consult with PI for longer/extended leave. You may not expect financial support for the extended leave. &lt;br /&gt;
&lt;br /&gt;
We expect students to respect the rules and work diligently, which is essential for us to to receive funding to support everyone in the lab.&lt;br /&gt;
&lt;br /&gt;
=== Lab Resource ===&lt;br /&gt;
&lt;br /&gt;
When use the cluster, be considerate. Don&#039;t spread your job all over the nodes (use all the processors on one node before using other nodes), so that others that need the multiprocessors can utilize them.&lt;br /&gt;
&lt;br /&gt;
CPU &amp;amp; GPU resources in the lab (email Dr. Ren if you need write permission) https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit#gid=0&lt;br /&gt;
&lt;br /&gt;
More about using the cluster: https://biomolmd.org/mw/index.php/Lab:newuser&lt;br /&gt;
&lt;br /&gt;
=== Lab Responsibility ===&lt;br /&gt;
&lt;br /&gt;
Each of you will share some lab responsibility, such as maintenance, purchasing, organizing group meeting etc. Senior lab members are expected to advise and help out new lab members on research.&lt;br /&gt;
&lt;br /&gt;
=== Lab security  ===&lt;br /&gt;
&lt;br /&gt;
* Do not use university resource for personal use.&lt;br /&gt;
&lt;br /&gt;
* Do not install or alter operating system and software, change system setting or have root privileges (including sudo) on lab computers/workstations/laptops, unless with explicit permission from PI.&lt;br /&gt;
&lt;br /&gt;
* You are responsible to make sure your workstation and user account (password) are secure. &lt;br /&gt;
&lt;br /&gt;
* The university monitors the internet activity of every network port. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;Always lock the door when you are the last one to leave.&lt;br /&gt;
&lt;br /&gt;
=== Meetings and Conference  ===&lt;br /&gt;
&lt;br /&gt;
*Funding&lt;br /&gt;
&lt;br /&gt;
The lab provides support for each of you to go to meetings and conferences to present your work in orals or posters. The amount ($500 - $1000 a year) depends on funding availability and your presentation (oral has higher priority) etc. You are also strongly encouraged to seek for support from department, college and society etc, many in the format of award. &lt;br /&gt;
&lt;br /&gt;
Oral presentations receives a higher priority for support than posters.&lt;br /&gt;
&lt;br /&gt;
*Save all your receipts and program documents etc.&lt;br /&gt;
*Send me the following in electronic format (word doc, PDF) &lt;br /&gt;
**Your abstract before submission for me to check &lt;br /&gt;
**Published abstract (web print or scanned pdf)&lt;br /&gt;
**Official program page that has your presentation or poster title and author names (web print or scanned pdf is fine).&lt;br /&gt;
**The final powerpoint files for presentation or poster&lt;br /&gt;
===Graduate students fellowships===&lt;br /&gt;
http://www.grad.nd.edu/gfd/&lt;br /&gt;
&lt;br /&gt;
http://www.lib.msu.edu/harris23/grants/3gradinf.htm#a&lt;br /&gt;
&lt;br /&gt;
NSF https://www.nsfgrfp.org/ NSF&lt;br /&gt;
&lt;br /&gt;
NDSEG https://ndseg.sysplus.com/ &lt;br /&gt;
&lt;br /&gt;
NIH  https://researchtraining.nih.gov/programs/fellowships &lt;br /&gt;
&lt;br /&gt;
American heart https://professional.heart.org/en/research-programs/aha-funding-opportunities/predoctoral-fellowship &lt;br /&gt;
&lt;br /&gt;
MSU resource: https://libguides.lib.msu.edu/c.php?g=96743&amp;amp;p=622546&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background:white&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size:10.5pt&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#222222&amp;quot;&amp;gt;NSF, [https://www.nsfgrfp.org/ https://www.nsfgrfp.org/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background:white&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size:10.5pt&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#222222&amp;quot;&amp;gt;NIH, [https://researchtraining.nih.gov/programs/fellowships/f31 https://researchtraining.nih.gov/programs/fellowships/f31]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size:10.5pt&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#222222&amp;quot;&amp;gt;America Heart Association [https://professional.heart.org/professional/ResearchPrograms/ApplicationInformation/UCM_443316_Predoctoral-Fellowship.jsp https://professional.heart.org/professional/ResearchPrograms/ApplicationInformation/UCM_443316_Predoctoral-Fellowship.jsp]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
SAMRT:&amp;amp;nbsp;[https://www.asee.org/fellowship-programs/graduate https://www.asee.org/fellowship-programs/graduate]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
NDSEG&amp;amp;nbsp;[https://ndseg.asee.org/ https://ndseg.asee.org/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Fellowship Databases: ==&lt;br /&gt;
&lt;br /&gt;
[http://www.grad.nd.edu/gfd/ https://gradschool.cornell.edu/fellowships]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.lib.msu.edu/harris23/grants/3gradinf.htm#a https://awardsdatabase.usc.edu/]&lt;br /&gt;
&lt;br /&gt;
[http://grad.berkeley.edu/news/headlines/guide-to-fellowships-grants/ http://grad.berkeley.edu/news/headlines/guide-to-fellowships-grants/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Technical reading materials =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Molecular Modeling ==&lt;br /&gt;
&lt;br /&gt;
 Book: Molecular Modelling, Principles and Pllications, Andrew Leach&lt;br /&gt;
 Computer simulations of liquids, Allen &amp;amp; Tildesley&lt;br /&gt;
 Book: Molecular Simulations, Frenkel and Smit&lt;br /&gt;
&lt;br /&gt;
You can use Google to find these books online.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Free energy ==&lt;br /&gt;
&lt;br /&gt;
Book:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;Free energy Calculations, Theory and Applications in Chemistry and Biology&#039;&#039;&#039;, Chipot and Pophorille, Springer&lt;br /&gt;
&lt;br /&gt;
Review by Simonson &amp;amp; Roux (charge correction/solution-gas-phase): Concepts and protocols for electrostatic free energies&lt;br /&gt;
&lt;br /&gt;
 [https://utexas.box.com/s/fx8ixqhz9zj9i5ebv3rzrgclwiighnd6 https://utexas.box.com/s/fx8ixqhz9zj9i5ebv3rzrgclwiighnd6]&lt;br /&gt;
&lt;br /&gt;
More about charge corrections when system/ligand being disappeared is not neutral&lt;br /&gt;
&lt;br /&gt;
 [https://utexas.box.com/s/nj6jcufmms5hs1xqu5pywkwp3kax3y6k https://utexas.box.com/s/nj6jcufmms5hs1xqu5pywkwp3kax3y6k]&lt;br /&gt;
&lt;br /&gt;
== Force Fields ==&lt;br /&gt;
&lt;br /&gt;
MSI force field handbook:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;[https://utexas.box.com/s/ge7f4q6svq5ammy736c7d729ms6jxzzw https://utexas.box.com/s/ge7f4q6svq5ammy736c7d729ms6jxzzw]&lt;br /&gt;
&lt;br /&gt;
== Molecular binding termodynamics &amp;amp; simlations ==&lt;br /&gt;
&lt;br /&gt;
Gilson &amp;amp; Zhou&lt;br /&gt;
&lt;br /&gt;
  [https://utexas.box.com/s/esttb5govnir7mvnvydcid4ukv7nxmnc https://utexas.box.com/s/esttb5govnir7mvnvydcid4ukv7nxmnc]&lt;br /&gt;
  [https://utexas.box.com/s/dugh8ba95gf8v0fnsnzf6a63beu47qee https://utexas.box.com/s/dugh8ba95gf8v0fnsnzf6a63beu47qee]&lt;br /&gt;
  [https://utexas.box.com/s/p2fcjdzdssuxicopv5mkl843grrjinoh https://utexas.box.com/s/p2fcjdzdssuxicopv5mkl843grrjinoh] &lt;br /&gt;
&lt;br /&gt;
Hamelberg &amp;amp; McCammon&lt;br /&gt;
&lt;br /&gt;
  [https://utexas.box.com/s/bsayz0jmfgd7o8ibx0pqtkoqwuk108tm https://utexas.box.com/s/bsayz0jmfgd7o8ibx0pqtkoqwuk108tm]&lt;br /&gt;
&lt;br /&gt;
Ren lab:&lt;br /&gt;
&lt;br /&gt;
  [http://www.pnas.org/content/pnas/105/17/6290.full.pdf http://www.pnas.org/content/pnas/105/17/6290.full.pdf]&lt;br /&gt;
&lt;br /&gt;
== Data analysis ==&lt;br /&gt;
&lt;br /&gt;
 R for Data Science: [http://r4ds.had.co.nz/ http://r4ds.had.co.nz/]&lt;br /&gt;
&lt;br /&gt;
= Writing =&lt;br /&gt;
&lt;br /&gt;
== Writing a scientific paper, step by painful step by Kevin D. Lafferty ==&lt;br /&gt;
&lt;br /&gt;
  [http://trophiccascades.forestry.oregonstate.edu/sites/trophic/files/Lafferty_WritingScientificPaper.pdf http://trophiccascades.forestry.oregonstate.edu/sites/trophic/files/Lafferty_WritingScientificPaper.pdf] &lt;br /&gt;
&lt;br /&gt;
== Recipe for a Quality Scientific Paper: Fulfill Readers&amp;amp;nbsp;and Reviewers&amp;amp;nbsp;Expectations ==&lt;br /&gt;
&lt;br /&gt;
 Prof Yaoqi Zhou [https://utexas.box.com/s/m93b92gwzcxgi1iw8qw7gdf6z7duzmm1 https://utexas.box.com/s/m93b92gwzcxgi1iw8qw7gdf6z7duzmm1] &lt;br /&gt;
&lt;br /&gt;
== Making better figures ==&lt;br /&gt;
&lt;br /&gt;
  [http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003833 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003833]&lt;br /&gt;
&lt;br /&gt;
== 21 suggestions ==&lt;br /&gt;
&lt;br /&gt;
 [https://www.scitechedit.com/images/21_writing_tips.pdf https://www.scitechedit.com/images/21_writing_tips.pdf] &lt;br /&gt;
&lt;br /&gt;
== Ten simple rules for structuring papers ==&lt;br /&gt;
&lt;br /&gt;
 [http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Literature search =&lt;br /&gt;
&lt;br /&gt;
pubmed:&amp;amp;nbsp;[https://www.ncbi.nlm.nih.gov/pubmed/ https://www.ncbi.nlm.nih.gov/pubmed/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Web of science (use UT eid when off campus):&amp;amp;nbsp;[https://guides.lib.utexas.edu/az.php?a=w https://guides.lib.utexas.edu/az.php?a=w]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hot paper search&amp;amp;nbsp;[https://www.oligotherapeutics.org/hot-papers-search/ https://www.oligotherapeutics.org/hot-papers-search/]&lt;br /&gt;
&lt;br /&gt;
Off campus access&amp;amp;nbsp;to paper download&amp;amp;nbsp;via ezproxy:&amp;amp;nbsp;[https://legacy.lib.utexas.edu/help/proxy.html#subscription https://legacy.lib.utexas.edu/help/proxy.html#subscription]&lt;br /&gt;
&lt;br /&gt;
Check out resources (including classes) offered by university library&lt;br /&gt;
&lt;br /&gt;
= Presentation =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#1f497d&amp;quot;&amp;gt;[http://blogs.nature.com/naturejobs/2017/01/11/scientific-presentations-a-cheat-sheet/ http://blogs.nature.com/naturejobs/2017/01/11/scientific-presentations-a-cheat-sheet/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#1f497d&amp;quot;&amp;gt;[http://www.nextscientist.com/improve-presentation-skills-of-phd-students/ http://www.nextscientist.com/improve-presentation-skills-of-phd-students/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Career Development =&lt;br /&gt;
&lt;br /&gt;
== The Professor Is In: The Essential Guide To Turning Your Ph.D. Into a Job==&lt;br /&gt;
&lt;br /&gt;
 [https://www.amazon.com/Professor-Essential-Guide-Turning-Ph-D/dp/0553419420 https://www.amazon.com/Professor-Essential-Guide-Turning-Ph-D/dp/0553419420]&lt;br /&gt;
&lt;br /&gt;
 Some contents are inspired by&amp;amp;nbsp;[https://twitter.com/thehauer/status/1021179403680862218?s=19 https://twitter.com/thehauer/status/1021179403680862218?s=19] &lt;br /&gt;
== Communication kit ==&lt;br /&gt;
&lt;br /&gt;
nstructions on writing cover letters, formatting CVs, writing abstracts, personal statements, etc.&lt;br /&gt;
&lt;br /&gt;
[http://mitcommlab.mit.edu/be/use-the-commkit/ http://mitcommlab.mit.edu/be/use-the-commkit/]&lt;br /&gt;
&lt;br /&gt;
== Lab Resources ==&lt;br /&gt;
&lt;br /&gt;
===Disk spaces ===&lt;br /&gt;
Your home dir is in /home/YOURUSERNAME, which is physically on Nova and space is limited. But each of you have space in /work/YOURUSERNAME (physically on SUN), which is at least 2 TB (more if needed). You can access home and work dir similarly on all computers in the lab. If you have MD jobs producing large trajectories and you wan to keep them for analysis (until paper pub), please use /work. You can check your space and quota limits in /opt/quota.* Once you reach quota you can not log in or execute commands.&lt;br /&gt;
===Using Lab Cluster===&lt;br /&gt;
[[Lab:newuser| new user set up to access lab cluster]]&lt;br /&gt;
&lt;br /&gt;
=== Cluster Monitoring ===&lt;br /&gt;
https://biomol.bme.utexas.edu/~pren/nodes.html &lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing CPU &amp;amp; GPU resource sign up]&lt;br /&gt;
&lt;br /&gt;
=== GPU Monitoring ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/~rq875/checkgpu.log https://biomol.bme.utexas.edu/~rq875/checkgpu.log] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Tinker Tutorials ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut] &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Poltype Github ===&lt;br /&gt;
&lt;br /&gt;
https://github.com/TinkerTools/poltype2&lt;br /&gt;
&lt;br /&gt;
=== Linux Utilities ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Lab Guide for Grad Students ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1PKyWNTntusPeRrOiGaLAkUvJbuuc4cVBfE4Lo9ZMt2I/edit https://docs.google.com/document/d/1PKyWNTntusPeRrOiGaLAkUvJbuuc4cVBfE4Lo9ZMt2I/edit] &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== UT Resources ==&lt;br /&gt;
&lt;br /&gt;
=== Ombuds ===&lt;br /&gt;
&lt;br /&gt;
*[https://ombuds.utexas.edu/student/about-us https://ombuds.utexas.edu/student/about-us] &lt;br /&gt;
*Can listen to your concerns, give advice, and direct you to resources &lt;br /&gt;
&lt;br /&gt;
=== Employee Assistance Program ===&lt;br /&gt;
&lt;br /&gt;
Counseling&lt;br /&gt;
&lt;br /&gt;
*[https://eap.utexas.edu/counseling-consultations https://eap.utexas.edu/counseling-consultations]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Wellness (sometimes has fitness videos)&lt;br /&gt;
&lt;br /&gt;
*[https://healthpoint.utexas.edu/ https://healthpoint.utexas.edu/]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Night rides (Lyft discount) ===&lt;br /&gt;
&lt;br /&gt;
*[https://parking.utexas.edu/night https://parking.utexas.edu/night]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== University Health Services ===&lt;br /&gt;
&lt;br /&gt;
*List of services [https://www.healthyhorns.utexas.edu/appointments.html#services https://www.healthyhorns.utexas.edu/appointments.html#services]&amp;amp;nbsp; &lt;br /&gt;
*As employees, a lot of care is free. Sometimes there is a copay, but it is very affordable usually &lt;br /&gt;
&lt;br /&gt;
COVID testing&lt;br /&gt;
&lt;br /&gt;
*[https://www.healthyhorns.utexas.edu/coronavirus_testing.html https://www.healthyhorns.utexas.edu/coronavirus_testing.html]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Women’s Health&lt;br /&gt;
&lt;br /&gt;
*[https://www.healthyhorns.utexas.edu/womenshealth.html https://www.healthyhorns.utexas.edu/womenshealth.html]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Free nurse advice line&lt;br /&gt;
&lt;br /&gt;
*[https://healthpoint.utexas.edu/247-nurse-line https://healthpoint.utexas.edu/247-nurse-line]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Student Emergency Services ===&lt;br /&gt;
&lt;br /&gt;
Services offered [https://deanofstudents.utexas.edu/emergency/howwecanhelp.php https://deanofstudents.utexas.edu/emergency/howwecanhelp.php]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Student Emergency Fund&lt;br /&gt;
&lt;br /&gt;
*[https://deanofstudents.utexas.edu/emergency/studentemergencyfund.php https://deanofstudents.utexas.edu/emergency/studentemergencyfund.php]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Services for Students with Disabilities ===&lt;br /&gt;
&lt;br /&gt;
*[https://diversity.utexas.edu/disability/about/ https://diversity.utexas.edu/disability/about/]&amp;amp;nbsp; &lt;br /&gt;
*The process is a bit difficult sometimes, be aware &lt;br /&gt;
&lt;br /&gt;
== Life in Austin ==&lt;br /&gt;
&lt;br /&gt;
=== Coffee Shops ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/4nDa3AMZDFoTA9FTA https://goo.gl/maps/4nDa3AMZDFoTA9FTA] &lt;br /&gt;
&lt;br /&gt;
=== Food ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/v4fQHJ4YhYtMrNh29 https://goo.gl/maps/v4fQHJ4YhYtMrNh29]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Essential Stores ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/iTLRvaAf4anVkm7j6 https://goo.gl/maps/iTLRvaAf4anVkm7j6]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Outdoor Landmarks / Hiking ===&lt;br /&gt;
&lt;br /&gt;
Highest point in Austin, not much of an actual hike&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/nd2aAXqoyVPivADH6 https://goo.gl/maps/nd2aAXqoyVPivADH6]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Pennybacker Bridge (park on side of road, can go up either side of road)&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/zfYHwUkRTYwTQfu69 https://goo.gl/maps/zfYHwUkRTYwTQfu69]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Overlook&amp;amp;nbsp;Trail (3ish miles each way, nice overlook part way, decent elevation change)&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/Cx9YdkuQWWmKBGAe9 https://goo.gl/maps/Cx9YdkuQWWmKBGAe9]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Bat Observation&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/ZHfnn54qKY6icEq3A https://goo.gl/maps/ZHfnn54qKY6icEq3A] &lt;br /&gt;
*Austin has a bat colony. The bats migrate but they like to hang out under the Congress bridge. &lt;br /&gt;
*You can park in a paid lot or take the bus&amp;amp;nbsp;and watch the bats fly sometime around sunset. You can also watch the bats from the river or on top of the bridge. &lt;br /&gt;
*It’s really neat and an Austin staple.&amp;amp;nbsp;Sometimes there are a lot of people. &lt;br /&gt;
&lt;br /&gt;
Parks to wander around near campus&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/fRs2w2LCX7emZNuWA https://goo.gl/maps/fRs2w2LCX7emZNuWA] &lt;br /&gt;
*[https://goo.gl/maps/Vu7L1DZDevn1FXNG6 https://goo.gl/maps/Vu7L1DZDevn1FXNG6] &lt;br /&gt;
*[https://goo.gl/maps/2qn9a8U1w3ZZY72u9 https://goo.gl/maps/2qn9a8U1w3ZZY72u9]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Pet Care Resources ===&lt;br /&gt;
&lt;br /&gt;
*Sometimes you can get pet supplies at the APA thrift stores &lt;br /&gt;
*Austin is very dog friendly and has many dog parks &lt;br /&gt;
&lt;br /&gt;
Great web resources&lt;br /&gt;
&lt;br /&gt;
*[https://www.austinpetdoctor.com/pet-education-center/ https://www.austinpetdoctor.com/pet-education-center/]&amp;amp;nbsp; &lt;br /&gt;
*[https://goo.gl/maps/SHm6N2Xgrdptcfsx7 https://goo.gl/maps/SHm6N2Xgrdptcfsx7] &lt;br /&gt;
*[https://goo.gl/maps/A4qmGfa6VQqomRFq9 https://goo.gl/maps/A4qmGfa6VQqomRFq9]&amp;amp;nbsp;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Lab:labinfo&amp;diff=2068</id>
		<title>Lab:labinfo</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Lab:labinfo&amp;diff=2068"/>
		<updated>2024-12-19T16:58:00Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Graduate students fellowships */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Welcome, Ren Lab Members! =&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== General&amp;amp;nbsp;Information ==&lt;br /&gt;
&lt;br /&gt;
=== Lab Website ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/ https://biomol.bme.utexas.edu/] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Lab Office Number ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;BME 3.516&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
=== How to Find Lab ===&lt;br /&gt;
&lt;br /&gt;
* Go to the 3rd floor of BME (ground floor on Dean Keeton side, next floor up on the South side)&lt;br /&gt;
* There is a hallway on the west side of the building that runs north-south&lt;br /&gt;
* if you come in from the lobby it is on the right side of the building running straight back&lt;br /&gt;
* the last door at the end of the hallway (located near Stair 3)&lt;br /&gt;
&lt;br /&gt;
=== Dr. Ren&#039;s Office Number ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;BME 5.202M&#039;&#039;&#039; (located in 5th floor faculty suite)&lt;br /&gt;
&lt;br /&gt;
== Communication and File Sharing ==&lt;br /&gt;
&lt;br /&gt;
=== Slack ===&lt;br /&gt;
&lt;br /&gt;
*utren.slack.com &lt;br /&gt;
*accounts will be created for new lab members/rotation students &lt;br /&gt;
*noteworthy channels&lt;br /&gt;
*##software for discussing various lab software + issues&lt;br /&gt;
*##cat for sending cat pics&lt;br /&gt;
*##paper-literature for sharing helpful papers + interesting new general papers&lt;br /&gt;
*##amoebaplus&lt;br /&gt;
*##poltype&lt;br /&gt;
*##general - general Ren lab stuff&lt;br /&gt;
*##allinclude - basically general but including some Schnieders lab members&lt;br /&gt;
&lt;br /&gt;
=== Lab Contacts ===&lt;br /&gt;
https://docs.google.com/spreadsheets/d/1Lea3_EAsVyOcMja7Ox_mNfj8ZNzj6Dupd8w5dNuFr4I/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Lab Meetings ===&lt;br /&gt;
&lt;br /&gt;
https://docs.google.com/spreadsheets/d/133vg99syg17xPR-H-UH0B2gLlC9469AFAwMQx2LGn4s/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Individual Meetings ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1yLw5xenlOgIdsylFVk4fDnu7s5juZvgFgU8ztYvMfQE/edit?pli=1#gid=0 https://docs.google.com/spreadsheets/d/1yLw5xenlOgIdsylFVk4fDnu7s5juZvgFgU8ztYvMfQE/edit?pli=1#gid=0] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Cluster Sign-Up Sheet ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?pli=1#gid=0 https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?pli=1#gid=0]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== AMMM Meeting Sign-Up Sheet (Summer) ===&lt;br /&gt;
https://docs.google.com/document/d/1Pn2ZhHBQ82miVhl6CGG0zj2rMQxTLvTznrGColcNYhQ/edit?usp=sharing&lt;br /&gt;
&lt;br /&gt;
=== Suggested Literature (in Box) ===&lt;br /&gt;
&lt;br /&gt;
[https://utexas.app.box.com/folder/103794407727 https://utexas.app.box.com/folder/103794407727] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Learning and reading ==&lt;br /&gt;
You are expected to learn from your labmates and by reading literature regularly. Most learnings in grad school/postdoc training are not from classroom!&lt;br /&gt;
&lt;br /&gt;
You will run MD simulations and free energy calculations, using polarizable force field AMOEBA. These are expertise our lab has developed over past two decades so anyone to graduate from this lab should understand how and why on the following relevant subjects. You all should spend time read papers and documents I have been sharing. If you don&#039;t understand what you do and only run others&#039; scripts to get numbers, you won&#039;t go far.&lt;br /&gt;
* Polarizable multipole force field AMOEBA. why and how&lt;br /&gt;
** Understand AMOEBA model (read slides and latest review paper Jing et al)&lt;br /&gt;
** Using POLTYPE to get parameters and understand what POLTYPE is doing (read POLTYPE papers)&lt;br /&gt;
* Hydration free energy. Salt effect and charge correction (if solute has net charge)&lt;br /&gt;
** FEP and BAR&lt;br /&gt;
** Other methods including TI and WHAM (PMF)&lt;br /&gt;
&lt;br /&gt;
* Binding free energy calculations&lt;br /&gt;
** restraint and standard state correction&lt;br /&gt;
** Neutralizing counter ion and background salt; what to do when ligand has net charge&lt;br /&gt;
** It is OK to use other&#039;s script (Brandon, CW) to set thing up and learn. But you need to know what the program is doing, how and why again.&lt;br /&gt;
* How to compile Tinker CPU and GPU code&lt;br /&gt;
&lt;br /&gt;
* Advanced models/enhanced sampling methods&lt;br /&gt;
** AMOEBA+&lt;br /&gt;
** AI based models&lt;br /&gt;
** Adaptive biasing force (ABF)&lt;br /&gt;
** Metadynamics (well tempered)&lt;br /&gt;
** OSRW&lt;br /&gt;
** few years ago our lab members did a seminar course together and covered a wide range of topics: https://biomol.bme.utexas.edu/wiki/index.php?title=Course:ABS&lt;br /&gt;
&lt;br /&gt;
Many topics above found on lab wiki (https://biomol.bme.utexas.edu/tinkergpu) and a BOX folder I shared with lab members (for example AMOEBA folder has slides and papers introducing AMOEBA). If you don&#039;t have/see anything or have question, contact asap. &lt;br /&gt;
It is important to establish a routine, setting aside time to read regularly (daily, weekly). I would start from basic and whatever relevant to what you are doing now and gradually cover more and more.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Lab policy &amp;amp; resource =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Financial support ===&lt;br /&gt;
&lt;br /&gt;
PhD students are typically fully supported via either GRA ot TA. However funding is not always guaranteed. Studenst and postdocs are expected to work deligently and be productive, which in turn will help us to secure the funding to support your stipend, fringe, tuition and other expense.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Work schedule ===&lt;br /&gt;
&lt;br /&gt;
Postdocs are required to fill in time sheet per university policy. While we don&#039;t require everyone follow a fixed schedule, everyone is expected to follow &amp;quot;reasonable&amp;quot; working hours (e.g. 9am - 5pm). People who show chronic tardiness and fail to comply after multiple warnings will be asked to leave.&lt;br /&gt;
&lt;br /&gt;
=== Vocation and leave  ===&lt;br /&gt;
Graduate students and postdocs are supported by either state or federal funds (including TA and RA ship). You are considered employees (hence the benefit etc.). We typically observe the university official holiday and vacation policy (http://www.utexas.edu/hr/holiday/ and http://www.utexas.edu/hr/current/leave/annual.html). You are allowed to take 4 weeks off for vacation each year, holidays and sick days not included. &#039;&#039;&#039;Please consult with PI in advance to plan on a vacation.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Please note&#039;&#039;&#039;Winter, spring and summer breaks are NOT vacation time&#039;&#039;&#039;. These are breaks for classes and undergraduate students, not for staff and employees. You can certainly take vacations during the breaks (use against the 4-week a year vacation time).&lt;br /&gt;
&lt;br /&gt;
You need to consult with PI for longer/extended leave. You may not expect financial support for the extended leave. &lt;br /&gt;
&lt;br /&gt;
We expect students to respect the rules and work diligently, which is essential for us to to receive funding to support everyone in the lab.&lt;br /&gt;
&lt;br /&gt;
=== Lab Resource ===&lt;br /&gt;
&lt;br /&gt;
When use the cluster, be considerate. Don&#039;t spread your job all over the nodes (use all the processors on one node before using other nodes), so that others that need the multiprocessors can utilize them.&lt;br /&gt;
&lt;br /&gt;
CPU &amp;amp; GPU resources in the lab (email Dr. Ren if you need write permission) https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit#gid=0&lt;br /&gt;
&lt;br /&gt;
More about using the cluster: https://biomolmd.org/mw/index.php/Lab:newuser&lt;br /&gt;
&lt;br /&gt;
=== Lab Responsibility ===&lt;br /&gt;
&lt;br /&gt;
Each of you will share some lab responsibility, such as maintenance, purchasing, organizing group meeting etc. Senior lab members are expected to advise and help out new lab members on research.&lt;br /&gt;
&lt;br /&gt;
=== Lab security  ===&lt;br /&gt;
&lt;br /&gt;
* Do not use university resource for personal use.&lt;br /&gt;
&lt;br /&gt;
* Do not install or alter operating system and software, change system setting or have root privileges (including sudo) on lab computers/workstations/laptops, unless with explicit permission from PI.&lt;br /&gt;
&lt;br /&gt;
* You are responsible to make sure your workstation and user account (password) are secure. &lt;br /&gt;
&lt;br /&gt;
* The university monitors the internet activity of every network port. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;Always lock the door when you are the last one to leave.&lt;br /&gt;
&lt;br /&gt;
=== Meetings and Conference  ===&lt;br /&gt;
&lt;br /&gt;
*Funding&lt;br /&gt;
&lt;br /&gt;
The lab provides support for each of you to go to meetings and conferences to present your work in orals or posters. The amount ($500 - $1000 a year) depends on funding availability and your presentation (oral has higher priority) etc. You are also strongly encouraged to seek for support from department, college and society etc, many in the format of award. &lt;br /&gt;
&lt;br /&gt;
Oral presentations receives a higher priority for support than posters.&lt;br /&gt;
&lt;br /&gt;
*Save all your receipts and program documents etc.&lt;br /&gt;
*Send me the following in electronic format (word doc, PDF) &lt;br /&gt;
**Your abstract before submission for me to check &lt;br /&gt;
**Published abstract (web print or scanned pdf)&lt;br /&gt;
**Official program page that has your presentation or poster title and author names (web print or scanned pdf is fine).&lt;br /&gt;
**The final powerpoint files for presentation or poster&lt;br /&gt;
===Graduate students fellowships===&lt;br /&gt;
http://www.grad.nd.edu/gfd/&lt;br /&gt;
&lt;br /&gt;
http://www.lib.msu.edu/harris23/grants/3gradinf.htm#a&lt;br /&gt;
&lt;br /&gt;
https://www.nsfgrfp.org/ NSF&lt;br /&gt;
https://ndseg.sysplus.com/ NDSEG&lt;br /&gt;
https://researchtraining.nih.gov/programs/fellowships NIH &lt;br /&gt;
https://professional.heart.org/en/research-programs/aha-funding-opportunities/predoctoral-fellowship American heart&lt;br /&gt;
MSU resource: https://libguides.lib.msu.edu/c.php?g=96743&amp;amp;p=622546&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background:white&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size:10.5pt&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#222222&amp;quot;&amp;gt;NSF, [https://www.nsfgrfp.org/ https://www.nsfgrfp.org/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background:white&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size:10.5pt&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#222222&amp;quot;&amp;gt;NIH, [https://researchtraining.nih.gov/programs/fellowships/f31 https://researchtraining.nih.gov/programs/fellowships/f31]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size:10.5pt&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#222222&amp;quot;&amp;gt;America Heart Association [https://professional.heart.org/professional/ResearchPrograms/ApplicationInformation/UCM_443316_Predoctoral-Fellowship.jsp https://professional.heart.org/professional/ResearchPrograms/ApplicationInformation/UCM_443316_Predoctoral-Fellowship.jsp]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
SAMRT:&amp;amp;nbsp;[https://www.asee.org/fellowship-programs/graduate https://www.asee.org/fellowship-programs/graduate]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
NDSEG&amp;amp;nbsp;[https://ndseg.asee.org/ https://ndseg.asee.org/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Fellowship Databases: ==&lt;br /&gt;
&lt;br /&gt;
[http://www.grad.nd.edu/gfd/ https://gradschool.cornell.edu/fellowships]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.lib.msu.edu/harris23/grants/3gradinf.htm#a https://awardsdatabase.usc.edu/]&lt;br /&gt;
&lt;br /&gt;
[http://grad.berkeley.edu/news/headlines/guide-to-fellowships-grants/ http://grad.berkeley.edu/news/headlines/guide-to-fellowships-grants/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Technical reading materials =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Molecular Modeling ==&lt;br /&gt;
&lt;br /&gt;
 Book: Molecular Modelling, Principles and Pllications, Andrew Leach&lt;br /&gt;
 Computer simulations of liquids, Allen &amp;amp; Tildesley&lt;br /&gt;
 Book: Molecular Simulations, Frenkel and Smit&lt;br /&gt;
&lt;br /&gt;
You can use Google to find these books online.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Free energy ==&lt;br /&gt;
&lt;br /&gt;
Book:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;Free energy Calculations, Theory and Applications in Chemistry and Biology&#039;&#039;&#039;, Chipot and Pophorille, Springer&lt;br /&gt;
&lt;br /&gt;
Review by Simonson &amp;amp; Roux (charge correction/solution-gas-phase): Concepts and protocols for electrostatic free energies&lt;br /&gt;
&lt;br /&gt;
 [https://utexas.box.com/s/fx8ixqhz9zj9i5ebv3rzrgclwiighnd6 https://utexas.box.com/s/fx8ixqhz9zj9i5ebv3rzrgclwiighnd6]&lt;br /&gt;
&lt;br /&gt;
More about charge corrections when system/ligand being disappeared is not neutral&lt;br /&gt;
&lt;br /&gt;
 [https://utexas.box.com/s/nj6jcufmms5hs1xqu5pywkwp3kax3y6k https://utexas.box.com/s/nj6jcufmms5hs1xqu5pywkwp3kax3y6k]&lt;br /&gt;
&lt;br /&gt;
== Force Fields ==&lt;br /&gt;
&lt;br /&gt;
MSI force field handbook:&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;[https://utexas.box.com/s/ge7f4q6svq5ammy736c7d729ms6jxzzw https://utexas.box.com/s/ge7f4q6svq5ammy736c7d729ms6jxzzw]&lt;br /&gt;
&lt;br /&gt;
== Molecular binding termodynamics &amp;amp; simlations ==&lt;br /&gt;
&lt;br /&gt;
Gilson &amp;amp; Zhou&lt;br /&gt;
&lt;br /&gt;
  [https://utexas.box.com/s/esttb5govnir7mvnvydcid4ukv7nxmnc https://utexas.box.com/s/esttb5govnir7mvnvydcid4ukv7nxmnc]&lt;br /&gt;
  [https://utexas.box.com/s/dugh8ba95gf8v0fnsnzf6a63beu47qee https://utexas.box.com/s/dugh8ba95gf8v0fnsnzf6a63beu47qee]&lt;br /&gt;
  [https://utexas.box.com/s/p2fcjdzdssuxicopv5mkl843grrjinoh https://utexas.box.com/s/p2fcjdzdssuxicopv5mkl843grrjinoh] &lt;br /&gt;
&lt;br /&gt;
Hamelberg &amp;amp; McCammon&lt;br /&gt;
&lt;br /&gt;
  [https://utexas.box.com/s/bsayz0jmfgd7o8ibx0pqtkoqwuk108tm https://utexas.box.com/s/bsayz0jmfgd7o8ibx0pqtkoqwuk108tm]&lt;br /&gt;
&lt;br /&gt;
Ren lab:&lt;br /&gt;
&lt;br /&gt;
  [http://www.pnas.org/content/pnas/105/17/6290.full.pdf http://www.pnas.org/content/pnas/105/17/6290.full.pdf]&lt;br /&gt;
&lt;br /&gt;
== Data analysis ==&lt;br /&gt;
&lt;br /&gt;
 R for Data Science: [http://r4ds.had.co.nz/ http://r4ds.had.co.nz/]&lt;br /&gt;
&lt;br /&gt;
= Writing =&lt;br /&gt;
&lt;br /&gt;
== Writing a scientific paper, step by painful step by Kevin D. Lafferty ==&lt;br /&gt;
&lt;br /&gt;
  [http://trophiccascades.forestry.oregonstate.edu/sites/trophic/files/Lafferty_WritingScientificPaper.pdf http://trophiccascades.forestry.oregonstate.edu/sites/trophic/files/Lafferty_WritingScientificPaper.pdf] &lt;br /&gt;
&lt;br /&gt;
== Recipe for a Quality Scientific Paper: Fulfill Readers&amp;amp;nbsp;and Reviewers&amp;amp;nbsp;Expectations ==&lt;br /&gt;
&lt;br /&gt;
 Prof Yaoqi Zhou [https://utexas.box.com/s/m93b92gwzcxgi1iw8qw7gdf6z7duzmm1 https://utexas.box.com/s/m93b92gwzcxgi1iw8qw7gdf6z7duzmm1] &lt;br /&gt;
&lt;br /&gt;
== Making better figures ==&lt;br /&gt;
&lt;br /&gt;
  [http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003833 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1003833]&lt;br /&gt;
&lt;br /&gt;
== 21 suggestions ==&lt;br /&gt;
&lt;br /&gt;
 [https://www.scitechedit.com/images/21_writing_tips.pdf https://www.scitechedit.com/images/21_writing_tips.pdf] &lt;br /&gt;
&lt;br /&gt;
== Ten simple rules for structuring papers ==&lt;br /&gt;
&lt;br /&gt;
 [http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005619]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Literature search =&lt;br /&gt;
&lt;br /&gt;
pubmed:&amp;amp;nbsp;[https://www.ncbi.nlm.nih.gov/pubmed/ https://www.ncbi.nlm.nih.gov/pubmed/]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Web of science (use UT eid when off campus):&amp;amp;nbsp;[https://guides.lib.utexas.edu/az.php?a=w https://guides.lib.utexas.edu/az.php?a=w]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Hot paper search&amp;amp;nbsp;[https://www.oligotherapeutics.org/hot-papers-search/ https://www.oligotherapeutics.org/hot-papers-search/]&lt;br /&gt;
&lt;br /&gt;
Off campus access&amp;amp;nbsp;to paper download&amp;amp;nbsp;via ezproxy:&amp;amp;nbsp;[https://legacy.lib.utexas.edu/help/proxy.html#subscription https://legacy.lib.utexas.edu/help/proxy.html#subscription]&lt;br /&gt;
&lt;br /&gt;
Check out resources (including classes) offered by university library&lt;br /&gt;
&lt;br /&gt;
= Presentation =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#1f497d&amp;quot;&amp;gt;[http://blogs.nature.com/naturejobs/2017/01/11/scientific-presentations-a-cheat-sheet/ http://blogs.nature.com/naturejobs/2017/01/11/scientific-presentations-a-cheat-sheet/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-family:&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;color:#1f497d&amp;quot;&amp;gt;[http://www.nextscientist.com/improve-presentation-skills-of-phd-students/ http://www.nextscientist.com/improve-presentation-skills-of-phd-students/]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Career Development =&lt;br /&gt;
&lt;br /&gt;
== The Professor Is In: The Essential Guide To Turning Your Ph.D. Into a Job==&lt;br /&gt;
&lt;br /&gt;
 [https://www.amazon.com/Professor-Essential-Guide-Turning-Ph-D/dp/0553419420 https://www.amazon.com/Professor-Essential-Guide-Turning-Ph-D/dp/0553419420]&lt;br /&gt;
&lt;br /&gt;
 Some contents are inspired by&amp;amp;nbsp;[https://twitter.com/thehauer/status/1021179403680862218?s=19 https://twitter.com/thehauer/status/1021179403680862218?s=19] &lt;br /&gt;
== Communication kit ==&lt;br /&gt;
&lt;br /&gt;
nstructions on writing cover letters, formatting CVs, writing abstracts, personal statements, etc.&lt;br /&gt;
&lt;br /&gt;
[http://mitcommlab.mit.edu/be/use-the-commkit/ http://mitcommlab.mit.edu/be/use-the-commkit/]&lt;br /&gt;
&lt;br /&gt;
== Lab Resources ==&lt;br /&gt;
&lt;br /&gt;
===Disk spaces ===&lt;br /&gt;
Your home dir is in /home/YOURUSERNAME, which is physically on Nova and space is limited. But each of you have space in /work/YOURUSERNAME (physically on SUN), which is at least 2 TB (more if needed). You can access home and work dir similarly on all computers in the lab. If you have MD jobs producing large trajectories and you wan to keep them for analysis (until paper pub), please use /work. You can check your space and quota limits in /opt/quota.* Once you reach quota you can not log in or execute commands.&lt;br /&gt;
===Using Lab Cluster===&lt;br /&gt;
[[Lab:newuser| new user set up to access lab cluster]]&lt;br /&gt;
&lt;br /&gt;
=== Cluster Monitoring ===&lt;br /&gt;
https://biomol.bme.utexas.edu/~pren/nodes.html &lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1EOlUwFpdNU2uBZ5XrHSvZnRYCUCOw5tCSkFisTm3big/edit?usp=sharing CPU &amp;amp; GPU resource sign up]&lt;br /&gt;
&lt;br /&gt;
=== GPU Monitoring ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/~rq875/checkgpu.log https://biomol.bme.utexas.edu/~rq875/checkgpu.log] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Tinker Tutorials ===&lt;br /&gt;
&lt;br /&gt;
[https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut] &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Poltype Github ===&lt;br /&gt;
&lt;br /&gt;
https://github.com/TinkerTools/poltype2&lt;br /&gt;
&lt;br /&gt;
=== Linux Utilities ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit https://docs.google.com/document/d/1cnmSItdRXDBcpVBGhwDahJVJ2jeh4l2oDVpMBLtlySE/edit] &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Lab Guide for Grad Students ===&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/document/d/1PKyWNTntusPeRrOiGaLAkUvJbuuc4cVBfE4Lo9ZMt2I/edit https://docs.google.com/document/d/1PKyWNTntusPeRrOiGaLAkUvJbuuc4cVBfE4Lo9ZMt2I/edit] &amp;amp;nbsp; &amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== UT Resources ==&lt;br /&gt;
&lt;br /&gt;
=== Ombuds ===&lt;br /&gt;
&lt;br /&gt;
*[https://ombuds.utexas.edu/student/about-us https://ombuds.utexas.edu/student/about-us] &lt;br /&gt;
*Can listen to your concerns, give advice, and direct you to resources &lt;br /&gt;
&lt;br /&gt;
=== Employee Assistance Program ===&lt;br /&gt;
&lt;br /&gt;
Counseling&lt;br /&gt;
&lt;br /&gt;
*[https://eap.utexas.edu/counseling-consultations https://eap.utexas.edu/counseling-consultations]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Wellness (sometimes has fitness videos)&lt;br /&gt;
&lt;br /&gt;
*[https://healthpoint.utexas.edu/ https://healthpoint.utexas.edu/]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Night rides (Lyft discount) ===&lt;br /&gt;
&lt;br /&gt;
*[https://parking.utexas.edu/night https://parking.utexas.edu/night]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== University Health Services ===&lt;br /&gt;
&lt;br /&gt;
*List of services [https://www.healthyhorns.utexas.edu/appointments.html#services https://www.healthyhorns.utexas.edu/appointments.html#services]&amp;amp;nbsp; &lt;br /&gt;
*As employees, a lot of care is free. Sometimes there is a copay, but it is very affordable usually &lt;br /&gt;
&lt;br /&gt;
COVID testing&lt;br /&gt;
&lt;br /&gt;
*[https://www.healthyhorns.utexas.edu/coronavirus_testing.html https://www.healthyhorns.utexas.edu/coronavirus_testing.html]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Women’s Health&lt;br /&gt;
&lt;br /&gt;
*[https://www.healthyhorns.utexas.edu/womenshealth.html https://www.healthyhorns.utexas.edu/womenshealth.html]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Free nurse advice line&lt;br /&gt;
&lt;br /&gt;
*[https://healthpoint.utexas.edu/247-nurse-line https://healthpoint.utexas.edu/247-nurse-line]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Student Emergency Services ===&lt;br /&gt;
&lt;br /&gt;
Services offered [https://deanofstudents.utexas.edu/emergency/howwecanhelp.php https://deanofstudents.utexas.edu/emergency/howwecanhelp.php]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Student Emergency Fund&lt;br /&gt;
&lt;br /&gt;
*[https://deanofstudents.utexas.edu/emergency/studentemergencyfund.php https://deanofstudents.utexas.edu/emergency/studentemergencyfund.php]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Services for Students with Disabilities ===&lt;br /&gt;
&lt;br /&gt;
*[https://diversity.utexas.edu/disability/about/ https://diversity.utexas.edu/disability/about/]&amp;amp;nbsp; &lt;br /&gt;
*The process is a bit difficult sometimes, be aware &lt;br /&gt;
&lt;br /&gt;
== Life in Austin ==&lt;br /&gt;
&lt;br /&gt;
=== Coffee Shops ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/4nDa3AMZDFoTA9FTA https://goo.gl/maps/4nDa3AMZDFoTA9FTA] &lt;br /&gt;
&lt;br /&gt;
=== Food ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/v4fQHJ4YhYtMrNh29 https://goo.gl/maps/v4fQHJ4YhYtMrNh29]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Essential Stores ===&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/iTLRvaAf4anVkm7j6 https://goo.gl/maps/iTLRvaAf4anVkm7j6]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
=== Outdoor Landmarks / Hiking ===&lt;br /&gt;
&lt;br /&gt;
Highest point in Austin, not much of an actual hike&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/nd2aAXqoyVPivADH6 https://goo.gl/maps/nd2aAXqoyVPivADH6]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Pennybacker Bridge (park on side of road, can go up either side of road)&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/zfYHwUkRTYwTQfu69 https://goo.gl/maps/zfYHwUkRTYwTQfu69]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Overlook&amp;amp;nbsp;Trail (3ish miles each way, nice overlook part way, decent elevation change)&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/Cx9YdkuQWWmKBGAe9 https://goo.gl/maps/Cx9YdkuQWWmKBGAe9]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Bat Observation&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/ZHfnn54qKY6icEq3A https://goo.gl/maps/ZHfnn54qKY6icEq3A] &lt;br /&gt;
*Austin has a bat colony. The bats migrate but they like to hang out under the Congress bridge. &lt;br /&gt;
*You can park in a paid lot or take the bus&amp;amp;nbsp;and watch the bats fly sometime around sunset. You can also watch the bats from the river or on top of the bridge. &lt;br /&gt;
*It’s really neat and an Austin staple.&amp;amp;nbsp;Sometimes there are a lot of people. &lt;br /&gt;
&lt;br /&gt;
Parks to wander around near campus&lt;br /&gt;
&lt;br /&gt;
*[https://goo.gl/maps/fRs2w2LCX7emZNuWA https://goo.gl/maps/fRs2w2LCX7emZNuWA] &lt;br /&gt;
*[https://goo.gl/maps/Vu7L1DZDevn1FXNG6 https://goo.gl/maps/Vu7L1DZDevn1FXNG6] &lt;br /&gt;
*[https://goo.gl/maps/2qn9a8U1w3ZZY72u9 https://goo.gl/maps/2qn9a8U1w3ZZY72u9]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
=== Pet Care Resources ===&lt;br /&gt;
&lt;br /&gt;
*Sometimes you can get pet supplies at the APA thrift stores &lt;br /&gt;
*Austin is very dog friendly and has many dog parks &lt;br /&gt;
&lt;br /&gt;
Great web resources&lt;br /&gt;
&lt;br /&gt;
*[https://www.austinpetdoctor.com/pet-education-center/ https://www.austinpetdoctor.com/pet-education-center/]&amp;amp;nbsp; &lt;br /&gt;
*[https://goo.gl/maps/SHm6N2Xgrdptcfsx7 https://goo.gl/maps/SHm6N2Xgrdptcfsx7] &lt;br /&gt;
*[https://goo.gl/maps/A4qmGfa6VQqomRFq9 https://goo.gl/maps/A4qmGfa6VQqomRFq9]&amp;amp;nbsp;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=TinkerMeeting%22tinkerconf&amp;diff=2062</id>
		<title>TinkerMeeting&quot;tinkerconf</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=TinkerMeeting%22tinkerconf&amp;diff=2062"/>
		<updated>2024-12-04T14:46:15Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;TINKER Meetings&#039;&#039;&#039; &lt;br /&gt;
*[[TinkerMeeting:tinkermeeting-2017| 2017, Washington Univ. St. Louis]]&lt;br /&gt;
*[[TinkerMeeting:tinkermeeting-2018| 2018, UT Austin ]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2019| 2019, Paris, France, joint CHARMM/Tinker meeting ]]&lt;br /&gt;
*[[Tinkermeeting:Harrinton2020| 2020&amp;amp;nbsp;Harrington Symposium, UT Austin; Cancelled due to COVID ]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2022| 2022, Maryland]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2023| 2023, St. Louis]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2024| 2024, Pisa, Italy]]&lt;br /&gt;
*2025, Dallas, TBD&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=TinkerMeeting%22tinkerconf&amp;diff=2061</id>
		<title>TinkerMeeting&quot;tinkerconf</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=TinkerMeeting%22tinkerconf&amp;diff=2061"/>
		<updated>2024-12-04T14:44:46Z</updated>

		<summary type="html">&lt;p&gt;Admin: updates&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;TINKER Meetings&#039;&#039;&#039; &lt;br /&gt;
*[[TinkerMeeting:tinkermeeting-2017| 2017, Washington Univ. St. Louis]]&lt;br /&gt;
*[[TinkerMeeting:tinkermeeting-2018| 2018, UT Austin ]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2019| 2019, Paris, joint CHARMM/Tinker meeting ]]&lt;br /&gt;
*[[Tinkermeeting:Harrinton2020| 2020&amp;amp;nbsp;Harrington Symposium, UT Austin; Cancelled due to COVID ]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2022| 2022, Maryland]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2023| 2023, St. Louis]]&lt;br /&gt;
*[[Tinkermeeting:tinkermeeting2024| 2024, Pisa, Italy]]&lt;br /&gt;
*2025, Dallas, TBD&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2056</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2056"/>
		<updated>2024-11-20T22:04:52Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* More on running Tinker and tinker9 (GPU) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker executables from [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the oppurtunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
On renlab cluster, there is &amp;quot;packmol&amp;quot; installed at /home/liuchw/Softwares/packmol-20.14.4/packmol&lt;br /&gt;
&lt;br /&gt;
Two examples for generating a cubic box:&lt;br /&gt;
&lt;br /&gt;
example 1: generate a pure liquid box, using water as an example. In the real cases, one could calculate the number of molecules and the length of the cube according to desired density. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output water-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;example 2: soak a MeOH molecule into the above box. We first let MeOH be in the center of the box with coordinates (9,9,9), and then soak with water in 18.6 A cubic box. &amp;lt;syntaxhighlight lang=&amp;quot;abap&amp;quot;&amp;gt;&lt;br /&gt;
filetype tinker&lt;br /&gt;
output liquid-box.xyz&lt;br /&gt;
tolerance 2.0&lt;br /&gt;
&lt;br /&gt;
structure MeOH.xyz&lt;br /&gt;
number 1&lt;br /&gt;
center&lt;br /&gt;
fixed 9.0 9.0 9.0 0.0 0.0 0.0&lt;br /&gt;
end structure&lt;br /&gt;
&lt;br /&gt;
structure Wat.xyz&lt;br /&gt;
number 216&lt;br /&gt;
inside cube 0. 0. 0. 18.6&lt;br /&gt;
end structure&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;In the above two examples, all one needs are the &amp;quot;Wat.xyz&amp;quot; and &amp;quot;MeOH.xyz&amp;quot; files. After the box is generated, it is straightforward to use Tinker to minimize the structure. &lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/&lt;br /&gt;
&lt;br /&gt;
== Compiling &amp;amp; running: ==&lt;br /&gt;
[[Software:tinkergpu]] &lt;br /&gt;
&lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 #source /home/liuchw/.bashrc.tinker9&lt;br /&gt;
 #export TINKER9=/home/pren/tinker9/tinker9_sugar/build/&lt;br /&gt;
 #export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-11.8/targets/x86_64-linux/lib/&lt;br /&gt;
 export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=0 # device number; can use 1 or 2 if there are multiple GPU cards&lt;br /&gt;
 $TINKER9/tinker9 dynamic bench7.xyz -k bench7.key 5000 2.0 1000.0 4 298.15 1.0 N &amp;gt; out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman (tinker 8 CPU only)&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Preferred/Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 archive (&#039;&#039;&#039;dcd-archive&#039;&#039;&#039; to produce compressed traj for large systems; need .xyz or .pdb to render in VMD)&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
 vdw-cutoff 9 (12 for amoeba)&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 9.0 (7.0 for amoeba)&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001 (only for amoeba)&lt;br /&gt;
 polar-predict (only for amoeba)&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
Documentation: https://tinkerdoc.readthedocs.io/en/latest/text/feature/integrator-langevin-piston.html#implementation-2 &lt;br /&gt;
Semi-isotropic pressure control not finished yet&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.01”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. You can even turn off polarization initially (polarizeterm NONE) during EQ and add it back (&#039;&#039;&#039;polar-eps 0.001&#039;&#039;&#039; or tighter for production) &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equlibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to spede up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error. &lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be.&amp;amp;nbsp;Water/ions are&amp;amp;nbsp;relaxed after this step. &lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run&amp;amp;nbsp;1.5&amp;amp;nbsp;ns NPT to compute the average density/box size (ignore the first 300ps). &#039;&#039;&#039;For GPU, only &amp;quot;barostat MonteCarlo&amp;quot; is available.&#039;&#039;&#039;&amp;amp;nbsp; &lt;br /&gt;
**NVT MD for ~2ns with box fixed at the average lengths from above. &lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 0.1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
  1     1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
	&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2055</id>
		<title>Tinkermeeting:tinkermeeting2022</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2055"/>
		<updated>2024-11-18T15:49:35Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Charlles  Abreu&lt;br /&gt;
|abreu@eq.ufrj.br&lt;br /&gt;
|U Rio de Janeiro&lt;br /&gt;
|-&lt;br /&gt;
|Olivier Adjoua&lt;br /&gt;
|passi.adjoua@sorbonne-universite.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Cole Allen&lt;br /&gt;
|coleallen@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Felix Aviat&lt;br /&gt;
|felixaviat@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Madison Berger&lt;br /&gt;
|madison.berger@utdallas.edu&lt;br /&gt;
|UTexas Dallas&lt;br /&gt;
|-&lt;br /&gt;
|Oleg Borodin&lt;br /&gt;
|oleg.a.borodin.civ@mail.mil&lt;br /&gt;
|Army Rsch Lab&lt;br /&gt;
|-&lt;br /&gt;
|Bernie Brooks&lt;br /&gt;
|bernard.brooks@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Siqin Cao&lt;br /&gt;
|scao66@wisc.edu&lt;br /&gt;
|UWisconsin&lt;br /&gt;
|-&lt;br /&gt;
|Dave Cerutti&lt;br /&gt;
|dscerutti@gmail.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Chris Chipot&lt;br /&gt;
|chipot@illinois.edu&lt;br /&gt;
|UIllinois/CNRS&lt;br /&gt;
|-&lt;br /&gt;
|Igor Chollet&lt;br /&gt;
|igor.cholletpro@gmail.com&lt;br /&gt;
|Sorbonne, Paris &lt;br /&gt;
|-&lt;br /&gt;
|Moses Chung         &lt;br /&gt;
|  kchung25@wustl.edu        &lt;br /&gt;
|           Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Carine Clavaguera&lt;br /&gt;
|carine.clavaguera@universite-paris-saclay.fr|carine.clavaguera@universite-paris-saclay.fr&lt;br /&gt;
|UParis-Saclay&lt;br /&gt;
|-&lt;br /&gt;
|Chris Cooper&lt;br /&gt;
|christopher.cooper@usm.cl&lt;br /&gt;
|USM, Chile&lt;br /&gt;
|-&lt;br /&gt;
|Rae Corrigan&lt;br /&gt;
|rae-corrigan@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Tom Darden&lt;br /&gt;
|tom@eyesopen.com&lt;br /&gt;
|OpenEye&lt;br /&gt;
|-&lt;br /&gt;
|Omar Demerdash&lt;br /&gt;
|demerdashon@ornl.gov&lt;br /&gt;
|Oak Ridge Lab&lt;br /&gt;
|-&lt;br /&gt;
|Zach Glick&lt;br /&gt;
|zlg@gatech.edu&lt;br /&gt;
|Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Rose Gogal&lt;br /&gt;
|rose-gogal@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Hatice Gokcan&lt;br /&gt;
|hgokcan@andrew.cmu.edu&lt;br /&gt;
|Carnegie Mellon&lt;br /&gt;
|-&lt;br /&gt;
|Justin Gourary&lt;br /&gt;
|jtgourary@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Nohad Gresh&lt;br /&gt;
|gresh@lct.jussieu.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Alan Grossfield&lt;br /&gt;
|alan_grossfield@urmc.rochester.edu&lt;br /&gt;
|URochester&lt;br /&gt;
|-&lt;br /&gt;
|JC Gumbart&lt;br /&gt;
|jcgumbart@gatech.edu&lt;br /&gt;
|Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Dave Hardy&lt;br /&gt;
|dhardy@ks.uiuc.edu&lt;br /&gt;
|UIllinois&lt;br /&gt;
|-&lt;br /&gt;
|Florent Hédin&lt;br /&gt;
|florent@qubit-pharmaceuticals.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Chris Ho&lt;br /&gt;
|cho@newdrugdesign.com&lt;br /&gt;
|New Drug Design&lt;br /&gt;
|-&lt;br /&gt;
|Xuhui Huang&lt;br /&gt;
|xhuang@chem.wisc.edu&lt;br /&gt;
|UWisconsin&lt;br /&gt;
|-&lt;br /&gt;
|Toshiko Ichiye&lt;br /&gt;
|ti9@georgetown.edu&lt;br /&gt;
|Georgetown&lt;br /&gt;
|-&lt;br /&gt;
|Olexandr Isayev&lt;br /&gt;
|olexandr@cmu.edu&lt;br /&gt;
|Carnegie Mellon&lt;br /&gt;
|-&lt;br /&gt;
|Zach Jarin&lt;br /&gt;
|zachary.jarin@nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Théo Jeffrelot-Inizan&lt;br /&gt;
|theo.jaffrelot-inizan@lct.jussieu.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Francis Jing&lt;br /&gt;
|francijing@gmail.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Luc-Henri Jolly&lt;br /&gt;
|lhj@ip2ct.upmc.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Ken Jordan&lt;br /&gt;
|jordan@pitt.edu&lt;br /&gt;
|UPittsburgh&lt;br /&gt;
|-&lt;br /&gt;
|Bill Jorgensen&lt;br /&gt;
|william.jorgensen@yale.edu&lt;br /&gt;
|Yale&lt;br /&gt;
|-&lt;br /&gt;
|Christophe Jurczak&lt;br /&gt;
|christophe@quantonation.com&lt;br /&gt;
|Quantonation&lt;br /&gt;
|-&lt;br /&gt;
|Léa El Khoury&lt;br /&gt;
|lea@qubit-pharmaceuticals.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Klauda&lt;br /&gt;
|jbklauda@umd.edu&lt;br /&gt;
|UMaryland&lt;br /&gt;
|-&lt;br /&gt;
|Anmol Kumar&lt;br /&gt;
|anmol@outerbanks.umaryland.edu&lt;br /&gt;
|UMD Baltimore&lt;br /&gt;
|-&lt;br /&gt;
|Louis Lagardère&lt;br /&gt;
|louis.lagardere@gmail.com&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Jie Liang&lt;br /&gt;
|jliang@uic.edu&lt;br /&gt;
|UI Chicago&lt;br /&gt;
|-&lt;br /&gt;
|Filippo Lipparini&lt;br /&gt;
|filippo.lipparini@unipi.it&lt;br /&gt;
|UPisa, Italy&lt;br /&gt;
|-&lt;br /&gt;
|Chengwen Liu&lt;br /&gt;
|liuchw2010@gmail.com&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Daniele Loco&lt;br /&gt;
|daniele.loco01@gmail.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Ao Ma&lt;br /&gt;
|aoma@uic.edu&lt;br /&gt;
|UI Chicago&lt;br /&gt;
|-&lt;br /&gt;
|Nastasia Mauger&lt;br /&gt;
|nastasia.mauger@courriel.upmc.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Matthieu Montes&lt;br /&gt;
|matthieu.montes@cnam.fr&lt;br /&gt;
|CNAM, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Devin Mulvey&lt;br /&gt;
|dmm219@pitt.edu&lt;br /&gt;
|UPittsburgh&lt;br /&gt;
|-&lt;br /&gt;
|Jorge Nochebuena&lt;br /&gt;
|jorge.nochebuena@utdallas.edu&lt;br /&gt;
|UTexas Dallas&lt;br /&gt;
|-&lt;br /&gt;
|Michele Nottoli&lt;br /&gt;
|michele.nottoli@phd.unipi.it&lt;br /&gt;
|UPisa, Italy &lt;br /&gt;
|-&lt;br /&gt;
|Andrew Pang          &lt;br /&gt;
|andrewpang@gatech.edu            &lt;br /&gt;
|    Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Rich Pastor&lt;br /&gt;
|pastorr@nhlbi.nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Lalith Perera&lt;br /&gt;
|pereral2@niehs.nih.gov&lt;br /&gt;
|NIEHS NIH&lt;br /&gt;
|-&lt;br /&gt;
|Jean-Philip Piquemal&lt;br /&gt;
|jean-philip.piquemal@sorbonne-universite.fr|jean-philip.piquemal@sorbonne-universite.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Thomas Plé&lt;br /&gt;
|thomas.ple@hotmail.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Travis Pollard&lt;br /&gt;
|travis.p.pollard.civ@army.mil&lt;br /&gt;
|Army Rsch Lab&lt;br /&gt;
|-&lt;br /&gt;
|Jay Ponder&lt;br /&gt;
|ponder@dasher.wustl.edu&lt;br /&gt;
|Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Rui Qi&lt;br /&gt;
|rui.qi@roivant.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Josh Rackers&lt;br /&gt;
|jracker@sandia.gov&lt;br /&gt;
|Sandia Natl Lab&lt;br /&gt;
|-&lt;br /&gt;
|Pengyu Ren&lt;br /&gt;
|pren@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Amy Rice&lt;br /&gt;
|rice.amym@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Marc Riera&lt;br /&gt;
|mreirari@ucsd.edu&lt;br /&gt;
|UC San Diego&lt;br /&gt;
|-&lt;br /&gt;
|Chris Rowley&lt;br /&gt;
|christopherrowley@cunet.carleton.ca&lt;br /&gt;
|Carleton U, CA&lt;br /&gt;
|-&lt;br /&gt;
|Mike Schnieders&lt;br /&gt;
|michael-schnieders@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Ada Sedova&lt;br /&gt;
|sedovaaa@ornl.gov&lt;br /&gt;
|Oak Ridge Lab&lt;br /&gt;
|-&lt;br /&gt;
|Yihan Shao&lt;br /&gt;
|yihan.shao@ou.edu&lt;br /&gt;
|UOklahoma&lt;br /&gt;
|-&lt;br /&gt;
|Jana Shen&lt;br /&gt;
|jana.shen@rx.umaryland.edu&lt;br /&gt;
|UMD Baltimore&lt;br /&gt;
|-&lt;br /&gt;
|Roseane Silva&lt;br /&gt;
|roseane@wustl.edu&lt;br /&gt;
|Washington U &lt;br /&gt;
|-&lt;br /&gt;
|Andrew Thiel         &lt;br /&gt;
|andrew-thiel@uiowa.edu               &lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Richard Van&lt;br /&gt;
|van@ou.edu&lt;br /&gt;
|UOklahoma&lt;br /&gt;
|-&lt;br /&gt;
|Sameer Varma&lt;br /&gt;
|svarma@usf.edu&lt;br /&gt;
|USouth Florida&lt;br /&gt;
|-&lt;br /&gt;
|Elizabeth Wait&lt;br /&gt;
|elizabethewait@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Brandon Walker&lt;br /&gt;
|bdw2292@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Yanxing Wang&lt;br /&gt;
|yxw@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Zhi Wang&lt;br /&gt;
|wangzhi@wustl.edu&lt;br /&gt;
|Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Chuanjie Wu&lt;br /&gt;
|chuanjiewu@gmail.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Xiongwu Wu&lt;br /&gt;
|wuxw@nhlbi.nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Wei Yang&lt;br /&gt;
|yang@sb.fsu.edu&lt;br /&gt;
|Florida State&lt;br /&gt;
|-&lt;br /&gt;
|Ketsia Zinga         &lt;br /&gt;
|kzinga@utexas.edu                &lt;br /&gt;
|    UTexas Austin&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2054</id>
		<title>Tinkermeeting:tinkermeeting2022</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2054"/>
		<updated>2024-11-18T15:48:30Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Charlles  Abreu&lt;br /&gt;
|abreu@eq.ufrj.br&lt;br /&gt;
|U Rio de Janeiro&lt;br /&gt;
|-&lt;br /&gt;
|Olivier Adjoua&lt;br /&gt;
|passi.adjoua@sorbonne-universite.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Cole Allen&lt;br /&gt;
|coleallen@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Felix Aviat&lt;br /&gt;
|felixaviat@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Madison Berger&lt;br /&gt;
|madison.berger@utdallas.edu&lt;br /&gt;
|UTexas Dallas&lt;br /&gt;
|-&lt;br /&gt;
|Oleg Borodin&lt;br /&gt;
|oleg.a.borodin.civ@mail.mil&lt;br /&gt;
|Army Rsch Lab&lt;br /&gt;
|-&lt;br /&gt;
|Bernie Brooks&lt;br /&gt;
|bernard.brooks@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Siqin Cao&lt;br /&gt;
|scao66@wisc.edu&lt;br /&gt;
|UWisconsin&lt;br /&gt;
|-&lt;br /&gt;
|Dave Cerutti&lt;br /&gt;
|dscerutti@gmail.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Chris Chipot&lt;br /&gt;
|chipot@illinois.edu&lt;br /&gt;
|UIllinois/CNRS&lt;br /&gt;
|-&lt;br /&gt;
|Igor Chollet&lt;br /&gt;
|igor.cholletpro@gmail.com&lt;br /&gt;
|Sorbonne, Paris &lt;br /&gt;
|-&lt;br /&gt;
|Moses Chung         &lt;br /&gt;
|  kchung25@wustl.edu        &lt;br /&gt;
|           Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Carine Clavaguera&lt;br /&gt;
|carine.clavaguera@universite-paris-saclay.fr|carine.clavaguera@universite-paris-saclay.fr&lt;br /&gt;
|UParis-Saclay&lt;br /&gt;
|-&lt;br /&gt;
|Chris Cooper&lt;br /&gt;
|christopher.cooper@usm.cl&lt;br /&gt;
|USM, Chile&lt;br /&gt;
|-&lt;br /&gt;
|Rae Corrigan&lt;br /&gt;
|rae-corrigan@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Tom Darden&lt;br /&gt;
|tom@eyesopen.com&lt;br /&gt;
|OpenEye&lt;br /&gt;
|-&lt;br /&gt;
|Omar Demerdash&lt;br /&gt;
|demerdashon@ornl.gov&lt;br /&gt;
|Oak Ridge Lab&lt;br /&gt;
|-&lt;br /&gt;
|Zach Glick&lt;br /&gt;
|zlg@gatech.edu&lt;br /&gt;
|Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Rose Gogal&lt;br /&gt;
|rose-gogal@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Hatice Gokcan&lt;br /&gt;
|hgokcan@andrew.cmu.edu&lt;br /&gt;
|Carnegie Mellon&lt;br /&gt;
|-&lt;br /&gt;
|Justin Gourary&lt;br /&gt;
|jtgourary@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Nohad Gresh&lt;br /&gt;
|gresh@lct.jussieu.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Alan Grossfield&lt;br /&gt;
|alan_grossfield@urmc.rochester.edu&lt;br /&gt;
|URochester&lt;br /&gt;
|-&lt;br /&gt;
|JC Gumbart&lt;br /&gt;
|jcgumbart@gatech.edu&lt;br /&gt;
|Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Dave Hardy&lt;br /&gt;
|dhardy@ks.uiuc.edu&lt;br /&gt;
|UIllinois&lt;br /&gt;
|-&lt;br /&gt;
|Florent Hédin&lt;br /&gt;
|florent@qubit-pharmaceuticals.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Chris Ho&lt;br /&gt;
|cho@newdrugdesign.com&lt;br /&gt;
|New Drug Design&lt;br /&gt;
|-&lt;br /&gt;
|Xuhui Huang&lt;br /&gt;
|xhuang@chem.wisc.edu&lt;br /&gt;
|UWisconsin&lt;br /&gt;
|-&lt;br /&gt;
|Toshiko Ichiye&lt;br /&gt;
|ti9@georgetown.edu&lt;br /&gt;
|Georgetown&lt;br /&gt;
|-&lt;br /&gt;
|Olexandr Isayev&lt;br /&gt;
|olexandr@cmu.edu&lt;br /&gt;
|Carnegie Mellon&lt;br /&gt;
|-&lt;br /&gt;
|Zach Jarin&lt;br /&gt;
|zachary.jarin@nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Théo Jeffrelot-Inizan&lt;br /&gt;
|theo.jaffrelot-inizan@lct.jussieu.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Francis Jing&lt;br /&gt;
|francijing@gmail.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Luc-Henri Jolly&lt;br /&gt;
|lhj@ip2ct.upmc.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Ken Jordan&lt;br /&gt;
|jordan@pitt.edu&lt;br /&gt;
|UPittsburgh&lt;br /&gt;
|-&lt;br /&gt;
|Bill Jorgensen&lt;br /&gt;
|william.jorgensen@yale.edu&lt;br /&gt;
|Yale&lt;br /&gt;
|-&lt;br /&gt;
|Christophe Jurczak&lt;br /&gt;
|christophe@quantonation.com&lt;br /&gt;
|Quantonation&lt;br /&gt;
|-&lt;br /&gt;
|Léa El Khoury&lt;br /&gt;
|lea@qubit-pharmaceuticals.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Klauda&lt;br /&gt;
|jbklauda@umd.edu&lt;br /&gt;
|UMaryland&lt;br /&gt;
|-&lt;br /&gt;
|Anmol Kumar&lt;br /&gt;
|anmol@outerbanks.umaryland.edu&lt;br /&gt;
|UMD Baltimore&lt;br /&gt;
|-&lt;br /&gt;
|Louis Lagardère&lt;br /&gt;
|louis.lagardere@gmail.com&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Jie Liang&lt;br /&gt;
|jliang@uic.edu&lt;br /&gt;
|UI Chicago&lt;br /&gt;
|-&lt;br /&gt;
|Filippo Lipparini&lt;br /&gt;
|filippo.lipparini@unipi.it&lt;br /&gt;
|UPisa, Italy&lt;br /&gt;
|-&lt;br /&gt;
|Chengwen Liu&lt;br /&gt;
|liuchw2010@gmail.com&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Daniele Loco&lt;br /&gt;
|daniele.loco01@gmail.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Ao Ma&lt;br /&gt;
|aoma@uic.edu&lt;br /&gt;
|UI Chicago&lt;br /&gt;
|-&lt;br /&gt;
|Nastasia Mauger&lt;br /&gt;
|nastasia.mauger@courriel.upmc.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Matthieu Montes&lt;br /&gt;
|matthieu.montes@cnam.fr&lt;br /&gt;
|CNAM, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Devin Mulvey&lt;br /&gt;
|dmm219@pitt.edu&lt;br /&gt;
|UPittsburgh&lt;br /&gt;
|-&lt;br /&gt;
|Jorge Nochebuena&lt;br /&gt;
|jorge.nochebuena@utdallas.edu&lt;br /&gt;
|UTexas Dallas&lt;br /&gt;
|-&lt;br /&gt;
|Michele Nottoli&lt;br /&gt;
|michele.nottoli@phd.unipi.it&lt;br /&gt;
|UPisa, Italy &lt;br /&gt;
|-&lt;br /&gt;
|Andrew Pang          &lt;br /&gt;
|andrewpang@gatech.edu            &lt;br /&gt;
|    Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Rich Pastor&lt;br /&gt;
|pastorr@nhlbi.nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Lalith Perera&lt;br /&gt;
|pereral2@niehs.nih.gov&lt;br /&gt;
|NIEHS NIH&lt;br /&gt;
|-&lt;br /&gt;
|Jean-Philip Piquemal&lt;br /&gt;
|[[Mailto:jean-philip.piquemal@sorbonne-universite.fr|jean-philip.piquemal@sorbonne-universite.fr]]&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Thomas Plé&lt;br /&gt;
|thomas.ple@hotmail.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Travis Pollard&lt;br /&gt;
|travis.p.pollard.civ@army.mil&lt;br /&gt;
|Army Rsch Lab&lt;br /&gt;
|-&lt;br /&gt;
|Jay Ponder&lt;br /&gt;
|ponder@dasher.wustl.edu&lt;br /&gt;
|Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Rui Qi&lt;br /&gt;
|rui.qi@roivant.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Josh Rackers&lt;br /&gt;
|jracker@sandia.gov&lt;br /&gt;
|Sandia Natl Lab&lt;br /&gt;
|-&lt;br /&gt;
|Pengyu Ren&lt;br /&gt;
|pren@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Amy Rice&lt;br /&gt;
|rice.amym@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Marc Riera&lt;br /&gt;
|mreirari@ucsd.edu&lt;br /&gt;
|UC San Diego&lt;br /&gt;
|-&lt;br /&gt;
|Chris Rowley&lt;br /&gt;
|christopherrowley@cunet.carleton.ca&lt;br /&gt;
|Carleton U, CA&lt;br /&gt;
|-&lt;br /&gt;
|Mike Schnieders&lt;br /&gt;
|michael-schnieders@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Ada Sedova&lt;br /&gt;
|sedovaaa@ornl.gov&lt;br /&gt;
|Oak Ridge Lab&lt;br /&gt;
|-&lt;br /&gt;
|Yihan Shao&lt;br /&gt;
|yihan.shao@ou.edu&lt;br /&gt;
|UOklahoma&lt;br /&gt;
|-&lt;br /&gt;
|Jana Shen&lt;br /&gt;
|jana.shen@rx.umaryland.edu&lt;br /&gt;
|UMD Baltimore&lt;br /&gt;
|-&lt;br /&gt;
|Roseane Silva&lt;br /&gt;
|roseane@wustl.edu&lt;br /&gt;
|Washington U &lt;br /&gt;
|-&lt;br /&gt;
|Andrew Thiel         &lt;br /&gt;
|andrew-thiel@uiowa.edu               &lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Richard Van&lt;br /&gt;
|van@ou.edu&lt;br /&gt;
|UOklahoma&lt;br /&gt;
|-&lt;br /&gt;
|Sameer Varma&lt;br /&gt;
|svarma@usf.edu&lt;br /&gt;
|USouth Florida&lt;br /&gt;
|-&lt;br /&gt;
|Elizabeth Wait&lt;br /&gt;
|elizabethewait@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Brandon Walker&lt;br /&gt;
|bdw2292@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Yanxing Wang&lt;br /&gt;
|yxw@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Zhi Wang&lt;br /&gt;
|wangzhi@wustl.edu&lt;br /&gt;
|Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Chuanjie Wu&lt;br /&gt;
|chuanjiewu@gmail.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Xiongwu Wu&lt;br /&gt;
|wuxw@nhlbi.nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Wei Yang&lt;br /&gt;
|yang@sb.fsu.edu&lt;br /&gt;
|Florida State&lt;br /&gt;
|-&lt;br /&gt;
|Ketsia Zinga         &lt;br /&gt;
|kzinga@utexas.edu                &lt;br /&gt;
|    UTexas Austin&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2053</id>
		<title>Tinkermeeting:tinkermeeting2022</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2053"/>
		<updated>2024-11-18T15:48:05Z</updated>

		<summary type="html">&lt;p&gt;Admin: Attendees&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Charlles  Abreu&lt;br /&gt;
|abreu@eq.ufrj.br&lt;br /&gt;
|U Rio de Janeiro&lt;br /&gt;
|-&lt;br /&gt;
|Olivier Adjoua&lt;br /&gt;
|passi.adjoua@sorbonne-universite.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Cole Allen&lt;br /&gt;
|coleallen@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Felix Aviat&lt;br /&gt;
|felixaviat@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Madison Berger&lt;br /&gt;
|madison.berger@utdallas.edu&lt;br /&gt;
|UTexas Dallas&lt;br /&gt;
|-&lt;br /&gt;
|Oleg Borodin&lt;br /&gt;
|oleg.a.borodin.civ@mail.mil&lt;br /&gt;
|Army Rsch Lab&lt;br /&gt;
|-&lt;br /&gt;
|Bernie Brooks&lt;br /&gt;
|bernard.brooks@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Siqin Cao&lt;br /&gt;
|scao66@wisc.edu&lt;br /&gt;
|UWisconsin&lt;br /&gt;
|-&lt;br /&gt;
|Dave Cerutti&lt;br /&gt;
|dscerutti@gmail.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Chris Chipot&lt;br /&gt;
|chipot@illinois.edu&lt;br /&gt;
|UIllinois/CNRS&lt;br /&gt;
|-&lt;br /&gt;
|Igor Chollet&lt;br /&gt;
|igor.cholletpro@gmail.com&lt;br /&gt;
|Sorbonne, Paris &lt;br /&gt;
|-&lt;br /&gt;
|Moses Chung         &lt;br /&gt;
|  kchung25@wustl.edu        &lt;br /&gt;
|           Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Carine Clavaguera&lt;br /&gt;
|[[Mailto:carine.clavaguera@universite-paris-saclay.fr|carine.clavaguera@universite-paris-saclay.fr]]&lt;br /&gt;
|UParis-Saclay&lt;br /&gt;
|-&lt;br /&gt;
|Chris Cooper&lt;br /&gt;
|christopher.cooper@usm.cl&lt;br /&gt;
|USM, Chile&lt;br /&gt;
|-&lt;br /&gt;
|Rae Corrigan&lt;br /&gt;
|rae-corrigan@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Tom Darden&lt;br /&gt;
|tom@eyesopen.com&lt;br /&gt;
|OpenEye&lt;br /&gt;
|-&lt;br /&gt;
|Omar Demerdash&lt;br /&gt;
|demerdashon@ornl.gov&lt;br /&gt;
|Oak Ridge Lab&lt;br /&gt;
|-&lt;br /&gt;
|Zach Glick&lt;br /&gt;
|zlg@gatech.edu&lt;br /&gt;
|Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Rose Gogal&lt;br /&gt;
|rose-gogal@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Hatice Gokcan&lt;br /&gt;
|hgokcan@andrew.cmu.edu&lt;br /&gt;
|Carnegie Mellon&lt;br /&gt;
|-&lt;br /&gt;
|Justin Gourary&lt;br /&gt;
|jtgourary@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Nohad Gresh&lt;br /&gt;
|gresh@lct.jussieu.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Alan Grossfield&lt;br /&gt;
|alan_grossfield@urmc.rochester.edu&lt;br /&gt;
|URochester&lt;br /&gt;
|-&lt;br /&gt;
|JC Gumbart&lt;br /&gt;
|jcgumbart@gatech.edu&lt;br /&gt;
|Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Dave Hardy&lt;br /&gt;
|dhardy@ks.uiuc.edu&lt;br /&gt;
|UIllinois&lt;br /&gt;
|-&lt;br /&gt;
|Florent Hédin&lt;br /&gt;
|florent@qubit-pharmaceuticals.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Chris Ho&lt;br /&gt;
|cho@newdrugdesign.com&lt;br /&gt;
|New Drug Design&lt;br /&gt;
|-&lt;br /&gt;
|Xuhui Huang&lt;br /&gt;
|xhuang@chem.wisc.edu&lt;br /&gt;
|UWisconsin&lt;br /&gt;
|-&lt;br /&gt;
|Toshiko Ichiye&lt;br /&gt;
|ti9@georgetown.edu&lt;br /&gt;
|Georgetown&lt;br /&gt;
|-&lt;br /&gt;
|Olexandr Isayev&lt;br /&gt;
|olexandr@cmu.edu&lt;br /&gt;
|Carnegie Mellon&lt;br /&gt;
|-&lt;br /&gt;
|Zach Jarin&lt;br /&gt;
|zachary.jarin@nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Théo Jeffrelot-Inizan&lt;br /&gt;
|theo.jaffrelot-inizan@lct.jussieu.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Francis Jing&lt;br /&gt;
|francijing@gmail.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Luc-Henri Jolly&lt;br /&gt;
|lhj@ip2ct.upmc.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Ken Jordan&lt;br /&gt;
|jordan@pitt.edu&lt;br /&gt;
|UPittsburgh&lt;br /&gt;
|-&lt;br /&gt;
|Bill Jorgensen&lt;br /&gt;
|william.jorgensen@yale.edu&lt;br /&gt;
|Yale&lt;br /&gt;
|-&lt;br /&gt;
|Christophe Jurczak&lt;br /&gt;
|christophe@quantonation.com&lt;br /&gt;
|Quantonation&lt;br /&gt;
|-&lt;br /&gt;
|Léa El Khoury&lt;br /&gt;
|lea@qubit-pharmaceuticals.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Klauda&lt;br /&gt;
|jbklauda@umd.edu&lt;br /&gt;
|UMaryland&lt;br /&gt;
|-&lt;br /&gt;
|Anmol Kumar&lt;br /&gt;
|anmol@outerbanks.umaryland.edu&lt;br /&gt;
|UMD Baltimore&lt;br /&gt;
|-&lt;br /&gt;
|Louis Lagardère&lt;br /&gt;
|louis.lagardere@gmail.com&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Jie Liang&lt;br /&gt;
|jliang@uic.edu&lt;br /&gt;
|UI Chicago&lt;br /&gt;
|-&lt;br /&gt;
|Filippo Lipparini&lt;br /&gt;
|filippo.lipparini@unipi.it&lt;br /&gt;
|UPisa, Italy&lt;br /&gt;
|-&lt;br /&gt;
|Chengwen Liu&lt;br /&gt;
|liuchw2010@gmail.com&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Daniele Loco&lt;br /&gt;
|daniele.loco01@gmail.com&lt;br /&gt;
|Qubit&lt;br /&gt;
|-&lt;br /&gt;
|Ao Ma&lt;br /&gt;
|aoma@uic.edu&lt;br /&gt;
|UI Chicago&lt;br /&gt;
|-&lt;br /&gt;
|Nastasia Mauger&lt;br /&gt;
|nastasia.mauger@courriel.upmc.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Matthieu Montes&lt;br /&gt;
|matthieu.montes@cnam.fr&lt;br /&gt;
|CNAM, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Devin Mulvey&lt;br /&gt;
|dmm219@pitt.edu&lt;br /&gt;
|UPittsburgh&lt;br /&gt;
|-&lt;br /&gt;
|Jorge Nochebuena&lt;br /&gt;
|jorge.nochebuena@utdallas.edu&lt;br /&gt;
|UTexas Dallas&lt;br /&gt;
|-&lt;br /&gt;
|Michele Nottoli&lt;br /&gt;
|michele.nottoli@phd.unipi.it&lt;br /&gt;
|UPisa, Italy &lt;br /&gt;
|-&lt;br /&gt;
|Andrew Pang          &lt;br /&gt;
|andrewpang@gatech.edu            &lt;br /&gt;
|    Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
|Rich Pastor&lt;br /&gt;
|pastorr@nhlbi.nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Lalith Perera&lt;br /&gt;
|pereral2@niehs.nih.gov&lt;br /&gt;
|NIEHS NIH&lt;br /&gt;
|-&lt;br /&gt;
|Jean-Philip Piquemal&lt;br /&gt;
|[[Mailto:jean-philip.piquemal@sorbonne-universite.fr|jean-philip.piquemal@sorbonne-universite.fr]]&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Thomas Plé&lt;br /&gt;
|thomas.ple@hotmail.fr&lt;br /&gt;
|Sorbonne, Paris&lt;br /&gt;
|-&lt;br /&gt;
|Travis Pollard&lt;br /&gt;
|travis.p.pollard.civ@army.mil&lt;br /&gt;
|Army Rsch Lab&lt;br /&gt;
|-&lt;br /&gt;
|Jay Ponder&lt;br /&gt;
|ponder@dasher.wustl.edu&lt;br /&gt;
|Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Rui Qi&lt;br /&gt;
|rui.qi@roivant.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Josh Rackers&lt;br /&gt;
|jracker@sandia.gov&lt;br /&gt;
|Sandia Natl Lab&lt;br /&gt;
|-&lt;br /&gt;
|Pengyu Ren&lt;br /&gt;
|pren@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Amy Rice&lt;br /&gt;
|rice.amym@gmail.com&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Marc Riera&lt;br /&gt;
|mreirari@ucsd.edu&lt;br /&gt;
|UC San Diego&lt;br /&gt;
|-&lt;br /&gt;
|Chris Rowley&lt;br /&gt;
|christopherrowley@cunet.carleton.ca&lt;br /&gt;
|Carleton U, CA&lt;br /&gt;
|-&lt;br /&gt;
|Mike Schnieders&lt;br /&gt;
|michael-schnieders@uiowa.edu&lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Ada Sedova&lt;br /&gt;
|sedovaaa@ornl.gov&lt;br /&gt;
|Oak Ridge Lab&lt;br /&gt;
|-&lt;br /&gt;
|Yihan Shao&lt;br /&gt;
|yihan.shao@ou.edu&lt;br /&gt;
|UOklahoma&lt;br /&gt;
|-&lt;br /&gt;
|Jana Shen&lt;br /&gt;
|jana.shen@rx.umaryland.edu&lt;br /&gt;
|UMD Baltimore&lt;br /&gt;
|-&lt;br /&gt;
|Roseane Silva&lt;br /&gt;
|roseane@wustl.edu&lt;br /&gt;
|Washington U &lt;br /&gt;
|-&lt;br /&gt;
|Andrew Thiel         &lt;br /&gt;
|andrew-thiel@uiowa.edu               &lt;br /&gt;
|UIowa&lt;br /&gt;
|-&lt;br /&gt;
|Richard Van&lt;br /&gt;
|van@ou.edu&lt;br /&gt;
|UOklahoma&lt;br /&gt;
|-&lt;br /&gt;
|Sameer Varma&lt;br /&gt;
|svarma@usf.edu&lt;br /&gt;
|USouth Florida&lt;br /&gt;
|-&lt;br /&gt;
|Elizabeth Wait&lt;br /&gt;
|elizabethewait@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Brandon Walker&lt;br /&gt;
|bdw2292@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Yanxing Wang&lt;br /&gt;
|yxw@utexas.edu&lt;br /&gt;
|UTexas Austin&lt;br /&gt;
|-&lt;br /&gt;
|Zhi Wang&lt;br /&gt;
|wangzhi@wustl.edu&lt;br /&gt;
|Washington U&lt;br /&gt;
|-&lt;br /&gt;
|Chuanjie Wu&lt;br /&gt;
|chuanjiewu@gmail.com&lt;br /&gt;
|Roivant&lt;br /&gt;
|-&lt;br /&gt;
|Xiongwu Wu&lt;br /&gt;
|wuxw@nhlbi.nih.gov&lt;br /&gt;
|NHLBI NIH&lt;br /&gt;
|-&lt;br /&gt;
|Wei Yang&lt;br /&gt;
|yang@sb.fsu.edu&lt;br /&gt;
|Florida State&lt;br /&gt;
|-&lt;br /&gt;
|Ketsia Zinga         &lt;br /&gt;
|kzinga@utexas.edu                &lt;br /&gt;
|    UTexas Austin&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2052</id>
		<title>Tinkermeeting:tinkermeeting2022</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tinkermeeting:tinkermeeting2022&amp;diff=2052"/>
		<updated>2024-11-18T15:42:29Z</updated>

		<summary type="html">&lt;p&gt;Admin: Created page with &amp;quot;2022 Maryland  #########################################################################  ATTENDEE LIST FOR TINKER DEVELOPER WORKSHOP, JUNE 2-4 2022, NIH, BETHESDA  #########################################################################   Charlles Abreu        abreu@eq.ufrj.br                      U Rio de Janeiro  Olivier Adjoua        passi.adjoua@sorbonne-universite.fr   Sorbonne, Paris  Cole Allen            coleallen@utexas.edu                  UTexas Austin  Feli...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;2022 Maryland&lt;br /&gt;
&lt;br /&gt;
######################################################################### &lt;br /&gt;
ATTENDEE LIST FOR TINKER DEVELOPER WORKSHOP, JUNE 2-4 2022, NIH, BETHESDA &lt;br /&gt;
#########################################################################  &lt;br /&gt;
Charlles Abreu        abreu@eq.ufrj.br                      U Rio de Janeiro &lt;br /&gt;
Olivier Adjoua        passi.adjoua@sorbonne-universite.fr   Sorbonne, Paris &lt;br /&gt;
Cole Allen            coleallen@utexas.edu                  UTexas Austin &lt;br /&gt;
Felix Aviat           felixaviat@gmail.com                  NHLBI NIH &lt;br /&gt;
Madison Berger        madison.berger@utdallas.edu           UTexas Dallas &lt;br /&gt;
Oleg Borodin          oleg.a.borodin.civ@mail.mil           Army Rsch Lab &lt;br /&gt;
Bernie Brooks         bernard.brooks@gmail.com              NHLBI NIH &lt;br /&gt;
Siqin Cao             scao66@wisc.edu                       UWisconsin &lt;br /&gt;
Dave Cerutti          dscerutti@gmail.com                   Roivant &lt;br /&gt;
Chris Chipot          chipot@illinois.edu                   UIllinois/CNRS &lt;br /&gt;
Igor Chollet          igor.cholletpro@gmail.com             Sorbonne, Paris &lt;br /&gt;
Moses Chung           kchung25@wustl.edu                    Washington U &lt;br /&gt;
Carine Clavaguera     carine.clavaguera &lt;br /&gt;
                          @universite-paris-saclay.fr       UParis-Saclay &lt;br /&gt;
Chris Cooper          christopher.cooper@usm.cl             USM, Chile &lt;br /&gt;
Rae Corrigan          rae-corrigan@uiowa.edu                UIowa           &lt;br /&gt;
Tom Darden            tom@eyesopen.com                      OpenEye &lt;br /&gt;
Omar Demerdash        demerdashon@ornl.gov                  Oak Ridge Lab &lt;br /&gt;
Zach Glick            zlg@gatech.edu                        Georgia Tech &lt;br /&gt;
Rose Gogal            rose-gogal@uiowa.edu                  UIowa &lt;br /&gt;
Hatice Gokcan         hgokcan@andrew.cmu.edu                Carnegie Mellon &lt;br /&gt;
Justin Gourary        jtgourary@utexas.edu                  UTexas Austin &lt;br /&gt;
Nohad Gresh           gresh@lct.jussieu.fr                  Sorbonne, Paris &lt;br /&gt;
Alan Grossfield       alan_grossfield@urmc.rochester.edu    URochester &lt;br /&gt;
JC Gumbart            jcgumbart@gatech.edu                  Georgia Tech &lt;br /&gt;
Dave Hardy            dhardy@ks.uiuc.edu                    UIllinois &lt;br /&gt;
Florent Hédin         florent@qubit-pharmaceuticals.com     Qubit &lt;br /&gt;
Chris Ho              cho@newdrugdesign.com                 New Drug Design &lt;br /&gt;
Xuhui Huang           xhuang@chem.wisc.edu                  UWisconsin &lt;br /&gt;
Toshiko Ichiye        ti9@georgetown.edu                    Georgetown &lt;br /&gt;
Olexandr Isayev       olexandr@cmu.edu                      Carnegie Mellon &lt;br /&gt;
Zach Jarin            zachary.jarin@nih.gov                 NHLBI NIH &lt;br /&gt;
Théo Jeffrelot-Inizan theo.jaffrelot-inizan@lct.jussieu.fr  Sorbonne, Paris &lt;br /&gt;
Francis Jing          francijing@gmail.com                  Qubit &lt;br /&gt;
Luc-Henri Jolly       lhj@ip2ct.upmc.fr                     Sorbonne, Paris &lt;br /&gt;
Ken Jordan            jordan@pitt.edu                       UPittsburgh &lt;br /&gt;
Bill Jorgensen        william.jorgensen@yale.edu            Yale &lt;br /&gt;
Christophe Jurczak    christophe@quantonation.com           Quantonation &lt;br /&gt;
Léa El Khoury         lea@qubit-pharmaceuticals.com         Qubit &lt;br /&gt;
Jeff Klauda           jbklauda@umd.edu                      UMaryland &lt;br /&gt;
Anmol Kumar           anmol@outerbanks.umaryland.edu        UMD Baltimore &lt;br /&gt;
Louis Lagardère       louis.lagardere@gmail.com             Sorbonne, Paris &lt;br /&gt;
Jie Liang             jliang@uic.edu                        UI Chicago &lt;br /&gt;
Filippo Lipparini     filippo.lipparini@unipi.it            UPisa, Italy &lt;br /&gt;
Chengwen Liu          liuchw2010@gmail.com                  UTexas Austin &lt;br /&gt;
Daniele Loco          daniele.loco01@gmail.com              Qubit &lt;br /&gt;
Ao Ma                 aoma@uic.edu                          UI Chicago &lt;br /&gt;
Nastasia Mauger       nastasia.mauger@courriel.upmc.fr      Sorbonne, Paris &lt;br /&gt;
Matthieu Montes       matthieu.montes@cnam.fr               CNAM, Paris &lt;br /&gt;
Devin Mulvey          dmm219@pitt.edu                       UPittsburgh &lt;br /&gt;
Jorge Nochebuena      jorge.nochebuena@utdallas.edu         UTexas Dallas &lt;br /&gt;
Michele Nottoli       michele.nottoli@phd.unipi.it          UPisa, Italy &lt;br /&gt;
Andrew Pang           andrewpang@gatech.edu                 Georgia Tech &lt;br /&gt;
Rich Pastor           pastorr@nhlbi.nih.gov                 NHLBI NIH &lt;br /&gt;
Lalith Perera         pereral2@niehs.nih.gov                NIEHS NIH &lt;br /&gt;
Jean-Philip Piquemal  jean-philip.piquemal &lt;br /&gt;
                          @sorbonne-universite.fr           Sorbonne, Paris &lt;br /&gt;
Thomas Plé            thomas.ple@hotmail.fr                 Sorbonne, Paris &lt;br /&gt;
Travis Pollard        travis.p.pollard.civ@army.mil         Army Rsch Lab &lt;br /&gt;
Jay Ponder            ponder@dasher.wustl.edu               Washington U &lt;br /&gt;
Rui Qi                rui.qi@roivant.com                    Roivant &lt;br /&gt;
Josh Rackers          jracker@sandia.gov                    Sandia Natl Lab &lt;br /&gt;
Pengyu Ren            pren@utexas.edu                       UTexas Austin &lt;br /&gt;
Amy Rice              rice.amym@gmail.com                   NHLBI NIH &lt;br /&gt;
Marc Riera            mreirari@ucsd.edu                     UC San Diego &lt;br /&gt;
Chris Rowley          christopherrowley@cunet.carleton.ca   Carleton U, CA &lt;br /&gt;
Mike Schnieders       michael-schnieders@uiowa.edu          UIowa &lt;br /&gt;
Ada Sedova            sedovaaa@ornl.gov                     Oak Ridge Lab &lt;br /&gt;
Yihan Shao            yihan.shao@ou.edu                     UOklahoma &lt;br /&gt;
Jana Shen             jana.shen@rx.umaryland.edu            UMD Baltimore &lt;br /&gt;
Roseane Silva         roseane@wustl.edu                     Washington U &lt;br /&gt;
Andrew Thiel          andrew-thiel@uiowa.edu                UIowa &lt;br /&gt;
Richard Van           van@ou.edu                            UOklahoma &lt;br /&gt;
Sameer Varma          svarma@usf.edu                        USouth Florida &lt;br /&gt;
Elizabeth Wait        elizabethewait@utexas.edu             UTexas Austin &lt;br /&gt;
Brandon Walker        bdw2292@utexas.edu                    UTexas Austin &lt;br /&gt;
Yanxing Wang          yxw@utexas.edu                        UTexas Austin &lt;br /&gt;
Zhi Wang              wangzhi@wustl.edu                     Washington U &lt;br /&gt;
Chuanjie Wu           chuanjiewu@gmail.com                  Roivant &lt;br /&gt;
Xiongwu Wu            wuxw@nhlbi.nih.gov                    NHLBI NIH &lt;br /&gt;
Wei Yang              yang@sb.fsu.edu                       Florida State &lt;br /&gt;
Ketsia Zinga          kzinga@utexas.edu                     UTexas Austin&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:amoeba_FF&amp;diff=2011</id>
		<title>Tutorial:amoeba FF</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:amoeba_FF&amp;diff=2011"/>
		<updated>2024-04-16T13:50:58Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;See [https://biomolmd.org/mw/index.php/Tutorial:tinkertut#AMOEBA_Force_Field_Papers: &amp;quot;this page&amp;quot;] under Tutorials&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:amoeba_FF&amp;diff=2010</id>
		<title>Tutorial:amoeba FF</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:amoeba_FF&amp;diff=2010"/>
		<updated>2024-04-16T13:50:23Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;See [https://biomolmd.org/mw/index.php/Tutorial:tinkertut page] under Tutorials&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:amoeba_FF&amp;diff=2009</id>
		<title>Tutorial:amoeba FF</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:amoeba_FF&amp;diff=2009"/>
		<updated>2024-04-16T13:49:31Z</updated>

		<summary type="html">&lt;p&gt;Admin: Created page with &amp;quot;See page under Tutorials&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;See [[Tutorial:tinkertut#AMOEBA_Force_Field_Papers|page]] under Tutorials&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=MediaWiki:Sidebar&amp;diff=2008</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=MediaWiki:Sidebar&amp;diff=2008"/>
		<updated>2024-04-16T13:48:00Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;*Naviation&lt;br /&gt;
&lt;br /&gt;
*Welcome &lt;br /&gt;
**mainpage|mainpage-description&lt;br /&gt;
**lab:labinfo|Lab Information&lt;br /&gt;
**TinkerMeeting&amp;quot;tinkerconf |Tinker Annual Meetings&lt;br /&gt;
&lt;br /&gt;
*Software&lt;br /&gt;
**Software:tinkercpu | Tinker CPU&lt;br /&gt;
**Software:tinkergpu | Tinker GPU&lt;br /&gt;
**Software:labsoft| List of software in lab&lt;br /&gt;
&lt;br /&gt;
*Tutorials&lt;br /&gt;
**tutorial:tinkertut| Using Tinker &amp;amp; AMOEBA&lt;br /&gt;
**tutorial:tools| Tools for Tinker&lt;br /&gt;
**Lab:newuser | Using lab cluster&lt;br /&gt;
**tutroial:alltut|Other tutorials&lt;br /&gt;
**tutorial:amber| AMBER&lt;br /&gt;
**tutorial:amm| Adv Mol Modeling&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*AMOEBA ForceField &lt;br /&gt;
**tutorial:amoeba FF| Background papers&lt;br /&gt;
**Project:amoeba | Official parameters &lt;br /&gt;
**Poltype:Poltype | POLTYPE &lt;br /&gt;
**Software:forcebalance | ForceBalance&lt;br /&gt;
**Project:ML | ML    &lt;br /&gt;
 &lt;br /&gt;
*Coarse-Grained RNA (RACER) &lt;br /&gt;
**Project:Development-rna |Development &lt;br /&gt;
**Project:tutorials-rna |Tutorials   &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;br /&gt;
&lt;br /&gt;
* navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help-mediawiki&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2007</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2007"/>
		<updated>2024-04-16T13:45:44Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* AMOEBA Force Field Papers: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker executables from [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the oppurtunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/ &lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9 (above) Or tinker-openmm:&lt;br /&gt;
&lt;br /&gt;
  export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
  export CUDA_VISIBLE_DEVICES=0 # device number, 0, 1...is the 1st, 2nd...&lt;br /&gt;
  #source cuda, tinker-openmm, gcc related env var (see tinker-openmm install)&lt;br /&gt;
  nohup dynamic_omm.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.0001”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equlibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to spede up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error. &lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be.&amp;amp;nbsp;Water/ions are&amp;amp;nbsp;relaxed after this step. &lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run&amp;amp;nbsp;1.5&amp;amp;nbsp;ns NPT to compute the average density/box size (ignore the first 300ps). &#039;&#039;&#039;For GPU, only &amp;quot;barostat MonteCarlo&amp;quot; is available.&#039;&#039;&#039;&amp;amp;nbsp; &lt;br /&gt;
**NVT MD for ~2ns with box fixed at the average lengths from above. &lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
===AMEOBA FF:===&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
===AMOEBA+ model (water published, small and biomolecules in progress)===&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
===AMOEBA+NN model: incorporating Neural Networks===&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
	&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2006</id>
		<title>Tutorial:tinkertut</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Tutorial:tinkertut&amp;diff=2006"/>
		<updated>2024-04-16T13:44:52Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* AMOEBA Force Field Papers: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Purposes =&lt;br /&gt;
This page provide tutorials on using AMOEBA force field via Tinker (CPU) and Tinker-OpenMM (GPU) programs.&lt;br /&gt;
&lt;br /&gt;
= Tutorials =&lt;br /&gt;
&lt;br /&gt;
Some simple tutorials about Tinker I used in my teaching below. Note you can directly download tinker executables from [https://dasher.wustl.edu/tinker/ https://dasher.wustl.edu/tinker/]&amp;amp;nbsp;(Windows, mac. linux) for the following tutorials.&lt;br /&gt;
&lt;br /&gt;
You can either use command lines in Windows CMD window or Linux terminals, or use FFX interface for some exercises. &#039;&#039;&#039;Actually applications always use command lines to operate in Linux OS&#039;&#039;&#039;. If you are not familiar with Linux, this is the oppurtunity to practice.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/span&amp;gt;[https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/ &amp;lt;span style=&amp;quot;background-color:#ffff00;&amp;quot;&amp;gt;https://biomol.bme.utexas.edu/~pren/courses/tinker-tut/&amp;lt;/span&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
Below you will find more detailed instructions and discussions.&lt;br /&gt;
&lt;br /&gt;
= Input files =&lt;br /&gt;
&lt;br /&gt;
You can find examples of input files in tinker distribution under tinker/bench, tinker/example or tinker/test. Two files are required to run TINKER calculations: *.xyz and *.key For example, open butane.xyz and butane.key in tinker/example/ (available in all official distributions) to see what’s inside.&lt;br /&gt;
&lt;br /&gt;
== *.xyz file ==&lt;br /&gt;
&lt;br /&gt;
*The first number on the 1st line is how many atoms total. &lt;br /&gt;
*There may be a second line that specify the box dimensions if the system is periodic (newer format since tinker 6) &lt;br /&gt;
*The first column is the atomic index &lt;br /&gt;
*The second column is the atomic symbol &lt;br /&gt;
*The 3 -5th columns are x,y,z coordinates in Angstrom &lt;br /&gt;
*The 6th is the “atom type” defined in the *.key file. This is the index tinker uses to assign parameters from the key/parameter file. &lt;br /&gt;
*The 7th – last columns are lists of atoms that are connected to the current atom&lt;br /&gt;
&lt;br /&gt;
== *.key file ==&lt;br /&gt;
&lt;br /&gt;
The key file may have all the actual parameters or a link to the actual parameters file specified in the first line. The parameters specify the bond, angle, torsion, vdW and electrostatic interactions between atoms based on the “atom type”. If you see an error related to OMP, please set the OPENMP-THREADS in the key file to a number less than the # of CPU cores on your computer. This sets how many CPU cores are used in the parallel execution.&lt;br /&gt;
&lt;br /&gt;
For example, in protein.key below, borrowed from tinker/bench/bench7.key, the first line specific the actual parameters are contain in the amoebapro13.prm. More examples can be found in tinker/bench, tinker/example, or tinker/test.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 parameters           $TINKERDIR/params/amoebapro13.prm&lt;br /&gt;
 # &lt;br /&gt;
 # the amoebapro13.prm is the AMOEBA protein force field in tinker/params/. If you have a ligand you can add the parameters below. More info below&lt;br /&gt;
 #&lt;br /&gt;
 # verbose                                  &#039;&#039;# printing info for every step, for debugging mostly&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #randomseed            123456789&lt;br /&gt;
 integrator            respa                &#039;&#039;#this multi-time step integrator allows TINKER to use 2 fs time step&#039;&#039;&lt;br /&gt;
 #HEAVY-HYDROGEN                    #&#039;&#039;This will increase H atom mass automatically so 3 or 3.5 fs time step can be used.                          &#039;&#039;&lt;br /&gt;
 &amp;amp;nbsp;                                  #&#039;&#039;Kinetics will  be affected               &#039;&#039;&lt;br /&gt;
 neighbor-list                              &#039;&#039;# this below requires your box is twice the cutoff plus 2-3 Ang.&#039;&#039;&lt;br /&gt;
                                           # &#039;&#039;If your box is too small for vdw cutoff but OK for Ewald, you can use &amp;quot;mpole-list&amp;quot; here.&#039;&#039;&lt;br /&gt;
 #openmp-threads    16                       &#039;&#039;# how many core you want to use on the node.&#039;&#039;&lt;br /&gt;
 #&lt;br /&gt;
 #  Define the Periodic Box and Cutoffs&lt;br /&gt;
 #&lt;br /&gt;
 a-axis                62.23&lt;br /&gt;
 vdw-cutoff            12.0&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Ewald Summation&lt;br /&gt;
 #&lt;br /&gt;
 ewald&lt;br /&gt;
 ewald-cutoff          7.0                  &#039;&#039;# we use such small cutoff because dipole/quadrupole die off faster than point charge.&#039;&#039;&lt;br /&gt;
 # pme-grid  64 64 64                         &#039;&#039;#If speed is a concern, set this mannually to be slightly bigger than simulation box size. E.g. use 64 is box is 62.23 (1.2x is the best but slower). &#039;&#039;&lt;br /&gt;
                                            &#039;&#039;Must be even with factors of only 2, 3 and 5. see source/kewald.f for a list. Sometimes the default grid size is conservative&#039;&#039; &lt;br /&gt;
 &#039;&#039;                                  &#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
 #fft-package           FFTW&lt;br /&gt;
 #&lt;br /&gt;
 #  Set Parameters for Induced Dipole Convergence&lt;br /&gt;
 #&lt;br /&gt;
 #polarization OPT3                         #OPT4 is mre accurate but OPT3 is faster&#039;&#039;&#039;&lt;br /&gt;
 polar-eps             0.001                &#039;&#039;# the induced dipole convergence threshold&#039;&#039;&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #&lt;br /&gt;
 # Example of overwriting the parameters in the .prm file. The bond parameters between &lt;br /&gt;
 # atom classes 1 and 4 are redefined below, which&lt;br /&gt;
 # will overwrite those already in the amoebapro13.prm. &lt;br /&gt;
 #this is only for illustration purpose&lt;br /&gt;
 # bond          1    4          200.00     1.1&lt;br /&gt;
&lt;br /&gt;
= How to generate input files of your own =&lt;br /&gt;
&lt;br /&gt;
== proteins, nucleic acids, common organics ==&lt;br /&gt;
&lt;br /&gt;
In tinker/params, you can find pre-existing parameters for certain molecular systems, both AMOEBA, amber, charmm, opls, mmff, and mm2/3.&lt;br /&gt;
&lt;br /&gt;
== PDB to xyz ==&lt;br /&gt;
&lt;br /&gt;
If you have a pdb file you can convert it tinker xyz file by specifying a prm file above. It will remove the heteroatoms such as ligand, which you can use POLTYPE to generate parameters for.&lt;br /&gt;
&lt;br /&gt;
First you need to determine the protonation state of charged residue. Tools like propka can do this quikly: [http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&lt;br /&gt;
&lt;br /&gt;
Once you decided the protonation state, make sure the residue name in PDB file match the protonation state (list below). For example, ASH is the neutral form of ASP. Then you can run &amp;quot;pdbxyz.x&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&#039;GLY&#039; &#039;ALA&#039; &#039;VAL&#039; &#039;LEU&#039; &#039;ILE&#039; &#039;SER&#039; &#039;THR&#039; &#039;CYS&#039; &#039;CYX&#039; &#039;CYD&#039; &#039;PRO&#039; &#039;PHE&#039; &#039;TYR&#039; &#039;TYD&#039; &#039;TRP&#039; &#039;HIS&#039; &#039;HID&#039; &#039;HIE&#039; &#039;ASP&#039; &#039;ASH&#039; &#039;ASN&#039; &#039;GLU&#039; &#039;GLH&#039; &#039;GLN&#039; &#039;MET&#039; &#039;LYS&#039; &#039;LYD&#039; &#039;ARG&#039; &#039;ORN&#039; &#039;AIB&#039; &#039;PCA&#039; &#039;UNK&#039;&lt;br /&gt;
&lt;br /&gt;
UNK means unownk; AIB, ORN and PCA&amp;amp;nbsp; are modified AA.&lt;br /&gt;
&lt;br /&gt;
[https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN https://www.ebi.ac.uk/pdbe/entry/pdb/3q9g/modified/ORN]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA http://www.ebi.ac.uk/pdbe/entry/pdb/4ua7/modified/PCA]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Terminal residue names:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
COH ACE NH2 NME&amp;amp;nbsp; FOR&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HETATM&#039;&#039;&#039; (residue name) recoginzed by pdbxyz:&lt;br /&gt;
&lt;br /&gt;
HOH K CA MG NA CL&lt;br /&gt;
&lt;br /&gt;
== AMOEBA library ==&lt;br /&gt;
&lt;br /&gt;
For AMOEBA, please use amoeba09.prm for common small molecules, amoebapro13.prm for proteins. Nucleic acid parameters coming soon (end of 2017). More information here: [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Amoeba]&lt;br /&gt;
&lt;br /&gt;
If you have a protein, you use &amp;quot;pdbxyz&amp;quot; to convert it to tinker xyz file. It will ask you for a key file (1bty.key below) or you can create a key file with &amp;quot;parameters $TINKERDIR/params/amoebapro13.prm&amp;quot; in it:&lt;br /&gt;
&lt;br /&gt;
 pdbxyz 1bty.pdb -k ./1bty.key&lt;br /&gt;
&lt;br /&gt;
== AMOEBA for a new ligand ==&lt;br /&gt;
&lt;br /&gt;
Note that pdbxyz recognize proteins, water (res name HOH and some ions). The ligand (benzamidine above) is stripped. For that you need to derive your own parameters. For AMOEBA this can be done using POLTYPE: [https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype https://biomol.bme.utexas.edu/wiki/index.php/Research_ex:Poltype]&lt;br /&gt;
&lt;br /&gt;
 Input: ligand.sdf or ligand.pdb (for example, you can truncate the ligand &amp;quot;BEN&amp;quot; out of the 1bty.pdb) &lt;br /&gt;
 Output: will produce the xyz and corresponding key files (ttt.xyz and ttt.key):&lt;br /&gt;
&lt;br /&gt;
If you will merge the ligand xyz file with another molecule, &#039;&#039;&#039;make sure you set the suitable range for atom types (an option for pOLTYPE) so that they won&#039;t overlap.&#039;&#039;&#039; See the &amp;quot;Check the results section&amp;quot; on POLTYPE website before using them. Use &amp;quot;analyze.x&amp;quot; to make sure the xyz and key files work correctly: &amp;quot;analyze.x ttt.xyz -k ttt.key ep&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== build a solvent box ==&lt;br /&gt;
&lt;br /&gt;
=== arbirary solvent ===&lt;br /&gt;
&lt;br /&gt;
Use xyzedit.x to build a water (or any solvent) box starting from a water monomer (e.g. tinker/test/water.xyz). You can specify many monomers to add and how big the box is. Type xyzedit.x at the command line and you will be asked to enter relevant inputs (or you may type all the parameters in one line).&lt;br /&gt;
&lt;br /&gt;
Make sure edit the key file to add box size and Ewald related keywords (see [http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file http://biomol.bme.utexas.edu/tinker-openmm/index.php/TINKER-OPENMM:Tinker-tut#.2A.key_file])&lt;br /&gt;
&lt;br /&gt;
=== prebuilt water box ===&lt;br /&gt;
&lt;br /&gt;
Some prebuilt waterboxs:&amp;amp;nbsp;[http://biomol.bme.utexas.edu/~pren/downloads/waterbox http://biomol.bme.utexas.edu/~pren/downloads/waterbox]&lt;br /&gt;
&lt;br /&gt;
Larger boxes can be created as supercells of smaller boxes, e.g. this following command will create a box 64x larger than the orignial box.&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 echo -e &amp;quot;5\n4\n\n&amp;quot; | crystal.x watersmall.xyz -k tinker.key&lt;br /&gt;
== Combining two xyz files ==&lt;br /&gt;
&lt;br /&gt;
Tinker &amp;quot;xyzedit.x&amp;quot; program (option 20) can be used to combine two xyz files into one (matching key file for each xyz is required). You can merge the key or parameter files by appending one to the other, but please make sure the atom types are not overlapping between the two.&lt;br /&gt;
&lt;br /&gt;
For the above 1BTY example, poltype will translate/rotate the ligand in standard orientation. You may need a script to copy the coordinates from ligand.pdb into ttt.xyz (hwich you get out of the POLTYPE run).&lt;br /&gt;
&lt;br /&gt;
Then you can use xyzedit.x to combine 1bty.xyz and lig.xyz into one xyz file with the two molecules orient/position as in PDB. Merge the key file by appending ttt.key (except the first line which contains header already in amoebapro13.prm of 1bty.key) to 1bty.key; again avoid overlapping atom types between the ligand and protein.&lt;br /&gt;
&lt;br /&gt;
== Soaking solute in solvent ==&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;Tinker &amp;quot;xyzedit.x&amp;quot; is an interactive program (option 20) that can be used for this as well. You just need a molecule.xyz and waterbox.xyz along with matching key files (actual names do not matter).&lt;br /&gt;
&lt;br /&gt;
Some water files (monomers, boxes) are in tinker/example or test folder. One can make a water box of different size using this program too (starting from one water or a cluster of water and use option 19). Option 21 can add ions to solvent box. To distiguish between AMOEBA or fixed charged FF simulation files, check the key file to see which prm file it is pointing to.&lt;br /&gt;
&lt;br /&gt;
Or you can use this utility: [http://www.ime.unicamp.br/~martinez/packmol/home.shtml http://www.ime.unicamp.br/~martinez/packmol/home.shtml]&lt;br /&gt;
&lt;br /&gt;
After construct the simulations, relax the system using minimize and dynamics (restraint the solute first), with proper restraints and heating. See [[Tutorial:tinkertut#MD_setup-initial_equilibration|MD setup]] for details&lt;br /&gt;
&lt;br /&gt;
== Check your xyz/key files and common errors ==&lt;br /&gt;
&lt;br /&gt;
Once you have a pair of xyz and key (and prm file the key uses one), you can use &amp;quot;analyze&amp;quot; to do some basic check&lt;br /&gt;
&lt;br /&gt;
analyze xxx.xyz -k xxx.key e&amp;quot; will print energy and its components.&lt;br /&gt;
&lt;br /&gt;
 If there are any error related to missing parameters, you need to fix them. &lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key em&amp;quot; prints total charge and dipole moments etc.&lt;br /&gt;
&lt;br /&gt;
 The total charge should match your expectation (0, -1, +1) etc&lt;br /&gt;
 If this is a box of solute in water, you should add neutralizing ions (K+ or Cl-) and then &amp;quot;additional&amp;quot; 0.1 mM KCl. So the next charge should be 0!&lt;br /&gt;
&lt;br /&gt;
&amp;quot;analyze xxx.xyz -k xxx.key ep&amp;quot; prints all parameters&lt;br /&gt;
&lt;br /&gt;
 Check if every atom has a multipole (number of multipole matches no of atoms) &lt;br /&gt;
 check if every atom has vdw (if an atom has 0.000 0.000 for vdw R and eps, that means the vdw parameters are missing; need to add) &lt;br /&gt;
 check polarization groups are making sense. If you see every atom is its own group, this is likely wrong. Typically we keep each function group (e.g. benzyl) as one group. &lt;br /&gt;
&lt;br /&gt;
analyze with EL will print out large interactions, for example large ele or vdw interactions of two atoms that are too close (in early PDB structure this can happen)&lt;br /&gt;
&lt;br /&gt;
analyze with &amp;quot;ED&amp;quot; option (debug) will print out all individual interactions and lot more information. The output&amp;amp;nbsp;is of course huge if you do this to a large bix, but you can use &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;vdwterm only, bondterm only, angleterm only. multpoleterm only, polarizeterm only, etc&amp;lt;/span&amp;gt;&#039;&#039;&#039; to check a specific energy component. Or use &#039;&#039;&#039;bondterm none, angleterm none&#039;&#039;&#039;....ect to turn off some interactions you don&#039;t want to check. A full list of xxxTERM can be found in &amp;lt;span style=&amp;quot;color:#2980b9;&amp;quot;&amp;gt;&#039;&#039;&#039;tinker/source/prmkey.f&#039;&#039;&#039;&amp;lt;/span&amp;gt;(grep TERM).&lt;br /&gt;
=== Induced dipole not converging error ===&lt;br /&gt;
&lt;br /&gt;
If analyze give you error related to induced dipole not converging, the structure is bad. If you see &amp;quot;induced dipole not converging&amp;quot; error in the beginning of your MD, it is also due to bad structures (atoms too close). The structure needs refinement, or missing parameters above. To refine the structure&lt;br /&gt;
&lt;br /&gt;
1. minimize the structure. you can turn off polarization (polarizeterm none) or even permanent ele completely (multipoleterm none &amp;amp; polarizeterm none) first to minimize using vdw to move close atoms apart. Then turn on multipole and then induce back&lt;br /&gt;
&lt;br /&gt;
2 For MD simulations of protein/RNA/DNA in water, run MD first at low T with pro/rna/dna &amp;quot;heavy atoms&amp;quot; restrained (e.g. restrain-position -1 1000 5.0 or restrain-position 2 , , , 1.0) to let water &amp;amp; counter ions to relax for few ns. Then gradually heat up and remove the restraints. &#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#d35400;&amp;quot;&amp;gt;Note &amp;quot;restrain-position -1 1000 0.0&amp;quot; or &amp;quot;restrain-position 2 , , , 0.0&amp;quot; DOENOT mean 0 restraint (k=0.0) on atoms 1 to 1000 or atom 2!!!&amp;amp;nbsp; &amp;quot;0.0&amp;quot; is replaced by 100.0 in tinker by default.&amp;lt;/span&amp;gt;&#039;&#039;&#039; If you don&#039;t want restraint, comment out/remove these lines.&lt;br /&gt;
&lt;br /&gt;
3. But if you see this error randomly over few hundreds of ps, which may happen for tough systems of large/many charges e.g DNA/RNA, you can add &amp;quot;&amp;lt;span style=&amp;quot;color:#e74c3c;&amp;quot;&amp;gt;&#039;&#039;&#039;USOLVE-CUTOFF 0.0&#039;&#039;&#039;&amp;lt;/span&amp;gt;&amp;quot; option to key. This will change the precondition behavior and make induced dipole solver more stable. It is not used by default because for &amp;quot;easy&amp;quot; systems like boxes of water, this makes MD little slower (more iterations to converge induced dipoles). If still have stability issue you may further add &amp;quot;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;color:#e67e22;&amp;quot;&amp;gt;USOLVE-DIAG xx&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;quot; where xx is 2.0 by default and a smaller number towards 1 (e.g. 1.5) will make more stable but slightly slower.&lt;br /&gt;
&lt;br /&gt;
4. If system is rather big,&amp;amp;nbsp;use &amp;quot;polar-eps 0.01&amp;quot; or 0.001 during system setup and 0.0001 for production.&lt;br /&gt;
&lt;br /&gt;
== Modified PRO &amp;amp; NA residues ==&lt;br /&gt;
&lt;br /&gt;
=== Build a structure with modified residues ===&lt;br /&gt;
&lt;br /&gt;
Modify residues in a PDB file.&lt;br /&gt;
&lt;br /&gt;
Input: PDB files of the biopolymer, an original residue and a modified residue. The original residue must be present in the biopolymer, and the modified residue must share at least 3 atoms with the original residue with identical coordinates. The modified residue is usually obtained by manually modifying the original residue.&lt;br /&gt;
&lt;br /&gt;
Output: A PDB file with specified residues modified to the new residue. [https://biomol.bme.utexas.edu/~zj2244/tutorial/modeling/modres/modified_pdb/ link]&lt;br /&gt;
&lt;br /&gt;
 # change residues 2 and 14 in dna15.pdb from res_A to res_pA&lt;br /&gt;
 morphling.py -i dna15.pdb -o pdna15.pdb -t0 res_A.pdb -t1 res_pA.pdb -n 2,14&lt;br /&gt;
&lt;br /&gt;
=== Convert pdb to xyz ===&lt;br /&gt;
&lt;br /&gt;
[https://github.com/zjing7/modified-na link]&lt;br /&gt;
&lt;br /&gt;
= More on running Tinker and tinker9 (GPU) =&lt;br /&gt;
==Manual==&lt;br /&gt;
https://tinkerdoc.readthedocs.io/en/latest/ &lt;br /&gt;
== Command line ==&lt;br /&gt;
&lt;br /&gt;
Tinker programs can be run interactively, which is the best way to learn what are the required inputs. Tinker programs can also run in background with all parameters specified, for the purpose of automation:&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;analyze.x ttt.xyz -k ttt.key ep&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039;dynamic.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&#039;&#039;&#039;&lt;br /&gt;
 &#039;&#039;# the bench7.xyz above can be found in tinker official distribution inside tinker/bench/&#039;&#039;&lt;br /&gt;
 #2-fs time step for MD here is ok because of the &amp;quot;integrator respa&amp;quot; in the key file&lt;br /&gt;
&lt;br /&gt;
Or for tinker9 (above) Or tinker-openmm:&lt;br /&gt;
&lt;br /&gt;
  export CUDA_DEVICE_ORDER=PCI_BUS_ID&lt;br /&gt;
  export CUDA_VISIBLE_DEVICES=0 # device number, 0, 1...is the 1st, 2nd...&lt;br /&gt;
  #source cuda, tinker-openmm, gcc related env var (see tinker-openmm install)&lt;br /&gt;
  nohup dynamic_omm.x bench7 100000 3.0 6.0 2 298.0 N &amp;gt; ben7.log &amp;amp;&lt;br /&gt;
&lt;br /&gt;
== Pause and resume MD ==&lt;br /&gt;
&lt;br /&gt;
Tinker creates .dyn file that contains coordinates and velocities needed for restart MD. To stop MD, simply create a .end file (e.g. touch myrun.end) in the folder where MD is running. At the next time MD frame was written, the end file will signal Tinker to stop. To resume later simply rerun dynamics with the presence of the .dyn file. Note the output file of dynamics does not resume the count of MD steps/frames.&lt;br /&gt;
&lt;br /&gt;
== Additional notes for &amp;quot;tinker-openmm&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
*It s recommended to use the respa inetgrator and 2-fs time step &lt;br /&gt;
*&amp;quot;heavy-hydrogen&amp;quot; in key file allows a 3-fs time step (not reommended) &lt;br /&gt;
*Bussi thermostat &lt;br /&gt;
*Only MC barostat is available for now. We are adding virial/Langevin piston pressure to openmm.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= How to specify different ensembles for MD simulation =&lt;br /&gt;
&lt;br /&gt;
== For TINKER-openmm ==&lt;br /&gt;
&#039;&#039;&#039;Tinker-Openmm is no longer supported since 2021. Use tinker9 for GPU MD (see [[Software:tinkergpu|Tinker GPU]])&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Not many options available.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
For NVT, use Bussi for thermostat, RESPA integrator (2fs)&lt;br /&gt;
&lt;br /&gt;
For NPT, use Montecarlo for Barostat, Bussi thermostat. Verlet (1 fs) is safer than RESPA for use with MC barostat if very accurate density is needed.&lt;br /&gt;
&lt;br /&gt;
See below for keyword syntax.&lt;br /&gt;
&lt;br /&gt;
== Available thermostat and barostat in TINKER (2021) ==&lt;br /&gt;
&lt;br /&gt;
Thermostats:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD (lines you add to .key file)&lt;br /&gt;
 Bussi-Parrinello           thermostat bussi&lt;br /&gt;
 Berendsen                  thermostat berendsen&lt;br /&gt;
 Andersen Stochastic        thermostat andersen&lt;br /&gt;
 Nose-Hoover                thermostat nose-hoover&lt;br /&gt;
&lt;br /&gt;
There are 3 barostats available via the “barostat” keyword:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Berendsen                  barostat berendsen&lt;br /&gt;
 Monte-Carlo                barostat montecarlo&lt;br /&gt;
 Lagevin                    Barostat Langevin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above thermostat and barostats are available for the Verlet, Beeman and RESPA integrators, and can be used in combination with those integrators. These integrators are available via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                     KEYWORD&lt;br /&gt;
 Verlet                     integrator verlet&lt;br /&gt;
 Beeman                     integrator beeman&lt;br /&gt;
 RESPA                      integrator respa&lt;br /&gt;
&lt;br /&gt;
Note that the &#039;&#039;&#039;defaults&#039;&#039;&#039; are Bussi for thermostat, Berendsen for barostat, and Beeman for integrator.&lt;br /&gt;
&lt;br /&gt;
Then there are two special integrators, a stochastic one, and a Nose-Hoover that does NPT. The stochastic integrator uses a kind of Langevin temperature bath for thermostating, and does listen to the barostat keyword. The Nose-Hoover integrator uses a separate code branch and does only NPT with Nose-Hoover methods following Martyna-Tuckerman-Klein. You can get these via:&lt;br /&gt;
&lt;br /&gt;
 METHOD                      KEYWORD&lt;br /&gt;
 Stochastic                   integrator stochastic (no need for other T control)&lt;br /&gt;
 Nose-Hoover NPT             integrator nose-hoover (no need other keywords for T or P; starting structures need to reasonable)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Recommended NVT and NPT combinations&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
NVT keywords combination in the key file (2fs time step)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi &lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, relative isotropic and homogenous systems)&lt;br /&gt;
&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
 barostat MonteCarlo&lt;br /&gt;
 integrator RESPA&lt;br /&gt;
&lt;br /&gt;
Recommended NPT (2fs, anisotropic systems such as membrane, or large local volume fluctuation in protein folding. Slower than above for virial calculations)&lt;br /&gt;
&lt;br /&gt;
 barostat Langevin&lt;br /&gt;
 Integrator RESPA   #or Verlet/1 fs; T control not needed&lt;br /&gt;
 a-axis 40 #change this to your actual box size; b or c can be different from a&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Alternative NPT (1fs, built in P and T control)&lt;br /&gt;
&lt;br /&gt;
 integrator nose-hoover&lt;br /&gt;
&lt;br /&gt;
== Recommended keywords (add somewhere in the .key file) for NVT ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
 thermostat bussi&lt;br /&gt;
&lt;br /&gt;
Command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 2 298  (100000 steps, 2.0 fs time step, dump structure every 1.0 ps, option 2 is NVT, 298 is the target T)&lt;br /&gt;
&lt;br /&gt;
It is also possible to combine &amp;quot;&#039;&#039;&#039;integrator Beeman&#039;&#039;&#039;&amp;quot; or &#039;&#039;&#039;&amp;quot;thermostat Berendsen”&#039;&#039;&#039; or &#039;&#039;&#039;&amp;quot;thermostat Andersen&amp;quot;&#039;&#039;&#039;. But RESPA allows large time steps (2.0 or 2.5 fs) than Beeman. Berendsen thermostat does not provide canonical ensemble fluctuation.&lt;br /&gt;
&lt;br /&gt;
== NVE ==&lt;br /&gt;
&lt;br /&gt;
 integrator respa&lt;br /&gt;
&lt;br /&gt;
command:&lt;br /&gt;
&lt;br /&gt;
 dynamic xxx.xyz 100000 2.0 1.0 1&lt;br /&gt;
&lt;br /&gt;
No need for thermostat or barostat of course. It is best to use smaller time step such as 1.0fs to conserve energy better. May even use smaller polar-eps (10^-6) than default (10^-5) in the key file.&lt;br /&gt;
&lt;br /&gt;
== Non periodic system, e.g. gas molecules not in a box ==&lt;br /&gt;
&amp;lt;div class=&amp;quot;_&amp;quot; style=&amp;quot;background:#eee; border:1px solid #ccc; padding:5px 10px&amp;quot;&amp;gt;integrate stochastic&amp;lt;/div&amp;gt; &lt;br /&gt;
If there is no box (a-axis) in the key file, or no box dimensions in the den file, the system is non-periodic. This will set the stochastic temperature control along with the stochastic MD integration. &#039;&#039;&#039;For gas phase molecular cluster (very few atoms), the recommended time step is 0.1 fs&#039;&#039;&#039;.&lt;br /&gt;
= Free energy calculations =&lt;br /&gt;
&lt;br /&gt;
Theory about free energy calculation: http://alchemistry.org/wiki/Bennett_Acceptance_Ratio&lt;br /&gt;
&lt;br /&gt;
About AMOEBA softcore and BAR, read our book chapter: &lt;br /&gt;
&lt;br /&gt;
[[File:PL_BAR_softcore.pdf|page=3|300px]]&lt;br /&gt;
&lt;br /&gt;
== MD setup-initial equilibration ==&lt;br /&gt;
&lt;br /&gt;
Determine protonation state of ionizable groups (ASP, GLU, LYS, ARG, HIS). Use propka here&amp;amp;nbsp;[http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/ http://nbcr-222.ucsd.edu/pdb2pqr_2.0.0/]&amp;amp;nbsp;for proteins. For ligand, you may use pka predicction tool&amp;amp;nbsp;from Chemaxon. &lt;br /&gt;
*Add water and counter ions (neutralize system) so that the density is ~1.0 g/cc. The distance between protein and box wall should be&amp;amp;nbsp;10-15 A. Check/remove extra water in the binding pocket as necessary (keep the crystal water molecules in the pocket) &lt;br /&gt;
*In the key file, set&amp;amp;nbsp;PME-grid&amp;amp;nbsp;to be&amp;amp;nbsp;1.2x&amp;amp;nbsp;box size in Ang. For example, if box size is 55, “pme-grid&amp;amp;nbsp;64 64 64” is enough. The default of Tinker is usually more conservative. See kewald.f for allowed grid values. Add &#039;&#039;&#039;“neighbor-list”, “polar-eps 0.0001”, “vdw-cutoff&amp;amp;nbsp;12”, &amp;quot;vdw-correction&amp;quot; “integrator respa”, “ewald”, “ewald-cutoff 7.0” &#039;&#039;&#039;&amp;amp;nbsp;to .key file. &lt;br /&gt;
*Minimize the box before MD. If you see errors related to polarization (induced dipole not converge), do this in two steps: first minimize with electrostatic (multipoleterm NONE) and polarization turned off (polarizeterm NONE in .key file), to ~5.0 or lower; then minimize again with ele then ele+polarization back on to ~2.0 or lower. You may use position-restraints&amp;amp;nbsp;&#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; if you don&#039;t want your solute to undergo dramtic changes. (RESTRAIN-POSITION -1 200 50.0, means restrain atoms 1 to 200 using a force constant of K=50 kcal/mol).&amp;amp;nbsp; &lt;br /&gt;
*MD relaxation. You may use GPU for MD now (dynamic_omm.x).&amp;amp;nbsp;Use repsa integrator and 2fs time step.&amp;amp;nbsp;Add&amp;amp;nbsp;&#039;&#039;&#039;position-restraints&#039;&#039;&#039; to restrain protein &amp;amp; ligands &#039;&#039;&#039;(HEAVY ATOMS only)&#039;&#039;&#039; in the key file&amp;amp;nbsp;initially; For metal ion-protein binding or weak binding ligand,&amp;amp;nbsp;we&amp;amp;nbsp;also suggest to use ~3 distance restraints between ion/ligand and first shell atoms. This is to prevent water disrupt the initial solute structure during the equlibration.&amp;amp;nbsp; &lt;br /&gt;
**Use 2 fs for all MD below.&amp;amp;nbsp;If you want to use 3fs (e.g for large systems),&amp;amp;nbsp;you need to&amp;amp;nbsp;&amp;quot;heavy-hydrogen&amp;quot; in the key file.&amp;amp;nbsp;Another way to spede up is to use the OPTx: &amp;quot;polarization OPT4&amp;quot; or &amp;quot;polarization OPT3&amp;quot; OPT3 is faster but bigger error. &lt;br /&gt;
**With the positional/distance restraints, run ~2ns&amp;amp;nbsp; NVT MD to gradually (e.g. exponentially) heat up the system from 10K&amp;amp;nbsp; to 298K or whatever expt T should be.&amp;amp;nbsp;Water/ions are&amp;amp;nbsp;relaxed after this step. &lt;br /&gt;
**Run NVT at 298K or expt T for ~2ns &#039;&#039;&#039;while gradually turning off all the position and distance restraints on protein-ligands.&#039;&#039;&#039; &lt;br /&gt;
**Run&amp;amp;nbsp;1.5&amp;amp;nbsp;ns NPT to compute the average density/box size (ignore the first 300ps). &#039;&#039;&#039;For GPU, only &amp;quot;barostat MonteCarlo&amp;quot; is available.&#039;&#039;&#039;&amp;amp;nbsp; &lt;br /&gt;
**NVT MD for ~2ns with box fixed at the average lengths from above. &lt;br /&gt;
**Check protein RMSD (esp. around binding pocket) from crystal structure after every step above. If any step gives large RMSD, redo that (and previous step) with longer/slower MD to correct the problems.   &lt;br /&gt;
*MD production run. For alchemical free energy, this involves setting the ligand group and various lambda values for ele and vdw to scale the interactions between ligand and surrounding (see below BAR section). &lt;br /&gt;
&lt;br /&gt;
== Hydration or binding using BAR ==&lt;br /&gt;
&lt;br /&gt;
Alchemical free energy calculations are available in TINKER, Tinker9 GPU (TINKER-OpenMM no longer supported). One needs to specify the ligand or solute using the group keyword&amp;amp;nbsp;in the key file (example below). The lambda scaling schedule can be specified by user, automated by the &amp;quot;bar.x&amp;quot; in TINKER. For each set of lambda value (scaling the interaction betweem ligand and enviroemnt and inside ligand), one needs to perform one MD simulation. The bar.x is then used to analyze the dG between neighboring steps i and j, using the arc files from MD simulation i and j. The total free energy is then sum of 1-2, 2-3, ...N-1 and N.&amp;amp;nbsp;See this reference for examples: &#039;&#039;J Comput Chem. 2017 Sep 5;38(23):2047-2055&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note &#039;&#039;&#039;GPU MD and bar code&#039;&#039;&#039;&amp;amp;nbsp;is much faster than the CPU one&amp;amp;nbsp;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Running BAR code in Tinker==&lt;br /&gt;
To compute free energy between two states (i and j), the bar.x (CPU or GPU) will need two trajectories (and two key files of course) of the same simulation length (frames). the two states can be neighboring lambda states in HFE or binding. &lt;br /&gt;
&lt;br /&gt;
See above (and PNAS 2008 paper) for BAR equations.&lt;br /&gt;
&lt;br /&gt;
Step 1 (bar option 1) is to generate two files, each contain the energy of its own state and perturbed energy (Eii, Eij). The second energy is using arc i and key of state j (bar will do this for you).&lt;br /&gt;
&lt;br /&gt;
 tinker9 bar 1 arc1 300 arc2 300 N &amp;gt; barfile &amp;amp;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;tinker 9 bar&amp;quot; is for GPU. You can replace with CPU version bar.x (slower). the arc1 and arc2 can be in different folders with their matching key files.&lt;br /&gt;
&lt;br /&gt;
Example barfile produced from this step: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.bar.&lt;br /&gt;
&lt;br /&gt;
The output below shows 500 frame used, 300K, for frame 1, energy of Eii, Eij and volume of the system (since we can do NPT where volume changes)&lt;br /&gt;
  500    300.00  comments&lt;br /&gt;
       1          -6396.8707        -6396.7580        27379.1152&lt;br /&gt;
&lt;br /&gt;
The second section of this same file will have Ejj, Eji, volume&lt;br /&gt;
&lt;br /&gt;
Step  2 (bar option 2) &lt;br /&gt;
Use the barfile produced from above to compute dG , dH and dS&lt;br /&gt;
 tinker9 bar 2 {barfile} {startsnapshot} {totalsnapshot} 1 {startsnapshot} {totalsnapshot} 1 &amp;gt; {enefile}&lt;br /&gt;
Note this step is much faster since it uses energy from above. You can also set to use a subset of the total frames, e.g. to exam how the dG converge with longer simulaitons.&lt;br /&gt;
Example out: https://github.com/leucinw/autoBAR/blob/main/examples/Phenol-HFE/liquid/liquid-e000-v000.ene&lt;br /&gt;
&lt;br /&gt;
== HFE ==&lt;br /&gt;
&lt;br /&gt;
Common keywords for hydration free energy calculation (suggest NPT with MC barostat or Langevin piston barostat)&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 a-axis 40&lt;br /&gt;
 vdw-cutoff 12&lt;br /&gt;
 vdw-correction&lt;br /&gt;
 Ewald&lt;br /&gt;
 Ewald-cutoff 7.0&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 barostat Monte Carlo   #NPT. Use Langevin NPT if care e.g. membrane &lt;br /&gt;
 thermostat Bussi&lt;br /&gt;
 Integrator RESPA # 2-fs time step for solution; 1 for gas&lt;br /&gt;
 neighbor-list&lt;br /&gt;
 polar-eps 0.0001&lt;br /&gt;
 polar-predict&lt;br /&gt;
 #openmp-threads    16 #this is for CPU&lt;br /&gt;
 Vdw-annihilation      #this is to help sampling conformation at low lambda by removing intrmol vdw interactions; not needed for rigid solute.&lt;br /&gt;
&lt;br /&gt;
The ele and vdw schedules are found in our previous paper. Also recommended as below. Note you can add or remove steps based dG results and error bars.&lt;br /&gt;
&lt;br /&gt;
Run NPT for each lambda below. 2-5 ns for each lambda typically depending how complex your system (eg, 2ns is sufficient for K+ in water but a large ligand mayneed 5ns). Use BAR-NPT to analyze free energy between neighboring lambda (ignore first 200 ps). The toal FE is the sum of each step. You can check cumulative free energy convergence as a function of simulation time. Add more MD if needed.&lt;br /&gt;
&lt;br /&gt;
Repeat the set of simulations for ligand in solution and ligand itself in gas phase (not necessary if gas energy is 0 like single ion). The gas phase part should use the matching keywords as above (but no a-axis, Ewald, and time step for constant T MD is 1fs).&lt;br /&gt;
&lt;br /&gt;
Typical lambda schedule:&lt;br /&gt;
&lt;br /&gt;
 Ele L	Vdw L&lt;br /&gt;
 0	0&lt;br /&gt;
 0	0.4&lt;br /&gt;
 0	0.5&lt;br /&gt;
 0	0.525&lt;br /&gt;
 0	0.55&lt;br /&gt;
 0	0.575&lt;br /&gt;
 0	0.6&lt;br /&gt;
 0	0.625&lt;br /&gt;
 0	0.65&lt;br /&gt;
 0	0.675&lt;br /&gt;
 0	0.7&lt;br /&gt;
 0	0.725&lt;br /&gt;
 0	0.75&lt;br /&gt;
 0	0.775&lt;br /&gt;
 0	0.8&lt;br /&gt;
 0	0.9&lt;br /&gt;
 0	1&lt;br /&gt;
 0.1	1&lt;br /&gt;
 0.2	1&lt;br /&gt;
 0.3	1&lt;br /&gt;
 0.4	1&lt;br /&gt;
 0.5	1&lt;br /&gt;
 0.6	1&lt;br /&gt;
 0.7	1&lt;br /&gt;
 0.8	1&lt;br /&gt;
 0.9	1&lt;br /&gt;
&lt;br /&gt;
== binding free energy ==&lt;br /&gt;
&lt;br /&gt;
For host-guest binding, the simulation process similiar to above but involve two sets: one is host-guest-water, and the other guest-water. In both cases, guest is the ligand that is being scaled. For host-guest-water, one also applies&amp;amp;nbsp;a bond restraint between host and guest. This restraint can be turned off in one or two steps for lambda=1 but should be kept when L&amp;lt;1.&lt;br /&gt;
&lt;br /&gt;
 One way is to set the restraint K=0 when Lele, Lvdw=1, then K=90% when Lele=0.9/Lvdw=1, then K=100% when Lele=80%/Lvdw=1..... K=100% for all rest of L including L=0. &lt;br /&gt;
 The goal is for L=1 (host-guest full interaction), there is no restraint. when L=0, restraint is at 100%. The L=0 state seems &amp;quot;incorrect&amp;quot; due to the restraint but can be corrected (below).&lt;br /&gt;
&lt;br /&gt;
This &amp;quot;bond&amp;quot; is between group of guest/ligand and group of host atoms. It is best to minimize the distance between the centers of the two groups (for sampling).  For example, if you are simulating an ion binding to a spherical cavity like CPP, you can pick 3 atoms on the host whose center is roughly the center of the ion; the restraint will be between the ion and this group. A correction is needed to &amp;quot;remove&amp;quot; the effect of this restraint and standard volume that goes into the final binding free energy.&#039;&#039;&#039;Tinker/utiity/freefix.f&#039;&#039;&#039; can be used to calculate the correction. Note this correction is typically positive (make binding energy less negative) since restraint leads to overestimation of binding.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;*The correction for lambda=0 from RTln(C0*V), where C0=1/1660 A^3 and V=integrate{4*pi*r^2*exp[-k*(r-r0)^2/RT]dr}. k=15 kcal/mol in the example below. If you are using a harmonic restraint (example below) and the equilibrium r0 is not 0, numerical integration is necessary. A good reference is JACS v126, NO. 24, 2004.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Brandon setup script can also set up protein-lig distance restraint now. Basically select a central heavy atom on ligand (or a function group) and another group of nearby 3-4 Ca from protein.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt; Francis wrote a program to pick restraints based on Boresch paper. It can include additional angle and torsion restraints. However we found it is best to just use the simple distance restraints. The additional restraints may introduce bias towards ligand or host dynamics if not picked carefully.&amp;lt;/pre&amp;gt; [[Tinkergpu:get_rot_rest]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you use distance restraint when lambda =1 for both ele and vdw, you can remove the effect of restraint from FEP or BAR; or you can avoid this correction if the restraint strength is set to 0 when the lambda =1 (gradually turned on when lambda-&amp;gt; 0 for both vdw and ele).&lt;br /&gt;
&lt;br /&gt;
 ligand                  -1 24, 26    &#039;&#039;#negative means range: atoms 1 to 24 plus 26&#039;&#039;&lt;br /&gt;
 vdw-lambda              1.00&lt;br /&gt;
 ele-lambda              0.50&lt;br /&gt;
 GROUP 1 -1 3 //ligand group&lt;br /&gt;
 GROUP 2 100, 102, 138 //protein group&lt;br /&gt;
 RESTRAIN-GROUPS  1  2  15.0  2.0 2.0&lt;br /&gt;
 Vdw-annihilation&lt;br /&gt;
 #lower bound &amp;amp; upper bound (2.0, 2.0) do not have to be the same. 15 is the force constant.&lt;br /&gt;
&lt;br /&gt;
Each set of lambda corresponds to one separate MD simulations of 5-10ns or longer. Save MD frames at every 3-5 ps. Use bar.x (bar_omm.x for GPU) to analyze the free energy dG between the neighboring lambda values.&lt;br /&gt;
&lt;br /&gt;
Unlike HFE, no need for gas-phase simulation since the end states of the ligand-water vs. ligand-protein cancels.&lt;br /&gt;
&lt;br /&gt;
Some scripts fron CW:&amp;amp;nbsp;[https://github.com/leucinw/ComputTools/tree/master/bardemo https://github.com/leucinw/ComputTools/tree/master/bardemo]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==ion HFE steps==&lt;br /&gt;
To compute ion hydration FE, &lt;br /&gt;
* prepare ion.xyz and waterbox.xyz. One key file containing all parameters (amoeba09.prm has ion and bunch of ions). If you have a new ion, add its parameters including multipoles, polarizability/damping, vdw &lt;br /&gt;
* water box should be ~50 A. A list of prebuilt water box (you many need to change atom types in xyz if you are using different key) https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#prebuilt_water_box &lt;br /&gt;
* use xyzedit to soak ion in water (see tutorial above about building and combining xyz)&lt;br /&gt;
* Run NPT for ~1ns to relax. See tutorial on this page about dynamics on GPU NPT keywords (using Langevin or MonteCarlo)&lt;br /&gt;
* Take the last relaxed structure to create inputs for HFE. Best to create a series of folders, one for each lambda with inputs and run scripts. See here for lambda schedule https://biomol.bme.utexas.edu/tinkergpu/index.php?title=Tinkergpu:Tinker-tut#HFE&lt;br /&gt;
* Get a list of nodes from Google spreadsheet of lab cluster. Ask for it if you can&#039;t find ~10 GPU nodes.&lt;br /&gt;
* each MD for ~2ns (add more if needed)&lt;br /&gt;
* Use a script to send jobs to each node. You can have 2 jobs concurrent on one GPU and rotate your jobs (~50 lambdas) through.&amp;lt;br /&amp;gt;&lt;br /&gt;
== hydration and binding free energy examples ==&lt;br /&gt;
&lt;br /&gt;
*Ethanol solvation free energy [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/01_solvation/Ethanol.zip download] &lt;br /&gt;
*PBP-phosphate binding [https://biomol.bme.utexas.edu/~zj2244/tutorial/free_energy/02_protein_ligand_binding/PBP_PO4.zip download] &lt;br /&gt;
&lt;br /&gt;
Please unzip the files and see README for instructions.&lt;br /&gt;
&lt;br /&gt;
== HFE and binding free energy calc using Brandon&#039;s script ==&lt;br /&gt;
&lt;br /&gt;
Set up from complex PDB and ligand xyz/key (POLTYE):&amp;amp;nbsp;[https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD https://github.com/bdw2292/AMOEBAAnnihilator/blob/main/README_HELP.MD]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
*create conda env according to instructions on the annihilator github page &lt;br /&gt;
*make&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;something like&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;/home/eew947/.allpurpose.bashrc&amp;lt;/code&amp;gt;&amp;amp;nbsp;with your username replacing mine everywhere in it &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;ssh&amp;lt;/code&amp;gt;&amp;amp;nbsp;to node you want to start from &lt;br /&gt;
*&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;source ~/.allpurpose.bashrc&amp;lt;/code&amp;gt; &lt;br /&gt;
*prepare&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;annihilator.ini&amp;lt;/code&amp;gt; &lt;br /&gt;
*if you want to use daemon, you have to add the keyword for it in annihilator *ini and have it already running before starting annihilator &lt;br /&gt;
*start annihilator by&amp;amp;nbsp;&amp;lt;code data-stringify-type=&amp;quot;code&amp;quot;&amp;gt;nohup yourpathtoannihilatorhere/AMOEBAAnnihilatorModules/amoebaannihilator.py &amp;amp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OSRW ==&lt;br /&gt;
&lt;br /&gt;
Only implemented in tinker CPU. GPU version is under development.&lt;br /&gt;
&lt;br /&gt;
= Visualization =&lt;br /&gt;
&lt;br /&gt;
== Force Field Explorer ==&lt;br /&gt;
&lt;br /&gt;
By Mike Schneider and Jay Ponder, [http://dasher.wustl.edu http://dasher.wustl.edu] Can visualize the xyz and arc (MD trajectory) files; create and start TINKER calcualtions&lt;br /&gt;
&lt;br /&gt;
== VMD ==&lt;br /&gt;
&lt;br /&gt;
Choose TINKER format when open a xyz file. Trajectory file (.arc) also works.&lt;br /&gt;
&lt;br /&gt;
== Pymol ==&lt;br /&gt;
&lt;br /&gt;
Sometimes the xyz file can not be displayed correctly&lt;br /&gt;
&lt;br /&gt;
= Other resources =&lt;br /&gt;
&lt;br /&gt;
[https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials https://sites.google.com/site/biomolsimstw/workshop-materials/tutorials]&lt;br /&gt;
&lt;br /&gt;
Please email me if you have tutorials related to AMOEBA or Tinker you would like to share.&lt;br /&gt;
&lt;br /&gt;
= AMOEBA Force Field Papers: =&lt;br /&gt;
&lt;br /&gt;
AMEOBA FF:&lt;br /&gt;
&lt;br /&gt;
#Water model: Ren, P. Y.; Ponder, J. W., Polarizable atomic multipole water model for molecular mechanics simulation. Journal of Physical Chemistry B &#039;&#039;&#039;2003&#039;&#039;&#039;, 107 (24), 5933-5947. &lt;br /&gt;
#Small molecules: Ren, P.; Wu, C.; Ponder, J. W., Polarizable Atomic Multipole-based Molecular Mechanics for Organic Molecules. J Chem Theory Comput &#039;&#039;&#039;2011&#039;&#039;&#039;, 7 (10), 3143-3161. &lt;br /&gt;
#Proteins: Shi, Y.; Xia, Z.; Zhang, J.; Best, R.; Wu, C.; Ponder, J. W.; Ren, P., The Polarizable Atomic Multipole-based AMOEBA Force Field for Proteins. J Chem Theory Comput &#039;&#039;&#039;2013&#039;&#039;&#039;, 9 (9), 4046-4063. &lt;br /&gt;
#DMP/TMP/Base &amp;amp; nucleic acids:&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
*Zhang, C.; Lu, C.; Wang, Q.; Ponder, J. W.; Ren, P., Polarizable Multipole-Based Force Field for Dimethyl and Trimethyl Phosphate. J Chem Theory Comput 2015, 11 (11), 5326-39. &lt;br /&gt;
*Zhang, C.; Bell, D.; Harger, M.; Ren, P., Polarizable Multipole-Based Force Field for Aromatic Molecules and Nucleobases. J Chem Theory Comput 2017, 13 (2), 666-678. &lt;br /&gt;
*Zhang, C.; Lu, C.; Jing, Z.; Wu, C.; Piquemal, J. P.; Ponder, J. W.; Ren, P., AMOEBA Polarizable Atomic Multipole Force Field for Nucleic Acids. J Chem Theory Comput 2018, 14 (4), 2084-2108. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; AMOEBA+ model (water published, small and biomolecules in progress)&lt;br /&gt;
&lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., AMOEBA+ Classical Potential for Modeling Molecular Interactions. J Chem Theory Comput 2019. &lt;br /&gt;
#Liu, C.; Piquemal, J. P.; Ren, P., Implementation of Geometry-Dependent Charge Flux into the Polarizable AMOEBA+ Potential. J Phys Chem Lett 2019, 11, 419-426.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; AMOEBA+NN model: incorporating Neural Networks&lt;br /&gt;
&lt;br /&gt;
Wang, Y., et al. (2024). &amp;quot;Incorporating Neural Networks into the AMOEBA Polarizable Force Field.&amp;quot; The Journal of Physical Chemistry B 128(10): 2381-2388.&lt;br /&gt;
	&lt;br /&gt;
&lt;br /&gt;
==Lectures on Force Field, AMOEBA, AMOEBA+==&lt;br /&gt;
Under &#039;&#039;&#039;Adv Mol Modeling&#039;&#039;&#039; menu:&lt;br /&gt;
 [[Tutorial:amm#Molecular_Mechanics_and_Force_Fields_(AMOEBA,_AMOEBA+) | Link]]&lt;br /&gt;
&lt;br /&gt;
= More Explicit Free Energy Calc Steps - Brandon Walker =&lt;br /&gt;
&lt;br /&gt;
Old/obsolete description here: [[Tinker-tut:free_eng_Bbdw|Obsolete description here]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=2000</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=2000"/>
		<updated>2024-02-15T15:38:34Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Run */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
For csh, source the follow (or add to .cshrc)&lt;br /&gt;
  source /opt/qchem/6.1/qcenv.csh&lt;br /&gt;
For bash (add to .bashrc)&lt;br /&gt;
  source /opt/qchem/6.1/qcenv.sh&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads/processors). &lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Important features&lt;br /&gt;
 Default mem is 12GB. please set your own in input&lt;br /&gt;
 ALMO-EDA second generation for energy decomposition&lt;br /&gt;
 New DFT methods such as wB97M2... https://manual.q-chem.com/6.1/sect_DFTsugg.html&lt;br /&gt;
 User manual and examples: https://manual.q-chem.com/latest/&lt;br /&gt;
&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run this to get host id before emailing qchem for license:&lt;br /&gt;
 /opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
&lt;br /&gt;
Create the qchem.lic following qchem email:&lt;br /&gt;
 SERVER bme-uranus.bme.utexas.edu 043201278653&lt;br /&gt;
 USE_SERVER&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06  58888&lt;br /&gt;
 VENDOR qchemlm  port=58889 OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
Note the 58888 58889 ports are added above and enabled below:&lt;br /&gt;
 firewall-cmd --zone=internal --add-port=58888-58889/tcp --permanent&lt;br /&gt;
 firewall-cmd --reload&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1999</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1999"/>
		<updated>2024-02-15T15:13:30Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Q-chem 6 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
For csh, source the follow (or add to .cshrc)&lt;br /&gt;
  source /opt/qchem/6.1/qcenv.csh&lt;br /&gt;
For bash (add to .bashrc)&lt;br /&gt;
  source /opt/qchem/6.1/qcenv.sh&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads/processors). &lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Important features&lt;br /&gt;
 Default mem is 12GB. please set your own in input&lt;br /&gt;
 ALMO-EDA second generation for energy decomposition&lt;br /&gt;
 New DFT methods such as wB97M2... https://manual.q-chem.com/6.1/sect_DFTsugg.html&lt;br /&gt;
&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run this to get host id before emailing qchem for license:&lt;br /&gt;
 /opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
&lt;br /&gt;
Create the qchem.lic following qchem email:&lt;br /&gt;
 SERVER bme-uranus.bme.utexas.edu 043201278653&lt;br /&gt;
 USE_SERVER&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06  58888&lt;br /&gt;
 VENDOR qchemlm  port=58889 OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
Note the 58888 58889 ports are added above and enabled below:&lt;br /&gt;
 firewall-cmd --zone=internal --add-port=58888-58889/tcp --permanent&lt;br /&gt;
 firewall-cmd --reload&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1998</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1998"/>
		<updated>2024-02-15T02:47:50Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Run */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
For csh, source the follow (or add to .cshrc)&lt;br /&gt;
  source /opt/qchem/6.1/qcenv.csh&lt;br /&gt;
For bash (add to .bashrc)&lt;br /&gt;
  source /opt/qchem/6.1/qcenv.sh&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads/processors). &lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Important features&lt;br /&gt;
 Default mem is 12GB. please set your own in input&lt;br /&gt;
 ALMO-EDA second generation for energy decomposition&lt;br /&gt;
 New DFT methods such wB97... https://manual.q-chem.com/6.1/sect_DFTsugg.html&lt;br /&gt;
&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run this to get host id before emailing qchem for license:&lt;br /&gt;
 /opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
&lt;br /&gt;
Create the qchem.lic following qchem email:&lt;br /&gt;
 SERVER bme-uranus.bme.utexas.edu 043201278653&lt;br /&gt;
 USE_SERVER&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06  58888&lt;br /&gt;
 VENDOR qchemlm  port=58889 OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
Note the 58888 58889 ports are added above and enabled below:&lt;br /&gt;
 firewall-cmd --zone=internal --add-port=58888-58889/tcp --permanent&lt;br /&gt;
 firewall-cmd --reload&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1997</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1997"/>
		<updated>2024-02-15T02:40:11Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Install */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run this to get host id before emailing qchem for license:&lt;br /&gt;
 /opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
&lt;br /&gt;
Create the qchem.lic following qchem email:&lt;br /&gt;
 SERVER bme-uranus.bme.utexas.edu 043201278653&lt;br /&gt;
 USE_SERVER&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06  58888&lt;br /&gt;
 VENDOR qchemlm  port=58889 OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
Note the 58888 58889 ports are added above and enabled below:&lt;br /&gt;
 firewall-cmd --zone=internal --add-port=58888-58889/tcp --permanent&lt;br /&gt;
 firewall-cmd --reload&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1996</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1996"/>
		<updated>2024-02-15T02:20:44Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Install Flexnet */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run this to get host id before emailing qchem for license:&lt;br /&gt;
 /opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
Grep port in the qchemlm.log and add to firewall:&lt;br /&gt;
 firewall-cmd --zone=internal --add-port=27000/tcp --permanent&lt;br /&gt;
 firewall-cmd --reload&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
&lt;br /&gt;
Create the qchem.lic following qchem email:&lt;br /&gt;
 SERVER bme-uranus.bme.utexas.edu 043201278653&lt;br /&gt;
 USE_SERVER&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1995</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1995"/>
		<updated>2024-02-15T02:19:33Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Install */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run &#039;&#039;/opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before request license&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
Grep port in the qchemlm.log and add to firewall:&lt;br /&gt;
 firewall-cmd --zone=internal --add-port=27000/tcp --permanent&lt;br /&gt;
 firewall-cmd --reload&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
&lt;br /&gt;
Create the qchem.lic following qchem email:&lt;br /&gt;
 SERVER bme-uranus.bme.utexas.edu 043201278653&lt;br /&gt;
 USE_SERVER&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1994</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1994"/>
		<updated>2024-02-13T22:48:11Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Install Flexnet */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run &#039;&#039;/opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before request license&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y (optional)&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1993</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1993"/>
		<updated>2024-02-13T22:48:01Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Install Flexnet */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run &#039;&#039;/opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before request license&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
 sudo dnf update -y&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1992</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1992"/>
		<updated>2024-02-13T22:47:48Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Install */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install Flexnet===&lt;br /&gt;
Flexnet came with qchem install already&lt;br /&gt;
&lt;br /&gt;
Need to run &#039;&#039;/opt/qchem/6.1/bin/flexnet/lmutil  lmhostid&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before request license&lt;br /&gt;
&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
&lt;br /&gt;
 sudo dnf update -y&lt;br /&gt;
&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
=== Install ===&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1991</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1991"/>
		<updated>2024-02-13T22:43:09Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Q-chem 6 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install===&lt;br /&gt;
Flexnext came with qc.tar already&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
Flexnet on the latest Rocky Linux requires lsb package:&lt;br /&gt;
 sudo dnf install -y yum-utils&lt;br /&gt;
&lt;br /&gt;
 sudo dnf config-manager --set-enabled devel&lt;br /&gt;
&lt;br /&gt;
 sudo dnf update -y&lt;br /&gt;
&lt;br /&gt;
 sudo dnf install redhat-lsb-core&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=File:Tinker2018group.jpg&amp;diff=1990</id>
		<title>File:Tinker2018group.jpg</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=File:Tinker2018group.jpg&amp;diff=1990"/>
		<updated>2024-02-06T16:18:44Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Poltype:Poltype&amp;diff=1989</id>
		<title>Poltype:Poltype</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Poltype:Poltype&amp;diff=1989"/>
		<updated>2024-01-30T16:16:45Z</updated>

		<summary type="html">&lt;p&gt;Admin: Link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;https://github.com/TinkerTools/poltype2&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1988</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1988"/>
		<updated>2023-12-20T21:58:26Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* openbabel */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
 -rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
 -rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
 -rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
 -rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
 -rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
 -rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
 -rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
 -rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install===&lt;br /&gt;
Flexnext came with qc.tar already&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1987</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1987"/>
		<updated>2023-12-20T21:55:53Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* openbabel */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
-rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
-rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
-rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
-rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
-rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
-rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
-rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
-rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
-rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
-rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
-rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
-rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
-rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
-rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
-rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
-rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
-rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
-rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
-rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
-rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;obabel -L formats&#039;&#039;&#039; list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install===&lt;br /&gt;
Flexnext came with qc.tar already&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1986</id>
		<title>Software:labsoft</title>
		<link rel="alternate" type="text/html" href="https://biomolmd.org/mw/index.php?title=Software:labsoft&amp;diff=1986"/>
		<updated>2023-12-20T21:55:24Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* openbabel */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:labsoftware]]&lt;br /&gt;
=Also see Tutorial=&lt;br /&gt;
&lt;br /&gt;
https://biomolmd.org/mw/index.php/Tutroial:alltut&lt;br /&gt;
&lt;br /&gt;
=3D molecule builder=&lt;br /&gt;
Free software for building and modifying chemical structure in 3D&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
 * can build polypeptide, nucleic acids using Insert function&lt;br /&gt;
 * cheap structural optimization &amp;amp; energy minimization using GAFF, MMFF, UFF etc &lt;br /&gt;
&lt;br /&gt;
== iqmol ==&lt;br /&gt;
&lt;br /&gt;
 * Can build using common chemical groups and fragments&lt;br /&gt;
 * Geometry optimizaiton using Qchem server (or our own server on water.bme.utexas.edu)&lt;br /&gt;
&lt;br /&gt;
==Arguslab==&lt;br /&gt;
*Has built-in semi-empirical and simple force field optimization.&lt;br /&gt;
*Nive building function (polypeptides are easy)&lt;br /&gt;
*No longer supported. Sometimes crashes.&lt;br /&gt;
== ACD labs ==&lt;br /&gt;
Academic version: http://www.acdlabs.com/resources/freeware/chemsketch/&lt;br /&gt;
&lt;br /&gt;
= ForceBalance =&lt;br /&gt;
&lt;br /&gt;
Installation files: ~pren/forcebalance-installation/&lt;br /&gt;
&lt;br /&gt;
 to Update: svn update&lt;br /&gt;
&lt;br /&gt;
run on node100 and beyond to install:&lt;br /&gt;
&lt;br /&gt;
 source ~pren/.cshrc.force &lt;br /&gt;
 python setup.py install --prefix=/home/pren/forcebalance&lt;br /&gt;
&lt;br /&gt;
replace the last PATH to your desired path (or just use mine) Won&#039;t work on bme-nova or water (too old).&lt;br /&gt;
&lt;br /&gt;
Check python: python -c &#039;import sys; print sys.path&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; How did I compile python 2.7 (not able to do yum on old nodes): [[Sysadmin:python27_Install|python 2.7]]&lt;br /&gt;
&lt;br /&gt;
Tutorial and example how to fit liquid and gas-phase dimer energy is in /Users/pren/Dropbox/RESEARCH/AMOEBA/AMOEBA-halogen/leeping/CondensedPhase_Update_03-07&lt;br /&gt;
&lt;br /&gt;
= pymol =&lt;br /&gt;
&lt;br /&gt;
== Linux ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Try this first: /opt/software/CHEM/pymol2016/pymol &#039;&#039;&#039; Official installation guide&lt;br /&gt;
&lt;br /&gt;
 [http://www.pymolwiki.org/index.php/TOPTOC http://www.pymolwiki.org/index.php/TOPTOC]&lt;br /&gt;
&lt;br /&gt;
== 64 bit on Centos 6.6 ==&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/pymol64/pymol/pymol&lt;br /&gt;
&lt;br /&gt;
Can be run on biomol, bme-venus, bme-pluto, bme-neptune and bme-saturn.&lt;br /&gt;
&lt;br /&gt;
[http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install http://www.pymolwiki.org/index.php/User:Tlinnet/Linux_Install]&lt;br /&gt;
&lt;br /&gt;
replace the fist wget:&lt;br /&gt;
&lt;br /&gt;
 wget [http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm]&lt;br /&gt;
&lt;br /&gt;
[http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/ http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/]&lt;br /&gt;
&lt;br /&gt;
After install all the rpms, don&#039;t need to installpymol.sh, just run&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymol &lt;br /&gt;
&lt;br /&gt;
Run this before pymol if need MPEG support&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/pymol64/pymol/pymolMPEG.sh&lt;br /&gt;
&lt;br /&gt;
== pymol prebuild ==&lt;br /&gt;
&lt;br /&gt;
Download from here: [http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/]&lt;br /&gt;
&lt;br /&gt;
[http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/ http://biomol.bme.utexas.edu/~pren/courses/bme346-soft/archive/] (linux)&lt;br /&gt;
&lt;br /&gt;
These educational version has no Ray tracing ability&lt;br /&gt;
&lt;br /&gt;
== pymol on windows (with Ray Tracing) ==&lt;br /&gt;
&lt;br /&gt;
[http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/ http://tubiana.me/how-to-install-and-compile-pymol-windows-linux-mac/]&lt;br /&gt;
&lt;br /&gt;
From this site: [http://www.pymolwiki.org/index.php/Windows_Install http://www.pymolwiki.org/index.php/Windows_Install]&lt;br /&gt;
&lt;br /&gt;
Download the 4 files (*.whl) below from [http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol http://www.lfd.uci.edu/~gohlke/pythonlibs/#pymol]&lt;br /&gt;
&lt;br /&gt;
Open a CMD windows as admin, cd Downloads\ and run the following (if you install 64 bit pythin, you may need download 64 bits for below as well)&lt;br /&gt;
&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pip-8.1.2-py2.py3-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install &amp;quot;numpy-1.11.1+mkl-cp27-cp27m-win32.whl&amp;quot;&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install Pmw-2.0.1-py2-none-any.whl&lt;br /&gt;
 C:\Users\macbook12\Downloads&amp;gt;C:\Python27\python.exe pip-8.1.2-py2.py3-none-any.whl/pip install pymol-1.7.6.0-cp27-none-win32.whl&lt;br /&gt;
&lt;br /&gt;
Create a folder from command line (this allows you to write output etc in your own folder)&lt;br /&gt;
&lt;br /&gt;
 mkdir&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
&lt;br /&gt;
Make a shortcut to C:\pthyon29\scripts\pymol (right click) and move it to above folder.&lt;br /&gt;
&lt;br /&gt;
 Right click the shortcut and select “properties”, change the “starts in” filed to&amp;amp;nbsp;%HOMEPATH%\pymol&lt;br /&gt;
 You can rename the shortcut to mypymol.cmd or anything you like.&lt;br /&gt;
&lt;br /&gt;
= Math =&lt;br /&gt;
&lt;br /&gt;
== Matlab ==&lt;br /&gt;
&lt;br /&gt;
Matlab is available on water (linux) and bme-black (windows)&lt;br /&gt;
&lt;br /&gt;
= Chemistry =&lt;br /&gt;
&lt;br /&gt;
== pubchem ==&lt;br /&gt;
&lt;br /&gt;
Here you can download the 3D structure quickly of known compounds. Or smile string, 2d structure etc. [http://pubchem.ncbi.nlm.nih.gov http://pubchem.ncbi.nlm.nih.gov]&lt;br /&gt;
&lt;br /&gt;
== logP ==&lt;br /&gt;
&lt;br /&gt;
You can enter the smile string and it predicts the logP. It&#039;ll be useful to screen for bioavailability. It is a quick empirical prediction. You can get the smile string from pubchem or babel.&lt;br /&gt;
&lt;br /&gt;
[http://www.molinspiration.com/services/logp.html http://www.molinspiration.com/services/logp.html] [http://www.molinspiration.com/cgi-bin/properties http://www.molinspiration.com/cgi-bin/properties] --&lt;br /&gt;
&lt;br /&gt;
== add H to proteins based on predicted pKa ==&lt;br /&gt;
&lt;br /&gt;
To add H to proteins based on predicted pKa&lt;br /&gt;
&lt;br /&gt;
1. Use PROPKA and PDB2PQR to add hydrogens to your x-ray structure:&lt;br /&gt;
&lt;br /&gt;
 PDB2PQR: [http://pdb2pqr.sourceforge.net/ http://pdb2pqr.sourceforge.net/]&lt;br /&gt;
 [http://www.poissonboltzmann.org/ http://www.poissonboltzmann.org/] &lt;br /&gt;
 PROPKA: [http://propka.ki.ku.dk/ http://propka.ki.ku.dk/] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; 2. H++ [http://biophysics.cs.vt.edu/index.php http://biophysics.cs.vt.edu/index.php]&lt;br /&gt;
&lt;br /&gt;
== Openeye ==&lt;br /&gt;
&lt;br /&gt;
We have academic license for a suite of software from openeye for&#039;&#039;&#039;similarity search, docking, molecular conformation generation&#039;&#039;&#039; (2d to 3d conversion) etc.&lt;br /&gt;
&lt;br /&gt;
=== 2016-2018 ===&lt;br /&gt;
&lt;br /&gt;
REHL 6 version, including fastroc on GPU&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/openeye2016/openeye/&lt;br /&gt;
&lt;br /&gt;
Source /opt/software/CHEM/openeye2016/openeye/bashrc&lt;br /&gt;
&lt;br /&gt;
See /opt/software/CHEM/openeye2016/openeye/readme for fastroc on GPU example.&lt;br /&gt;
&lt;br /&gt;
=== 2013 edition ===&lt;br /&gt;
&lt;br /&gt;
You can only run the new openeye software on RHEL5 or centos5, which means water.bme.utexas.edu or bme-nova. The license file is in /opt/openeye/license/ which expires in Aug 2013.&lt;br /&gt;
&lt;br /&gt;
Set up bashrc:&lt;br /&gt;
&lt;br /&gt;
 export OE_LICENSE=/opt/openeye/license/oe_license.txt&lt;br /&gt;
 export OE_DIR=/opt/openeye/RHEL5/openeye/&lt;br /&gt;
 export PATH=/opt/openeye/RHEL5/openeye/bin:$PATH&lt;br /&gt;
&lt;br /&gt;
That should be it...Try type &amp;quot;rocs&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== tutorial ===&lt;br /&gt;
&lt;br /&gt;
ROCS and eon&lt;br /&gt;
&lt;br /&gt;
 [[Software:openeye| similarity search]]&lt;br /&gt;
&lt;br /&gt;
=== old version ===&lt;br /&gt;
&lt;br /&gt;
How do I install the license file (/opt/openeye/license)? Place the license file named oe_license.txt in the OpenEye directory and define the environme nt variable OE_LICENSE to point to the location of the license file.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
On windows the envir var can be set up for $OE_DIR (see below). The oe_license.txt should be located under the $OE_DIR. On WinXP/Vista/Windows7, use Start-&amp;gt;Settings-&amp;gt;Control Panel-&amp;gt;System-&amp;gt;Advanced-&amp;gt;Environment Va riables&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#How do I install my license file oe_license.txt on linux? &lt;br /&gt;
&lt;br /&gt;
License files should be defined by environment variable $OE_LICENSE. It is recommended that t hese files be located at OE_DIR=/usr/local/openeye/etc/oe_license.txt. License files can also&lt;br /&gt;
&lt;br /&gt;
 be used if named oe_license.txt and either (1) present in the current working directory or (&lt;br /&gt;
&lt;br /&gt;
2) present in the directory defined by environment variable $OE_DIR. However, these methods a re not as reliable and not generally recommended.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; /usr/local/openeye/ $OE_DIR /usr/local/openeye/etc/oe_license.txt $OE_LICENSE&lt;br /&gt;
&lt;br /&gt;
== NIH online tool ==&lt;br /&gt;
&lt;br /&gt;
*Convert molecular name to structure using URL &lt;br /&gt;
**Example: [http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2 http://cactus.nci.nih.gov/chemical/structure/aspirin/file?format=mol2] &lt;br /&gt;
**Full Description: &lt;br /&gt;
***[http://cactus.nci.nih.gov/chemical/structure/documentation http://cactus.nci.nih.gov/chemical/structure/documentation] &lt;br /&gt;
***[http://cactus.nci.nih.gov/blog/?p=68 http://cactus.nci.nih.gov/blog/?p=68]     &lt;br /&gt;
*Convert smile to PDB etc, 2d to 3D using Corina. &lt;br /&gt;
&lt;br /&gt;
== openbabel ==&lt;br /&gt;
Latest openbabel 3.1 is installed cluster wide:&lt;br /&gt;
 /opt/software/openbabel311/bin/obabel&lt;br /&gt;
&lt;br /&gt;
Add to your path in bashrc or cshrc and you can use this &amp;quot;obabel&amp;quot; in any node or WS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A great chemoinformatics tool, for converting files from one format to another and now generate 3D structure for molecule. Available on linux, window and Mac osx.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&#039;&#039;Now support 2d to 3d conversion&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
-rwxr-xr-x. 1 root root  43920 Dec 20 15:50 obabel&lt;br /&gt;
-rwxr-xr-x. 1 root root  30224 Dec 20 15:50 obconformer&lt;br /&gt;
-rwxr-xr-x. 1 root root  34752 Dec 20 15:50 obenergy&lt;br /&gt;
-rwxr-xr-x. 1 root root  39600 Dec 20 15:50 obfit&lt;br /&gt;
-rwxr-xr-x. 1 root root  39408 Dec 20 15:50 obfitall&lt;br /&gt;
-rwxr-xr-x. 1 root root  35432 Dec 20 15:50 obgen&lt;br /&gt;
-rwxr-xr-x. 1 root root  34416 Dec 20 15:50 obgrep&lt;br /&gt;
-rwxr-xr-x. 1 root root  35736 Dec 20 15:50 obminimize&lt;br /&gt;
-rwxr-xr-x. 1 root root  43896 Dec 20 15:50 obmm&lt;br /&gt;
-rwxr-xr-x. 1 root root  40776 Dec 20 15:50 obprobe&lt;br /&gt;
-rwxr-xr-x. 1 root root  39832 Dec 20 15:50 obprop&lt;br /&gt;
-rwxr-xr-x. 1 root root  39576 Dec 20 15:50 obrotamer&lt;br /&gt;
-rwxr-xr-x. 1 root root  34024 Dec 20 15:50 obrotate&lt;br /&gt;
-rwxr-xr-x. 1 root root  81104 Dec 20 15:50 obspectrophore&lt;br /&gt;
-rwxr-xr-x. 1 root root  29264 Dec 20 15:50 obsym&lt;br /&gt;
-rwxr-xr-x. 1 root root  30072 Dec 20 15:50 obtautomer&lt;br /&gt;
-rwxr-xr-x. 1 root root  29480 Dec 20 15:50 obthermo&lt;br /&gt;
-rwxr-xr-x. 1 root root  29184 Dec 20 15:50 roundtrip&lt;br /&gt;
-rwxr-xr-x. 1 root root  29704 Dec 20 15:50 test_inchiwrite&lt;br /&gt;
-rwxr-xr-x. 1 root root 975472 Dec 20 15:50 test_runner&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See here for detailed description: [http://openbabel.org/wiki/Guides http://openbabel.org/wiki/Guides]&lt;br /&gt;
&lt;br /&gt;
babel -H list all formats supported (including read Gaussian fchk and output so you can convert other format such as pdb for visualization).&lt;br /&gt;
&lt;br /&gt;
The installation source files are in /opt/openbabel-2.2.0/ or /opt/software/CHEM/openbabel/&lt;br /&gt;
&lt;br /&gt;
= Computational Chemistry =&lt;br /&gt;
&lt;br /&gt;
== Tips about setting memory disk etc ==&lt;br /&gt;
&lt;br /&gt;
QM jobs are usually highly demanding of CPU, memory and disk. It is important to set the limit properly in the input file.&lt;br /&gt;
&lt;br /&gt;
In Gaussian for example, you can do so by&lt;br /&gt;
&lt;br /&gt;
 %&#039;&#039;&#039;NProc&#039;&#039;&#039;=8   or   &amp;amp;nbsp;%&#039;&#039;&#039;CPU&#039;&#039;&#039;=8 (in Gaussain 16)&lt;br /&gt;
 %&#039;&#039;&#039;Mem&#039;&#039;&#039;=15000MB&lt;br /&gt;
 %Chk=ccb.chk&lt;br /&gt;
 &lt;br /&gt;
 #MP2/aug-cc-pvtz Density=MP2 &#039;&#039;&#039;MaxDisk&#039;&#039;&#039;=150GB&lt;br /&gt;
&lt;br /&gt;
Gaussian 16 manual (some keywords changed) [https://gaussian.com/running/?tabid=6 https://gaussian.com/running/?tabid=6] &amp;amp; [https://gaussian.com/link0/ https://gaussian.com/link0/]&lt;br /&gt;
&lt;br /&gt;
These limits should be less than what is available/free on the specific node. You can find out these information on Linux by using these commands:&lt;br /&gt;
&lt;br /&gt;
 nproc  #number of threads (2x no of cores)&lt;br /&gt;
 free -g # memory usage&lt;br /&gt;
 df -h   # disk space usage (look for /scratch) &lt;br /&gt;
&lt;br /&gt;
You should not use more than 8-12 threads for each QM job due to the poor parallel salability.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;df -h&amp;quot; to check available scratch disk space. Your MaxDisk should be much less than (e.g. 50%; even less if there other jobs running on the same node) available since others may need the scratch disk too. DO NOT STRESS the node or it will slow down everyone. If your QM job crashes, you will need manually clean the /scratch disk (you could use a script to run jobs/clean afterwards).&lt;br /&gt;
&lt;br /&gt;
&amp;quot;free -g&amp;quot; output changed from centos 6 to 7.&lt;br /&gt;
&lt;br /&gt;
 [pren@node41 ~]$ free -g&lt;br /&gt;
              total       used       free     shared    buffers     cached&lt;br /&gt;
 Mem:            31         14         16          0          0         11&lt;br /&gt;
 -/+ buffers/cache:          2         &#039;&#039;&#039;28&#039;&#039;&#039;&lt;br /&gt;
 Swap:           15 1717986918         15&lt;br /&gt;
&lt;br /&gt;
Above is Centos 6 (3 rows)ouput. the &amp;quot;-/+buff&amp;quot; number under free (28 GB) is what&#039;s available&lt;br /&gt;
&lt;br /&gt;
 [pren@node64 ~]$ free -g&lt;br /&gt;
               total        used        free      shared  buff/cache   available&lt;br /&gt;
 Mem:             31          10           4           0          16          &#039;&#039;&#039;20&#039;&#039;&#039;&lt;br /&gt;
 Swap:            15           0          15&lt;br /&gt;
&lt;br /&gt;
Above is centos 7 (two rows). The &amp;quot;20&amp;quot; GB under &amp;quot;available&amp;quot; is the number (or less) you should use for&amp;amp;nbsp;%mem&lt;br /&gt;
&lt;br /&gt;
== Gaussian ==&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 16 ===&lt;br /&gt;
&lt;br /&gt;
Latest as of 2019&lt;br /&gt;
&lt;br /&gt;
To use the latest Gaussian: “g16 myjob.com” (basically replace g09 with g16).&lt;br /&gt;
&lt;br /&gt;
But first you need to create and source this file (if csh):&lt;br /&gt;
&lt;br /&gt;
 setenv g16root &amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 setenv GAUSS_SCRDIR &amp;quot;/scratch&amp;quot;&lt;br /&gt;
 source $g16root/g16/bsd/g16.login&lt;br /&gt;
&lt;br /&gt;
If bash:&lt;br /&gt;
&lt;br /&gt;
 g16root=&amp;quot;/opt/software/Gaussian16/bin/avx&amp;quot;&lt;br /&gt;
 GAUSS_SCRDIR=&amp;quot;/scratch&amp;quot;&lt;br /&gt;
 export g16root GAUSS_SCRDIR&lt;br /&gt;
 . $g16root/g16/bsd/g16.profile&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
==== Gaussian 16 tutorial ====&lt;br /&gt;
&lt;br /&gt;
Input syntax: case-insensitive, free-format (sensitive to blank lines). Space, comma and tab can be used as a delimiter. All keywords and options may be shortened to their shortest unique abbreviation. Keyword and options:&lt;br /&gt;
&lt;br /&gt;
 keyword = option&lt;br /&gt;
 keyword(option)&lt;br /&gt;
 keyword=(option1, option2, …)&lt;br /&gt;
 keyword(option1, option2, …)&lt;br /&gt;
&lt;br /&gt;
 %rwf=/scratch/Gau-water/,60GB&lt;br /&gt;
 %chk=water.chk&amp;amp;nbsp;! Link 0 section. Output and resource specification&lt;br /&gt;
 %mem=8GB&lt;br /&gt;
 %nproc=8&lt;br /&gt;
 # MP2/6-31G(d)	! Route section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 water energy	! Title section. End with a blank line&lt;br /&gt;
  &lt;br /&gt;
 0   1	! Molecule specification. End with a blank line&lt;br /&gt;
 O  -0.464   0.177   0.0	 &lt;br /&gt;
 H  -0.464   1.137   0.0	 &lt;br /&gt;
 H   0.441  -0.143   0.0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Output files: *.out or *.log (energy, coordinates, frequencies, ...). *.chk (electron density and other information; can be read by other programs)&lt;br /&gt;
&lt;br /&gt;
The energy can be found in the output file in the format&lt;br /&gt;
&lt;br /&gt;
 SCF Done:  E(RB3LYP) =  ###     A.U. after   ## cycles&lt;br /&gt;
&lt;br /&gt;
A successfully finished job ends with the line&lt;br /&gt;
&lt;br /&gt;
 Normal termination of Gaussian XXX&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Types of computation: sp (default, single point calculation), opt (geometry optimization), freq (frequency), polar (polarizability)&lt;br /&gt;
&lt;br /&gt;
Computational methods (in general order of increasing accuracy and cost): HF, DFT methods (B3LYP, wB97XD), MP2, CCSD(T). For transition metal ions,&amp;amp;nbsp;restricted open-shell wavefunctions may be needed. Preface the keywork by RO, e.g. ROHF. Implicit solvation (SCRF).&lt;br /&gt;
&lt;br /&gt;
Basis sets:&lt;br /&gt;
&lt;br /&gt;
6-31G, 6-31+G(d), 6-311++G(2d,2p) ...&lt;br /&gt;
&lt;br /&gt;
def2TZVPP, def2QZVPP, ...&lt;br /&gt;
&lt;br /&gt;
cc-pVTZ, aug-cc-pVQZ,&amp;amp;nbsp;aug-cc-pV5Z, ...&lt;br /&gt;
&lt;br /&gt;
Gen (user-specified basis set. Useful for hybrid basis sets and for some transition metals)&lt;br /&gt;
&lt;br /&gt;
Basis set extrapolation. The energy typically decreases with increasing size of the basis set. Assuming a simple relationship between the energy and the size of basis set, such as E(n) = E(CBS) + K/n or E(n) = E(CBS) + exp(-A*n), one can do extrapolation to obtain E(CBS). n is the number of zetas in cc-pV*Z basis set. Of course, the larger basis sets are used as input, the better the interpolation results are. ([https://doi.org/10.1021/acs.jctc.5b00267 https://doi.org/10.1021/acs.jctc.5b00267])&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Single point calculation&lt;br /&gt;
&lt;br /&gt;
The interaction energy between fragments. Counterpoise correction (basis-set superposition error).&lt;br /&gt;
&lt;br /&gt;
 # B3LYP/6-31G(d) Counterpoise=2 &lt;br /&gt;
 &lt;br /&gt;
 Counterpoise on water dimer&lt;br /&gt;
 &lt;br /&gt;
 0,1 0,1 0,1&lt;br /&gt;
 O(Fragment=1)  0.00  0.00  0.00&lt;br /&gt;
 H(Fragment=1)  0.49  0.76 -0.29&lt;br /&gt;
 H(Fragment=1)  0.49 -0.76 -0.29&lt;br /&gt;
 O(Fragment=2)  0.00  0.00  2.98&lt;br /&gt;
 H(Fragment=2) -0.91  0.00  3.24&lt;br /&gt;
 H(Fragment=2) -0.01  0.00  2.03&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp; Geometry optimization Optimization with restraint on cartesian coordinate (X), bond (B), angle (A) or dihedral (D).&lt;br /&gt;
&lt;br /&gt;
 %chk=Asp-090-000.chk&lt;br /&gt;
 %nproc=12&lt;br /&gt;
 %mem=50GB&lt;br /&gt;
 # opt=ModRedundant freq b3lyp/6-31g(d) scrf=pcm nosymm&amp;amp;nbsp;! Geometry optimization with redundant internal coordinate, followed by frequency calculation&lt;br /&gt;
 &lt;br /&gt;
 Ace-Asp-NMe&lt;br /&gt;
 &lt;br /&gt;
 -1 1&lt;br /&gt;
    C      -0.051237       0.026635      -0.000187&lt;br /&gt;
    C      -0.047739      -0.050718       1.518390&lt;br /&gt;
    O       1.019569      -0.121175       2.135311&lt;br /&gt;
    H      -1.074728       0.094187      -0.430415&lt;br /&gt;
    H       0.437648      -0.877255      -0.425686&lt;br /&gt;
    H       0.518496       0.921014      -0.335147&lt;br /&gt;
    N      -1.258811      -0.011713       2.130962&lt;br /&gt;
    C      -1.492666      -0.118061       3.568820&lt;br /&gt;
    C      -1.021236      -1.406075       4.262506&lt;br /&gt;
    H      -2.112694      -0.008704       1.555853&lt;br /&gt;
    O      -0.872499      -1.416891       5.492335&lt;br /&gt;
    H      -0.814136       0.646375       4.025748&lt;br /&gt;
    C      -2.942279       0.313077       3.948700&lt;br /&gt;
    C      -4.058922      -0.713527       3.975701&lt;br /&gt;
    O      -3.832849      -1.916173       3.694369&lt;br /&gt;
    O      -5.221538      -0.313729       4.245555&lt;br /&gt;
    H      -2.888069       0.717014       4.990238&lt;br /&gt;
    H      -3.258114       1.180766       3.321244&lt;br /&gt;
    N      -0.758839      -2.493440       3.494647&lt;br /&gt;
    C      -0.287386      -3.768629       3.978826&lt;br /&gt;
    H      -0.964272      -2.486848       2.487606&lt;br /&gt;
    H       0.203785      -4.348693       3.168012&lt;br /&gt;
    H      -1.127920      -4.384617       4.365829&lt;br /&gt;
    H       0.452648      -3.653697       4.800493&lt;br /&gt;
 &lt;br /&gt;
 D   7  8 13 14  F&amp;amp;nbsp;! This Dihedral angle is fixed during optimization&lt;br /&gt;
 D   8 13 14 15  F&lt;br /&gt;
 D   2  7  8  9  F&lt;br /&gt;
 D   7  8  9 19  F&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the restraint is specified correctly, you will see the output&lt;br /&gt;
&lt;br /&gt;
 ! D9    D(3,2,7,8)             -6.5623         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D10   D(3,2,7,10)          -171.5371         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D11   D(2,7,8,9)            -60.0011         Frozen                         &amp;amp;nbsp;!&lt;br /&gt;
 ! D12   D(2,7,8,12)            51.2325         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
 ! D13   D(2,7,8,13)           165.3165         estimate D2E/DX2               &amp;amp;nbsp;!&lt;br /&gt;
&lt;br /&gt;
The coordinates in each iteration start with the line &amp;quot;Standard orientation&amp;quot; or &amp;quot;Input orientation&amp;quot; depending on the setting.&lt;br /&gt;
&lt;br /&gt;
                         Standard orientation:&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
 Center     Atomic      Atomic             Coordinates (Angstroms)&lt;br /&gt;
 Number     Number       Type             X           Y           Z&lt;br /&gt;
 ---------------------------------------------------------------------&lt;br /&gt;
      1          6           0       -3.158798   -1.400996   -1.145889&lt;br /&gt;
      2          6           0       -2.360207   -0.768947   -0.008899&lt;br /&gt;
      3          8           0       -2.910645   -0.063771    0.836128&lt;br /&gt;
&lt;br /&gt;
Convergence criteria. Sometimes it&#039;s ok that the Force convergence is met but the displacement convergence is not.&lt;br /&gt;
&lt;br /&gt;
         Item               Value     Threshold  Converged?&lt;br /&gt;
 Maximum Force            0.000028     0.000450     YES&lt;br /&gt;
 RMS     Force            0.000005     0.000300     YES&lt;br /&gt;
 Maximum Displacement     0.001759     0.001800     YES&lt;br /&gt;
 RMS     Displacement     0.000433     0.001200     YES&lt;br /&gt;
&lt;br /&gt;
Check frequencies to make sure minimum energy point is reached. If there is (large) negative frequency, it means the maximum point on a concave curve.&lt;br /&gt;
&lt;br /&gt;
 Harmonic frequencies (cm**-1), IR intensities (KM/Mole), Raman scattering&lt;br /&gt;
 activities (A**4/AMU), depolarization ratios for plane and unpolarized&lt;br /&gt;
 incident light, reduced masses (AMU), force constants (mDyne/A),&lt;br /&gt;
 and normal coordinates:&lt;br /&gt;
                     1                      2                      3&lt;br /&gt;
                     A                      A                      A&lt;br /&gt;
 Frequencies --   -29.6237                28.3840                40.0446&lt;br /&gt;
 Red. masses --     9.3990                 5.7633                 3.4850&lt;br /&gt;
 Frc consts  --     0.0049                 0.0027                 0.0033&lt;br /&gt;
 IR Inten    --     5.0560                10.5798                 1.2347&lt;br /&gt;
  Atom  AN      X      Y      Z        X      Y      Z        X      Y      Z&lt;br /&gt;
     1   6    -0.10   0.00   0.09    -0.15   0.14   0.03    -0.11  -0.06   0.09&lt;br /&gt;
     2   6    -0.04   0.03   0.03    -0.07   0.05   0.02    -0.06  -0.04   0.04&lt;br /&gt;
     3   8     0.02   0.12  -0.01     0.00   0.06   0.06    -0.04  -0.11   0.11&lt;br /&gt;
     4   1    -0.18  -0.12   0.18    -0.24   0.08   0.03    -0.02   0.16  -0.14&lt;br /&gt;
&lt;br /&gt;
=== Gaussian 09 ===&lt;br /&gt;
&lt;br /&gt;
The csh source file is ~pren/.g09gh&lt;br /&gt;
&lt;br /&gt;
This version can use multiple CPU cores. See ~pren/QuantumMechanics/gaussian-test/ for examples.&lt;br /&gt;
&lt;br /&gt;
If you source it and see permission error, this is because the files in /opt/g09gh/... are only readable/executable by users in &amp;quot;users&amp;quot; group. Change the group and passwd files accordingly (by admin). Log out and log back in!&lt;br /&gt;
&lt;br /&gt;
Change the source file to bash if you are using bash.&lt;br /&gt;
&lt;br /&gt;
Below is obsolete.....(as of Aug 2015)&lt;br /&gt;
&lt;br /&gt;
If you see an error about out of space but you are sure you are, try this (as root): echo 0 &amp;gt; /proc/sys/kernel/randomize_va_space&lt;br /&gt;
&lt;br /&gt;
Before we have g03 compiled using pgi 32 bit. As a results we can not use more than 2G memory, but we can use multiprocessors on the same node. To use this version, you need these lines in your .cshrc or in a separate file and source before you run.&lt;br /&gt;
&lt;br /&gt;
 setenv PGI /usr/pgi&lt;br /&gt;
 setenv g03root /opt&lt;br /&gt;
 source $g03root/g03/bsd/g03.login.pgi&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
We now have the 64-bit intel compiled version. We can use as much as memory you like with it, BUT NO MULTIPROCESSOR. Still this single cpu version will be faster than the previous version using multiprocessors.&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/cce/10.1.011/bin/iccvars.csh&lt;br /&gt;
 source /opt/intel/fce/10.1.011/bin/ifortvars.csh&lt;br /&gt;
 setenv g03root /opt/gaussian&lt;br /&gt;
 source $g03root/g03/bsd/g03.login&lt;br /&gt;
 setenv GAUSS_SCRDIR /scratch&lt;br /&gt;
&lt;br /&gt;
The intel version is not necessarily faster since you can’t use multiple processor as the old PGI version.&lt;br /&gt;
&lt;br /&gt;
You can only use the intel version of Gaussian on bme-sun and cluster nodes, which have fedora 7 OS. It does not work on nodes 16-18 , however, since they have AMD processors. Source ~pren/.g03.intel and you can start using g03.&lt;br /&gt;
&lt;br /&gt;
If you upgraded your OS on your workstation, you can’t use the old PGI version of g03 on your workstation. But you should be able to continue to use it on our cluster. Your previous .cshrc should continue to work. You may also try source ~pren/.g03.pgi&lt;br /&gt;
&lt;br /&gt;
You can take a look at the two files .g03* to see the difference.&lt;br /&gt;
&lt;br /&gt;
Each software is compiled for specific OS environment so you should expect many things will be broken when you mess with your workstation.&lt;br /&gt;
&lt;br /&gt;
Also you probably can’t switch from one to another without logging out your shell, which resets your environmental variables.&lt;br /&gt;
&lt;br /&gt;
    You need to set maxdisk=1000MW (example) in the gaussian input (if you have an error of memory allocation, try not specify&amp;amp;nbsp;%chk in your input, and delete all the temp files before you restart)&lt;br /&gt;
    You need a directory /scratch. This may not be created on new workstation yet&lt;br /&gt;
    You need /usr/pgi to use the pgi 32 bit version&lt;br /&gt;
    Remember to clean /scratch aftewards but watch out that you don&#039;t delete files belong to others&lt;br /&gt;
&lt;br /&gt;
On fedroa 10, we need glibc 386 library to run PGI (/lib/ld-linux.so.2). cd /opt/fedora-iso/fc10-rpms rpm -Uvh glibc-2.9-3.* glibc-*-2.9-3.x86_64.rpm ALso need /usr/pgi and /scratch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&amp;amp;nbsp;&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
(Last update:&amp;amp;nbsp;Sept. 18, 2019 by Chengwen)&lt;br /&gt;
&lt;br /&gt;
Psi4 is a Python/C++, Open source, quantum software package that can be run as&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
#An executable on command line &lt;br /&gt;
#Python module in python script &lt;br /&gt;
&lt;br /&gt;
To run on command line, log in to one of the nodes with&amp;amp;nbsp;big memory/disk&lt;br /&gt;
&amp;lt;pre&amp;gt;node35, node36, node37, node38, node51, node52, node54, node56, node59, node70, node83&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then source this file and you are ready to run psi4 jobs&lt;br /&gt;
&amp;lt;pre&amp;gt;source /home/liuchw/.bashrc.psi4conda&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A tutorial on the input files and how to run psi4 can be found here:&amp;amp;nbsp;[https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html https://leucinw.github.io/home/tutorial/2019/08/02/tut-psi4.html]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== jmol ==&lt;br /&gt;
&lt;br /&gt;
can view Gaussian and many other format; make small molecules.&lt;br /&gt;
&lt;br /&gt;
/opt/software/CHEM/jmol-13.2.3/jmol.sh&lt;br /&gt;
&lt;br /&gt;
== Avogadro ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&#039;&#039;&#039;Installed on bme-earth (2/2014). &amp;quot;ssh -X bme-earth&amp;quot; and the &amp;quot;avogadro&amp;quot;.&#039;&#039;&#039;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avogadro is a free, open source, cross-platform molecular editor designed for flexible use in computational chemistry, molecular modeling, bioinformatics, materials science, and related areas.  &lt;br /&gt;
 Packages are available for Mac OSX, Windows and Linux, as well as source code provided under the GNU GPL.&lt;br /&gt;
&lt;br /&gt;
Can built peptides etc.&lt;br /&gt;
&lt;br /&gt;
 To download:&lt;br /&gt;
 [http://avogadro.openmolecules.net/wiki/Get_Avogadro http://avogadro.openmolecules.net/wiki/Get_Avogadro]&lt;br /&gt;
&lt;br /&gt;
== Gabedit ==&lt;br /&gt;
&lt;br /&gt;
Read and visualize Gaussian, Gamess, Mopac, molpro... file (first structure and last structure in optimization). Runs on Linux!&lt;br /&gt;
&lt;br /&gt;
 /opt/software/CHEM/Gabedit/gabedit &lt;br /&gt;
&lt;br /&gt;
To visualize (gaussian optimized) structure, click on menu &amp;quot;Geometry&amp;quot; and then &amp;quot;draw&amp;quot; right click on black window and select read ....&lt;br /&gt;
&lt;br /&gt;
= MS Windows =&lt;br /&gt;
&lt;br /&gt;
FreeCommander: Free file manager. Alternative to total commander. Dual panels. Capable of synchronization and compare directories. Download: [http://www.freecommander.com/ http://www.freecommander.com/]&lt;br /&gt;
&lt;br /&gt;
= Visualization: =&lt;br /&gt;
&lt;br /&gt;
== Facio ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2/2007 Jenny&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
There is a new visulization software Facio available, which is publicly available at no charge. You can download it for your windows machine from the website. Although Facio is a native application of Windows environment, it can work on Linux with the help of WINE, which we have already. To download the software for your WINDOWS machine and know more about the software, please visit this website:&lt;br /&gt;
&lt;br /&gt;
 [http://www1.bbiq.jp/zzzfelis/Facio.html http://www1.bbiq.jp/zzzfelis/Facio.html]&lt;br /&gt;
&lt;br /&gt;
To use facio on your workstation without vmware or remote access, please place the following alias in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 alias facio &amp;quot;/opt/cxoffice/bin/wine /opt/software/Facio1081/Facio.exe&amp;quot;&lt;br /&gt;
&lt;br /&gt;
It is an OpenGL-based graphics program for molecular modeling and visualization of quantum chemical calculations(GAUSSIAN and GAMESS), so it is easy to write the GAUSSIAN input file, view the output for optimized Geometry or load checkpoint file etc. It can also load TINKER xyz,PDB...format files. I am also attaching the manual on this email for your reference.&lt;br /&gt;
&lt;br /&gt;
== Jchem and Marvin ==&lt;br /&gt;
&lt;br /&gt;
[http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html] visualization, pka, logP, logD, 2D to 3D, fragmentation and many other usages.&lt;br /&gt;
&lt;br /&gt;
*&#039;&#039;&#039;Windows: Version 5.3 installed on bme-mercury&#039;&#039;&#039; OBSOLETE &lt;br /&gt;
*&#039;&#039;&#039;Linux: Version 5.2 (11/2009)&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon5.2/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;&#039; setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can then use ChemAxon software For example type &amp;quot;mview /opt/database/known_drug/cmc20021_he.mol2&amp;quot;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
I have installed a very useful Jchem package ([http://www.chemaxon.com/products.html http://www.chemaxon.com/products.html])&lt;br /&gt;
&lt;br /&gt;
To access, put “/opt/software/CHEM/ChemAxon/JChem/bin” in your path, and add the following environmental variable in your .cshrc file&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;setenv CHEMAXON_LICENSE_URL /opt/software/CHEM/chemaxon/license.cxl&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Now you can use the executables in bin on your worksrtation: mview can let you view a database of small molecules, for example:&lt;br /&gt;
&lt;br /&gt;
 “mview /opt/database/kinase-biogen/ligands_4pengyu.sdf”&lt;br /&gt;
 You can clean up and convert 2d structure to 3d structure using Edit/clean/3d …&lt;br /&gt;
&lt;br /&gt;
Msapce let you viz PDB structure of proteins. Msketch let you draw a new molecule&lt;br /&gt;
&lt;br /&gt;
Mview read gaussian output file.&lt;br /&gt;
&lt;br /&gt;
To install on your windows/linux computer, you can use the installation file in /opt/software/CHEM/chemaxon/ (note chemaxon and ChemAxon are two different directories). Copy the license.cxl into /User/yourusername/chemaxon (to make the new folder chemaxon yourself) for vista. For XP, create the same directory in user directory and copy the license file.&lt;br /&gt;
&lt;br /&gt;
== vmd ==&lt;br /&gt;
&lt;br /&gt;
Since vmd186 is not functioning correctly on Linux workstation, you may want to use vmd 1.8.5 (type plain vmd) for now. To use the rmsd plot function, create a file .vmdrc in your home directory with the following content:&lt;br /&gt;
&lt;br /&gt;
lappend auto_path {/usr/local/lib/vmd/plugins/noarch/tcl/rmsdtt} vmd_install_extension rmsdtt rmsdtt_tk_cb &amp;quot;WMC PhysBio/RMSDTT&amp;quot; menu main on&lt;br /&gt;
&lt;br /&gt;
For admin: To install vmd, cd into /opt/vmdxxx/, run “configure LINUXAMD64 OPENGL”, and the cd ./src and “make install”.&lt;br /&gt;
&lt;br /&gt;
= Simulation: GROMACS =&lt;br /&gt;
&lt;br /&gt;
=== Installation (updated 8/20/2014) ===&lt;br /&gt;
&lt;br /&gt;
Installed under /opt/, can run on all nodes.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;/opt/gromacs-4.5.3-mpi/bin&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;/opt/gromacs-4.5.3-intel/bin (need source ~pren/.cshrc.f13)&amp;lt;/span&amp;gt; &lt;br /&gt;
*/opt/gromacs-4.5.4/bin&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
Add /opt/gromacs-4.5.3-mpi/bin to your path (cshrc or bashrc) to use the executables.&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;In gromacs-4.5.3-mpi/bin&amp;amp;nbsp;&#039;&#039;&#039;mdrun_mpi&#039;&#039;&#039;&amp;amp;nbsp;is that one does mpi parallel simualtions, &#039;&#039;&#039;mdrun&#039;&#039;&#039; is serial.&amp;lt;/span&amp;gt;&lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
*General Instruction:&amp;amp;nbsp;[http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp http://ccmst.gatech.edu/wiki/index.php?title=GROMACS&amp;amp;nbsp];* &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;On nova fftw (3.2.4) was built by mike in /opt/fftw, copied to in /usr/local on NOVA&amp;lt;/span&amp;gt; &lt;br /&gt;
*On nodes fftw (3.2.4) was installed through yum, in /usr/lib64 (single, double, long double) &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;How mike compiled /opt/gromacs-4.5.4:&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/home/schnied/Software/gromacs-4.5.4/config.log&amp;lt;/span&amp;gt; &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Here is how I compiled gromacs-4.5.3-mpi on NOVA (fftw is in /opt/fftw)&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;Use intel compiler 10:&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source /opt/intel/fce/10.0.023/bin/ifortvars.csh;&amp;amp;nbsp;source /opt/intel/cce/10.0.023/bin/iccvars.csh&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​cd /home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --program-suffix=_mpi --enable-float --with-fft=fftw3 CPPFLAGS=-I/opt/fftw3/include LDFLAGS=-L/opt/fftw3/lib --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&#039;&#039;&#039;Note the enable-float (single precision) was used for fftw so it should be used for gromacs to be consistent&#039;&#039;&#039;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 6; make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;I then copied everything to /opt/gromacs-4.5.3-mpi&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​How to compile gromacs-4.5.3-intel using intel compiler (v13) and mkl (2013) fftw on NOVA&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​reference:&amp;amp;nbsp;[http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf http://www.hpcadvisorycouncil.com/pdf/GROMACS_Best_Practices.pdf]&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make clean&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;source ~/.cshrc.f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;./configure --enable-mpi --with-fft=mkl CC=icc F77=ifort CXX=icpc --program-suffix=_mpi --prefix=/home/pren/gromacs/gromacs-4.5.3&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make -j 4&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;make install&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;copy to /opt/gromacs-4.5.3-intel&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt; &lt;br /&gt;
**&amp;lt;span style=&amp;quot;color:#0000ff&amp;quot;&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;To run mdrun_mpi etc on nodes, source ~pren/.cshrc,f13&amp;lt;/span&amp;gt;&amp;lt;/span&amp;gt;   &lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;​&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;If you run mdrun_mpi and see error related fftw3f library not found, that is because fftw library is not installed in /usr/lib64 (yum install fftw* should solve this)&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Check Gromacs WIKI following the link below&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 [http://wiki.gromacs.org/index.php/Main_Page http://wiki.gromacs.org/index.php/Main_Page]&lt;br /&gt;
&lt;br /&gt;
== Quick Guide ==&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/pdb2gmx -f prozn.pdb -o prozn -ff oplsaa -p prozn.top -ter ~/gromacs/parallel/bin/editconf -f prozn.gro -o proznw.gro -d 0.8 -bt octahedron cp prozn.top proznwat.top ~/gromacs/parallel/bin/genbox -cp proznw.gro -cs spc216 -o proznwat.gro -p proznwat.top&lt;br /&gt;
&lt;br /&gt;
// any constraints, rstarin put right behind the itp in top file.&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f em -c proznwat.gro -o em -p proznwat.top ~/gromacs/parallel/bin/mdrun -v -s em.tpr -o em.trj -c after_em -g emlog&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpdboot -n 4 -f ./mpd.hosts --ncpus=2&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_em -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
#in case refined with short no-constraint md &lt;br /&gt;
&lt;br /&gt;
~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md0 -p proznwat.top -shuffle -np 8&lt;br /&gt;
&lt;br /&gt;
restart from the last frame (or given time, see grompp): ~/gromacs/parallel/bin/grompp -v -f md -o md -c after_md.gro -t md.trj -p proznwat.top -shuffle -np 2&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color: rgb(255, 0, 0)&amp;quot;&amp;gt;mpirun -n 2&amp;lt;/span&amp;gt; mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp;&lt;br /&gt;
&lt;br /&gt;
#mpirun -n 2 ~pren/gromacs/parallel/bin/mdrun_mpi -v -e md -s md.tpr -o md.trj -c after_md.gro -g md.log &amp;gt; &amp;amp; md.job &amp;amp; &lt;br /&gt;
&lt;br /&gt;
trjconv -f md.trj -o movie.pdb -n now.ndx -s md -b 1 -e 100 -skip 1&lt;br /&gt;
&lt;br /&gt;
 make_ndx -f after_md.gro -o now.ndx&lt;br /&gt;
     1 | 12 | 13 | 14&lt;br /&gt;
&lt;br /&gt;
make index to creat new index&lt;br /&gt;
&lt;br /&gt;
        a 1-10  //a group of atoms from 1-10&lt;br /&gt;
     name 17 pep  // rename group 17&lt;br /&gt;
     1 &amp;amp;&amp;amp;nbsp;! pep   // a group with all protein atoms except 1-10 (pep)&lt;br /&gt;
&lt;br /&gt;
== Running mpi ==&lt;br /&gt;
&lt;br /&gt;
If you see an error related to &amp;quot;libmpich.so.1.2:&amp;quot; not found, add the mpich2 lib path&lt;br /&gt;
&lt;br /&gt;
 setenv LD_LIBRARY_PATH &amp;quot;/opt/mpich2-fc13-p26/lib/:/opt/software/CHEM/openbabel-2.3.0/lib:&amp;quot;{$ATLAS}&lt;br /&gt;
&lt;br /&gt;
[[Research:Remd|REMD HOWTO]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Benchmarks&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here are some observations for Kinase system (38772 atoms) using our own cluster from node18 to node30.&lt;br /&gt;
&lt;br /&gt;
 Using 8 , the speed is 2.54 ns/day. &lt;br /&gt;
 Using 12 , the speed is 3.14 ns/day. &lt;br /&gt;
 Using 15 , the speed is 3.38 ns/day.  &lt;br /&gt;
 The scaling become worse beyond 20, the speed is lower than 1ns/day.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= GPU nodes =&lt;br /&gt;
&lt;br /&gt;
== hostnames ==&lt;br /&gt;
&lt;br /&gt;
 [[Sysadmin:nodes#GPU_nodes| gpu nodes]]&lt;br /&gt;
&lt;br /&gt;
run &amp;quot;bash&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm before use. If has error (esp amber), please try different /opt/software/bash/bashrc.amber.*&lt;br /&gt;
&lt;br /&gt;
== installation ==&lt;br /&gt;
&lt;br /&gt;
We already has Canopy version pythin2.7 but If need to install python: [http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/ http://toomuchdata.com/2014/02/16/how-to-install-python-on-centos/]&lt;br /&gt;
&lt;br /&gt;
*Centos 6.5 &lt;br /&gt;
&lt;br /&gt;
 node2xxx&lt;br /&gt;
 mount -t nfs 10.0.0.200:/opt /opt&lt;br /&gt;
 mkdir ~/.ssh&lt;br /&gt;
 cp -r /opt/system-setup/rootssh2013/* ~/.ssh&lt;br /&gt;
 restorceon -R ~/.ssh&lt;br /&gt;
 node-setup.sh&lt;br /&gt;
&lt;br /&gt;
*yum update &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*install nvidia graphics driver: /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
&lt;br /&gt;
 reboot&lt;br /&gt;
&lt;br /&gt;
*Install both nvidia cuda toolkit: &lt;br /&gt;
&lt;br /&gt;
  updated:7.5  is latest for OpenMM&lt;br /&gt;
 /opt/nvidia/cuda_6.5.14_linux_64.run (say No to nvidia driver)&lt;br /&gt;
 /opt/nvidia/cuda_6.0.37_linux_64.run (say yes to obsolte/uncompatible and No to nvidia driver)&lt;br /&gt;
&lt;br /&gt;
*Install gdk_ in /opt/nvidia (2016 August: this is now necessary for new stuff Jay put in for detecting GPU automatically) &lt;br /&gt;
&lt;br /&gt;
*mkdir /usr/local/bash &lt;br /&gt;
&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber bashrc.amber (newer CPU)&lt;br /&gt;
 ln -s /opt/software/bash/.bashrc.amber.earth bashrc.amber (older CPU)&lt;br /&gt;
&amp;lt;div&amp;gt;ln -s /opt/software/bash/.bashrc.amber.970 bashrc.amber (new CPU/GTX 970: node210 211)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Run bash; &amp;amp;nbsp;source&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;/opt/software/bash/.bashrc.amber.earth;&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;cd /opt/software/amber14-gpu-earth/test/cuda/dhfr/; ./Run.dhfr.ntb2_ntt1.my&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;(&amp;lt;span style=&amp;quot;font-family: Arial, Verdana, sans-serif; font-size: 12px&amp;quot;&amp;gt;If you are using different source, go to the corresponsing amber dir)&amp;lt;/span&amp;gt;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 If this bombs, have to make a copy of the amber-14-gpu, and recompile for that CPU (see amber-GPU below)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Install openMM - Don&#039;t have to, just need to link openmm to usr/local/openmm, SEE BELOW&lt;br /&gt;
&lt;br /&gt;
  source /opt/software/bash/.bashrc.openmm&lt;br /&gt;
 /opt/software/OpenMM6.1-Linux64/install.sh (this install precompiled opemm into /usr/local and /opt/software/python27&lt;br /&gt;
&lt;br /&gt;
= OpenMM-GPU setup =&lt;br /&gt;
&lt;br /&gt;
*Yum update your cents 6.5 and reboot &lt;br /&gt;
*Install nvidia driver in /opt/nvidia/NVIDIA-Linux-x86_64-343.22.run &lt;br /&gt;
*Install nvidia toolkit (opt/nvidia/cuda_6.5xxx cuda_6.0 for openMM6.1 on node201-207) to /usr/loca/ and skip the driver installation (already done above) &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;Cuda 6.5 required for gtx970 on node210. &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*install python 2.7 from Canopy into /opt/software/python27/ (python27-780 for GTX780, openmm6.1 on node201-207) &lt;br /&gt;
&lt;br /&gt;
 &#039;&#039;~pren/canopy-1.4.1-rh5-64.sh&#039;&#039;&lt;br /&gt;
 this step is already done, no need to repeat for new computers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;Do one of the following (1-3, 2 or 3 is the latest)&amp;lt;/span&amp;gt; &lt;br /&gt;
&amp;lt;div&amp;gt;&amp;amp;nbsp;1. For node 201-207, go to the openmm prebuilt binary folder OpenMM6.1-Linux64 (copy a fresh one from ~pren/OpenMM6.1-linux64, you can delete this after done)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;quot;.\install.sh&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Here you have to use python2.7. See /opt/software/bash/bashrc.openmm&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; 2. For nodes 201-211, GTX 780 or 970/980, download &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;openmm6.2&amp;lt;/span&amp;gt; source (/opt/software/OpenMM6.2-Linux64) from github and compile by following instruction (on latest GPU 980)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm.970&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;[http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation http://biomol.bme.utexas.edu/wiki/index.php/Software:Tutorials#Installation]&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Once the aboove step is done, I copied the /usr/local/openmm to /opt/software/openmmxxx, and the new node only need a link to&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp; &amp;amp;nbsp; &amp;quot;ln -s /opt/software/openmm6.2-installed /usr/local/openmm&amp;quot;, where &amp;quot;openmm6.2-installed&amp;quot; was compiled on node201 and copied to opt.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;Future nodes, no need to recompile the openmm. Just use the link above. Openmm install things into the shared python directory and /usr/local/openmm!!!&amp;lt;/span&amp;gt;&#039;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;-----------------------------------------------------&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;3. For &amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;any new openmm distro&amp;lt;/span&amp;gt;:&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;install nvidia and cuda drive as above.&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Copy &amp;quot;/opt/software/python27&amp;quot; to a new python27-openmm6.x&amp;quot;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Make a new bashrc.openmm.6.x with python changed accordingly&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;Download and compile openmm as in 2.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;------------------------------------------------------&amp;lt;/div&amp;gt; &lt;br /&gt;
*test &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;div&amp;gt;bash&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source /opt/software/bash/bashrc.openmm or&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;source &amp;amp;nbsp;/opt/software/bash/bashrc.openmm.970 (on any GPU nodes to use openmm6.2 - need /usr/local/openmm linked to /opt/software/openmm6.2-installed)&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;/home/pren/OpenMM/shfr-test/simulateMTS.py&amp;lt;/div&amp;gt; &amp;lt;/div&amp;gt; &lt;br /&gt;
*&#039;&#039;&#039;Notes&#039;&#039;&#039;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;: OpenMM python: /opt/software/python27/appdata/canopy-1.4.1.1975.rh5-x86_64/lib/python2.7/site-packages/simtk/openmm/app&amp;amp;nbsp;&amp;lt;/span&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 /home/pren/forcebalancev2/lib/python2.7/site-packages/forcebalance/openmmio.py&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&amp;lt;span style=&amp;quot;white-space: normal&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= AMBER-GPU &amp;amp;nbsp;=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Run AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;pre&amp;gt; source /home/pren/amber-git/amber17/bashrc.amber16&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== Install AMBER-GPU&amp;amp;nbsp; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;September 2017 &amp;amp;nbsp;--Chengwen&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Compile &#039;&#039;&#039;Amber18-gpu&#039;&#039;&#039; for new gpu nodes (&#039;&#039;&#039;node70 to 100&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
1. Install cuda7.0 from /opt/nvidia/ (Caution: do NOT install graphic driver)&#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Copy amber file from /home/pren/amber-git:&lt;br /&gt;
&lt;br /&gt;
   cp -r /home/pren/amber-git/amber /home/liuchw/&lt;br /&gt;
&lt;br /&gt;
3. Set environmental variables:&lt;br /&gt;
&amp;lt;pre&amp;gt;  source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
  export AMBERHOME=/home/liuchw/amber&lt;br /&gt;
  export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
  export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
  export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
  export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
  export CUDA_HOME=/usr/local/cuda-7.0 &lt;br /&gt;
  export DO_PARALLEL=&#039;mpirun -np 1&#039;&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4. Configure and install&lt;br /&gt;
&lt;br /&gt;
   cd $AMBERHOME&lt;br /&gt;
  ./configure -cuda -mpi -noX11 intel &lt;br /&gt;
   make install&lt;br /&gt;
&lt;br /&gt;
5. Copy the compiled whole directory to /opt/software/ &#039;&#039;&#039;(root)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
   cp -r amber /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
6. Change $AMBERHOME to /opt/software/amber18-gpu&lt;br /&gt;
&lt;br /&gt;
====== &amp;amp;nbsp; ======&lt;br /&gt;
&lt;br /&gt;
== Install CPU version ==&lt;br /&gt;
&lt;br /&gt;
See /home/pren/amber-git/readme for installation notes&lt;br /&gt;
&lt;br /&gt;
Serial version: /home/pren/amber-git/amber17/ambercpu Parallel version: /home/pren/amber-git/amber17/ambercpu-mpi&lt;br /&gt;
&lt;br /&gt;
Before running jobs (e.g. mmpbsa.py) source bashrc.ambercpu or bashrc.ambercpumpi&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
== September 2014 ==&lt;br /&gt;
&lt;br /&gt;
compiled Amber14-gpu from /home/pren/amber12-2013/&lt;br /&gt;
&lt;br /&gt;
First, install CUDA software AND drivers from NVIDIA website. You should be able to confirm CUDA is installed by running the test /usr/local/bin/deviceQuery or nvidia-smi. You need to define the following environment variables. AMBERHOME and CUDA_HOME need to be defined. Also, the library_path needs to be defined for amber and mpich2. Make sure that a compatible version of python is defined as well. Example:&lt;br /&gt;
&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-6.5/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-6.5/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
 export AMBERHOME=/opt/software/amber14-gpu&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export LD_LIBRARY_PATH=/opt/mpich2-1.4.1p1/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
 alias python=/usr/bin/env\ python2.6&lt;br /&gt;
 export PYTHONPATH=/usr/bin/python2.6&lt;br /&gt;
 export PATH=/opt/mpich2-1.4.1p1/bin/mpicc/:/opt/mpich2-1.4.1p1/bin:$PATH&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-6.5&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Second, compile AMBER by the following:&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 2&#039;&lt;br /&gt;
 make test #(or try the executable test/test_amber_cuda_parallel.sh&amp;amp;nbsp;; actual cases in  test/cuda/)&lt;br /&gt;
&lt;br /&gt;
 Run dhfr test: /opt/software/amber16-gpu/test/cuda/dhfr/Run*.my&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If you get x11 lib error, yum install *x11* and yum install libXt-devel*.&#039;&#039; This install pmemd,cuda.mpi in /opt/software/amber14-gpu/bin/&lt;br /&gt;
&lt;br /&gt;
Due to the linking of libraries (intel,nvidia,amber), there will probably be errors. It is easier to compile amber without the flags -mpi and -cuda and then to add those after solving any problems.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2015/6/11 Install on node210, GTX970&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;cd ~pren/amber-git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Update git: amber.readme.git&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git checkout master&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;git pull&amp;amp;nbsp;&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cp amber amber15-gpu (later moved to /op/software/amber16-gpu)&lt;br /&gt;
&lt;br /&gt;
source /opt/software/bash/bashrc.amber.970&lt;br /&gt;
&lt;br /&gt;
 ./configure -mpi -cuda intel&lt;br /&gt;
 make install&lt;br /&gt;
&lt;br /&gt;
test...&lt;br /&gt;
&lt;br /&gt;
== Run AMBER on GPU ==&lt;br /&gt;
&lt;br /&gt;
1) Log into node201, 202... (2 GTX 780 cards installed). or node 210 3 GTX970 installed&lt;br /&gt;
&lt;br /&gt;
2) nvidia-smi to check which cards are available/busy (by checking the temperature and fan load)&lt;br /&gt;
&lt;br /&gt;
 If no card is being used, you can ignore this step. Otherwise you should specify to use the next available card.&lt;br /&gt;
 To select specific GPU card to run, &amp;quot;export CUDA_VISIBLE_DEVICES=&amp;quot;0&amp;quot;&amp;quot; ( [http://ambermd.org/gpus/#Running http://ambermd.org/gpus/#Running] for explanation)&lt;br /&gt;
 &amp;quot;0&amp;quot; means the first card, 1 second, 2 the third. ****Also works for OPENMM&lt;br /&gt;
&lt;br /&gt;
3) bash; source&amp;amp;nbsp;/usr/local/bash/bashrc.amber or&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-size: 12px&amp;quot;&amp;gt;bashrc.amber.970 (&amp;gt; node210)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
4) Run (using 1 card, specify 1 after np option below; use 2 card, specify 2...)&lt;br /&gt;
&amp;lt;div&amp;gt;export &amp;amp;nbsp;DO_PARALLEL=&amp;quot;/opt/mpich2-1.4.1p1/bin/mpirun -np 1&amp;quot; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber14-gpu/bin/pmemd.cuda_SPFP.MPI&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;or on &amp;gt; node210&amp;amp;nbsp;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;lt;span style=&amp;quot;background-color:#ffff00&amp;quot;&amp;gt;export sander=&amp;quot;/opt/software/amber16-gpu/bin/pmemd.cuda.MPI&amp;quot;&amp;lt;/span&amp;gt;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$DO_PARALLEL $sander -O -o $output -c inpcrd.equil -r restrt -x mdcrd &amp;lt; dummy&amp;lt;/div&amp;gt; &lt;br /&gt;
== Run AMBER GPU (Sep 2017) ==&lt;br /&gt;
&lt;br /&gt;
GPU version of AMBER was compiled for use on new GPU nodes (node 70 to 90+).&amp;amp;nbsp; Executables are in /opt/software/amber18-gpu. In order to run them, the following environmental variables need to be specified:&lt;br /&gt;
&lt;br /&gt;
 #AMBER GPU&lt;br /&gt;
 source /opt/intel/composer_xe_2013.2.146/bin/compilervars.sh intel64&lt;br /&gt;
 export AMBERHOME=/opt/software/amber18-gpu&lt;br /&gt;
 export PATH=$PATH:/usr/local/cuda-7.0/bin&lt;br /&gt;
 export LD_LIBRARY_PATH=/usr/local/cuda-7.0/lib64:${LD_LIBRARY_PATH}&lt;br /&gt;
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$AMBERHOME/lib&lt;br /&gt;
 export PATH=$PATH:/opt/mpich2-1.4.1p1/bin/mpicc/&lt;br /&gt;
 export CUDA_HOME=/usr/local/cuda-7.0&lt;br /&gt;
 export DO_PARALLEL=&#039;mpirun -np 1&#039;&lt;br /&gt;
&lt;br /&gt;
== Tips to run amber GPU as fast as you can ==&lt;br /&gt;
&lt;br /&gt;
 use single precision floating point SPFP, NOT DPFP&lt;br /&gt;
 write out infrequently (ntpr=1000,ntwx=1000, ntwr=1000)&lt;br /&gt;
 Pressure is expensive to calculate (~15% slower than NVT). Use NPT to estimate density and then use NVT for production run. &lt;br /&gt;
 in NPT, baraostat=2 (Monte Carlo is a little cheaper.&lt;br /&gt;
 Use 4fs (dt=0.004) time step (H mass repartition) if you only care about thermodynamics (kinetics is wrong).&lt;br /&gt;
 More tips can be found here: [http://ambermd.org/gpus/#Max_Perf http://ambermd.org/gpus/#Max_Perf] &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Using a single card, I was able to get &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;102ns/day&amp;lt;/span&amp;gt;&amp;amp;nbsp;on JAC system (23K atoms) using dt=0.002 (2fs), and &amp;lt;span style=&amp;quot;color:#b22222&amp;quot;&amp;gt;220ns/day&amp;amp;nbsp;using dt=0.004&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
6) &#039;&#039;&#039;NVT Example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/jac/Run.jac.my SPFP&lt;br /&gt;
&lt;br /&gt;
 see  Run.jac.my for options in NVT.&lt;br /&gt;
&lt;br /&gt;
7) &#039;&#039;&#039;NPT example&#039;&#039;&#039;: /opt/software/amber14-gpu/test/cuda/dhfr&lt;br /&gt;
&lt;br /&gt;
 see Run.dhfr.ntb2_ntt1.my for NPT options.&lt;br /&gt;
&lt;br /&gt;
Amber 14 manual: [http://ambermd.org/doc12/Amber14.pdf http://ambermd.org/doc12/Amber14.pdf]&lt;br /&gt;
&lt;br /&gt;
Occasioanlly when you two cards, you may see errors like this. Just rerun&lt;br /&gt;
&lt;br /&gt;
  &amp;quot;gpu_allreduce cudaDeviceSynchronize failed an illegal memory access was encountered&lt;br /&gt;
&lt;br /&gt;
== 4fs timestep ==&lt;br /&gt;
&amp;lt;div&amp;gt;For a 4fs timestep, you need to repartition the H mass. This is done using parmed. Note that this needs to be done on bme- Sugar, and that AMBERHOME needs to point to a amber14 installation in your .bashrc. &amp;amp;nbsp;The installation of parmed in /opt/software/amber14-gpu is broken. instead, you need to use&amp;amp;nbsp;&amp;lt;span style=&amp;quot;font-family: arial, sans-serif; font-size: 12.7272720336914px&amp;quot;&amp;gt;/opt/software/ParmeEd-master/parmed.py&amp;lt;/span&amp;gt;. Prep a parmtop as normal. startparmed by invoking the file parmed.py with the prmtop as a -p command ex. parmed.py -p Myparm.prmtop. Then, invoke HMassRepartition. This adjusts H masses to 3.024 daltons, lowering mass of heavy atoms. Then, to save the resulting .prmtop, invoke &amp;quot;parmout MyNewParm.prmtop&amp;quot;. then invoke go. The resulting prmtop can then be used as input for AMBER simulations using the .inpcrd generated by leap.&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Curves+ =&lt;br /&gt;
&lt;br /&gt;
== Curves+ for analysis of nucleic acid structure ==&lt;br /&gt;
&lt;br /&gt;
Read both user guide and reference&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/curves-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
[https://dx.doi.org/10.1093/nar/gkr316 https://dx.doi.org/10.1093/nar/gkr316]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
 rm r+bdna*.*&lt;br /&gt;
 &lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0&lt;br /&gt;
 1:12&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
 # numbers following namelist variables:&lt;br /&gt;
 # [# strands, up to 4] [#nt in strand 1, negative means 3’ to 5’; if 1, then auto-detected] [#nt in strand 2] …&lt;br /&gt;
 # [nt indices in strand 1, 0 means gap, negative means excluding from axis calculation (for flipped base, the other base must be present, otherwise the base pair should be omitted)]&lt;br /&gt;
 # [nt indices in strand 2]&lt;br /&gt;
 # …&lt;br /&gt;
&lt;br /&gt;
To analyze single strand:&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 1 -1 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 /Users/RL/Code/Cur+ &amp;lt;&amp;lt;!&lt;br /&gt;
 &amp;amp;inp file=1bna, lis=r+bdna,&lt;br /&gt;
 lib=/Users/RL/Code/standard,&lt;br /&gt;
 &amp;amp;end&lt;br /&gt;
 2 1 -1 0 0 0&lt;br /&gt;
 0 0 0 0 0 0 0 0 0 0 0 0&lt;br /&gt;
 24:13&lt;br /&gt;
 !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Trajectory analysis using CANAL ==&lt;br /&gt;
&lt;br /&gt;
[https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html https://bisi.ibcp.fr/tools/curves_plus/canal-user-guide.html]&lt;br /&gt;
&lt;br /&gt;
Works with AMBER coordinate format&lt;br /&gt;
&lt;br /&gt;
Requires strict format for Curves+ output. Only supports duplex as of Version 1.3 February 2015. For modified NA, make sure the number of torsions is the same, and five sugar atoms are defined.&lt;br /&gt;
&lt;br /&gt;
To analyze a single strand, add a dummy strand as in the Curves+ example above.&lt;br /&gt;
&lt;br /&gt;
= Quick steps to run amber or OpenMM GPU =&lt;br /&gt;
&lt;br /&gt;
First, make sure your bashrc has nothing related to mpich, cuda, intel compiler in it. If you need them for specific apps, create a .bashrc.thatapp and source it before running the specific app.&lt;br /&gt;
&lt;br /&gt;
Log into NOVA and then node201, 202, 205, 206, 210, 211, or bme-pluto, saturn or earth&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;&amp;lt;span style=&amp;quot;background-color:#ffd700&amp;quot;&amp;gt;source /usr/local/bash/bashrc.amber or /usr/local/bash/bashrc.openmm&amp;amp;nbsp;&amp;lt;/span&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Source the one with xxxx.970 if you are running on 210, 211, earth.&lt;br /&gt;
&lt;br /&gt;
Nvidia-smi to check which device (card) is available. &amp;amp;nbsp;The unused card has a low temperature &amp;lt; 40 C and less memory usage &amp;lt; 30MB.&lt;br /&gt;
&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0” to chose card 1&lt;br /&gt;
 export CUDA_VISIBLE_DEVICES=“0,1” to choose both card 1 and 2 (only amber can use 2 cards in parallel for one simulation; don’t ever use 3)&lt;br /&gt;
&lt;br /&gt;
Then run your amber or open simulation. You can check the examples for amber (only root can actually run this): /opt/software/amber14-gpu/test/cuda/dhfr/Run.dhfr.ntb2_ntt1.my, and you will see the actual pmemd command is&lt;br /&gt;
&lt;br /&gt;
 &amp;quot;/opt/software/amber14-gpu-970/bin/pmemd.cuda.MPI” &lt;br /&gt;
&lt;br /&gt;
Everything else is the same as regular amber.&lt;br /&gt;
&lt;br /&gt;
Examples for openmm is in /home/pren/OpenMM/zzz/simulateMTS.py.&lt;br /&gt;
&lt;br /&gt;
More tips to run these fast, such as using 4fs time-step, write files/log as infrequent as possible, avoid pressure control etc can be found here: [http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can http://biomol.bme.utexas.edu/wiki/index.php/Software:links#Tips_to_run_amber_GPU_as_fast_as_you_can]&lt;br /&gt;
&lt;br /&gt;
= Simulaiton analysis with LOOS =&lt;br /&gt;
&lt;br /&gt;
LOOS by Alan Gorssfield.&lt;br /&gt;
&lt;br /&gt;
*Work with gromacs, amber, CHARMM and tinker trajectory. &lt;br /&gt;
*Compute various properties for you from the trajectory &lt;br /&gt;
*Just added native contact fraction calculation upon our request (the first frame define native) &lt;br /&gt;
*LOOS document: [http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html http://membrane.urmc.rochester.edu/Software/LOOS/Docs/main.html] &lt;br /&gt;
*Download the loos [http://sourceforge.net/projects/loos/ http://sourceforge.net/projects/loos/] &lt;br /&gt;
*Download the native contact routine [http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp http://biomol.bme.utexas.edu/~pren/down2009/native_contacts.cpp] &lt;br /&gt;
&lt;br /&gt;
To use the native_contact.cpp&lt;br /&gt;
&lt;br /&gt;
Here&#039;s what you need to do to build it:&lt;br /&gt;
&lt;br /&gt;
1) Download the newest LOOS from loos.sourceforge.net&lt;br /&gt;
&lt;br /&gt;
2) Unpack and build it. If you don&#039;t already have them installed, you&#039;ll need boost (and boost-devel, if it exists on your distribution), atlas, and scons installed. They should be readily available as packages for most majors linuxes. If I recall correctly, Ubuntu breaks boost into many small packages -- if so, install all of them.&lt;br /&gt;
&lt;br /&gt;
3) Copy native_contacts.cpp into the Tools subdirectory of LOOS.&lt;br /&gt;
&lt;br /&gt;
4) Edit Tools/SConscript, which is actually just a python script. You&#039;ll see a series of lines that create a variable called apps. Edit the last one, and append &amp;quot; native_contacts&amp;quot; to it.&lt;br /&gt;
&lt;br /&gt;
5) cd to the main LOOS directory, and say &amp;quot;scons&amp;quot; (or scons -j4 if you&#039;ve got a 4 core machine). This will build LOOS, and will build native_contacts in the Tools directory.&lt;br /&gt;
&lt;br /&gt;
6) If you want, say &amp;quot;scons install&amp;quot; -- this will create an installed copy, by default in /opt/loos (you can edit this by modifying the custom.py file in the main loos directory.&lt;br /&gt;
&lt;br /&gt;
1) I didn&#039;t do a huge amount of checking on it -- I wrote it, ran a couple of quick tests, and sent it along. Don&#039;t hesitate to contact me if you&#039;re having trouble making sense of it.&lt;br /&gt;
&lt;br /&gt;
2) The way it&#039;s written, native_contacts takes a selection (for instance, you could specify the protein, but only include core residues), breaks it into pieces by residue, and computes the contacts between the centers of mass of the residues. So, if you want the whole thing, you&#039;d just select the protein. If you wanted alpha carbons, you&#039;d do something like&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp; name == &amp;quot;CA&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Beta carbons would look very similar. If you wanted to exclude backbone, something like this would work (I haven&#039;t tested it)&lt;br /&gt;
&lt;br /&gt;
 segid == &amp;quot;PROT&amp;quot; &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The above assumes you&#039;re using a package that has segid&#039;s -- Amber doesn&#039;t, so you&#039;d have to specify a range of residue numbers instead, eg&lt;br /&gt;
&lt;br /&gt;
 resid &amp;gt;= 3 &amp;amp;&amp;amp; resid &amp;lt;=45  &amp;amp;&amp;amp;&amp;amp;nbsp;!(name =~ &amp;quot;^(C|O|CA|N)$&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the LOOS docs, in particular the page about the selection language, for more hints.&lt;br /&gt;
&lt;br /&gt;
*can LOOS directly work on AMBER mdcrd &lt;br /&gt;
&lt;br /&gt;
As for the latter question, yes, it&#039;ll work directly on the amber trajectory. If you just run it (say &amp;quot;native_contacts&amp;quot;) it&#039;ll list the command line arguments it wants. The &amp;quot;system&amp;quot; description should be a pdb file, or an amber parmtop, or a charmm/namd psf. PDB is fine, as long as it has the same atoms (in the same order). That&#039;s where LOOS will get the meta-data (atom name, residue name and number, etc). Depending on what format you use, there may or may not be coordinates -- psfs don&#039;t have them, for example, and parmtops don&#039;t either (although the code will automatically look for an accompanying inpcrd file, which does).&lt;br /&gt;
&lt;br /&gt;
For the next option (trajectory), it takes the name of the trajectory file, which it identifies based on the filename. Amusingly, you can mix and match packages (eg charmm psf with amber mdcrd).&lt;br /&gt;
&lt;br /&gt;
= Quantum Mechanics =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Psi4&#039;&#039;&#039; ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;** please see Chengwen&#039;s tutorial for using psi4&amp;amp;nbsp;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The latest version of Psi4 has been installed at /users/mh43854/bin/psi4updated. Installation required the latest gcc. To use, you need the following environemental variables( for bash). executable is &#039;&#039;&#039;/users/mh43854/bin/psi4updated/bin/psi4&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
export PYTHONPATH=/users/mh43854/bin/psi4updated/lib:$PYTHONPATH&amp;lt;br/&amp;gt; export LD_LIBRARY_PATH=/users/mh43854/gcc/lib64:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
Installation of GCC:&lt;br /&gt;
&lt;br /&gt;
I installed 4.9.4( download info is available at [http://www.gnu.org/prep/ftp.html http://www.gnu.org/prep/ftp.html]) at ~mh43854/gcc. To add prerequisites to the build, run &amp;lt;tt class=&amp;quot;backtick&amp;quot;&amp;gt;./contrib/download_prerequisites. &#039;&#039;mkdir&#039;&#039;&amp;lt;/tt&amp;gt;&#039;&#039;objdir&#039;&#039;. cd into objdir and run &#039;&#039;/gcc-4.9.4/configure --prefix= /path/to/install/dir/&#039;&#039;. make and then make install. This will take a long time.&lt;br /&gt;
&lt;br /&gt;
==Q-chem 6==&lt;br /&gt;
===Run===&lt;br /&gt;
Can be used on any nodes.&lt;br /&gt;
&lt;br /&gt;
Make sure no early version of qchem env sourcing in .cshrc or .bashrc:&lt;br /&gt;
&lt;br /&gt;
For csh, source the follow:&lt;br /&gt;
  source /opt/qchem/6/qcenv.csh&lt;br /&gt;
For bash: &lt;br /&gt;
  source /opt/qchem/6/qcenv.sh&lt;br /&gt;
&lt;br /&gt;
To run jobs (using 8 threads)&lt;br /&gt;
 qchem -nt 8 water.in water.out &amp;amp;&lt;br /&gt;
&lt;br /&gt;
Example of input in &lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/water&lt;br /&gt;
 /home/pren/QuantumMechanics/qchem/&lt;br /&gt;
===Install===&lt;br /&gt;
Flexnext came with qc.tar already&lt;br /&gt;
&lt;br /&gt;
In rc.local, add: &lt;br /&gt;
 /opt/qchem/6/bin/flexnet/lmgrd -l +/var/log/qchemlm.log  -c /opt/qchem/6/qcaux/license/&lt;br /&gt;
&lt;br /&gt;
The qcaux/license has two license files&lt;br /&gt;
 qchem.lic  qchem_UKVU_demo.lic&lt;br /&gt;
Change this_server in the above to bme-nova.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
Edit  the 2nd lic file (sent by q-chem)&lt;br /&gt;
 SERVER bme-nova.bme.utexas.edu b083fee3ba06&lt;br /&gt;
 VENDOR qchemlm  OPTIONS=/opt/qchem/etc/qchemlm.opt&lt;br /&gt;
&lt;br /&gt;
mkdir /opt/qchem/etc/, add qchemlm.opt (may need copy the qchemlm from bin/flexnet here, may not):&lt;br /&gt;
&lt;br /&gt;
 GROUP qchemusers pren zj2244 eew947 cda923 liuchw&lt;br /&gt;
 INCLUDE QCHEM GROUP qchemusers&lt;br /&gt;
&lt;br /&gt;
== Q-Chem 5 ==&lt;br /&gt;
2023: node34 still can run qchem&lt;br /&gt;
example job: /home/pren/QuantumMechanics/qchem/water/run&lt;br /&gt;
&amp;quot;run watera5z&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/501/qcenv.csh&lt;br /&gt;
 #setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
2017/7 Qchem 5 is now available on:&lt;br /&gt;
&lt;br /&gt;
 node40&lt;br /&gt;
 node41&lt;br /&gt;
 node42&lt;br /&gt;
 node142&lt;br /&gt;
 node38&lt;br /&gt;
&lt;br /&gt;
Need these lines in your source if you use csh (change if you bash)&lt;br /&gt;
&lt;br /&gt;
 setenv QCSCRATCH /opt/scratch/qchemscratch&lt;br /&gt;
 setenv QCLOCALSCR /scratch/qchemscratch&lt;br /&gt;
 setenv QCMPI mpich&lt;br /&gt;
 source /opt/qchem/5/qcenv.csh&lt;br /&gt;
 setenv LD_LIBRARY_PATH /usr/lib64/openmpi-1.10/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&lt;br /&gt;
== Qchem Q-chem 4.1 ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;8/1/2016 See Qchem under tutorial. Qchem (4.2) can be run on the following nodes (all cores):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;strike&amp;gt;node50-57, 8 cores each, 7GB mem&amp;lt;/strike&amp;gt;&lt;br /&gt;
 node35&lt;br /&gt;
 node36&lt;br /&gt;
 node37&lt;br /&gt;
 node38&lt;br /&gt;
 genome&lt;br /&gt;
&lt;br /&gt;
8/17/2013&lt;br /&gt;
&lt;br /&gt;
License email: [[Software:License#qchem|license from qchem]]&lt;br /&gt;
&lt;br /&gt;
Installed the serial and multiple-core version (not MPI yet, available if needed) in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To run qchem, see [[Software:Tutorials#qchem|tutorials]]. Below is the printout after installation. Note that there are few env (crutches) needed to be defined.&lt;br /&gt;
&lt;br /&gt;
  To run Q-Chem calculations simply source the setup script below.&lt;br /&gt;
                                                              &lt;br /&gt;
 [tcsh/csh]                                                      &lt;br /&gt;
 source /opt/qchem/4.1/qcenv.csh                          &lt;br /&gt;
                                                              &lt;br /&gt;
 [bash]                                                          &lt;br /&gt;
 . /opt/qchem/4.1/qcenv.sh                                &lt;br /&gt;
                                                              &lt;br /&gt;
 You can put the above lines in your shell startup script        &lt;br /&gt;
 ~/.cshrc for tcsh/csh or ~/.bashrc for bash.                    &lt;br /&gt;
                                                              &lt;br /&gt;
 To get the latest Q-Chem updates please run                     &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcupdate.sh                               &lt;br /&gt;
                                                              &lt;br /&gt;
 To regenerate license data please run                           &lt;br /&gt;
                                                              &lt;br /&gt;
 /opt/qchem/4.1/qcinstall.sh --update-lic        &lt;br /&gt;
&lt;br /&gt;
Installation files are in /opt/qchem/4.1&lt;br /&gt;
&lt;br /&gt;
To generate licesen for nodes (/opt/qchem/4.1/install-file/lincese_nodes), run&lt;br /&gt;
&lt;br /&gt;
  export QC=/opt/qchem/4.1&lt;br /&gt;
 $QC/bin/license_info &amp;lt;file_for_output&amp;gt; license@q-chem.com&lt;br /&gt;
&lt;br /&gt;
Give the nodes file. Mail the output file to&lt;br /&gt;
&lt;br /&gt;
== Q-Chem ==&lt;br /&gt;
&lt;br /&gt;
Version 4.0 is located in /work/opt/qchem4.0/.&lt;br /&gt;
&lt;br /&gt;
Version 3.2 is located in /opt/qchem-para.&lt;br /&gt;
&lt;br /&gt;
From: Zhen Xia &amp;lt;zhenxia@mail.utexas.edu&amp;gt; Date: Monday, February 27, 2012 1:53 PM To: Daniel Dykstra &amp;lt;dnl.dykstra@gmail.com&amp;gt;, Mike Schneiders &amp;lt;michael.schnieders@gmail.com&amp;gt;, Yue Shi &amp;lt;shiyue8638@gmail.com&amp;gt;, mu xiaojia &amp;lt;muxiaojia2010@gmail.com&amp;gt;, Qiantao Wang &amp;lt;qiantao.wang@gmail.com&amp;gt;, Gaurav Chattree &amp;lt;Gaurav.Chattree@mail.utexas.edu&amp;gt; Cc: Pengyu Ren &amp;lt;pren@mail.utexas.edu&amp;gt; Subject: Q-Chem update to 4.0 version&lt;br /&gt;
&lt;br /&gt;
HI, everyone,&lt;br /&gt;
&lt;br /&gt;
I’m glad to tell you that the Q-Chem software has been updated to 4.0 version. The new features of 4.0 version can be seen at: [http://www.q-chem.com/ http://www.q-chem.com/]. To use Q-Chem 4.0, please add the following paths to your shell profiles. An example of bash shell is looks like:&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;#QCHEM &amp;amp;nbsp; &amp;amp;nbsp;#qchem&lt;br /&gt;
&amp;lt;div&amp;gt;QC=/work/opt/qchem4.0&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QC &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export OMP_NUM_THREADS=1&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCAUX=$QC/aux;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCAUX &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCPLATFORM=LINUX_Ix86_64;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCPLATFORM&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;QCSCRATCH=/opt/scratch/qchemscratch; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCSCRATCH &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCLOCALSCR=/scratch&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCMPI=mpich&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export QCRSH=/usr/bin/ssh&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PBS_NODEFILE=/home/pren/qchemnode&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;noclobber=&amp;quot;&amp;quot; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;export PATH=/work/opt/qchem4.0/bin/:$PATH&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;if [ -e $QC/bin/qchem.setup.sh ] &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; then &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;$QC/bin/qchem.setup.sh &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp; &amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div&amp;gt;fi &amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
Please let me know if you have any questions.&lt;br /&gt;
&lt;br /&gt;
Cheers, Zhen&lt;br /&gt;
&lt;br /&gt;
== Spartan ==&lt;br /&gt;
&lt;br /&gt;
Update: Spartan 08 is installed on water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt; Bme-nova now has the QM package Spartan 06 (will update to 08 soon). A useful feature is RI-MP2 method, which is much more efficient than canonical MP2 for large molecules. We have 8 license for backend jobs but only one license for GUI. You can start the GUI by typing “spartan” (locally at bme-nova or ssh –X bme-nova from your own workstation).&lt;br /&gt;
&lt;br /&gt;
A manual is available at /opt/software/spartan06.129_26_int9e/Spartan06Manual.pdf.&lt;br /&gt;
&lt;br /&gt;
You can set up and submit jobs using the GUI and then exit (to free the license for others).&lt;br /&gt;
&lt;br /&gt;
== ORCA ==&lt;br /&gt;
&lt;br /&gt;
Free QM package. Run parallel. Compute CD? [[Research:Orca|orca HOWTO]]&lt;br /&gt;
&lt;br /&gt;
== cadpac ==&lt;br /&gt;
&lt;br /&gt;
[http://www-theor.ch.cam.ac.uk/software/cadpac.html http://www-theor.ch.cam.ac.uk/software/cadpac.html]&lt;br /&gt;
&lt;br /&gt;
== OpenMOPAC ==&lt;br /&gt;
&lt;br /&gt;
 Implement AM1 (stands for Austin Model 1), PM3 and other semiempirical methods (by James Stewart of UT Austin)&lt;br /&gt;
 These methods are also available in G03, GAMESS, etc.&lt;br /&gt;
 How good is SEM multipoles?&lt;br /&gt;
 What is the alternative to Gaussian in derive DMA?&lt;br /&gt;
 [http://www.openmopac.net/background.html http://www.openmopac.net/background.html]&lt;br /&gt;
&lt;br /&gt;
= Job Scheduling =&lt;br /&gt;
&lt;br /&gt;
*[http://gridengine.sunsource.net/ http://gridengine.sunsource.net/] &lt;br /&gt;
*[http://www.clusterresources.com/products/torque-resource-manager.php http://www.clusterresources.com/products/torque-resource-manager.php] &lt;br /&gt;
&lt;br /&gt;
= Docking alternatives: =&lt;br /&gt;
&lt;br /&gt;
== Rxdock: ==&lt;br /&gt;
https://rxdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://rdock.gitlab.io/ &lt;br /&gt;
&lt;br /&gt;
https://www.playmolecule.com/AceDock/&lt;br /&gt;
&lt;br /&gt;
== Autodock family ==&lt;br /&gt;
Autodock Vina (multiple ligands): https://github.com/ccsb-scripps/AutoDock-Vina&lt;br /&gt;
&lt;br /&gt;
ADFR: https://ccsb.scripps.edu/adfr/ &lt;br /&gt;
&lt;br /&gt;
Smina (expt with scoring function): https://sourceforge.net/projects/smina/&lt;br /&gt;
=Gold Docking=&lt;br /&gt;
==2023==&lt;br /&gt;
Vince email has a new activation key&lt;br /&gt;
Download using 771 and this new key: https://www.ccdc.cam.ac.uk/support-and-resources/csdsdownloads/&lt;br /&gt;
Installed on uranus /work2/Software, Can use any nodes.&lt;br /&gt;
&lt;br /&gt;
Before use, need to activate using this new key (search GOLD in Slack):&lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&#039;&#039;&#039;replace /work2/Software by /opt/software/CCDC below&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
Old:&lt;br /&gt;
 /work2/Software/CCDC2023/ccdc-utilities/software-activation/bin/ccdc_activator -a -k xxxx&lt;br /&gt;
&lt;br /&gt;
Run gui to prepare conf file: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/hermes/bin/gold  &lt;br /&gt;
&lt;br /&gt;
Run command line without GUI (may need clean your old GOLD_DIR and  LD_LIBRARY_PATH if you set for/used previous GOLD)&lt;br /&gt;
   /opt/software/CCDC/CCDC2023/ccdc-software/gold/GOLD/bin/gold_auto &lt;br /&gt;
&lt;br /&gt;
Other software, conformer generator, conquest, mercury,....can be found in: &lt;br /&gt;
  /opt/software/CCDC/CCDC2023/ccdc-software/xxx/bin&lt;br /&gt;
Documents for each software&lt;br /&gt;
 /opt/software/CCDC/CCDC2023/ccdc-software/xxx/docs&lt;br /&gt;
&lt;br /&gt;
In addition to /opt/software/CCDC/CCDC2023/, a copy is backed up to /opt/CCDC/CCDC2023/&lt;br /&gt;
&lt;br /&gt;
=2022=&lt;br /&gt;
  &lt;br /&gt;
2022 GOLD CCDC license and download  - installed on bme-uranus. /work2/Software/CCDC2022/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold (GUI license expired as of May 2023)&lt;br /&gt;
&lt;br /&gt;
/work2/Software/CCDC2022/Discovery_2022/bin/gold_auto with .conf file?&lt;br /&gt;
&lt;br /&gt;
 https://utexas.app.box.com/folder/153544625646 (edited) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Updated license info can be found&amp;amp;nbsp;:&#039;&#039;&#039;&lt;br /&gt;
Note updated as of 2022&lt;br /&gt;
[http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html http://legacy.lib.utexas.edu/chem/scifinder/ccdc.html]&lt;br /&gt;
=== &#039;&#039;&#039;2020&#039;&#039;&#039; ===&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;GOLD Tutorial&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Before running GOLD from the command line, it is recommended to follow a tutorial using the graphical interface to gain familarity with how GOLD works.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for docking two ligands into a protein while&amp;amp;nbsp;taking flexibility into consideration is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-Flexibility-Constraints.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
A tutorial for ligand binding pose prediction is located here:&lt;br /&gt;
&lt;br /&gt;
[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD-tutorial-PosePrediction.pdf]&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
Remove old env in your bashrc or cshrc if you have one (so far I don&#039;t think we need it for 2020 version)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Activate&amp;amp;nbsp;GOLD the first time you use it:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator&amp;amp;nbsp;-k&amp;amp;nbsp;570769-C9BD90-4986BB-904E59-D56C9B-025394&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you want to use&amp;amp;nbsp;gradphical interface for activating or setting up GOLD job initially (running job requires no GUI), you need a X grapics on your local computer.&lt;br /&gt;
&lt;br /&gt;
Mac has Xquartz.&amp;amp;nbsp; On windows, use mobaxterm that comes with X (or you can install&amp;amp;nbsp;VcXsrv&amp;amp;nbsp;&amp;amp; use it with ubuntu). Make sure you use &amp;lt;code&amp;gt;ssh -Y&amp;lt;/code&amp;gt;&amp;amp;nbsp;when logging into a node.&lt;br /&gt;
&lt;br /&gt;
You can check that X is working by typing &amp;lt;code&amp;gt;xeyes&amp;lt;/code&amp;gt;&amp;amp;nbsp;and hitting enter. You should get a pair of googly eyes (which may be in another window).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/CSD_2020/bin/ccdc_activator_gui &amp;lt;/code&amp;gt;&amp;amp; enter key from above (&#039;&#039;570769-C9BD90-4986BB-904E59-D56C9B-025394&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running graphical interface (e.g. to generate gold.conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ssh -Y nova&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
then&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bin/gold&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once you set up the job/create the conf file on nova, you can run the job on other nodes (below)&lt;br /&gt;
&lt;br /&gt;
GOLD user guide:&amp;amp;nbsp;[https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf https://www.ccdc.cam.ac.uk/support-and-resources/ccdcresources/GOLD_User_Guide.pdf]&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Running&amp;amp;nbsp;GOLD from the command line (you can use gold.conf above or mannually creat/edit conf)&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/CCDC/CCDC2020/Discovery_2020/bingold_auto gold.conf &amp;amp;&amp;amp;nbsp;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2018 update ===&lt;br /&gt;
&lt;br /&gt;
(installation and activation same as 2016)&lt;br /&gt;
&amp;lt;pre&amp;gt;setenv GOLD_DIR &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD&amp;quot;&lt;br /&gt;
setenv PVM_ROOT &amp;quot;/opt/CCDC2018/GoldSuite_2018/GOLD/pvm3&amp;quot;&lt;br /&gt;
setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&lt;br /&gt;
setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC2018/CSD_2018/csd/csd_license.dat&amp;quot;&lt;br /&gt;
setenv LD_LIBRARY_PATH /opt/CCDC2018/GoldSuite_2018/c_linux-64/lib/:$LD_LIBRARY_PATH&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To activate on a node or WS:&amp;amp;nbsp;/opt/CCDC2018/GoldSuite_2018/bin/gold,&amp;amp;nbsp; Enter site 771,&amp;amp;nbsp;&amp;amp;nbsp;Confirmation Code: 1f9986 and email.&lt;br /&gt;
&lt;br /&gt;
After installation, you may run the GUI (hermes) on workstation such as water.bme.utexas.edu&lt;br /&gt;
&lt;br /&gt;
=== 2016 ===&lt;br /&gt;
&lt;br /&gt;
Installation:&amp;amp;nbsp;/opt/CCDC/installation/csds-linux-x64.run &amp;amp;nbsp;Mannual in /op/CCDC&lt;br /&gt;
&lt;br /&gt;
Activate on a node (e.g. node101) by running /&amp;quot;&#039;opt/CCDC/GoldSuite_2016/bin/gold&amp;quot; (using X windows if you do so remotely). Windows will pop up, asking you to&amp;amp;nbsp;enter the site number (771) and purchase number/confirmation code to register online. This confirmation number changes every spring each year (1f9986&amp;amp;nbsp;for 2018). The code is now available from x-ray lab web site:&amp;amp;nbsp;[https://sites.utexas.edu/chem-x-ray/ https://sites.utexas.edu/chem-x-ray/] (right panel)&lt;br /&gt;
&lt;br /&gt;
Once activated, specify the license file:&amp;amp;nbsp;csd_licence.dat /opt/CCDC//CSD_2016/csd/csd_licence.dat&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
To run:&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv GOLD_DIR &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_ROOT &amp;quot;/opt/CCDC/GoldSuite_2016/GOLD/pvm3&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv PVM_RSH &amp;quot;/usr/bin/ssh&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv CCDC_CSD_LICENCE_FILE &amp;quot;/opt/CCDC/CSD_2016/csd/csd_licence.dat&amp;quot;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;setenv LD_LIBRARY_PATH /opt/CCDC/GoldSuite_2016/c_linux-64/lib/:$LD_LIBRARY_PATH&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then start pvm with a host file (first killall pvmd3 on all nodes you will be using and cleam /tmp/pvm*)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/pvm3/lib/LINUX64/pvmd3 hostfile&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Hostfile looks like this:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Node36.bme.utexas.edu&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Then (assuming gold.conf exists)&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;/opt/CCDC/GoldSuite_2016/GOLD/bin/parallel_gold_auto&amp;amp;nbsp; 16&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You need another gold.hosts file:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node101.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;node36.bme.utexas.edu 8&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;no_of_processes 8&#039;&#039;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;amp;nbsp;Notes from Dave Broadwell&lt;br /&gt;
&amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;CSDS licensing, which GOLD now also uses, is node-based - this means that each individual node that GOLD (or any of the CSD software) is to run on must be registered.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;You installation and registration on one of your cluster nodes has enabled use on that particular node - in order to run on other nodes they similarly will need to be registered. That can be achieved by running one of the programs (other than GOLD itself - you will need to run one of the programs with a GUI such as ConQuest, Mogul or Hermes), or if you need to register multiple nodes and/or need to do so at the command line we can provide a tool to help with that.&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;Once registered then hopefully your PVM use should work. I should note, however, that use of PVM to parallelise GOLD is no no longer our recommended method of doing so and PVM will become deprecated for use with GOLD at some point in a future release. There are some entries in our support database for PVM use - see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=PVM]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;In general, we now recommend use of a system such as univa grid and a script to split GOLD jobs and use the grid&#039;s scheduling system to run them - for an example script see:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine http://www.ccdc.cam.ac.uk/support-and-resources/support/search?q=Grid%20Engine]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;and in particular:&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;&amp;amp;nbsp;&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&#039;&#039;[http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c http://www.ccdc.cam.ac.uk/support-and-resources/support/case/?caseid=b40a45cb-d4a3-4da3-ae72-b7653398895c]&#039;&#039;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;lt;br/&amp;gt; &amp;amp;nbsp;&amp;lt;/div&amp;gt; &amp;lt;div style=&amp;quot;margin-left: 40px&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/div&amp;gt; &lt;br /&gt;
&amp;lt;span style=&amp;quot;background-color: rgb(255, 255, 0)&amp;quot;&amp;gt;You can split the jobs and combine the results by uinsg the script discussed in the link above (Once all the jobs have been launched, a script is generated that may be used to collate all the results once the dockings have completed. )&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= References =&lt;br /&gt;
&lt;br /&gt;
== Endnote ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.endnote.com/support/faqs/Styles/faq5.asp Set up journal abbreviations] &lt;br /&gt;
**[http://www.library.uq.edu.au/endnote/journal_terms.html Updated list of journals]   &lt;br /&gt;
&lt;br /&gt;
== Bibtex ==&lt;br /&gt;
&lt;br /&gt;
*[http://www.bibtex.org/ http://www.bibtex.org/]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>