Homec4science
Diffusion lammps (lammps-icms) Browse

lammps/doc/compute_property_molecule.html
4c1c65eab0f6lammps-icms

Last Change
Raw File

compute_property_molecule.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 property/molecule command
</H3>
<P><B>Syntax:</B>
</P>
<PRE>compute ID group-ID property/molecule input1 input2 ...
</PRE>
<UL><LI>ID, group-ID are documented in <A HREF = "compute.html">compute</A> command
<LI>property/molecule = style name of this compute command
<LI>input = one or more attributes
<PRE> possible attributes = mol
</PRE>
<PRE> mol = molecule ID
</PRE>
</UL>
<P><B>Examples:</B>
</P>
<PRE>compute 1 all property/molecule mol
</PRE>
<P><B>Description:</B>
</P>
<P>Define a computation that stores the specified attributes as global
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.
</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
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>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>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 <A HREF = "compute_bond_local.html">compute
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
<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>.
</P>
<P><B>Output info:</B>
</P>
<P>This compute calculates a global vector or global array depending on
the number of input values. The length of the vector or number of
rows in the array is the number of molecules. If a single input is
specified, a global vector is produced. If two or more inputs are
specified, a global array is produced where the number of columns =
the number of inputs. The vector or array can be accessed by any
command that uses global values from a compute as input. See <A HREF = "Section_howto.html#4_15">this
section</A> for an overview of LAMMPS output
options.
</P>
<P><B>Restrictions:</B> none
</P>
<P><B>Related commands:</B> none
</P>
<P><B>Default:</B> none
</P>
</HTML>
c4science · Help