Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F91830491
compute_pair_local.html
No One
Temporary
Actions
Download File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Subscribers
None
File Metadata
Details
File Info
Storage
Attached
Created
Thu, Nov 14, 22:33
Size
5 KB
Mime Type
text/html
Expires
Sat, Nov 16, 22:33 (2 d)
Engine
blob
Format
Raw Data
Handle
22300669
Attached To
rLAMMPS lammps
compute_pair_local.html
View Options
<HTML>
<CENTER><A
HREF =
"http://lammps.sandia.gov"
>
LAMMPS WWW Site
</A>
-
<A
HREF =
"Manual.html"
>
LAMMPS Documentation
</A>
-
<A
HREF =
"Section_commands.html#comm"
>
LAMMPS Commands
</A>
</CENTER>
<HR>
<H3>
compute pair/local command
</H3>
<P><B>
Syntax:
</B>
</P>
<PRE>
compute ID group-ID pair/local input1 input2 ...
</PRE>
<UL><LI>
ID, group-ID are documented in
<A
HREF =
"compute.html"
>
compute
</A>
command
<LI>
pair/local = style name of this compute command
<LI>
zero or more keywords may be appended
<LI>
keyword =
<I>
dist
</I>
or
<I>
eng
</I>
or
<I>
force
</I>
or
<I>
fx
</I>
or
<I>
fy
</I>
or
<I>
fz
</I>
or
<I>
fN
</I>
<PRE>
<I>
dist
</I>
= pairwise distance
<I>
eng
</I>
= pairwise energy
<I>
force
</I>
= pairwise force
<I>
fx
</I>
,
<I>
fy
</I>
,
<I>
fz
</I>
= components of pairwise force
<I>
pN
</I>
= pair style specific quantities for allowed N values
</PRE>
</UL>
<P><B>
Examples:
</B>
</P>
<PRE>
compute 1 all pair/local eng
compute 1 all pair/local dist eng force
compute 1 all pair/local dist eng fx fy fz
compute 1 all pair/local dist fx fy fz p1 p2 p3
</PRE>
<P><B>
Description:
</B>
</P>
<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
<A
HREF =
"pair_style.html"
>
pair_style
</A>
and
<A
HREF =
"pair_coeff.html"
>
pair_coeff
</A>
commands.
</P>
<P>
The output
<I>
dist
</I>
is the distance bewteen the pair of atoms.
</P>
<P>
The output
<I>
eng
</I>
is the interaction energy for the pair of atoms.
</P>
<P>
The output
<I>
force
</I>
is the force acting between the pair of atoms,
which is positive for a repulsive force and negative for an attractive
force. The outputs
<I>
fx
</I>
,
<I>
fy
</I>
, and
<I>
fz
</I>
are the xyz components of
<I>
force
</I>
on atom I.
</P>
<P>
A pair style may define additional pairwise quantities which can be
accessed as
<I>
p1
</I>
to
<I>
pN
</I>
, where N is defined by the pair style. Most
pair styles do not define any additional quantities, so N = 0. An
example of ones that do are the
<A
HREF =
"pair_gran.html"
>
granular pair styles
</A>
which calculate the tangential force between two particles and return
its components and magnitude acting on atom I for N = 1,2,3,4. See
individual pair styles for detils.
</P>
<P>
The output
<I>
dist
</I>
will be in distance
<A
HREF =
"units.html"
>
units
</A>
. The output
<I>
eng
</I>
will be in energy
<A
HREF =
"units.html"
>
units
</A>
. The outputs
<I>
force
</I>
,
<I>
fx
</I>
,
<I>
fy
</I>
, and
<I>
fz
</I>
will be in force
<A
HREF =
"units.html"
>
units
</A>
. The output
<I>
pN
</I>
will be in whatever units the pair style defines.
</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
<A
HREF =
"compute_property_local.html"
>
compute
property/local
</A>
command can be combined
with data from this command and output by the
<A
HREF =
"dump.html"
>
dump local
</A>
command in a consistent way.
</P>
<P>
IMPORTANT NOTE: 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
<A
HREF =
"special_bonds.html"
>
special_bonds
</A>
command.
</P>
<P><B>
Output info:
</B>
</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
<A
HREF =
"Section_howto.html#howto_15"
>
this
section
</A>
for an overview of LAMMPS output
options.
</P>
<P>
The output for
<I>
dist
</I>
will be in distance
<A
HREF =
"units.html"
>
units
</A>
. The
output for
<I>
eng
</I>
will be in energy
<A
HREF =
"units.html"
>
units
</A>
. The output for
<I>
force
</I>
will be in force
<A
HREF =
"units.html"
>
units
</A>
.
</P>
<P><B>
Restrictions:
</B>
none
</P>
<P><B>
Related commands:
</B>
</P>
<P><A
HREF =
"dump.html"
>
dump local
</A>
,
<A
HREF =
"compute_property_local.html"
>
compute
property/local
</A>
</P>
<P><B>
Default:
</B>
none
</P>
</HTML>
Event Timeline
Log In to Comment