ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@3614 f3b2605a-c512-4ea7-a41b-209d697bcdaa

Browse Source
This commit is contained in:
sjplimp
2009-12-22 01:14:57 +00:00
parent 2aa5636d76
commit c32e4b0b0b
3 changed files with 27 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/fix_store_force.html
View File

@ -41,14 +41,15 @@ potentially modify the force on each atom. Examples of such fixes are
<A HREF = "fix_shake.html">fix shake</A>, <A HREF = "fix_wall.html">fix wall</A>, and <A HREF = "fix_indent.html">fix
indent</A>.
</P>
<P>IMPORTANT NOTE: The order in which the various fixes, including this
one, which operate at the same point during the timestep is the same
as the order they are specified in the input script. Thus normally,
if you want to store per-atom forces due to force field interactions,
before constraints are applied, you should list this fix first, before
other fixes that apply constraints. However, if you wish to include
certain constraints (e.g. fix shake) in the stored force, then it
could be specified after some fixes and before others.
<P>IMPORTANT NOTE: The order in which various fixes are applied which
operate at the same point during the timestep, is the same as the
order they are specified in the input script. Thus normally, if you
want to store per-atom forces due to force field interactions, before
constraints are applied, you should list this fix first within that
set of fixes, i.e. before other fixes that apply constraints.
However, if you wish to include certain constraints (e.g. fix shake)
in the stored force, then it could be specified after some fixes and
before others.
</P>
<P><B>Restart, fix_modify, output, run start/stop, minimize info:</B>
</P>