diff --git a/doc/dump_modify.html b/doc/dump_modify.html index f9831c9be5..580aa3bc22 100644 --- a/doc/dump_modify.html +++ b/doc/dump_modify.html @@ -112,7 +112,7 @@ if this is not the case, a dump snapshot will only be written if the setting of this keyword is yes. If it is no, which is the default, then it will not be written.

-

The flush keyword determines whether a flush operation in invoked +

The flush keyword determines whether a flush operation is invoked after a dump snapshot is written to the dump file. A flush insures the output in that file is current (no buffering by the OS), even if LAMMPS halts before the simulation completes. Flushes cannot be diff --git a/doc/dump_modify.txt b/doc/dump_modify.txt index 16a04f5486..d3a2c98ad0 100644 --- a/doc/dump_modify.txt +++ b/doc/dump_modify.txt @@ -105,7 +105,7 @@ if this is not the case, a dump snapshot will only be written if the setting of this keyword is {yes}. If it is {no}, which is the default, then it will not be written. -The {flush} keyword determines whether a flush operation in invoked +The {flush} keyword determines whether a flush operation is invoked after a dump snapshot is written to the dump file. A flush insures the output in that file is current (no buffering by the OS), even if LAMMPS halts before the simulation completes. Flushes cannot be diff --git a/doc/thermo_modify.html b/doc/thermo_modify.html index 92f530d6be..4cac153196 100644 --- a/doc/thermo_modify.html +++ b/doc/thermo_modify.html @@ -19,7 +19,7 @@

  • keyword = lost or norm or flush or line or format or temp or press or every - lost value = error or warn or ignore +
      lost value = error or warn or ignore
   norm value = yes or no
   flush value = yes or no
   line value = one or multi
@@ -29,7 +29,8 @@
   temp value = compute ID that calculates a temperature
   press value = compute ID that calculates a pressure
   every value = v_name
