ICODE-ADC/lammps
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

2 more doc pages

Browse Source
This commit is contained in:
Steve Plimpton
2022-04-25 16:06:52 -06:00
parent bb8e953fb5
commit 65978c33b6
2 changed files with 16 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/fix_ave_histo.rst
View File

@ -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 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 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 <compute_com_chunk>` command creates a global array with 2 fix ave/histo commands are equivalent, since the :doc:`compute
3 columns: com/chunk <compute_com_chunk>` command creates a global array with 3
columns:
.. code-block:: LAMMPS .. 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 For a vector-style variable, only the wildcard forms "\*n" or
"m\*n" are allowed. You must specify the upper bound, because "m\*n" are allowed. You must specify the upper bound, because
vector-style variable lengths are not determined until the variable vector-style variable lengths are not determined until the variable
is evaluated. If n is specified larger than the vector length"\*n" is evaluated. If n is specified larger than the vector length
or "n\*" or "m\*n". turns out to be, zeroes are output for missing turns out to be, zeroes are output for missing vector values.
vector values.
---------- ----------

19
doc/src/fix_ave_time.rst
View File

@ -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 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 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 <compute_rdf>` command creates, in this case, a global array 2 fix ave/time commands are equivalent, since the :doc:`compute rdf
with 3 columns, each of length 50: <compute_rdf>` command creates, in this case, a global array with 3
columns, each of length 50:
.. code-block:: LAMMPS .. 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 For a vector-style variable, only the wildcard forms "\*n" or
"m\*n" are allowed. You must specify the upper bound, because "m\*n" are allowed. You must specify the upper bound, because
vector-style variable lengths are not determined until the variable vector-style variable lengths are not determined until the variable
is evaluated. If n is specified larger than the vector length"\*n" is evaluated. If n is specified larger than the vector length
or "n\*" or "m\*n". turns out to be, zeroes are output for missing turns out to be, zeroes are output for missing vector values.
vector values.
---------- ----------
@ -180,9 +180,12 @@ asterisk to effectively specify multiple values.
Note that there is a :doc:`compute reduce <compute_reduce>` command Note that there is a :doc:`compute reduce <compute_reduce>` command
which can sum per-atom quantities into a global scalar or vector which 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 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 <thermo_style>` or other fixes such as :doc:`fix nvt <fix_nh>` or :doc:`fix temp/rescale <fix_temp_rescale>`. See not in your input script, but by :doc:`thermodynamic output
the doc pages for these commands which give the IDs of these computes. <thermo_style>` or other fixes such as :doc:`fix nvt <fix_nh>` or
Users can also write code for their own compute styles and :doc:`add them to LAMMPS <Modify>`. :doc:`fix temp/rescale <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
<Modify>`.
If a value begins with "f\_", a fix ID must follow which has been 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 previously defined in the input script. If *mode* = scalar, then if