forked from lijiext/lammps
Added a statement to fix_rigid docs encouraging users to not use this fix when they want atoms to remain stationary.
git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@275 f3b2605a-c512-4ea7-a41b-209d697bcdaa
This commit is contained in:
parent
8ed88c02de
commit
42ed49dcfe
|
@ -97,6 +97,11 @@ boundary, the input data file must define the image flags for each
|
|||
atom correctly, so that LAMMPS can "unwrap" the atoms into a valid
|
||||
rigid body.
|
||||
</P>
|
||||
<P>Do not use this fix if you just want a group of atoms to remain
|
||||
stationary. A much better way to do this is to not include those atoms
|
||||
in your integration fix (i.e. use "fix 1 mobile nve" instead of "fix 1
|
||||
all nve", where "mobile" is the group of atoms that you want to move).
|
||||
</P>
|
||||
<P><B>Related commands:</B>
|
||||
</P>
|
||||
<P><A HREF = "delete_bonds.html">delete_bonds</A>, <A HREF = "neigh_modify.html">neigh_modify</A>
|
||||
|
|
|
@ -90,6 +90,11 @@ boundary, the input data file must define the image flags for each
|
|||
atom correctly, so that LAMMPS can "unwrap" the atoms into a valid
|
||||
rigid body.
|
||||
|
||||
Do not use this fix if you just want a group of atoms to remain
|
||||
stationary. A much better way to do this is to not include those atoms
|
||||
in your integration fix (i.e. use "fix 1 mobile nve" instead of "fix 1
|
||||
all nve", where "mobile" is the group of atoms that you want to move).
|
||||
|
||||
[Related commands:]
|
||||
|
||||
"delete_bonds"_delete_bonds.html, "neigh_modify"_neigh_modify.html
|
||||
|
|
Loading…
Reference in New Issue