<p>Define a computation that stores the specified attributes as local
data so it can be accessed by other <aclass="reference internal"href="Section_howto.html#howto-15"><spanclass="std std-ref">output commands</span></a>. If the input attributes refer
to bond information, then the number of datums generated, aggregated
across all processors, equals the number of bonds in the system.
Ditto for pairs, angles, etc.</p>
<p>If multiple attributes are specified then they must all generate the
same amount of information, so that the resulting local array has the
same number of rows for each column. This means that only bond
attributes can be specified together, or angle attributes, etc. Bond
and angle attributes can not be mixed in the same compute
property/local command.</p>
<p>If the inputs are pair attributes, the local data 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. For <em>natom1</em> and <em>natom2</em>, all
atom pairs in the neighbor list are considered (out to the neighbor
cutoff = force cutoff + <aclass="reference internal"href="neighbor.html"><spanclass="doc">neighbor skin</span></a>). For <em>patom1</em>
and <em>patom2</em>, the distance between the atoms must be less than the
force cutoff distance for that pair to be included, 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>
commands.</p>
<p>The optional <em>cutoff</em> keyword determines how the force cutoff distance
for an interaction is determined for the <em>patom1</em> and <em>patom2</em>
attributes. 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>If the inputs are bond, angle, etc attributes, the local data is
generated by looping over all the atoms owned on a processor and
extracting bond, angle, etc info. For bonds, info about an individual
bond will only be included if both atoms in the bond are in the
specified compute group. Likewise for angles, dihedrals, etc.</p>
<p>For bonds and angles, a bonds/angles that have been broken by setting
their bond/angle type to 0 will not be included. Bonds/angles that
have been turned off (see the <aclass="reference internal"href="fix_shake.html"><spanclass="doc">fix shake</span></a> or
<aclass="reference internal"href="delete_bonds.html"><spanclass="doc">delete_bonds</span></a> commands) by setting their bond/angle
type negative are written into the file. This is consistent with the
<aclass="reference internal"href="compute_bond_local.html"><spanclass="doc">compute bond/local</span></a> and <aclass="reference internal"href="compute_angle_local.html"><spanclass="doc">compute angle/local</span></a> commands</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, output from the <aclass="reference internal"href="compute_bond_local.html"><spanclass="doc">compute bond/local</span></a> command can be combined with bond
atom indices from this command and output by the <aclass="reference internal"href="dump.html"><spanclass="doc">dump local</span></a> command in a consistent way.</p>
<p>The <em>natom1</em> and <em>natom2</em>, or <em>patom1</em> and <em>patom2</em> attributes refer
to the atom IDs of the 2 atoms in each pairwise interaction computed
by the <aclass="reference internal"href="pair_style.html"><spanclass="doc">pair_style</span></a> command. The <em>ntype1</em> and
<em>ntype2</em>, or <em>ptype1</em> and <em>ptype2</em> attributes refer to the atom types
of the 2 atoms in each pairwise interaction.</p>
<divclass="admonition note">
<pclass="first admonition-title">Note</p>
<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 may 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.</p>
</div>
<p>The <em>batom1</em> and <em>batom2</em> attributes refer to the atom IDs of the 2
atoms in each <aclass="reference internal"href="bond_style.html"><spanclass="doc">bond</span></a>. The <em>btype</em> attribute refers to
the type of the bond, from 1 to Nbtypes = # of bond types. The number
of bond types is defined in the data file read by the
<p>The attributes that start with “a”, “d”, “i”, refer to similar values
for <aclass="reference internal"href="angle_style.html"><spanclass="doc">angles</span></a>, <aclass="reference internal"href="dihedral_style.html"><spanclass="doc">dihedrals</span></a>, and
<p>This compute calculates a local vector or local array depending on the
number of input values. The length of the vector or number of rows in
the array is the number of bonds, angles, etc. If a single input is
specified, a local vector is produced. If two or more inputs are
specified, a local array is produced where the number of columns = the
number of inputs. 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
options.</p>
<p>The vector or array values will be integers that correspond to the
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>.