<p>Store the forces on atoms in the group at the point during each
timestep when the fix is invoked, as described below. This is useful
for storing forces before constraints or other boundary conditions are
computed which modify the forces, so that unmodified forces can be
<aclass="reference internal"href="dump.html"><spanclass="doc">written to a dump file</span></a> or accessed by other <aclass="reference internal"href="Section_howto.html#howto-15"><spanclass="std std-ref">output commands</span></a> that use per-atom quantities.</p>
<p>This fix is invoked at the point in the velocity-Verlet timestepping
immediately after <aclass="reference internal"href="pair_style.html"><spanclass="doc">pair</span></a>, <aclass="reference internal"href="bond_style.html"><spanclass="doc">bond</span></a>,
<aclass="reference internal"href="improper_style.html"><spanclass="doc">improper</span></a>, and <aclass="reference internal"href="kspace_style.html"><spanclass="doc">long-range</span></a>
forces have been calculated. It is the point in the timestep when
various fixes that compute constraint forces are calculated and
potentially modify the force on each atom. Examples of such fixes are
<aclass="reference internal"href="fix_shake.html"><spanclass="doc">fix shake</span></a>, <aclass="reference internal"href="fix_wall.html"><spanclass="doc">fix wall</span></a>, and <aclass="reference internal"href="fix_indent.html"><spanclass="doc">fix indent</span></a>.</p>
<divclass="admonition note">
<pclass="first admonition-title">Note</p>
<pclass="last">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>
</div>
<p><strong>Restart, fix_modify, output, run start/stop, minimize info:</strong></p>
<p>No information about this fix is written to <aclass="reference internal"href="restart.html"><spanclass="doc">binary restart files</span></a>. None of the <aclass="reference internal"href="fix_modify.html"><spanclass="doc">fix_modify</span></a> options
are relevant to this fix.</p>
<p>This fix produces a per-atom array which can be accessed by various
<aclass="reference internal"href="Section_howto.html#howto-15"><spanclass="std std-ref">output commands</span></a>. The number of columns
for each atom is 3, and the columns store the x,y,z forces on each
atom. The per-atom values be accessed on any timestep.</p>
<p>No parameter of this fix can be used with the <em>start/stop</em> keywords of
the <aclass="reference internal"href="run.html"><spanclass="doc">run</span></a> command. This fix is not invoked during <aclass="reference internal"href="minimize.html"><spanclass="doc">energy minimization</span></a>.</p>
Built with <ahref="http://sphinx-doc.org/">Sphinx</a> using a <ahref="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <ahref="https://readthedocs.org">Read the Docs</a>.