<li><p class="first">zero or more keyword/value pairs may be appended</p>
</li>
<li><p class="first">keyword = <em>mode</em> or <em>cutoff</em> or <em>cutoff/multi</em> or <em>group</em> or <em>vel</em></p>
<pre class="literal-block">
<em>mode</em> value = <em>single</em> or <em>multi</em> = communicate atoms within a single or multiple distances
<em>cutoff</em> value = Rcut (distance units) = communicate atoms from this far away
<em>cutoff/multi</em> type value
type = atom type or type range (supports asterisk notation)
value = Rcut (distance units) = communicate atoms for selected types from this far away
<em>group</em> value = group-ID = only communicate atoms in the group
<em>vel</em> value = <em>yes</em> or <em>no</em> = do or do not communicate velocity info with ghost atoms
</pre>
</li>
</ul>
</div>
<div class="section" id="examples">
<h2>Examples</h2>
<pre class="literal-block">
comm_modify mode multi
comm_modify mode multi group solvent
comm_modift mode multi cutoff/multi 1 10.0 cutoff/multi 2*4 15.0
comm_modify vel yes
comm_modify mode single cutoff 5.0 vel yes
comm_modify cutoff/multi * 0.0
</pre>
</div>
<div class="section" id="description">
<h2>Description</h2>
<p>This command sets parameters that affect the inter-processor
communication of atom information that occurs each timestep as
coordinates and other properties are exchanged between neighboring
processors and stored as properties of ghost atoms.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">These options apply to the currently defined comm style. When
you specify a <a class="reference internal" href="comm_style.html"><span class="doc">comm_style</span></a> command, all communication
settings are restored to their default values, including those
previously reset by a comm_modify command. Thus if your input script
specifies a comm_style command, you should use the comm_modify command
after it.</p>
</div>
<p>The <em>mode</em> keyword determines whether a single or multiple cutoff
distances are used to determine which atoms to communicate.</p>
<p>The default mode is <em>single</em> which means each processor acquires
information for ghost atoms that are within a single distance from its
sub-domain. The distance is by default the maximum of the neighbor
cutoff across all atom type pairs.</p>
<p>For many systems this is an efficient algorithm, but for systems with
widely varying cutoffs for different type pairs, the <em>multi</em> mode can
be faster. In this case, each atom type is assigned its own distance
cutoff for communication purposes, and fewer atoms will be
communicated. See the <a class="reference internal" href="neighbor.html"><span class="doc">neighbor multi</span></a> command for a
neighbor list construction option that may also be beneficial for
simulations of this kind.</p>
<p>The <em>cutoff</em> keyword allows you to extend the ghost cutoff distance
for communication mode <em>single</em>, which is the distance from the borders
of a processor’s sub-domain at which ghost atoms are acquired from other
processors. By default the ghost cutoff = neighbor cutoff = pairwise
force cutoff + neighbor skin. See the <a class="reference internal" href="neighbor.html"><span class="doc">neighbor</span></a> command
for more information about the skin distance. If the specified Rcut is
greater than the neighbor cutoff, then extra ghost atoms will be acquired.
If the provided cutoff is smaller, the provided value will be ignored
and the ghost cutoff is set to the neighbor cutoff. Specifying a
cutoff value of 0.0 will reset any previous value to the default.</p>
<p>The <em>cutoff/multi</em> option is equivalent to <em>cutoff</em>, but applies to
communication mode <em>multi</em> instead. Since in this case the communication
cutoffs are determined per atom type, a type specifier is needed and
cutoff for one or multiple types can be extended. Also ranges of types
using the usual asterisk notation can be given.</p>
<p>These are simulation scenarios in which it may be useful or even
necessary to set a ghost cutoff > neighbor cutoff:</p>
<ul class="simple">
<li>a single polymer chain with bond interactions, but no pairwise interactions</li>
<li>bonded interactions (e.g. dihedrals) extend further than the pairwise cutoff</li>
<li>ghost atoms beyond the pairwise cutoff are needed for some computation</li>
</ul>
<p>In the first scenario, a pairwise potential is not defined. Thus the
pairwise neighbor cutoff will be 0.0. But ghost atoms are still
needed for computing bond, angle, etc interactions between atoms on
different processors, or when the interaction straddles a periodic
boundary.</p>
<p>The appropriate ghost cutoff depends on the <a class="reference internal" href="newton.html"><span class="doc">newton bond</span></a>
setting. For newton bond <em>off</em>, the distance needs to be the furthest
distance between any two atoms in the bond, angle, etc. E.g. the
distance between 1-4 atoms in a dihedral. For newton bond <em>on</em>, the
distance between the central atom in the bond, angle, etc and any
other atom is sufficient. E.g. the distance between 2-4 atoms in a
dihedral.</p>
<p>In the second scenario, a pairwise potential is defined, but its
neighbor cutoff is not sufficiently long enough to enable bond, angle,
etc terms to be computed. As in the previous scenario, an appropriate
ghost cutoff should be set.</p>
<p>In the last scenario, a <a class="reference internal" href="fix.html"><span class="doc">fix</span></a> or <a class="reference internal" href="compute.html"><span class="doc">compute</span></a> or
<a class="reference internal" href="pair_style.html"><span class="doc">pairwise potential</span></a> needs to calculate with ghost
atoms beyond the normal pairwise cutoff for some computation it
performs (e.g. locate neighbors of ghost atoms in a multibody pair
potential). Setting the ghost cutoff appropriately can insure it will
find the needed atoms.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">In these scenarios, if you do not set the ghost cutoff long
enough, and if there is only one processor in a periodic dimension
(e.g. you are running in serial), then LAMMPS may “find” the atom it
is looking for (e.g. the partner atom in a bond), that is on the far
side of the simulation box, across a periodic boundary. This will
typically lead to bad dynamics (i.e. the bond length is now the
simulation box length). To detect if this is happening, see the
Built with <a href="http://sphinx-doc.org/">Sphinx</a> using a <a href="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>.