Unverified Commit 0f78d025 authored by Evan Pretti's avatar Evan Pretti Committed by GitHub
Browse files

Merge pull request #4916 from epretti/update-charmm-amber-ffs

Add new CHARMM and Amber force fields
parents 2443dcee 94e0853a
...@@ -11,7 +11,7 @@ A First Example ...@@ -11,7 +11,7 @@ A First Example
*************** ***************
Lets begin with our first example of an OpenMM script. It loads a PDB file Lets begin with our first example of an OpenMM script. It loads a PDB file
called :file:`input.pdb` that defines a biomolecular system, parameterizes it using the Amber14 force field and TIP3P-FB water called :file:`input.pdb` that defines a biomolecular system, parameterizes it using the Amber19 force field and TIP3P-FB water
model, energy minimizes it, simulates it for 10,000 steps with a Langevin model, energy minimizes it, simulates it for 10,000 steps with a Langevin
integrator, and saves a snapshot frame to a DCD file called :file:`output.dcd` every 1000 time integrator, and saves a snapshot frame to a DCD file called :file:`output.dcd` every 1000 time
steps. steps.
...@@ -25,7 +25,7 @@ steps. ...@@ -25,7 +25,7 @@ steps.
from sys import stdout from sys import stdout
pdb = PDBFile('input.pdb') pdb = PDBFile('input.pdb')
forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml') forcefield = ForceField('amber19-all.xml', 'amber19/tip3pfb.xml')
system = forcefield.createSystem(pdb.topology, nonbondedMethod=PME, system = forcefield.createSystem(pdb.topology, nonbondedMethod=PME,
nonbondedCutoff=1*nanometer, constraints=HBonds) nonbondedCutoff=1*nanometer, constraints=HBonds)
integrator = LangevinMiddleIntegrator(300*kelvin, 1/picosecond, 0.004*picoseconds) integrator = LangevinMiddleIntegrator(300*kelvin, 1/picosecond, 0.004*picoseconds)
...@@ -87,14 +87,14 @@ Make sure you include the single quotes around the file name. OpenMM also can l ...@@ -87,14 +87,14 @@ Make sure you include the single quotes around the file name. OpenMM also can l
files in the newer PDBx/mmCIF format: just change :class:`PDBFile` to :class:`PDBxFile`. files in the newer PDBx/mmCIF format: just change :class:`PDBFile` to :class:`PDBxFile`.
:: ::
forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml') forcefield = ForceField('amber19-all.xml', 'amber19/tip3pfb.xml')
This line specifies the force field to use for the simulation. Force fields are This line specifies the force field to use for the simulation. Force fields are
defined by XML files. OpenMM includes XML files defining lots of standard force fields (see Section :numref:`force-fields`). defined by XML files. OpenMM includes XML files defining lots of standard force fields (see Section :numref:`force-fields`).
If you find you need to extend the repertoire of force fields available, If you find you need to extend the repertoire of force fields available,
you can find more information on how to create these XML files in Chapter :numref:`creating-force-fields`. you can find more information on how to create these XML files in Chapter :numref:`creating-force-fields`.
In this case we load two of those files: :file:`amber14-all.xml`, which contains the In this case we load two of those files: :file:`amber19-all.xml`, which contains the
Amber14 force field, and :file:`amber14/tip3pfb.xml`, which contains the TIP3P-FB water model. The Amber19 force field, and :file:`amber19/tip3pfb.xml`, which contains the TIP3P-FB water model. The
:class:`ForceField` object is assigned to a variable called :code:`forcefield`\ . :class:`ForceField` object is assigned to a variable called :code:`forcefield`\ .
:: ::
...@@ -456,11 +456,11 @@ the main force field, and possibly a second file to define the water model ...@@ -456,11 +456,11 @@ the main force field, and possibly a second file to define the water model
(either implicit or explicit). For example: (either implicit or explicit). For example:
:: ::
forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml') forcefield = ForceField('amber19-all.xml', 'amber19/tip3pfb.xml')
In some cases, one XML file may load several others. For example, :file:`amber14-all.xml` In some cases, one XML file may load several others. For example, :file:`amber19-all.xml`
is really just a shortcut for loading several different files that together make up is really just a shortcut for loading several different files that together make up
the AMBER14 force field. If you need finer grained control over which parameters the Amber19 force field. If you need finer grained control over which parameters
are loaded, you can instead specify the component files individually. are loaded, you can instead specify the component files individually.
Be aware that some force fields and water models include "extra particles", such Be aware that some force fields and water models include "extra particles", such
...@@ -472,47 +472,45 @@ must first add the extra particles to the :class:`Topology`. See section ...@@ -472,47 +472,45 @@ must first add the extra particles to the :class:`Topology`. See section
The force fields described below are the ones that are bundled with OpenMM. The force fields described below are the ones that are bundled with OpenMM.
Additional force fields are available online at https://github.com/openmm/openmmforcefields. Additional force fields are available online at https://github.com/openmm/openmmforcefields.
Amber14 Amber19
------- -------
The Amber14\ :cite:`Maier2015` force field is made up of various files that define The Amber19 force field is made up of various files that define parameters for
parameters for proteins, DNA, RNA, lipids, water, and ions. proteins, DNA, RNA, water, and ions.
.. tabularcolumns:: |l|L| .. tabularcolumns:: |l|L|
=================================== ============================================ =================================== ===========================================
File Parameters File Parameters
=================================== ============================================ =================================== ===========================================
:file:`amber14/protein.ff14SB.xml` Protein (recommended) :file:`amber19/protein.ff19SB.xml` Protein\ :cite:`Tian2020` (recommended, includes residue-specific CMAP terms)
:file:`amber14/protein.ff15ipq.xml` Protein (alternative) :file:`amber19/protein.ff19ipq.xml` Protein (alternative)
:file:`amber14/DNA.OL15.xml` DNA (recommended) :file:`amber19/DNA.OL21.xml` DNA\ :cite:`Zgarbova2021`
:file:`amber14/DNA.bsc1.xml` DNA (alternative)
:file:`amber14/RNA.OL3.xml` RNA :file:`amber14/RNA.OL3.xml` RNA
:file:`amber14/lipid17.xml` Lipid
:file:`amber14/GLYCAM_06j-1.xml` Carbohydrates and glycosylated proteins\ :cite:`Kirschner2007` :file:`amber14/GLYCAM_06j-1.xml` Carbohydrates and glycosylated proteins\ :cite:`Kirschner2007`
:file:`amber14/tip3p.xml` TIP3P water model\ :cite:`Jorgensen1983` and ions :file:`amber19/tip3p.xml` TIP3P water model\ :cite:`Jorgensen1983` and ions
:file:`amber14/tip3pfb.xml` TIP3P-FB water model\ :cite:`Wang2014` and ions :file:`amber19/tip3pfb.xml` TIP3P-FB water model\ :cite:`Wang2014` and ions
:file:`amber14/tip4pew.xml` TIP4P-Ew water model\ :cite:`Horn2004` and ions :file:`amber19/tip4pew.xml` TIP4P-Ew water model\ :cite:`Horn2004` and ions
:file:`amber14/tip4pfb.xml` TIP4P-FB water model\ :cite:`Wang2014` and ions :file:`amber19/tip4pfb.xml` TIP4P-FB water model\ :cite:`Wang2014` and ions
:file:`amber14/spce.xml` SPC/E water model\ :cite:`Berendsen1987` and ions :file:`amber19/spce.xml` SPC/E water model\ :cite:`Berendsen1987` and ions
:code:`amber14/opc.xml` OPC water model\ :cite:`Izadi2014` and ions :file:`amber19/opc.xml` OPC water model\ :cite:`Izadi2014` and ions
:code:`amber14/opc3.xml` OPC3 water model\ :cite:`Izadi2016` and ions :file:`amber19/opc3.xml` OPC3 water model\ :cite:`Izadi2016` and ions
=================================== ============================================ =================================== ===========================================
As a convenience, the file :file:`amber14-all.xml` can be used as a shortcut to include As a convenience, the file :file:`amber19-all.xml` can be used as a shortcut to
:file:`amber14/protein.ff14SB.xml`, :file:`amber14/DNA.OL15.xml`, :file:`amber14/RNA.OL3.xml`, include :file:`amber19/protein.ff19SB.xml`, :file:`amber19/DNA.OL21.xml`, and
and :file:`amber14/lipid17.xml`. In most cases, you can simply include that file, :file:`amber14/RNA.OL3.xml`. In most cases, you can simply include that file,
plus one of the water models, such as :file:`amber14/tip3pfb.xml` for the TIP3P-FB plus one of the water models, such as :file:`amber19/tip3pfb.xml` for the
water model and ions\ :cite:`Wang2014`: TIP3P-FB water model and ions\ :cite:`Wang2014`:
:: ::
forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml') forcefield = ForceField('amber19-all.xml', 'amber19/tip3pfb.xml')
GLYCAM is not included by default, since it is quite large. If your system contains GLYCAM is not included by default, since it is quite large. If your system contains
carbohydrates, include that file as well: carbohydrates, include that file as well:
:: ::
forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml', 'amber14/GLYCAM_06j-1.xml') forcefield = ForceField('amber19-all.xml', 'amber19/tip3pfb.xml', 'amber14/GLYCAM_06j-1.xml')
Be aware that GLYCAM works somewhat differently from most force fields. It uses Be aware that GLYCAM works somewhat differently from most force fields. It uses
its own nonstandard `naming convention <https://glycam.org/docs/forcefield/glycam-naming-2/index.html>`_ its own nonstandard `naming convention <https://glycam.org/docs/forcefield/glycam-naming-2/index.html>`_
...@@ -520,14 +518,68 @@ for carbohydrates, and requires your input file to follow it. If any residues h ...@@ -520,14 +518,68 @@ for carbohydrates, and requires your input file to follow it. If any residues h
names different from what it expects, GLYCAM will be unable to assign parameters names different from what it expects, GLYCAM will be unable to assign parameters
to them. to them.
.. tip:: The solvent model XML files included under the :file:`amber14/` directory .. tip::
Files in the :code:`amber14` directory are used by the older Amber14 force
field described below, but those also listed in the table above are shared between
the Amber14 and Amber19 force fields and can be used with the files in the
:code:`amber19` directory.
.. tip:: The solvent model XML files included under the :file:`amber19/` directory
include both water *and* ions compatible with that water model, so if you include both water *and* ions compatible with that water model, so if you
mistakenly specify :file:`tip3p.xml` instead of :file:`amber14/tip3p.xml`, mistakenly specify :file:`tip3p.xml` instead of :file:`amber19/tip3p.xml`,
you run the risk of having :class:`ForceField` throw an exception since you run the risk of having :class:`ForceField` throw an exception since
:file:`tip3p.xml` will be missing parameters for ions in your system. :file:`tip3p.xml` will be missing parameters for ions in your system.
.. warning::
The updated Lipid21 lipid force field is not yet supported in this port of
Amber19, as it makes use of Amber features not yet supported in
`ParmEd <https://github.com/parmed/parmed>`_. Amber19 should be preferred
over Amber14 for simulations not requiring a lipid force field, but Amber14
should be used if the Lipid17 force field is desired. Alternatively, to use
Amber19 with Lipid21, you can prepare your system with AmberTools_ before
loading it into OpenMM, as described in Section :numref:`using_amber_files`.
The converted parameter sets come from the `AmberTools 24 release <http://ambermd.org/AmberTools.php>`_
and were converted using the openmmforcefields_ package and `ParmEd <https://github.com/parmed/parmed>`_.
Amber14
-------
Similarly to the Amber19 force field, Amber14\ :cite:`Maier2015` is made up of
various files that define parameters for proteins, DNA, RNA, lipids, water, and
ions. The file :file:`amber14-all.xml` can be used as a shortcut to include
:file:`amber14/protein.ff14SB.xml`, :file:`amber14/DNA.OL15.xml`,
:file:`amber14/RNA.OL3.xml`, and :file:`amber14/lipid17.xml`. The same remarks
for Amber19 regarding water, ions, and GLYCAM apply to Amber14.
.. tabularcolumns:: |l|L|
=================================== ============================================
File Parameters
=================================== ============================================
:file:`amber14/protein.ff14SB.xml` Protein (recommended)
:file:`amber14/protein.ff15ipq.xml` Protein (alternative)
:file:`amber14/DNA.OL15.xml` DNA (recommended)
:file:`amber14/DNA.bsc1.xml` DNA (alternative)
:file:`amber14/RNA.OL3.xml` RNA
:file:`amber14/lipid17.xml` Lipid
:file:`amber14/GLYCAM_06j-1.xml` Carbohydrates and glycosylated proteins\ :cite:`Kirschner2007`
:file:`amber14/tip3p.xml` TIP3P water model\ :cite:`Jorgensen1983` and ions
:file:`amber14/tip3pfb.xml` TIP3P-FB water model\ :cite:`Wang2014` and ions
:file:`amber14/tip4pew.xml` TIP4P-Ew water model\ :cite:`Horn2004` and ions
:file:`amber14/tip4pfb.xml` TIP4P-FB water model\ :cite:`Wang2014` and ions
:file:`amber14/spce.xml` SPC/E water model\ :cite:`Berendsen1987` and ions
:file:`amber14/opc.xml` OPC water model\ :cite:`Izadi2014` and ions
:file:`amber14/opc3.xml` OPC3 water model\ :cite:`Izadi2016` and ions
=================================== ============================================
.. tip::
The XML files for water and ions provided in the :file:`amber14/` directory
are identical to those in the :file:`amber19/` directory. They are provided
in both directories for compatibility and convenience.
The converted parameter sets come from the `AmberTools 17 release <http://ambermd.org/AmberTools.php>`_ The converted parameter sets come from the `AmberTools 17 release <http://ambermd.org/AmberTools.php>`_
and were converted using the `openmmforcefields <https://github.com/openmm/openmmforcefields>`_ package and `ParmEd <https://github.com/parmed/parmed>`_. and were converted using the openmmforcefields_ package and `ParmEd <https://github.com/parmed/parmed>`_.
CHARMM36 CHARMM36
-------- --------
...@@ -541,7 +593,7 @@ for full references). ...@@ -541,7 +593,7 @@ for full references).
================================= ============================================ ================================= ============================================
File Parameters File Parameters
================================= ============================================ ================================= ============================================
:file:`charmm36.xml` Protein, DNA, RNA, lipids, carbohydrates, and small molecules :file:`charmm36_2024.xml` Protein, DNA, RNA, lipids, carbohydrates, and small molecules
:file:`charmm36/water.xml` Default CHARMM water model (a modified version of TIP3P\ :cite:`Jorgensen1983`) and ions :file:`charmm36/water.xml` Default CHARMM water model (a modified version of TIP3P\ :cite:`Jorgensen1983`) and ions
:file:`charmm36/spce.xml` SPC/E water model\ :cite:`Berendsen1987` and ions :file:`charmm36/spce.xml` SPC/E water model\ :cite:`Berendsen1987` and ions
:file:`charmm36/tip3p-pme-b.xml` TIP3P-PME-B water model\ :cite:`Price2004` and ions :file:`charmm36/tip3p-pme-b.xml` TIP3P-PME-B water model\ :cite:`Price2004` and ions
...@@ -552,19 +604,13 @@ File Parameters ...@@ -552,19 +604,13 @@ File Parameters
:file:`charmm36/tip5pew.xml` TIP5P-Ew water model\ :cite:`Rick2004` and ions :file:`charmm36/tip5pew.xml` TIP5P-Ew water model\ :cite:`Rick2004` and ions
================================= ============================================ ================================= ============================================
The file :file:`charmm36.xml` bundles everything but the water and ions into a single The file :file:`charmm36_2024.xml` bundles everything but the water and ions into a single
file. In most cases, you can simply include that file, plus one of the water models, file. In most cases, you can simply include that file, plus one of the water models,
such as :file:`charmm36/water.xml`, which specifies the default CHARMM water model such as :file:`charmm36/water.xml`, which specifies the default CHARMM water model
(a modified version of TIP3P\ :cite:`Jorgensen1983`) and ions: (a modified version of TIP3P\ :cite:`Jorgensen1983`) and ions:
:: ::
forcefield = ForceField('charmm36.xml', 'charmm36/water.xml') forcefield = ForceField('charmm36_2024.xml', 'charmm36/water.xml')
.. warning:: Drude polarizable sites and lone pairs are not yet supported
by `ParmEd <https://github.com/parmed/parmed>`_ and the CHARMM36 forcefields
that depend on these features are not included in this port.
To use the CHARMM 2019 polarizable force field\ :cite:`Lopes2013`,
include the single file :file:`charmm_polar_2019.xml`.
.. tip:: The solvent model XML files included under the :file:`charmm36/` directory .. tip:: The solvent model XML files included under the :file:`charmm36/` directory
include both water *and* ions compatible with that water model, so if you include both water *and* ions compatible with that water model, so if you
...@@ -595,8 +641,18 @@ such as :file:`charmm36/water.xml`, which specifies the default CHARMM water mod ...@@ -595,8 +641,18 @@ such as :file:`charmm36/water.xml`, which specifies the default CHARMM water mod
`CHARMM-GUI <http://charmm-gui.org/>`_, it's easiest to load `CHARMM-GUI <http://charmm-gui.org/>`_, it's easiest to load
the PSF file directly, as discussed in Section :numref:`using-charmm-files`. the PSF file directly, as discussed in Section :numref:`using-charmm-files`.
The converted parameter sets come from the `CHARMM36 July 2017 update <http://mackerell.umaryland.edu/charmm_ff.shtml>`_ .. warning:: Some residues and patches are not included in this port of
and were converted using the `openmmforcefields <https://github.com/openmm/openmmforcefields>`_ package and `parmed <https://github.com/parmed/parmed>`_. CHARMM36, either due to a lack of support for certain CHARMM
features in `ParmEd <https://github.com/parmed/parmed>`_, or
because they generate a large number of residue-patch combinations,
slowing down parameterization. The openmmforcefields_ package
includes residues and patches not present in this port within
additional force field XML files that can be loaded as needed.
The converted parameter sets come from the
`CHARMM36 July 2024 update <http://mackerell.umaryland.edu/charmm_ff.shtml>`_,
which includes the CHARMM36m protein parameters. They were converted using the
openmmforcefields_ package and `ParmEd <https://github.com/parmed/parmed>`_.
Implicit Solvent Implicit Solvent
---------------- ----------------
...@@ -606,7 +662,7 @@ Born implicit solvent models from AMBER. To use them, include an extra file whe ...@@ -606,7 +662,7 @@ Born implicit solvent models from AMBER. To use them, include an extra file whe
creating the ForceField. For example, creating the ForceField. For example,
:: ::
forcefield = ForceField('amber14-all.xml', 'implicit/gbn2.xml') forcefield = ForceField('amber19-all.xml', 'implicit/gbn2.xml')
.. tabularcolumns:: |l|L| .. tabularcolumns:: |l|L|
...@@ -681,8 +737,8 @@ recommended for most simulations. ...@@ -681,8 +737,8 @@ recommended for most simulations.
CHARMM Polarizable Force Field CHARMM Polarizable Force Field
------------------------------ ------------------------------
To use the CHARMM 2019 polarizable force field\ :cite:`Lopes2013`, include the To use the CHARMM 2023 polarizable force field\ :cite:`Lopes2013`, include the
single file :file:`charmm_polar_2019.xml`. It includes parameters for proteins, lipids, single file :file:`charmm_polar_2023.xml`. It includes parameters for proteins, lipids, carbohydrates,
water, and ions. When using this force field, remember to add extra particles to water, and ions. When using this force field, remember to add extra particles to
the :class:`Topology` as described in section :numref:`adding-or-removing-extra-particles`. the :class:`Topology` as described in section :numref:`adding-or-removing-extra-particles`.
This force field also requires that you use one of the special integrators that This force field also requires that you use one of the special integrators that
...@@ -698,17 +754,19 @@ still useful for reproducing older results. ...@@ -698,17 +754,19 @@ still useful for reproducing older results.
.. tabularcolumns:: |l|L| .. tabularcolumns:: |l|L|
============================= ================================================================================ ============================= ==================================================================================
File Force Field File Force Field
============================= ================================================================================ ============================= ==================================================================================
:code:`amber96.xml` Amber96\ :cite:`Kollman1997` :code:`amber96.xml` Amber96\ :cite:`Kollman1997`
:code:`amber99sb.xml` Amber99\ :cite:`Wang2000` with modified backbone torsions\ :cite:`Hornak2006` :code:`amber99sb.xml` Amber99\ :cite:`Wang2000` with modified backbone torsions\ :cite:`Hornak2006`
:code:`amber99sbildn.xml` Amber99SB plus improved side chain torsions\ :cite:`Lindorff-Larsen2010` :code:`amber99sbildn.xml` Amber99SB plus improved side chain torsions\ :cite:`Lindorff-Larsen2010`
:code:`amber99sbnmr.xml` Amber99SB with modifications to fit NMR data\ :cite:`Li2010` :code:`amber99sbnmr.xml` Amber99SB with modifications to fit NMR data\ :cite:`Li2010`
:code:`amber03.xml` Amber03\ :cite:`Duan2003` :code:`amber03.xml` Amber03\ :cite:`Duan2003`
:code:`amber10.xml` Amber10 (documented in the AmberTools_ manual as `ff10`) :code:`amber10.xml` Amber10 (documented in the AmberTools_ manual as `ff10`)
:code:`charmm36.xml` July 2017 release of the CHARMM36 force field without CHARMM36m protein parameters
:code:`charmm_polar_2013.xml` 2013 version of the CHARMM polarizable force field\ :cite:`Lopes2013` :code:`charmm_polar_2013.xml` 2013 version of the CHARMM polarizable force field\ :cite:`Lopes2013`
============================= ================================================================================ :code:`charmm_polar_2019.xml` 2019 version of the CHARMM polarizable force field\ :cite:`Lopes2013`
============================= ==================================================================================
Several of these force fields support implicit solvent. To enable it, also Several of these force fields support implicit solvent. To enable it, also
include the corresponding OBC file. include the corresponding OBC file.
...@@ -732,7 +790,7 @@ Water Models ...@@ -732,7 +790,7 @@ Water Models
------------ ------------
The following files define popular water models. They can be used with force fields The following files define popular water models. They can be used with force fields
that do not provide their own water models. When using Amber14 or CHARMM36, use that do not provide their own water models. When using Amber19, Amber14 or CHARMM36, use
the water files included with those force fields instead, since they also include the water files included with those force fields instead, since they also include
ion parameters. ion parameters.
......
...@@ -242,7 +242,7 @@ latex_elements = { ...@@ -242,7 +242,7 @@ latex_elements = {
\\captionsetup[figure]{labelformat=empty} \\captionsetup[figure]{labelformat=empty}
% Backwards compatibility for sphinx < 1.5 % Backwards compatibility for sphinx < 1.5
\\let\\DUspan\\null % force DUspan to be defined \\let\\DUspan\\null % force DUspan to be defined
\\renewcommand{\DUspan}[2]{% \\renewcommand{\\DUspan}[2]{%
\\IfEqCase{#1}{% \\IfEqCase{#1}{%
{code}{\\small{}\\texttt{#2}\\normalsize{}} {code}{\\small{}\\texttt{#2}\\normalsize{}}
}[\\PackageError{DUspan}{Unrecognized option passed to DUspan: #1}{}]% }[\\PackageError{DUspan}{Unrecognized option passed to DUspan: #1}{}]%
......
...@@ -717,3 +717,25 @@ ...@@ -717,3 +717,25 @@
doi = {10.1063/1.4960175}, doi = {10.1063/1.4960175},
type = {Journal Article} type = {Journal Article}
} }
@article{Tian2020,
title={ff19SB: Amino-acid-specific protein backbone parameters trained against quantum mechanics energy surfaces in solution},
author={Tian, C. and Kasavajhala, K. and Belfon, K.A.A. and Raguette, L. and Huang, H. and Migues, A.N. and Bickel, J. and Wang, Y. and Pincay, J. and Wu, Q. and Simmerling, C.},
journal={Journal of Chemical Theory and Computation},
volume={16},
pages={528-552},
year={2020},
doi = {10.1021/acs.jctc.9b00591},
type = {Journal Article}
}
@article{Zgarbova2021,
title={Z-DNA as a touchstone for additive empirical force fields and a refinement of the alpha/gamma DNA torsions for AMBER},
author={Zgarbova, M. and Sponer, J. and Jurecka, P.},
journal={Journal of Chemical Theory and Computation},
volume={17},
pages={6292-6301},
year={2021},
doi = {10.1021/acs.jctc.1c00697},
type = {Journal Article}
}
...@@ -4,7 +4,7 @@ from openmm.unit import * ...@@ -4,7 +4,7 @@ from openmm.unit import *
from sys import stdout from sys import stdout
pdb = PDBFile('input.pdb') pdb = PDBFile('input.pdb')
forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml') forcefield = ForceField('amber19-all.xml', 'amber19/tip3pfb.xml')
system = forcefield.createSystem(pdb.topology, nonbondedMethod=PME, nonbondedCutoff=1*nanometer, constraints=HBonds) system = forcefield.createSystem(pdb.topology, nonbondedMethod=PME, nonbondedCutoff=1*nanometer, constraints=HBonds)
integrator = LangevinMiddleIntegrator(300*kelvin, 1/picosecond, 0.004*picoseconds) integrator = LangevinMiddleIntegrator(300*kelvin, 1/picosecond, 0.004*picoseconds)
simulation = Simulation(pdb.topology, system, integrator) simulation = Simulation(pdb.topology, system, integrator)
......
<ForceField>
<Include file="amber19/protein.ff19SB.xml"/>
<Include file="amber19/DNA.OL21.xml"/>
<Include file="amber14/RNA.OL3.xml"/>
</ForceField>
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
...@@ -153,7 +153,7 @@ def buildKeywordDictionary(major_version_num=MAJOR_VERSION_NUM, ...@@ -153,7 +153,7 @@ def buildKeywordDictionary(major_version_num=MAJOR_VERSION_NUM,
"openmm.app.internal.pdbx.writer"] "openmm.app.internal.pdbx.writer"]
setupKeywords["data_files"] = [] setupKeywords["data_files"] = []
setupKeywords["package_data"] = {"openmm" : [], setupKeywords["package_data"] = {"openmm" : [],
"openmm.app" : ['data/*.xml', 'data/*.pdb', 'data/amber14/*.xml', 'data/charmm36/*.xml', 'data/implicit/*.xml'], "openmm.app" : ['data/*.xml', 'data/*.pdb', 'data/amber14/*.xml', 'data/amber19/*.xml', 'data/charmm36/*.xml', 'data/implicit/*.xml'],
"openmm.app.internal" : []} "openmm.app.internal" : []}
setupKeywords["install_requires"] = ["numpy"] setupKeywords["install_requires"] = ["numpy"]
setupKeywords["platforms"] = ["Linux", "Mac OS X", "Windows"] setupKeywords["platforms"] = ["Linux", "Mac OS X", "Windows"]
......
...@@ -1336,7 +1336,7 @@ class TestForceField(unittest.TestCase): ...@@ -1336,7 +1336,7 @@ class TestForceField(unittest.TestCase):
def test_Disulfides(self): def test_Disulfides(self):
"""Test that various force fields handle disulfides correctly.""" """Test that various force fields handle disulfides correctly."""
pdb = PDBFile('systems/bpti.pdb') pdb = PDBFile('systems/bpti.pdb')
for ff in ['amber99sb.xml', 'amber14-all.xml', 'charmm36.xml', 'amberfb15.xml', 'amoeba2013.xml']: for ff in ['amber99sb.xml', 'amber14-all.xml', 'amber19-all.xml', 'charmm36.xml', 'charmm36_2024.xml', 'amberfb15.xml', 'amoeba2013.xml']:
forcefield = ForceField(ff) forcefield = ForceField(ff)
system = forcefield.createSystem(pdb.topology) system = forcefield.createSystem(pdb.topology)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment