Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F91854690
compute_angle_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
Fri, Nov 15, 04:25
Size
3 KB
Mime Type
text/html
Expires
Sun, Nov 17, 04:25 (1 d, 23 h)
Engine
blob
Format
Raw Data
Handle
22334209
Attached To
rLAMMPS lammps
compute_angle_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 angle/local command
</H3>
<P><B>
Syntax:
</B>
</P>
<PRE>
compute ID group-ID angle/local input1 input2 ...
</PRE>
<UL><LI>
ID, group-ID are documented in
<A
HREF =
"compute.html"
>
compute
</A>
command
<LI>
angle/local = style name of this compute command
<LI>
zero or more keywords may be appended
<LI>
keyword =
<I>
theta
</I>
or
<I>
eng
</I>
<PRE>
<I>
theta
</I>
= tabulate angles
<I>
eng
</I>
= tabulate angle energies
</PRE>
</UL>
<P><B>
Examples:
</B>
</P>
<PRE>
compute 1 all angle/local theta
compute 1 all angle/local eng theta
</PRE>
<P><B>
Description:
</B>
</P>
<P>
Define a computation that calculates properties of individual angle
interactions. The number of datums generated, aggregated across all
processors, equals the number of angles in the system.
</P>
<P>
The local data stored by this command is generated by looping over all
the atoms owned on a processor and their angles. An angle will only
be included if all 3 atoms in the angle are in the specified compute
group. Any angles that have been broken (see the
<A
HREF =
"angle_style.html"
>
angle_style
</A>
command) by setting their angle type to
0 are not included. Angles that have been turned off (see the
<A
HREF =
"fix_shake.html"
>
fix
shake
</A>
or
<A
HREF =
"delete_bonds.html"
>
delete_bonds
</A>
commands) by
setting their angle type negative are written into the file, but their
energy will be 0.0.
</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, angle 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><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 angles. 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>
theta
</I>
will be in degrees. The output for
<I>
eng
</I>
will
be in energy
<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