Merge branch 'develop' into schererc/develop

doc/src/Build_settings.rst

@@ -287,8 +287,8 @@ Output of JPG, PNG, and movie files
 
 The :doc:`dump image <dump_image>` command has options to output JPEG or
 PNG image files.  Likewise the :doc:`dump movie <dump_image>` command
-outputs movie files in MPEG format.  Using these options requires the
-following settings:
+outputs movie files in a variety of movie formats.  Using these options
+requires the following settings:
 
 .. tabs::
 
@@ -328,11 +328,12 @@ following settings:
          JPG_LIB = -ljpeg -lpng -lz       # library names
 
       As with CMake, you do not need to set ``JPG_INC`` or ``JPG_PATH``,
-      if make can find the graphics header and library files.  You must
-      specify ``JPG_LIB`` with a list of graphics libraries to include
-      in the link.  You must insure ffmpeg is in a directory where
-      LAMMPS can find it at runtime, that is a directory in your PATH
-      environment variable.
+      if make can find the graphics header and library files in their
+      default system locations.  You must specify ``JPG_LIB`` with a
+      list of graphics libraries to include in the link.  You must make
+      certain that the ffmpeg executable (or ffmpeg.exe on Windows) is
+      in a directory where LAMMPS can find it at runtime; that is
+      usually a directory list in your ``PATH`` environment variable.
 
 Using ``ffmpeg`` to output movie files requires that your machine
 supports the "popen" function in the standard runtime library.

doc/src/Howto_body.rst

@@ -239,7 +239,7 @@ is consistent with the 6 moments of inertia: ixx iyy izz ixy ixz iyz =
 
 .. parsed-literal::
 
-   3 1 27
+   3 1 19
    4
    1 1 4 0 0 0
    -0.7071 -0.7071 0

doc/src/Intro_citing.rst

@@ -30,8 +30,8 @@ initial versions of LAMMPS is:
   `S. Plimpton, Fast Parallel Algorithms for Short-Range Molecular Dynamics, J Comp Phys, 117, 1-19 (1995). <http://www.sandia.gov/~sjplimp/papers/jcompphys95.pdf>`_
 
 
-DOI for the LAMMPS code
-^^^^^^^^^^^^^^^^^^^^^^^
+DOI for the LAMMPS source code
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 LAMMPS developers use the `Zenodo service at CERN <https://zenodo.org/>`_
 to create digital object identifies (DOI) for stable releases of the

doc/src/kspace_style.rst

@@ -475,8 +475,8 @@ that package **and** the KSPACE package.  See the :doc:`Build package
 <Build_package>` page for more info.
 
 For MSM, a simulation must be 3d and one can use any combination of
-periodic, non-periodic, or shrink-wrapped boundaries (specified using
-the :doc:`boundary <boundary>` command).
+periodic, non-periodic, but not shrink-wrapped boundaries (specified
+using the :doc:`boundary <boundary>` command).
 
 For Ewald and PPPM, a simulation must be 3d and periodic in all
 dimensions.  The only exception is if the slab option is set with

doc/src/min_style.rst

@@ -4,7 +4,7 @@ min_style cg command
 ====================
 
 min_style hftn command
-====================
+======================
 
 min_style sd command
 ====================

doc/src/pair_none.rst

@@ -20,28 +20,37 @@ Examples
 Description
 """""""""""
 
-Using a pair style of none means pair forces and energies are not
-computed.
+Using a pair style of *none* means that any previous pair style setting
+will be deleted and pairwise forces and energies are not computed.
 
-With this choice, the force cutoff is 0.0, which means that only atoms
-within the neighbor skin distance (see the :doc:`neighbor <neighbor>`
-command) are communicated between processors.  You must insure the
-skin distance is large enough to acquire atoms needed for computing
-bonds, angles, etc.
+As a consequence there will be a pairwise force cutoff of 0.0, which has
+implications for the default setting of the neighbor list and the
+communication cutoff.  Those are the sum of the largest pairwise cutoff
+and the neighbor skin distance (see the documentation of the
+:doc:`neighbor <neighbor>` command and the :doc:`comm_modify
+<comm_modify>` command).  When you have bonds, angles, dihedrals, or
+impropers defined at the same time, you must set the communication
+cutoff so that communication cutoff distance is large enough to acquire
+and communicate sufficient ghost atoms from neighboring sub-domains as
+needed for computing bonds, angles, etc.
 
-A pair style of *none* will also prevent pairwise neighbor lists from
-being built.  However if the :doc:`neighbor <neighbor>` style is *bin*,
-data structures for binning are still allocated.  If the neighbor skin
-distance is small, then these data structures can consume a large
-amount of memory.  So you should either set the neighbor style to
-*nsq* or set the skin distance to a larger value.
+A pair style of *none* will also not request a pairwise neighbor list.
+However if the :doc:`neighbor <neighbor>` style is *bin*, data
+structures for binning are still allocated.  If the neighbor list cutoff
+is small, then these data structures can consume a large amount of
+memory.  So you should either set the neighbor style to *nsq* or set the
+skin distance to a larger value.
 
-See the :doc:`pair_style zero <pair_zero>` for a way to trigger the
-building of a neighbor lists, but compute no pairwise interactions.
+See the :doc:`pair_style zero <pair_zero>` for a way to set a pairwise
+cutoff and thus trigger the building of a neighbor lists and setting
+a corresponding communication cutoff, but compute no pairwise interactions.
 
 Restrictions
 """"""""""""
-none
+
+You must not use a :doc:`pair_coeff <pair_coeff>` command with this pair
+style.  Since there is no interaction computed, you cannot set any
+coefficients for it.
 
 Related commands
 """"""""""""""""