-    v_name = an equal-style variable name
+    v_name = an equal-style variable name 
+

    Examples: diff --git a/doc/thermo_modify.txt b/doc/thermo_modify.txt index cf5c621fa9..d8742d954a 100644 --- a/doc/thermo_modify.txt +++ b/doc/thermo_modify.txt @@ -24,7 +24,7 @@ keyword = {lost} or {norm} or {flush} or {line} or {format} or {temp} or {press} {temp} value = compute ID that calculates a temperature {press} value = compute ID that calculates a pressure {every} value = v_name - v_name = an equal-style variable name + v_name = an equal-style variable name :pre :ule [Examples:] diff --git a/doc/variable.html b/doc/variable.html index f3187a9bfb..033d06ce5a 100644 --- a/doc/variable.html +++ b/doc/variable.html @@ -415,12 +415,13 @@ the ID of a compute defined elsewhere in the input script. As discussed in the doc page for the compute command, computes can produce global, per-atom, or local values. Only global and per-atom values can be used in a variable. Computes can also -produce a scalar, vector, or array. An equal-style variable can use -scalar values, which means a scalar itself, or an element of a vector -or array. Atom-style variables can use either scalar or vector -values. A vector value can be a vector itself, or a column of an -array. See the doc pages for individual computes to see what kind of -values they produce. +produce a scalar, vector, or array. An equal-style variable can only +use scalar values, which means a global scalar, or an element of a +global or per-atom vector or array. Atom-style variables can use the +same scalar values. They can also use per-atom vector values. A +vector value can be a per-atom vector itself, or a column of an +per-atom array. See the doc pages for individual computes to see what +kind of values they produce.

    Examples of different kinds of compute references are as follows. There is no ambiguity as to what a reference means, since computes @@ -443,15 +444,17 @@ elsewhere in the input script. As discussed in the doc page for the fix command, fixes can produce global, per-atom, or local values. Only global and per-atom values can be used in a variable. Fixes can also produce a scalar, vector, or array. An equal-style -variable can use scalar values, which means a scalar itself, or an -element of a vector or array. Atom-style variables can use either -scalar or vector values. A vector value can be a vector itself, or a -column of an array. See the doc pages for individual fixes to see -what kind of values they produce. +variable can only use scalar values, which means a global scalar, or +an element of a global or per-atom vector or array. Atom-style +variables can use the same scalar values. They can also use per-atom +vector values. A vector value can be a per-atom vector itself, or a +column of an per-atom array. See the doc pages for individual fixes +to see what kind of values they produce.

    The different kinds of fix references are exactly the same as the compute references listed in the above table, where "c_" is replaced -by "f_". +by "f_". Again, there is no ambiguity as to what a reference means, +since fixes only produce global or per-atom quantities, never both.

    @@ -474,14 +477,15 @@ which will cause those variables to be evaluated. The name in the reference should be replaced by the name of a variable defined elsewhere in the input script. As discussed on this doc page, atom-style variables generate a per-atom vector of values; all other -variable styles generate a single scalar value. An equal-style -variable can use scalar values produce by another variable, but not -per-atom vectors. Atom-style variables can use either scalar or -per-atom vector values. +variable styles generate a global scalar value. An equal-style +variable can reference a global scalar value produced by another +variable, but not a per-atom vector produced by an atom-style +variable. Atom-style variables can reference either global scalar or +per-atom vector values produced by kind of variable.

    Examples of different kinds of variable references are as follows. There is no ambiguity as to what a reference means, since variables -only produce scalar or per-atom vectors, never both. +produce only a global scalar or a per-atom vectors, never both.

    f_ID global scalar, or per-atom vector
    diff --git a/doc/variable.txt b/doc/variable.txt index f65f8dc4b6..87f3d0b688 100644 --- a/doc/variable.txt +++ b/doc/variable.txt @@ -414,12 +414,13 @@ the ID of a compute defined elsewhere in the input script. As discussed in the doc page for the "compute"_compute.html command, computes can produce global, per-atom, or local values. Only global and per-atom values can be used in a variable. Computes can also -produce a scalar, vector, or array. An equal-style variable can use -scalar values, which means a scalar itself, or an element of a vector -or array. Atom-style variables can use either scalar or vector -values. A vector value can be a vector itself, or a column of an -array. See the doc pages for individual computes to see what kind of -values they produce. +produce a scalar, vector, or array. An equal-style variable can only +use scalar values, which means a global scalar, or an element of a +global or per-atom vector or array. Atom-style variables can use the +same scalar values. They can also use per-atom vector values. A +vector value can be a per-atom vector itself, or a column of an +per-atom array. See the doc pages for individual computes to see what +kind of values they produce. Examples of different kinds of compute references are as follows. There is no ambiguity as to what a reference means, since computes @@ -440,15 +441,17 @@ elsewhere in the input script. As discussed in the doc page for the "fix"_fix.html command, fixes can produce global, per-atom, or local values. Only global and per-atom values can be used in a variable. Fixes can also produce a scalar, vector, or array. An equal-style -variable can use scalar values, which means a scalar itself, or an -element of a vector or array. Atom-style variables can use either -scalar or vector values. A vector value can be a vector itself, or a -column of an array. See the doc pages for individual fixes to see -what kind of values they produce. +variable can only use scalar values, which means a global scalar, or +an element of a global or per-atom vector or array. Atom-style +variables can use the same scalar values. They can also use per-atom +vector values. A vector value can be a per-atom vector itself, or a +column of an per-atom array. See the doc pages for individual fixes +to see what kind of values they produce. The different kinds of fix references are exactly the same as the compute references listed in the above table, where "c_" is replaced -by "f_". +by "f_". Again, there is no ambiguity as to what a reference means, +since fixes only produce global or per-atom quantities, never both. f_ID: global scalar, or per-atom vector f_ID\[I\]: Ith element of global vector, or atom I's value in per-atom vector, or Ith column from per-atom array @@ -469,14 +472,15 @@ which will cause those variables to be evaluated. The name in the reference should be replaced by the name of a variable defined elsewhere in the input script. As discussed on this doc page, atom-style variables generate a per-atom vector of values; all other -variable styles generate a single scalar value. An equal-style -variable can use scalar values produce by another variable, but not -per-atom vectors. Atom-style variables can use either scalar or -per-atom vector values. +variable styles generate a global scalar value. An equal-style +variable can reference a global scalar value produced by another +variable, but not a per-atom vector produced by an atom-style +variable. Atom-style variables can reference either global scalar or +per-atom vector values produced by kind of variable. Examples of different kinds of variable references are as follows. There is no ambiguity as to what a reference means, since variables -only produce scalar or per-atom vectors, never both. +produce only a global scalar or a per-atom vectors, never both. v_name: scalar, or per-atom vector v_name\[I\]: atom I's value in per-atom vector :tb(s=:)
    v_name scalar, or per-atom vector