ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@3603 f3b2605a-c512-4ea7-a41b-209d697bcdaa

Browse Source
This commit is contained in:
sjplimp
2009-12-21 23:01:36 +00:00
parent 9c481bc49b
commit 13a3a1d174
6 changed files with 40 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
doc/compute_property_local.html
View File

@ -21,12 +21,14 @@
<LI>input = one or more attributes
<PRE> possible attributes = batom1 batom2 btype
<PRE> possible attributes = patom1 patom2
batom1 batom2 btype
aatom1 aatom2 aatom3 atype
datom1 datom2 datom3 dtype
iatom1 iatom2 iatom3 itype
</PRE>
<PRE> batom1, batom2 = IDs of 2 atoms in each bond
<PRE> patom1, patom2 = IDs of 2 atoms in each pair
batom1, batom2 = IDs of 2 atoms in each bond
btype = bond type of each bond
aatom1, aatom2, aatom3 = IDs of 3 atoms in each angle
atype = angle type of each angle
@ -49,6 +51,7 @@ data so it can be accessed by other <A HREF = "Section_howto.html#4_15">output
commands</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 input attributes are specified then they must all generate
the same amount of information, so that the resulting local array has
@ -62,6 +65,14 @@ 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>In the case of pairs, 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, 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>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
@ -72,10 +83,10 @@ bond/local</A> command can be combined with bond
atom indices from this command and output by the <A HREF = "dump.html">dump
local</A> command in a consistent way.
</P>
<P>The <I>batom1</I> and <I>batom2</I> attributes refer the atom IDs of the 2 atoms
in each <A HREF = "bond_style.html">bond</A>. The <I>btype</I> 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 <I>batom1</I> and <I>batom2</I> attributes refer to the atom IDs of the 2
atoms in each <A HREF = "bond_style.html">bond</A>. The <I>btype</I> 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
<A HREF = "read_data.html">read_data</A> command. The attributes that start with
"a", "d", "i", refer to similar values for <A HREF = "angle_style.html">angles</A>,
<A HREF = "dihedral_style.html">dihedrals</A>, and <A HREF = "improper_style.html">impropers</A>.