1
This directory contains instructions for creating a a moltemplate file
2
("oplsaa.lt") containing force-field definitions relevant to the
3
"ethylene+benzene" example. (However, these instructions should work
4
for other molecules too.)
6
First, check and see if there is an "oplsaa_subset.prm" file present.
7
If not, then download this file:
9
http://dasher.wustl.edu/tinker/distribution/params/oplsaa.prm
10
This file is also available here:
11
http://dasher.wustl.edu/ffe/distribution/params/oplsaa.prm
13
and save this file as "oplsaa_subset.prm". Then you must EDIT THIS FILE
14
so that it only contains atom types you plan to have in your simulation
15
(see below for details). Then run the opls_moltemplate.py script this way:
18
python oplsaa_moltemplate.py oplsaa_subset.prm
21
This will create a file named "oplsaa.lt"
22
Look over the newly created "oplsaa.lt" file.
23
Then move this file to wherever you plan to run moltemplate. For example:
27
----- DETAILS: Editing the "oplsaa_subset.prm" file -------
29
Again, before you run "oplsaa_moltemplate.py", you must edit the "oplsaa.prm"
30
file (or "oplsaa_subset.prm file) and eliminate atom types which do not
31
correspond to any of the atoms in your simulation. This means you must
32
look for lines near the beginning of this file which begin with the word "atom"
33
and refer to atom types which appear in the simulation you plan to run. All
34
other lines (beginning with the word "atom") must be deleted or commented out.
35
(Leave the rest of the file alone.)
38
If you were working with ethylene and benzene you would delete every line
39
beginning with the word "atom", except for these four lines:
42
atom 88 47 CM "Alkene H2-C=" 6 12.011 3
43
atom 89 46 HC "Alkene H-C=" 1 1.008 1
45
atom 90 48 CA "Aromatic C" 6 12.011 3
46
atom 91 49 HA "Aromatic H-C" 1 1.008 1
48
Then you are ready to run oplsaa_moltemplate.py on this file.
50
(You can try to delete more irrelevant information, but be careful.
51
It is not necessary, and it is easy to make mistakes.)
54
----- Using the "oplsaa.lt" file -----
56
Once you have created the "oplsaa.lt" file, you can create files (like
57
ethylene.lt) which define molecules that refer to these atom types.
58
Here is an excerpt from "ethyelene.lt":
60
Ethylene inherits OPLSAA {
62
list of atoms goes here ...
64
write('Data Bond List') {
65
list of bonds goes here ...
69
And then run moltemplate.
72
----------- CHARGE: -----------
74
By default, the OPLSAA force-field assigns atom charge according to atom type.
75
When you run moltemplate, it will create a file named "system.in.charges",
76
containing commands like:
78
set type 2 charge -0.42
79
set type 3 charge 0.21
81
(This assumes your main moltemplate file is named "system.lt". If it was
82
named something else, eg "polymer.lt", then the file created by moltemplate
83
will be named "polymer.in.charges".)
85
Include these commands somewhere in your LAMMPS input script
86
(or use the LAMMPS "include" command to load the commands in system.in.charges)
88
Note that the atom numbers (eg "2", "3") in this file will not match the
89
OPLS atom numbers. (Check the output_ttree/ttree_assignments.txt file,
90
created by moltemplate, to see a table of "@atom" type numbers translated
91
from OPLSAA into LAMMPS.)
93
----------- CREDIT -----------
95
If you use these tools and you publish a paper using OPLSAA, please also cite
96
the TINKER program. (Because these examples use the "oplsaa.prm" file which
97
is distributed with TINKER.) I think these are the relevant citations:
99
1) Ponder, J. W., & Richards, F. M. (1987). "An efficient newton‐like method for molecular mechanics energy minimization of large molecules. Journal of Computational Chemistry", 8(7), 1016-1024.
101
2) Ponder, J. W, (2004) "TINKER: Software tools for molecular design", http://dasher.wustl.edu/tinker/
103
-------------------------------
105
Jason Lambert and Andrew Jewett
108
Please email bugs to jewett.aij@gmail.com and jlamber9@gmail.com