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@11847 f3b2605a-c512-4ea7-a41b-209d697bcdaa

Browse Source
This commit is contained in:
sjplimp
2014-04-30 15:17:18 +00:00
parent 2cf0a3bafa
commit 2376ea9cb3
4 changed files with 29 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
doc/rerun.txt
View File

@ -109,17 +109,21 @@ every Nth snapshot is read, where N = {Nskip}. E.g. if {Nskip} = 3,
then only 1 out of every 3 snapshots is read, assuming the snapshot
timestamp is also consistent with the other criteria.
The {start} and {stop} keywords have the same meaning that they do for
the "run"_run.html command. They only need to be defined if (a) you
are using a "fix"_fix.html command that changes some value over time,
and (b) you want the reference point for elapsed time (from start to
stop) to be different than the {first} and {last} settings. See the
doc page for individual fixes to see which ones can be used with the
{start/stop} keywords. Note that if you define neither of the
{start}/{stop} or {first}/{last} keywords, then LAMMPS treats the
The {start} and {stop} keywords do not affect which snapshots are read
from the dump file(s). Rather, they have the same meaning that they
do for the "run"_run.html command. They only need to be defined if
(a) you are using a "fix"_fix.html command that changes some value
over time, and (b) you want the reference point for elapsed time (from
start to stop) to be different than the {first} and {last} settings.
See the doc page for individual fixes to see which ones can be used
with the {start/stop} keywords. Note that if you define neither of
the {start}/{stop} or {first}/{last} keywords, then LAMMPS treats the
pseudo run as going from 0 to a huge value (effectively infinity).
This means that any quantity that a fix scales as a fraction of
elapsed time in the run, will essentially remain at its intiial value.
Also note that an error will occur if you read a snapshot from the
dump file with a timestep value larger than the {stop} setting you
have specified.
The {dump} keyword is required and must be the last keyword specified.
Its arguments are passed internally to the "read_dump"_read_dump.html
@ -157,7 +161,7 @@ angle evaluations, if no pair style is being used.
Every time a snapshot is read, the timestep for the simulation is
reset, as if the "reset_timestep"_reset_timestep.html command were
used. This command has some restrictions as to what fixes can be
defined. See its doc page for details. For example, the fix
defined. See its doc page for details. For example, the "fix
deposit"_fix_deposit.html and "fix dt/reset"_fix_dt_reset.html fixes
are in this category. They also make no sense to use with a rerun
command.