Homec4science
Diffusion lammps (efficient_neuronet) Browse

lammps/doc/compute_cluster_atom.html
3bbf2592a472efficient_neuronet

Last Change
Raw File

compute_cluster_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 cluster/atom command
</H3>
<P><B>Syntax:</B>
</P>
<PRE>compute ID group-ID cluster/atom cutoff
</PRE>
<UL><LI>ID, group-ID are documented in <A HREF = "compute.html">compute</A> command
<LI>cluster/atom = style name of this compute command
<LI>cutoff = distance within which to label atoms as part of same cluster (distance units)
</UL>
<P><B>Examples:</B>
</P>
<PRE>compute 1 all cluster/atom 1.0
</PRE>
<P><B>Description:</B>
</P>
<P>Define a computation that assigns each atom a cluster ID.
</P>
<P>A cluster is defined as a set of atoms, each of which is within the
cutoff distance from one or more other atoms in the cluster. If an
atom has no neighbors within the cutoff distance, then it is a 1-atom
cluster. The ID of every atom in the cluster will be the smallest
atom ID of any atom in the cluster.
</P>
<P>Only atoms in the compute group are clustered and assigned cluster
IDs. Atoms not in the compute group are assigned a cluster ID = 0.
</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 or to have multiple compute/dump commands, each of a
<I>clsuter/atom</I> style.
</P>
<P>NOTE: If you have a bonded system, then the settings of
<A HREF = "special_bonds.html">special_bonds</A> command can remove pairwise
interactions between atoms in the same bond, angle, or dihedral. This
is the default setting for the <A HREF = "special_bonds.html">special_bonds</A>
command, and means those pairwise interactions do not appear in the
neighbor list. Because this fix uses the neighbor list, it also means
those pairs will not be included when computing the clusters. This
does not apply when using long-range coulomb (<I>coul/long</I>, <I>coul/msm</I>,
<I>coul/wolf</I> or similar. One way to get around this would be to set
special_bond scaling factors to very tiny numbers that are not exactly
zero (e.g. 1.0e-50). Another workaround is to write a dump file, and
use the <A HREF = "rerun.html">rerun</A> command to compute the clusters for
snapshots in the dump file. The rerun script can use a
<A HREF = "special_bonds.html">special_bonds</A> command that includes all pairs in
the neighbor list.
</P>
<P><B>Output info:</B>
</P>
<P>This compute calculates a per-atom vector, which 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 values will be an ID > 0, as explained above.
</P>
<P><B>Restrictions:</B> none
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "compute_coord_atom.html">compute coord/atom</A>
</P>
<P><B>Default:</B> none
</P>
<!-- PAGE BREAK -->
</HTML>
c4science · Help