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

fix typo for broken links in doc

Browse Source
This commit is contained in:
jbcouli
2023-07-09 17:43:39 -06:00
parent 146245e6ae
commit 0718114a67
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/fix_ave_grid.rst
View File

@ -129,12 +129,12 @@ overlays the simulation box. For 2d simulations, *Nz* must be 1. The
very coarse compared to the particle count, or very fine. If one or very coarse compared to the particle count, or very fine. If one or
more of the values = 1, then bins are 2d planes or 1d slices of the more of the values = 1, then bins are 2d planes or 1d slices of the
simulation domain. Note that if the total number of grid cells is simulation domain. Note that if the total number of grid cells is
small, it may be more efficient to use the doc:`fix ave/chunk small, it may be more efficient to use the :doc:`fix ave/chunk
<fix_ave_chunk>` command which can treat a grid defined by the <fix_ave_chunk>` command which can treat a grid defined by the
:doc:`compute chunk/atom <compute_chunk_atom>` command as a global :doc:`compute chunk/atom <compute_chunk_atom>` command as a global
grid where each processor owns a copy of all the grid cells. If *Nx* grid where each processor owns a copy of all the grid cells. If *Nx*
= *Ny* = *Nz* = 1 is used, the same calculation would be more = *Ny* = *Nz* = 1 is used, the same calculation would be more
efficiently performed by the doc:`fix ave/atom <fix_ave_atom>` efficiently performed by the :doc:`fix ave/atom <fix_ave_atom>`
command. command.
If the simulation box size or shape changes during a simulation, the If the simulation box size or shape changes during a simulation, the

8
doc/src/variable.rst
View File

@ -1441,7 +1441,7 @@ timestep that the variable needs the tallies. An input script can
also request variables be evaluated before or after or in between also request variables be evaluated before or after or in between
runs, e.g. by including them in a :doc:`print <print>` command. runs, e.g. by including them in a :doc:`print <print>` command.
LAMMPS keeps track of all of this as it performs a doc:`run <run>` or LAMMPS keeps track of all of this as it performs a :doc:`run <run>` or
:doc:`minimize <minimize>` simulation, as well as in between :doc:`minimize <minimize>` simulation, as well as in between
simulations. An error will be generated if you attempt to evaluate a simulations. An error will be generated if you attempt to evaluate a
variable when LAMMPS knows it cannot produce accurate values. For variable when LAMMPS knows it cannot produce accurate values. For
@ -1453,7 +1453,7 @@ command, then an error will occur.
However, there are two special cases to be aware when a variable However, there are two special cases to be aware when a variable
requires invocation of a compute (directly or indirectly). The first requires invocation of a compute (directly or indirectly). The first
is if the variable is evaluated before the first doc:`run <run>` or is if the variable is evaluated before the first :doc:`run <run>` or
:doc:`minimize <minimize>` command in the input script. In this case, :doc:`minimize <minimize>` command in the input script. In this case,
LAMMPS will generate an error. This is because many computes require LAMMPS will generate an error. This is because many computes require
initializations which have not yet taken place. One example is the initializations which have not yet taken place. One example is the
@ -1463,10 +1463,10 @@ energy or virial quantities; these values are not tallied until the
first simulation begins. first simulation begins.
The second special case is when a variable that depends on a compute The second special case is when a variable that depends on a compute
is evaluated in between doc:`run <run>` or :doc:`minimize <minimize>` is evaluated in between :doc:`run <run>` or :doc:`minimize <minimize>`
commands. It is possible for other input script commands issued commands. It is possible for other input script commands issued
following the previous run, but before the variable is evaluated, to following the previous run, but before the variable is evaluated, to
change the system. For example, the doc:`delete_atoms <delete_atoms>` change the system. For example, the :doc:`delete_atoms <delete_atoms>`
command could be used to remove atoms. Since the compute will not command could be used to remove atoms. Since the compute will not
re-initialize itself until the next simulation or it may depend on re-initialize itself until the next simulation or it may depend on
energy/virial computations performed before the system was changed, it energy/virial computations performed before the system was changed, it