<spanid="index-0"></span><h1>pair_style coul/cut command<aclass="headerlink"href="#pair-style-coul-cut-command"title="Permalink to this headline">¶</a></h1>
<p>where <em>alpha</em> is the damping parameter, and erc() and erfc() are
error-fuction and complementary error-function terms. This potential
is essentially a short-range, spherically-truncated,
charge-neutralized, shifted, pairwise <em>1/r</em> summation. With a
manipulation of adding and substracting a self term (for i = j) to the
first and second term on the right-hand-side, respectively, and a
small enough <em>alpha</em> damping parameter, the second term shrinks and
the potential becomes a rapidly-converging real-space summation. With
a long enough cutoff and small enough alpha parameter, the energy and
forces calcluated by the Wolf summation method approach those of the
Ewald sum. So it is a means of getting effective long-range
interactions with a short-range potential.</p>
<hrclass="docutils"/>
<p>Style <em>coul/streitz</em> is the Coulomb pair interaction defined as part
of the Streitz-Mintmire potential, as described in <aclass="reference internal"href="#streitz"><span>this paper</span></a>, in which charge distribution about an atom is modeled
as a Slater 1*s* orbital. More details can be found in the referenced
paper. To fully reproduce the published Streitz-Mintmire potential,
which is a variable charge potential, style <em>coul/streitz</em> must be
used with <aclass="reference internal"href="pair_eam.html"><em>pair_style eam/alloy</em></a> (or some other
short-range potential that has been parameterized appropriately) via
the <aclass="reference internal"href="pair_hybrid.html"><em>pair_style hybrid/overlay</em></a> command. Likewise,
charge equilibration must be performed via the <aclass="reference internal"href="fix_qeq.html"><em>fix qeq/slater</em></a> command. For example:</p>
<divclass="highlight-python"><divclass="highlight"><pre>pair_style hybrid/overlay coul/streitz 12.0 wolf 0.31 eam/alloy
pair_coeff * * coul/streitz AlO.streitz Al O
pair_coeff * * eam/alloy AlO.eam.alloy Al O
fix 1 all qeq/slater 1 12.0 1.0e-6 100 coul/streitz
</pre></div>
</div>
<p>The keyword <em>wolf</em> in the coul/streitz command denotes computing
Coulombic interactions via Wolf summation. An additional damping
parameter is required for the Wolf summation, as described for the
coul/wolf potential above. Alternatively, Coulombic interactions can
be computed via an Ewald summation. For example:</p>
<p>Keyword <em>ewald</em> does not need a damping parameter, but a
<aclass="reference internal"href="kspace_style.html"><em>kspace_style</em></a> must be defined, which can be style
<em>ewald</em> or <em>pppm</em>. The Ewald method was used in Streitz and
Mintmire’s original paper, but a Wolf summation offers a speed-up in
some cases.</p>
<p>For the fix qeq/slater command, the <em>qfile</em> can be a filename that
contains QEq parameters as discussed on the <aclass="reference internal"href="fix_qeq.html"><em>fix qeq</em></a>
command doc page. Alternatively <em>qfile</em> can be replaced by
“coul/streitz”, in which case the fix will extract QEq parameters from
the coul/streitz pair style itself.</p>
<p>See the examples/strietz directory for an example input script that
uses the Streitz-Mintmire potential. The potentials directory has the
AlO.eam.alloy and AlO.streitz potential files used by the example.</p>
<p>Note that the Streiz-Mintmire potential is generally used for oxides,
but there is no conceptual problem with extending it to nitrides and
carbides (such as SiC, TiN). Pair coul/strietz used by itself or with
any other pair style such as EAM, MEAM, Tersoff, or LJ in
hybrid/overlay mode. To do this, you would need to provide a
Streitz-Mintmire parameterizaion for the material being modeled.</p>
<hrclass="docutils"/>
<p>Styles <em>coul/long</em> and <em>coul/msm</em> compute the same Coulombic
interactions as style <em>coul/cut</em> except that an additional damping
factor is applied so it can be used in conjunction with the
<aclass="reference internal"href="kspace_style.html"><em>kspace_style</em></a> command and its <em>ewald</em> or <em>pppm</em>
option. The Coulombic cutoff specified for this style means that
pairwise interactions within this distance are computed directly;
interactions outside that distance are computed in reciprocal space.</p>
<p>Style <em>coul/long/cs</em> is identical to <em>coul/long</em> except that a term is
added for the <aclass="reference internal"href="Section_howto.html#howto-25"><span>core/shell model</span></a> to allow
charges on core and shell particles to be separated by r = 0.0.</p>
<p>Styles <em>tip4p/cut</em> and <em>tip4p/long</em> implement the coulomb part of
the TIP4P water model of <aclass="reference internal"href="pair_lj.html#jorgensen"><span>(Jorgensen)</span></a>, which introduces
a massless site located a short distance away from the oxygen atom
along the bisector of the HOH angle. The atomic types of the oxygen and
hydrogen atoms, the bond and angle types for OH and HOH interactions,
and the distance to the massless charge site are specified as
pair_style arguments. Style <em>tip4p/cut</em> uses a global cutoff for
Coulomb interactions; style <em>tip4p/long</em> is for use with a long-range
Coulombic solver (Ewald or PPPM).</p>
<divclass="admonition warning">
<pclass="first admonition-title">Warning</p>
<pclass="last">For each TIP4P water molecule in your system, the atom
IDs for the O and 2 H atoms must be consecutive, with the O atom
first. This is to enable LAMMPS to “find” the 2 H atoms associated
with each O atom. For example, if the atom ID of an O atom in a TIP4P
water molecule is 500, then its 2 H atoms must have IDs 501 and 502.</p>
</div>
<p>See the <aclass="reference internal"href="Section_howto.html#howto-8"><span>howto section</span></a> for more
information on how to use the TIP4P pair styles and lists of
parameters to set. Note that the neighobr list cutoff for Coulomb
interactions is effectively extended by a distance 2*qdist when using
the TIP4P pair style, to account for the offset distance of the
fictitious charges on O atoms in water molecules. Thus it is
typically best in an efficiency sense to use a LJ cutoff >= Coulomb
cutoff + 2*qdist, to shrink the size of the neighbor list. This leads
to slightly larger cost for the long-range calculation, so you can
test the trade-off for your model.</p>
<hrclass="docutils"/>
<p>Note that these potentials are designed to be combined with other pair
potentials via the <aclass="reference internal"href="pair_hybrid.html"><em>pair_style hybrid/overlay</em></a>
command. This is because they have no repulsive core. Hence if they
are used by themselves, there will be no repulsion to keep two
oppositely charged particles from moving arbitrarily close to each
other.</p>
<p>The following coefficients must be defined for each pair of atoms
types via the <aclass="reference internal"href="pair_coeff.html"><em>pair_coeff</em></a> command as in the examples
above, or in the data file or restart files read by the
<aclass="reference internal"href="read_data.html"><em>read_data</em></a> or <aclass="reference internal"href="read_restart.html"><em>read_restart</em></a>
commands, or by mixing as described below:</p>
<ulclass="simple">
<li>cutoff (distance units)</li>
</ul>
<p>For <em>coul/cut</em> and <em>coul/debye</em>, the cutoff coefficient is optional.
If it is not used (as in some of the examples above), the default
global value specified in the pair_style command is used.</p>
<p>For <em>coul/long</em> and <em>coul/msm</em> no cutoff can be specified for an
individual I,J type pair via the pair_coeff command. All type pairs
use the same global Coulombic cutoff specified in the pair_style
command.</p>
<hrclass="docutils"/>
<p>Styles with a <em>cuda</em>, <em>gpu</em>, <em>intel</em>, <em>kk</em>, <em>omp</em>, or <em>opt</em> suffix are
functionally the same as the corresponding style without the suffix.
They have been optimized to run faster, depending on your available
hardware, as discussed in <aclass="reference internal"href="Section_accelerate.html"><em>Section_accelerate</em></a>
of the manual. The accelerated styles take the same arguments and
should produce the same results, except for round-off and precision
issues.</p>
<p>These accelerated styles are part of the USER-CUDA, GPU, USER-INTEL,
KOKKOS, USER-OMP and OPT packages, respectively. They are only
enabled if LAMMPS was built with those packages. See the <aclass="reference internal"href="Section_start.html#start-3"><span>Making LAMMPS</span></a> section for more info.</p>
<p>You can specify the accelerated styles explicitly in your input script
by including their suffix, or you can use the <aclass="reference internal"href="Section_start.html#start-7"><span>-suffix command-line switch</span></a> when you invoke LAMMPS, or you can
use the <aclass="reference internal"href="suffix.html"><em>suffix</em></a> command in your input script.</p>
<p>See <aclass="reference internal"href="Section_accelerate.html"><em>Section_accelerate</em></a> of the manual for
more instructions on how to use the accelerated styles effectively.</p>
<p>For atom type pairs I,J and I != J, the cutoff distance for the
<em>coul/cut</em> style can be mixed. The default mix value is <em>geometric</em>.
See the “pair_modify” command for details.</p>
<p>The <aclass="reference internal"href="pair_modify.html"><em>pair_modify</em></a> shift option is not relevant
for these pair styles.</p>
<p>The <em>coul/long</em> style supports the <aclass="reference internal"href="pair_modify.html"><em>pair_modify</em></a>
table option for tabulation of the short-range portion of the
long-range Coulombic interaction.</p>
<p>These pair styles do not support the <aclass="reference internal"href="pair_modify.html"><em>pair_modify</em></a>
tail option for adding long-range tail corrections to energy and
pressure.</p>
<p>These pair styles write their information to <aclass="reference internal"href="restart.html"><em>binary restart files</em></a>, so pair_style and pair_coeff commands do not need
to be specified in an input script that reads a restart file.</p>
<p>This pair style can only be used via the <em>pair</em> keyword of the
<aclass="reference internal"href="run_style.html"><em>run_style respa</em></a> command. It does not support the
<h2>Restrictions<aclass="headerlink"href="#restrictions"title="Permalink to this headline">¶</a></h2>
<p>The <em>coul/long</em>, <em>coul/msm</em> and <em>tip4p/long</em> styles are part of the
KSPACE package. The <em>coul/long/cs</em> style is part of the CORESHELL
package. They are only enabled if LAMMPS was built with that package
(which it is by default). See the <aclass="reference internal"href="Section_start.html#start-3"><span>Making LAMMPS</span></a> section for more info.</p>
</div>
<divclass="section"id="related-commands">
<h2>Related commands<aclass="headerlink"href="#related-commands"title="Permalink to this headline">¶</a></h2>
Built with <ahref="http://sphinx-doc.org/">Sphinx</a> using a <ahref="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <ahref="https://readthedocs.org">Read the Docs</a>.