<p>Define a computation that calculates properties of individual pairwise
interactions. The number of datums generated, aggregated across all
processors, equals the number of pairwise interactions in the system.</p>
<p>The local data stored by this command is generated by looping over the
pairwise neighbor list. Info about an individual pairwise interaction
will only be included if both atoms in the pair are in the specified
compute group, and if the current pairwise distance is less than the
force cutoff distance for that interaction, as defined by the
<aclass="reference internal"href="pair_style.html"><spanclass="doc">pair_style</span></a> and <aclass="reference internal"href="pair_coeff.html"><spanclass="doc">pair_coeff</span></a>
<p>The value <em>dist</em> will be in distance <aclass="reference internal"href="units.html"><spanclass="doc">units</span></a>. The value
<em>eng</em> will be in energy <aclass="reference internal"href="units.html"><spanclass="doc">units</span></a>. The values <em>force</em>, <em>fx</em>,
<em>fy</em>, and <em>fz</em> will be in force <aclass="reference internal"href="units.html"><spanclass="doc">units</span></a>. The values <em>pN</em>
will be in whatever units the pair style defines.</p>
<p>The optional <em>cutoff</em> keyword determines how the force cutoff distance
for an interaction is determined. For the default setting of <em>type</em>,
the pairwise cutoff defined by the <aclass="reference internal"href="pair_style.html"><spanclass="doc">pair_style</span></a>
command for the types of the two atoms is used. For the <em>radius</em>
setting, the sum of the radii of the two particles is used as a
cutoff. For example, this is appropriate for granular particles which
only interact when they are overlapping, as computed by <aclass="reference external"href="pair_gran.txt">granular pair styles</a>.</p>
<p>Note that as atoms migrate from processor to processor, there will be
no consistent ordering of the entries within the local vector or array
from one timestep to the next. The only consistency that is
guaranteed is that the ordering on a particular timestep will be the
same for local vectors or arrays generated by other compute commands.
For example, pair output from the <aclass="reference internal"href="compute_property_local.html"><spanclass="doc">compute property/local</span></a> command can be combined
with data from this command and output by the <aclass="reference internal"href="dump.html"><spanclass="doc">dump local</span></a>
<pclass="last">For pairs, if two atoms I,J are involved in 1-2, 1-3, 1-4
interactions within the molecular topology, their pairwise interaction
may be turned off, and thus they may not appear in the neighbor list,
and will not be part of the local data created by this command. More
specifically, this will be true of I,J pairs with a weighting factor
of 0.0; pairs with a non-zero weighting factor are included. The
weighting factors for 1-2, 1-3, and 1-4 pairwise interactions are set
by the <aclass="reference internal"href="special_bonds.html"><spanclass="doc">special_bonds</span></a> command. An exception is if
long-range Coulombics are being computed via the
<aclass="reference internal"href="kspace_style.html"><spanclass="doc">kspace_style</span></a> command, then atom pairs with
weighting factors of zero are still included in the neighbor list, so
that a portion of the long-range interaction contribution can be
computed in the pair style. Hence in that case, those atom pairs will
be part of the local data created by this command.</p>
</div>
<p><strong>Output info:</strong></p>
<p>This compute calculates a local vector or local array depending on the
number of keywords. The length of the vector or number of rows in the
array is the number of pairs. If a single keyword is specified, a
local vector is produced. If two or more keywords are specified, a
local array is produced where the number of columns = the number of
keywords. The vector or array can be accessed by any command that
uses local values from a compute as input. See <aclass="reference internal"href="Section_howto.html#howto-15"><spanclass="std std-ref">this section</span></a> for an overview of LAMMPS output
<em>force</em>, <em>fx</em>, <em>fy</em>, and <em>fz</em> will be in force <aclass="reference internal"href="units.html"><spanclass="doc">units</span></a>.
The outpur for <em>pN</em> will be in whatever units the pair style defines.</p>
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>.