From 65978c33b604eb5a4a21a5847a4ca5a9ec2b2e86 Mon Sep 17 00:00:00 2001 From: Steve Plimpton Date: Mon, 25 Apr 2022 16:06:52 -0600 Subject: [PATCH] 2 more doc pages --- doc/src/fix_ave_histo.rst | 10 +++++----- doc/src/fix_ave_time.rst | 19 +++++++++++-------- 2 files changed, 16 insertions(+), 13 deletions(-) diff --git a/doc/src/fix_ave_histo.rst b/doc/src/fix_ave_histo.rst index 3cd1bdf4db..5d36a372c3 100644 --- a/doc/src/fix_ave_histo.rst +++ b/doc/src/fix_ave_histo.rst @@ -144,8 +144,9 @@ asterisk means all indices from m to n (inclusive). Using a wildcard is the same as if the individual elements of the vector or columns of the array had been listed one by one. E.g. these -2 fix ave/histo commands are equivalent, since the :doc:`compute com/chunk ` command creates a global array with -3 columns: +2 fix ave/histo commands are equivalent, since the :doc:`compute +com/chunk ` command creates a global array with 3 +columns: .. code-block:: LAMMPS @@ -158,9 +159,8 @@ vector or columns of the array had been listed one by one. E.g. these For a vector-style variable, only the wildcard forms "\*n" or "m\*n" are allowed. You must specify the upper bound, because vector-style variable lengths are not determined until the variable - is evaluated. If n is specified larger than the vector length"\*n" - or "n\*" or "m\*n". turns out to be, zeroes are output for missing - vector values. + is evaluated. If n is specified larger than the vector length + turns out to be, zeroes are output for missing vector values. ---------- diff --git a/doc/src/fix_ave_time.rst b/doc/src/fix_ave_time.rst index f2d634ca75..2836e11fd0 100644 --- a/doc/src/fix_ave_time.rst +++ b/doc/src/fix_ave_time.rst @@ -127,8 +127,9 @@ asterisk means all indices from m to n (inclusive). Using a wildcard is the same as if the individual elements of the vector or columns of the array had been listed one by one. E.g. these -2 fix ave/time commands are equivalent, since the :doc:`compute rdf ` command creates, in this case, a global array -with 3 columns, each of length 50: +2 fix ave/time commands are equivalent, since the :doc:`compute rdf +` command creates, in this case, a global array with 3 +columns, each of length 50: .. code-block:: LAMMPS @@ -141,9 +142,8 @@ with 3 columns, each of length 50: For a vector-style variable, only the wildcard forms "\*n" or "m\*n" are allowed. You must specify the upper bound, because vector-style variable lengths are not determined until the variable - is evaluated. If n is specified larger than the vector length"\*n" - or "n\*" or "m\*n". turns out to be, zeroes are output for missing - vector values. + is evaluated. If n is specified larger than the vector length + turns out to be, zeroes are output for missing vector values. ---------- @@ -180,9 +180,12 @@ asterisk to effectively specify multiple values. Note that there is a :doc:`compute reduce ` command which can sum per-atom quantities into a global scalar or vector which can thus be accessed by fix ave/time. Or it can be a compute defined -not in your input script, but by :doc:`thermodynamic output ` or other fixes such as :doc:`fix nvt ` or :doc:`fix temp/rescale `. See -the doc pages for these commands which give the IDs of these computes. -Users can also write code for their own compute styles and :doc:`add them to LAMMPS `. +not in your input script, but by :doc:`thermodynamic output +` or other fixes such as :doc:`fix nvt ` or +:doc:`fix temp/rescale `. See the doc pages for +these commands which give the IDs of these computes. Users can also +write code for their own compute styles and :doc:`add them to LAMMPS +`. If a value begins with "f\_", a fix ID must follow which has been previously defined in the input script. If *mode* = scalar, then if