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

This commit is contained in:
sjplimp 2012-06-18 23:15:48 +00:00
parent a8af5ea42f
commit 63590758f8
8 changed files with 86 additions and 18 deletions

View File

@ -172,6 +172,12 @@ often and see if system energies/trajectories change.
yes</A> option so that velocites are stored by ghost
atoms.
</P>
<P>These pair styles will not restart exactly when using the
<A HREF = "read_restart.html">read_restart</A> command, though they should provide
statistically similar results. This is because the forces they
compute depend on atom velocities. See the
<A HREF = "read_restart.html">read_restart</A> command for more details.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "pair_coeff.html">pair_coeff</A>, <A HREF = "fix_nh.html">fix nvt</A>, <A HREF = "fix_langevin.html">fix

View File

@ -166,6 +166,12 @@ These pair styles requires you to use the "communicate vel
yes"_communicate.html option so that velocites are stored by ghost
atoms.
These pair styles will not restart exactly when using the
"read_restart"_read_restart.html command, though they should provide
statistically similar results. This is because the forces they
compute depend on atom velocities. See the
"read_restart"_read_restart.html command for more details.
[Related commands:]
"pair_coeff"_pair_coeff.html, "fix nvt"_fix_nh.html, "fix

View File

@ -242,6 +242,12 @@ all of this.
yes</A> option so that velocites are stored by ghost
atoms.
</P>
<P>These pair styles will not restart exactly when using the
<A HREF = "read_restart.html">read_restart</A> command, though they should provide
statistically similar results. This is because the forces they
compute depend on atom velocities. See the
<A HREF = "read_restart.html">read_restart</A> command for more details.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "pair_coeff.html">pair_coeff</A>

View File

@ -228,6 +228,12 @@ This pair style requires you to use the "communicate vel
yes"_communicate.html option so that velocites are stored by ghost
atoms.
These pair styles will not restart exactly when using the
"read_restart"_read_restart.html command, though they should provide
statistically similar results. This is because the forces they
compute depend on atom velocities. See the
"read_restart"_read_restart.html command for more details.
[Related commands:]
"pair_coeff"_pair_coeff.html

View File

@ -206,6 +206,12 @@ lubricate.
</P>
<P>Only spherical particles are allowed for pair_style lubricate/poly.
</P>
<P>These pair styles will not restart exactly when using the
<A HREF = "read_restart.html">read_restart</A> command, though they should provide
statistically similar results. This is because the forces they
compute depend on atom velocities. See the
<A HREF = "read_restart.html">read_restart</A> command for more details.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "pair_coeff.html">pair_coeff</A>, <A HREF = "pair_lubricateU.html">pair_style

View File

@ -200,6 +200,12 @@ lubricate.
Only spherical particles are allowed for pair_style lubricate/poly.
These pair styles will not restart exactly when using the
"read_restart"_read_restart.html command, though they should provide
statistically similar results. This is because the forces they
compute depend on atom velocities. See the
"read_restart"_read_restart.html command for more details.
[Related commands:]
"pair_coeff"_pair_coeff.html, "pair_style

View File

@ -33,18 +33,32 @@ stored in a restart file is given below.
</P>
<P>Restart files are saved in binary format to enable exact restarts,
meaning that the trajectories of a restarted run will precisely match
those produced by the original run had it continued on. Several
things can prevent exact restarts due to round-off effects, in which
case the trajectories in the 2 runs will slowly diverge. These
those produced by the original run had it continued on.
</P>
<P>Several things can prevent exact restarts due to round-off effects, in
which case the trajectories in the 2 runs will slowly diverge. These
include running on a different number of processors or changing
certain settings such as those set by the <A HREF = "newton.html">newton</A> or
<A HREF = "processors.html">processors</A> commands. LAMMPS will issue a warning in
these cases. Certain fixes will also not restart exactly, though they
should provide statistically similar results. These include <A HREF = "fix_shake.html">fix
shake</A> and <A HREF = "fix_langevin.html">fix langevin</A>. If a
restarted run is immediately different than the run which produced the
restart file, it could be a LAMMPS bug, so consider <A HREF = "Section_errors.html#err_2">reporting
it</A> if you think the behavior is wrong.
these cases.
</P>
<P>Certain fixes will not restart exactly, though they should provide
statistically similar results. These include <A HREF = "fix_shake.html">fix
shake</A> and <A HREF = "fix_langevin.html">fix langevin</A>.
</P>
<P>Certain pair styles will not restart exactly, though they should
provide statistically similar results. This is because the forces
they compute depend on atom velocities, which are used at half-step
values every timestep when forces are computed. When a run restarts,
forces are initiall evaluated with a full-step velocity, which is
different than if the run had continued. These pair styles include
<A HREF = "pair_gran.html">granular pair styles</A>, <A HREF = "pair_dpd.html">pair dpd</A>, and
<A HREF = "pair_lubricate.html">pair lubricate</A>.
</P>
<P>If a restarted run is immediately different than the run which
produced the restart file, it could be a LAMMPS bug, so consider
<A HREF = "Section_errors.html#err_2">reporting it</A> if you think the behavior is
wrong.
</P>
<P>Because restart files are binary, they may not be portable to other
machines. They can be converted to ASCII data files using the
@ -132,6 +146,8 @@ criteria including settings made via the
<A HREF = "doc/neigh_modify.html">neigh_modify</A> comand, <A HREF = "dump.html">dump</A> file
output, <A HREF = "region.html">geometric regions</A>, etc.
</P>
<HR>
<P><B>Restrictions:</B> none
</P>
<P><B>Related commands:</B>

View File

@ -30,18 +30,32 @@ stored in a restart file is given below.
Restart files are saved in binary format to enable exact restarts,
meaning that the trajectories of a restarted run will precisely match
those produced by the original run had it continued on. Several
things can prevent exact restarts due to round-off effects, in which
case the trajectories in the 2 runs will slowly diverge. These
those produced by the original run had it continued on.
Several things can prevent exact restarts due to round-off effects, in
which case the trajectories in the 2 runs will slowly diverge. These
include running on a different number of processors or changing
certain settings such as those set by the "newton"_newton.html or
"processors"_processors.html commands. LAMMPS will issue a warning in
these cases. Certain fixes will also not restart exactly, though they
should provide statistically similar results. These include "fix
shake"_fix_shake.html and "fix langevin"_fix_langevin.html. If a
restarted run is immediately different than the run which produced the
restart file, it could be a LAMMPS bug, so consider "reporting
it"_Section_errors.html#err_2 if you think the behavior is wrong.
these cases.
Certain fixes will not restart exactly, though they should provide
statistically similar results. These include "fix
shake"_fix_shake.html and "fix langevin"_fix_langevin.html.
Certain pair styles will not restart exactly, though they should
provide statistically similar results. This is because the forces
they compute depend on atom velocities, which are used at half-step
values every timestep when forces are computed. When a run restarts,
forces are initiall evaluated with a full-step velocity, which is
different than if the run had continued. These pair styles include
"granular pair styles"_pair_gran.html, "pair dpd"_pair_dpd.html, and
"pair lubricate"_pair_lubricate.html.
If a restarted run is immediately different than the run which
produced the restart file, it could be a LAMMPS bug, so consider
"reporting it"_Section_errors.html#err_2 if you think the behavior is
wrong.
Because restart files are binary, they may not be portable to other
machines. They can be converted to ASCII data files using the
@ -129,6 +143,8 @@ criteria including settings made via the
"neigh_modify"_doc/neigh_modify.html comand, "dump"_dump.html file
output, "geometric regions"_region.html, etc.
:line
[Restrictions:] none
[Related commands:]