From 95cf2cb86f8c7a7c5a322b0df8588ba3910d99b3 Mon Sep 17 00:00:00 2001 From: sjplimp Date: Fri, 18 May 2012 21:08:14 +0000 Subject: [PATCH] git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@8093 f3b2605a-c512-4ea7-a41b-209d697bcdaa --- doc/dump_modify.txt | 16 ++++++++-------- doc/thermo_modify.txt | 11 ++++++----- 2 files changed, 14 insertions(+), 13 deletions(-) diff --git a/doc/dump_modify.txt b/doc/dump_modify.txt index c51464d672..d37169a110 100644 --- a/doc/dump_modify.txt +++ b/doc/dump_modify.txt @@ -351,14 +351,14 @@ In this case, the variable is evaluated at the beginning of a run to determine the next timestep at which a dump snapshot will be written out. On that timestep, the variable will be evaluated again to determine the next timestep, etc. Thus the variable should return -timestep values. See the stagger() and logfreq() math functions for -"equal-style variables"_variable.html, as examples of useful functions -to use in this context. Other similar math functions could easily be -added as options for "equal-style variables"_variable.html. When -using the variable option with the {every} keyword, you also need to -use the {first} option if you want an initial snapshot written to the -dump file. The {every} keyword cannot be used with the dump {dcd} -style. +timestep values. See the stagger() and logfreq() and stride() math +functions for "equal-style variables"_variable.html, as examples of +useful functions to use in this context. Other similar math functions +could easily be added as options for "equal-style +variables"_variable.html. When using the variable option with the +{every} keyword, you also need to use the {first} option if you want +an initial snapshot written to the dump file. The {every} keyword +cannot be used with the dump {dcd} style. For example, the following commands will write snapshots at timesteps 0,10,20,30,100,200,300,1000,2000,etc: diff --git a/doc/thermo_modify.txt b/doc/thermo_modify.txt index e4b97dbed6..5d983afdf2 100644 --- a/doc/thermo_modify.txt +++ b/doc/thermo_modify.txt @@ -147,11 +147,12 @@ the beginning of a run to determine the next timestep at which a dump snapshot will be written out. On that timestep, the variable will be evaluated again to determine the next timestep, etc. Thus the variable should return timestep values. See the stagger() and -logfreq() math functions for "equal-style variables"_variable.html, as -examples of useful functions to use in this context. Other similar -math functions could easily be added as options for "equal-style -variables"_variable.html. In addition, thermodynamic output will -always occur on the first and last timestep of each run. +logfreq() and stride() math functions for "equal-style +variables"_variable.html, as examples of useful functions to use in +this context. Other similar math functions could easily be added as +options for "equal-style variables"_variable.html. In addition, +thermodynamic output will always occur on the first and last timestep +of each run. For example, the following commands will output thermodynamic info at timesteps 0,10,20,30,100,200,300,1000,2000,etc: