jianmu
/
lammps
forked from lijiext/lammps
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

This commit is contained in:
sjplimp 2014-06-11 15:46:45 +00:00
parent c890d390cc
commit aa850fa33a
2 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/run.html
View File

@ -102,13 +102,14 @@ Note that if <I>pre</I> is set to "no" for the very 1st run LAMMPS
performs, then it is overridden, since the initial setup computations
must be done.
</P>
<P>IMPORTANT NOTE: If your input script changes settings between 2 runs
(e.g. adds a <A HREF = "fix.html">fix</A> or <A HREF = "dump.html">dump</A> or
<A HREF = "compute.html">compute</A>, changes a <A HREF = "neigh_modify.html">neighbor</A> list
parameter, writes a restart file which can migrate atoms between
processors), then the initial setup must be performed. LAMMPS has no
easy way to check for this, but it would be an error to use the <I>pre
no</I> option in this case.
<P>IMPORTANT NOTE: If your input script changes the system between 2
runs, then the initial setup must be performed to insure the change is
recognized by all parts of the code that are affected. Examples are
adding a <A HREF = "fix.html">fix</A> or <A HREF = "dump.html">dump</A> or <A HREF = "compute.html">compute</A>,
changing a <A HREF = "neigh_modify.html">neighbor</A> list parameter, or writing
restart file which can migrate atoms between processors. LAMMPS has
no easy way to check if this has happened, but it is an error to use
the <I>pre no</I> option in this case.
</P>
<P>If <I>post</I> is specified as "no", the full timing summary is skipped;
only a one-line summary timing is printed.

15
doc/run.txt
View File

@ -95,13 +95,14 @@ Note that if {pre} is set to "no" for the very 1st run LAMMPS
performs, then it is overridden, since the initial setup computations
must be done.
IMPORTANT NOTE: If your input script changes settings between 2 runs
(e.g. adds a "fix"_fix.html or "dump"_dump.html or
"compute"_compute.html, changes a "neighbor"_neigh_modify.html list
parameter, writes a restart file which can migrate atoms between
processors), then the initial setup must be performed. LAMMPS has no
easy way to check for this, but it would be an error to use the {pre
no} option in this case.
IMPORTANT NOTE: If your input script changes the system between 2
runs, then the initial setup must be performed to insure the change is
recognized by all parts of the code that are affected. Examples are
adding a "fix"_fix.html or "dump"_dump.html or "compute"_compute.html,
changing a "neighbor"_neigh_modify.html list parameter, or writing
restart file which can migrate atoms between processors. LAMMPS has
no easy way to check if this has happened, but it is an error to use
the {pre no} option in this case.
If {post} is specified as "no", the full timing summary is skipped;
only a one-line summary timing is printed.