Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F74900198
compute_coord_atom.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
Tue, Jul 30, 07:25
Size
3 KB
Mime Type
text/html
Expires
Thu, Aug 1, 07:25 (2 d)
Engine
blob
Format
Raw Data
Handle
19449320
Attached To
rLAMMPS lammps
compute_coord_atom.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 coord/atom command
</H3>
<P><B>
Syntax:
</B>
</P>
<PRE>
compute ID group-ID coord/atom cutoff type1 type2 ...
</PRE>
<UL><LI>
ID, group-ID are documented in
<A
HREF =
"compute.html"
>
compute
</A>
command
<LI>
coord/atom = style name of this compute command
<LI>
cutoff = distance within which to count coordination neighbors (distance units)
<LI>
typeN = atom type for Nth coordination count (see asterisk form below)
</UL>
<P><B>
Examples:
</B>
</P>
<PRE>
compute 1 all coord/atom 2.0
compute 1 all coord/atom 6.0 1 2
compute 1 all coord/atom 6.0 2*4 5*8 *
</PRE>
<P><B>
Description:
</B>
</P>
<P>
Define a computation that calculates one or more coordination numbers
for each atom in a group.
</P>
<P>
A coordination number is defined as the number of neighbor atoms with
specified atom type(s) that are within the specified cutoff distance
from the central atom. Atoms not in the group are included in a
coordination number of atoms in the group.
</P>
<P>
The
<I>
typeN
</I>
keywords allow you to specify which atom types contribute
to each coordination number. One coordination number is computed for
each of the
<I>
typeN
</I>
keywords listed. If no
<I>
typeN
</I>
keywords are
listed, a single coordination number is calculated, which includes
atoms of all types (same as the "*" format, see below).
</P>
<P>
The
<I>
typeN
</I>
keywords can be specified in one of two ways. An explicit
numeric value can be used, as in the 2nd example above. Or a
wild-card asterisk can be used to specify a range of atom types. This
takes the form "*" or "*n" or "n*" or "m*n". If N = the number of
atom types, then an asterisk with no numeric values means all types
from 1 to N. A leading asterisk means all types from 1 to n
(inclusive). A trailing asterisk means all types from n to N
(inclusive). A middle asterisk means all types from m to n
(inclusive).
</P>
<P>
The value of all coordination numbers will be 0.0 for atoms not in the
specified compute group.
</P>
<P>
The neighbor list needed to compute this quantity is constructed each
time the calculation is performed (i.e. each time a snapshot of atoms
is dumped). Thus it can be inefficient to compute/dump this quantity
too frequently.
</P>
<P><B>
Output info:
</B>
</P>
<P>
If single
<I>
type1
</I>
keyword is specified (or if none are specified),
this compute calculates a per-atom vector. If multiple
<I>
typeN
</I>
keywords are specified, this compute calculates a per-atom array, with
N columns. These values can be accessed by any command that uses
per-atom values from a compute as input. See
<A
HREF =
"Section_howto.html#howto_15"
>
Section_howto
15
</A>
for an overview of LAMMPS output
options.
</P>
<P>
The per-atom vector or array values will be a number >= 0.0, as
explained above.
</P>
<P><B>
Restrictions:
</B>
none
</P>
<P><B>
Related commands:
</B>
</P>
<P><A
HREF =
"compute_cluster_atom.html"
>
compute cluster/atom
</A>
</P>
<P><B>
Default:
</B>
none
</P>
</HTML>
Event Timeline
Log In to Comment