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

fix typos

Browse Source
This commit is contained in:
Axel Kohlmeyer
2020-10-12 00:03:18 -04:00
parent d5e6bd3cdc
commit d0cf52fafd
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/read_data.rst
View File

@ -377,7 +377,7 @@ as that preserves the relative proximity of the positions for bonded atoms,
and then post-process the data by moving entire molecules and also then and then post-process the data by moving entire molecules and also then
adjust the box geometry as needed without affecting the positions. adjust the box geometry as needed without affecting the positions.
When you have non-zero image flags, changing the box also translates When you have non-zero image flags, changing the box also translates
atoms, and if a molecule staddles (periodic) box boundaries and thus atoms, and if a molecule straddles (periodic) box boundaries and thus
the image flags can be different for atoms in the same molecule, that the image flags can be different for atoms in the same molecule, that
can move bonded atoms far apart. can move bonded atoms far apart.
@ -392,8 +392,8 @@ can move bonded atoms far apart.
to processors. Note that you should not make the lo/hi values to processors. Note that you should not make the lo/hi values
radically smaller/larger than the extent of the atoms. For example, radically smaller/larger than the extent of the atoms. For example,
if your atoms extend from 0 to 50, you should not specify the box if your atoms extend from 0 to 50, you should not specify the box
bounds as -10000 and 10000 unless you also use the :doc:`processor bounds as -10000 and 10000 unless you also use the :doc:`processors
command <processor>`. This is because LAMMPS uses the specified box command <processors>`. This is because LAMMPS uses the specified box
size to layout the 3d grid of processors. A huge (mostly empty) box size to layout the 3d grid of processors. A huge (mostly empty) box
will be sub-optimal for performance when using "fixed" boundary will be sub-optimal for performance when using "fixed" boundary
conditions (see the :doc:`boundary <boundary>` command). When using conditions (see the :doc:`boundary <boundary>` command). When using