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

doc/if.html

@@ -13,15 +13,15 @@
 </H3>
 <P><B>Syntax:</B>
 </P>
-<PRE>if value1 operator value2 then T1 T2 ... else E1 E2 ... 
+<PRE>if value1 operator value2 then t1 t2 ... else e1 e2 ... 
 </PRE>
 <UL><LI>value1 = 1st value
 <LI>operator = "<" or "<=" or ">" or ">=" or "==" or "!="
 <LI>value2 = 2nd value
 <LI>then = required word
-<LI>T1,T2,...,TN = one or more commands to execute if condition is met
+<LI>t1,t2,...,tN = one or more LAMMPS commands to execute if condition is met, each enclosed in quotes
 <LI>else = optional argument
-<LI>E1,E2,...,EN = one or more commands to execute if condition is not met (optional arguments) 
+<LI>e1,e2,...,eN = one or more LAMMPS commands to execute if condition is not met, each enclosed in quotes (optional arguments) 
 </UL>
 <P><B>Examples:</B>
 </P>
@@ -41,14 +41,14 @@ executed, the variable(s) will be evaluated, which could calculate a
 user-defined formula that reflects the current state of the
 simulation.
 </P>
-<P>If the result of the if test is TRUE, then one or more commands (T1,
-T2, ..., TN) are executed.  If the result of the if test is FALSE and
+<P>If the result of the if test is TRUE, then one or more commands (t1,
+t2, ..., tN) are executed.  If the result of the if test is FALSE and
 no optional "else" argument is included, then the if command does
 nothing.  If the result of the if test is FALSE and the optional
-"else" argument is included, then one or more commands (E1,
-E2, ..., En) are executed.
+"else" argument is included, then one or more commands (e1,
+e2, ..., eN) are executed.
 </P>
-<P>Each then or else command (T1,E1,etc) can be any valid LAMMPS input
+<P>Each then or else command (t1, e1, etc) can be any valid LAMMPS input
 script command.  Each command should be enclosed in quotes, so it will
 be treated as a single argument, as in the examples above.
 </P>

doc/if.txt

@@ -10,15 +10,15 @@ if command :h3
 
 [Syntax:]
 
-if value1 operator value2 then T1 T2 ... else E1 E2 ... :pre
+if value1 operator value2 then t1 t2 ... else e1 e2 ... :pre
 
 value1 = 1st value
 operator = "<" or "<=" or ">" or ">=" or "==" or "!="
 value2 = 2nd value
 then = required word
-T1,T2,...,TN = one or more commands to execute if condition is met
+t1,t2,...,tN = one or more LAMMPS commands to execute if condition is met, each enclosed in quotes
 else = optional argument
-E1,E2,...,EN = one or more commands to execute if condition is not met (optional arguments) :ul
+e1,e2,...,eN = one or more LAMMPS commands to execute if condition is not met, each enclosed in quotes (optional arguments) :ul
 
 [Examples:]
 
@@ -38,14 +38,14 @@ executed, the variable(s) will be evaluated, which could calculate a
 user-defined formula that reflects the current state of the
 simulation.
 
-If the result of the if test is TRUE, then one or more commands (T1,
-T2, ..., TN) are executed.  If the result of the if test is FALSE and
+If the result of the if test is TRUE, then one or more commands (t1,
+t2, ..., tN) are executed.  If the result of the if test is FALSE and
 no optional "else" argument is included, then the if command does
 nothing.  If the result of the if test is FALSE and the optional
-"else" argument is included, then one or more commands (E1,
-E2, ..., En) are executed.
+"else" argument is included, then one or more commands (e1,
+e2, ..., eN) are executed.
 
-Each then or else command (T1,E1,etc) can be any valid LAMMPS input
+Each then or else command (t1, e1, etc) can be any valid LAMMPS input
 script command.  Each command should be enclosed in quotes, so it will
 be treated as a single argument, as in the examples above.
 

doc/run.html

@@ -28,10 +28,10 @@
     N2 = timestep at which last run will end
   <I>pre</I> value = <I>no</I> or <I>yes</I>
   <I>post</I> value = <I>no</I> or <I>yes</I> 
-  <I>every</I> values = M command1 command2 ...
+  <I>every</I> values = M c1 c2 ...
     M = break the run into M-timestep segments and invoke one or more commands between each segment
-    command1,command2,... = a single LAMMPS command, enclosed in quotes
-    command1 = NULL means no command will be invoked 
+    c1,c2,...,cN = one or more LAMMPS commands, each enclosed in quotes
+    c1 = NULL means no command will be invoked 
 </PRE>
 
 </UL>
@@ -114,14 +114,14 @@ this case.
 only a one-line summary timing is printed.
 </P>
 <P>The <I>every</I> keyword provides a means of breaking a LAMMPS run into a
-series of shorter runs.  Optionally, one or more LAMMPS commands will
-be executed in between the short runs.  If used, the <I>every</I> keyword
-must be the last keyword, since it has a variable number of arguments.
-Each of the trailing arguments is a single LAMMPS command, and each
-command should be enclosed in quotes, so that the entire command will
-be treated as a single argument.  This will also prevent any variables
-in the command from being evaluated until it is executed during the
-run.
+series of shorter runs.  Optionally, one or more LAMMPS commands (c1,
+c2, ..., cN) will be executed in between the short runs.  If used, the
+<I>every</I> keyword must be the last keyword, since it has a variable
+number of arguments.  Each of the trailing arguments is a single
+LAMMPS command, and each command should be enclosed in quotes, so that
+the entire command will be treated as a single argument.  This will
+also prevent any variables in the command from being evaluated until
+it is executed multiple times during the run.
 </P>
 <P>The <I>every</I> keyword is a means to avoid listing a long series of runs
 and interleaving commands in your input script.  For example, a

doc/run.txt

@@ -22,10 +22,10 @@ keyword = {upto} or {start} or {stop} or {pre} or {post} or {every} :l
     N2 = timestep at which last run will end
   {pre} value = {no} or {yes}
   {post} value = {no} or {yes} 
-  {every} values = M command1 command2 ...
+  {every} values = M c1 c2 ...
     M = break the run into M-timestep segments and invoke one or more commands between each segment
-    command1,command2,... = a single LAMMPS command, enclosed in quotes
-    command1 = NULL means no command will be invoked :pre
+    c1,c2,...,cN = one or more LAMMPS commands, each enclosed in quotes
+    c1 = NULL means no command will be invoked :pre
 :ule
 
 [Examples:]
@@ -107,14 +107,14 @@ If {post} is specified as "no", the full timing summary is skipped;
 only a one-line summary timing is printed.
 
 The {every} keyword provides a means of breaking a LAMMPS run into a
-series of shorter runs.  Optionally, one or more LAMMPS commands will
-be executed in between the short runs.  If used, the {every} keyword
-must be the last keyword, since it has a variable number of arguments.
-Each of the trailing arguments is a single LAMMPS command, and each
-command should be enclosed in quotes, so that the entire command will
-be treated as a single argument.  This will also prevent any variables
-in the command from being evaluated until it is executed during the
-run.
+series of shorter runs.  Optionally, one or more LAMMPS commands (c1,
+c2, ..., cN) will be executed in between the short runs.  If used, the
+{every} keyword must be the last keyword, since it has a variable
+number of arguments.  Each of the trailing arguments is a single
+LAMMPS command, and each command should be enclosed in quotes, so that
+the entire command will be treated as a single argument.  This will
+also prevent any variables in the command from being evaluated until
+it is executed multiple times during the run.
 
 The {every} keyword is a means to avoid listing a long series of runs
 and interleaving commands in your input script.  For example, a