From 0fe876a19982810ee6a8e9969d1ab0618021eaeb Mon Sep 17 00:00:00 2001
From: sjplimp <sjplimp@f3b2605a-c512-4ea7-a41b-209d697bcdaa>
Date: Sat, 26 Mar 2011 23:18:28 +0000
Subject: [PATCH] git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@5853
 f3b2605a-c512-4ea7-a41b-209d697bcdaa

---
 doc/Section_errors.html | 684 +++++++++++++++++++++++++++++++++-------
 doc/Section_errors.txt  | 684 +++++++++++++++++++++++++++++++++-------
 doc/pair_coeff.html     |   2 +-
 doc/pair_coeff.txt      |   2 +-
 4 files changed, 1134 insertions(+), 238 deletions(-)

diff --git a/doc/Section_errors.html b/doc/Section_errors.html
index ebf3222a71..8cd9ed6e46 100644
--- a/doc/Section_errors.html
+++ b/doc/Section_errors.html
@@ -236,7 +236,7 @@ the atoms are too far apart to make a valid angle.
 a particular processor.  The pairwise cutoff is too short or the atoms
 are too far apart to make a valid angle. 
 
-<DT><I>Angle atoms %d %d %d missing on proc %d at step %d</I> 
+<DT><I>Angle atoms %d %d %d missing on proc %d at step</I> 
 
 <DD>One or more of 3 atoms needed to compute a particular angle are
 missing on this processor.  Typically this is because the pairwise
@@ -319,14 +319,6 @@ still being processed.
 
 <DD>Argument of arcsin() must be between -1 and 1. 
 
-<DT><I>At least 1 proc could not allocate a CUDA gpu or memory</I> 
-
-<DD>You are not setup correctly to use a GPU from your CPU. 
-
-<DT><I>At least one process could not allocate a CUDA-enabled gpu</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Atom IDs must be consecutive for velocity create loop all</I> 
 
 <DD>Self-explanatory. 
@@ -406,6 +398,14 @@ read_restart, or create_box command.
 <DD>Two atoms in a FENE bond have become so far apart that the bond cannot
 be computed. 
 
+<DT><I>Bad TIP4P angle type for PPPM/TIP4P</I> 
+
+<DD>Specified angle type is not valid. 
+
+<DT><I>Bad TIP4P bond type for PPPM/TIP4P</I> 
+
+<DD>Specified bond type is not valid. 
+
 <DT><I>Bad grid of processors</I> 
 
 <DD>The 3d grid of processors defined by the processors command does not
@@ -437,6 +437,15 @@ compute.
 
 <DD>Big particles must be extended spheriods or ellipsoids. 
 
+<DT><I>Bigint setting in lmptype.h is invalid</I> 
+
+<DD>Size of bigint is less than size of tagint. 
+
+<DT><I>Bigint setting in lmptype.h is not compatible</I> 
+
+<DD>Bigint stored in restart file is not consistent with LAMMPS version
+you are running. 
+
 <DT><I>Bitmapped lookup tables require int/float be same size</I> 
 
 <DD>Cannot use pair tables on this machine, because of word sizes.  Use
@@ -468,7 +477,7 @@ the atoms are too far apart to make a valid bond.
 a particular processor.  The pairwise cutoff is too short or the atoms
 are too far apart to make a valid bond. 
 
-<DT><I>Bond atoms %d %d missing on proc %d at step %d</I> 
+<DT><I>Bond atoms %d %d missing on proc %d at step</I> 
 
 <DD>One or both of 2 atoms needed to compute a particular bond are
 missing on this processor.  Typically this is because the pairwise
@@ -575,10 +584,18 @@ See the region prism command for details.
 
 <DD>This is current restriction for NEB as implemented in LAMMPS. 
 
+<DT><I>Can only use TAD with 1-processor replicas for NEB</I> 
+
+<DD>This is current restriction for NEB as implemented in LAMMPS. 
+
 <DT><I>Cannot (yet) use PPPM with triclinic box</I> 
 
 <DD>This feature is not yet supported. 
 
+<DT><I>Cannot add atoms to fix move variable</I> 
+
+<DD>Atoms can not be added afterwards to this fix option. 
+
 <DT><I>Cannot change box to orthogonal when tilt is non-zero</I> 
 
 <DD>Self-explanatory 
@@ -625,6 +642,11 @@ but the atoms that have been defined have no IDs.
 <DD>Must use the lattice command before using the create_atoms
 command. 
 
+<DT><I>Cannot create/grow a vector/array of pointers for %s</I> 
+
+<DD>LAMMPS code is making an illegal call to the templated memory
+allocaters, to create a vector or array of pointers. 
+
 <DT><I>Cannot create_atoms after reading restart file with per-atom info</I> 
 
 <DD>The per-atom info was stored to be used when by a fix that you
@@ -636,6 +658,10 @@ there will not be a correct amount of per-atom info.
 <DD>The create_box command cannot be used after a read_data, read_restart,
 or create_box command. 
 
+<DT><I>Cannot currently use pair reax with pair hybrid</I> 
+
+<DD>This is not yet supported. 
+
 <DT><I>Cannot delete group all</I> 
 
 <DD>Self-explanatory. 
@@ -904,10 +930,6 @@ run a 2d simulation.
 all together (pair), or in pieces (inner/middle/outer).  You can't do
 both. 
 
-<DT><I>Cannot set both vel and wiggle in fix wall command</I> 
-
-<DD>Self-explantory. 
-
 <DT><I>Cannot set dipole for this atom style</I> 
 
 <DD>This atom style does not support dipole settings for each atom type. 
@@ -921,6 +943,14 @@ both.
 <DD>This atom style does not support mass settings for each atom type.
 Instead they are defined on a per-atom basis in the data file. 
 
+<DT><I>Cannot set non-zero image flag for non-periodic dimension</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Cannot set non-zero z velocity for 2d simulation</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Cannot set respa middle without inner/outer</I> 
 
 <DD>In the rRESPA integrator, you must define both a inner and outer
@@ -934,6 +964,10 @@ setting in order to use a middle setting.
 
 <DD>The attribute being set does not exist for the defined atom style. 
 
+<DT><I>Cannot set variable z velocity for 2d simulation</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Cannot skew triclinic box in z for 2d simulation</I> 
 
 <DD>Self-explanatory. 
@@ -981,6 +1015,18 @@ which is enabled by default, via the atom_modify command.
 
 <DD>Use the atom_modify command to create an atom map. 
 
+<DT><I>Cannot use TAD unless atom map exists for NEB</I> 
+
+<DD>See atom_modify map command to set this. 
+
+<DT><I>Cannot use TAD with a single replica for NEB</I> 
+
+<DD>NEB requires multiple replicas. 
+
+<DT><I>Cannot use TAD with atom_modify sort enabled for NEB</I> 
+
+<DD>This is a current restriction of NEB. 
+
 <DT><I>Cannot use a damped dynamics min style with fix box/relax</I> 
 
 <DD>This is a current restriction in LAMMPS.  Use another minimizer
@@ -991,6 +1037,14 @@ style.
 <DD>This is a current restriction in LAMMPS.  Use another minimizer
 style. 
 
+<DT><I>Cannot use compute cluster/atom unless atoms have IDs</I> 
+
+<DD>Atom IDs are used to identify clusters. 
+
+<DT><I>Cannot use cwiggle in variable formula between runs</I> 
+
+<DD>This is a function of elapsed time. 
+
 <DT><I>Cannot use delete_atoms unless atoms have IDs</I> 
 
 <DD>Your atoms do not have IDs, so the delete_atoms command cannot be
@@ -1007,6 +1061,10 @@ provided by an atom map.  An atom map does not exist (by default) for
 non-molecular problems.  Using the atom_modify map command will force
 an atom map to be created. 
 
+<DT><I>Cannot use fix ave/spatial z for 2 dimensional model</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Cannot use fix bond/break with non-molecular systems</I> 
 
 <DD>Self-explanatory. 
@@ -1105,6 +1163,36 @@ together.
 
 <DD>Self-explanatory. 
 
+<DT><I>Cannot use fix wall/reflect in periodic dimension</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Cannot use fix wall/reflect zlo/zhi for a 2d simulation</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Cannot use fix wall/srd in periodic dimension</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Cannot use fix wall/srd more than once</I> 
+
+<DD>Nor is their a need to since multiple walls can be specified
+in one command. 
+
+<DT><I>Cannot use fix wall/srd without fix srd</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Cannot use fix wall/srd zlo/zhi for a 2d simulation</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Cannot use force/neigh with triclinic box</I> 
+
+<DD>This is a current limitation of the GPU implementation
+in LAMMPS. 
+
 <DT><I>Cannot use kspace solver on system with no charge</I> 
 
 <DD>No atoms in system have a non-zero charge. 
@@ -1115,13 +1203,26 @@ together.
 the simulation box is very small in some dimension, compared to the
 neighbor cutoff.  Use the "nsq" style instead of "bin" style. 
 
-<DT><I>Cannot use newton pair with GPU GayBerne pair style</I> 
+<DT><I>Cannot use newton pair with GPU CHARMM pair style</I> 
 
-<DD>Self-explanatory. 
+<DD>See the newton command to change the setting. 
 
-<DT><I>Cannot use newton pair with GPU lj/cut pair style</I> 
+<DT><I>Cannot use newton pair with GPU Gay-Berne pair style</I> 
 
-<DD>Self-explanatory. 
+<DD>See the newton command to change the setting. 
+
+<DT><I>Cannot use newton pair with GPU LJ pair style</I> 
+
+<DD>See the newton command to change the setting. 
+
+<DT><I>Cannot use newton pair with GPU LJ96 pair style</I> 
+
+<DD>See the newton command to change the setting. 
+
+<DT><I>Cannot use non-zero forces in an energy minimization</I> 
+
+<DD>Fix setforce cannot be used in this manner.  Use fix addforce
+instead. 
 
 <DT><I>Cannot use nonperiodic boundares with fix ttm</I> 
 
@@ -1160,6 +1261,10 @@ create_box command has been used.
 
 <DD>Atom IDs are not defined, so they cannot be used to identify an atom. 
 
+<DT><I>Cannot use swiggle in variable formula between runs</I> 
+
+<DD>This is a function of elapsed time. 
+
 <DT><I>Cannot use variable energy with constant force in fix addforce</I> 
 
 <DD>This is because for constant force, LAMMPS can compute the change
@@ -1170,6 +1275,14 @@ in energy directly.
 <DD>The format of DCD dump files requires snapshots be output
 at a constant frequency. 
 
+<DT><I>Cannot use variable every setting for dump xtc</I> 
+
+<DD>The format of this file requires snapshots at regular intervals. 
+
+<DT><I>Cannot use vdisplace in variable formula between runs</I> 
+
+<DD>This is a function of elapsed time. 
+
 <DT><I>Cannot use velocity create loop all unless atoms have IDs</I> 
 
 <DD>Atoms in the simulation to do not have IDs, so this style
@@ -1201,6 +1314,10 @@ triclinic.
 
 <DD>Self-explanatory. 
 
+<DT><I>Compute ID for compute atom/molecule does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Compute ID for compute reduce does not exist</I> 
 
 <DD>Self-explanatory. 
@@ -1237,6 +1354,46 @@ triclinic.
 
 <DD>The atom style does not support angles. 
 
+<DT><I>Compute atom/molecule compute array is accessed out-of-range</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule compute does not calculate a per-atom array</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule compute does not calculate a per-atom vector</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule compute does not calculate per-atom values</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule fix array is accessed out-of-range</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule fix does not calculate a per-atom array</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule fix does not calculate a per-atom vector</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule fix does not calculate per-atom values</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule requires molecular atom style</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute atom/molecule variable is not atom-style variable</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Compute bond/local used when bonds are not allowed</I> 
 
 <DD>The atom style does not support bonds. 
@@ -1246,6 +1403,15 @@ triclinic.
 <DD>This is because the computation of the centro-symmetry values
 uses a pairwise neighbor list. 
 
+<DT><I>Compute cluster/atom cutoff is longer than pairwise cutoff</I> 
+
+<DD>Cannot identify clusters beyond cutoff. 
+
+<DT><I>Compute cluster/atom requires a pair style be defined</I> 
+
+<DD>This is so that the pair style defines a cutoff distance which
+is used to find clusters. 
+
 <DT><I>Compute cna/atom cutoff is longer than pairwise cutoff</I> 
 
 <DD>Self-explantory. 
@@ -1339,6 +1505,10 @@ developers.
 
 <DD>Self-explanatory. 
 
+<DT><I>Compute pair must use group all</I> 
+
+<DD>Pair styles accumlate energy on all atoms. 
+
 <DT><I>Compute pe must use group all</I> 
 
 <DD>Energies computed by potentials (pair, bond, etc) are computed on all
@@ -1468,6 +1638,18 @@ used.
 
 <DD>Self-explanatory. 
 
+<DT><I>Compute ti kspace style does not exist</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute ti pair style does not exist</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Compute ti tail when pair style does not compute tail corrections</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Compute used in variable between runs is not current</I> 
 
 <DD>Computes cannot be invoked by a variable in between runs.  Thus they
@@ -1512,6 +1694,10 @@ temperature is 0.0.
 
 <DD>Self-explanatory. 
 
+<DT><I>Could not find compute ID for TAD</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Could not find compute ID for temperature bias</I> 
 
 <DD>Self-explanatory. 
@@ -1657,6 +1843,10 @@ does not exist.
 
 <DD>Self-explanatory. 
 
+<DT><I>Could not find or initialize a specified accelerator device</I> 
+
+<DD>Your GPU setup is invalid. 
+
 <DT><I>Could not find set group ID</I> 
 
 <DD>Group ID specified in set command does not exist. 
@@ -1827,7 +2017,7 @@ or the atoms are too far apart to make a valid dihedral.
 on a particular processor.  The pairwise cutoff is too short or the
 atoms are too far apart to make a valid dihedral. 
 
-<DT><I>Dihedral atoms %d %d %d %d missing on proc %d at step %d</I> 
+<DT><I>Dihedral atoms %d %d %d %d missing on proc %d at step</I> 
 
 <DD>One or more of 4 atoms needed to compute a particular dihedral are
 missing on this processor.  Typically this is because the pairwise
@@ -1942,6 +2132,10 @@ needs them.
 
 <DD>This is a requirement of the CFG output format. 
 
+<DT><I>Dump cfg requires one snapshot per file</I> 
+
+<DD>Use the wildcard "*" character in the filename. 
+
 <DT><I>Dump custom and fix not computed at compatible times</I> 
 
 <DD>The fix must produce per-atom quantities on timesteps that dump custom
@@ -1996,10 +2190,6 @@ dump output.
 
 <DD>The variable must return a timestep greater than the current timestep. 
 
-<DT><I>Dump in CFG format requires one snapshot per file</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Dump local and fix not computed at compatible times</I> 
 
 <DD>The fix must produce per-atom quantities on timesteps that dump local
@@ -2111,6 +2301,11 @@ dumped.
 <DD>Only per-atom quantities that are defined for the atom style being
 used are allowed. 
 
+<DT><I>Duplicate particle in PeriDynamic bond - simulation box is too small</I> 
+
+<DD>This is likely because your box length is shorter than 2 times
+the bond length. 
+
 <DT><I>Electronic temperature dropped below zero</I> 
 
 <DD>Something has gone wrong with the fix ttm electron temperature model. 
@@ -2160,6 +2355,10 @@ smaller simulation or on more processors.
 
 <DD>Self-explanatory. 
 
+<DT><I>Fix ID for compute atom/molecule does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Fix ID for compute reduce does not exist</I> 
 
 <DD>Self-explanatory. 
@@ -2232,27 +2431,30 @@ conservative settings.
 <DD>Reset the ATOMPERBIN parameter at the top of fix_srd.cpp
 to a larger value, and re-compile the code. 
 
-<DT><I>Fix adapt atom attribute is not recognized</I> 
+<DT><I>Fix SRD: too many walls in bin</I> 
 
-<DD>Self-explanatory 
+<DD>This should not happen unless your system has been setup incorrectly. 
 
-<DT><I>Fix adapt pair parameter is not recognized</I> 
+<DT><I>Fix adapt kspace style does not exist</I> 
 
-<DD>Self-explanatory 
+<DD>Self-explanatory. 
 
 <DT><I>Fix adapt pair style does not exist</I> 
 
 <DD>Self-explanatory 
 
-<DT><I>Fix adapt pair types are not valid</I> 
+<DT><I>Fix adapt pair style param not supported</I> 
 
-<DD>The specified types must be between 1 and Ntypes and be
-used by the pair style. 
+<DD>The pair style does not know about the parameter you specified. 
 
 <DT><I>Fix adapt requires atom attribute diameter</I> 
 
 <DD>The atom style being used does not specify an atom diameter. 
 
+<DT><I>Fix adapt type pair range is not valid for pair hybrid sub-style</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Fix ave/atom compute array is accessed out-of-range</I> 
 
 <DD>Self-explanatory. 
@@ -2466,10 +2668,6 @@ all intensive/extensive when turned into an array by fix ave/time.
 
 <DD>Self-explanatory. 
 
-<DT><I>Fix ave/time compute does not calculate a array</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Fix ave/time compute does not calculate a scalar</I> 
 
 <DD>Only computes that calculate a scalar or vector quantity (not a
@@ -2480,6 +2678,10 @@ per-atom quantity) can be used with fix ave/time.
 <DD>Only computes that calculate a scalar or vector quantity (not a
 per-atom quantity) can be used with fix ave/time. 
 
+<DT><I>Fix ave/time compute does not calculate an array</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Fix ave/time compute vector is accessed out-of-range</I> 
 
 <DD>The index for the vector is out of bounds. 
@@ -2488,10 +2690,6 @@ per-atom quantity) can be used with fix ave/time.
 
 <DD>Self-explanatory. 
 
-<DT><I>Fix ave/time fix does not calculate a array</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Fix ave/time fix does not calculate a scalar</I> 
 
 <DD>A fix used by fix ave/time must generate global values. 
@@ -2500,6 +2698,10 @@ per-atom quantity) can be used with fix ave/time.
 
 <DD>A fix used by fix ave/time must generate global values. 
 
+<DT><I>Fix ave/time fix does not calculate an array</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Fix ave/time fix vector is accessed out-of-range</I> 
 
 <DD>The index for the vector is out of bounds. 
@@ -2571,6 +2773,10 @@ is a triclinic (non-orthogonal) box.
 <DD>Not all regions represent bounded volumes.  You cannot use
 such a region with the fix deposit command. 
 
+<DT><I>Fix efield requires atom attribute q</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Fix evaporate molecule requires atom attribute molecule</I> 
 
 <DD>The atom style being used does not define a molecule ID. 
@@ -2804,6 +3010,14 @@ was exceeded.
 
 <DD>Self-explanatory. 
 
+<DT><I>Fix rigid atom has non-zero image flag in a non-periodic dimension</I> 
+
+<DD>You cannot set image flags for non-periodic dimensions. 
+
+<DT><I>Fix rigid molecule requires atom attribute molecule</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Fix rigid/nvt period must be > 0.0</I> 
 
 <DD>Self-explanatory 
@@ -2838,10 +3052,6 @@ it turns off bonds that should contribute to the energy.
 
 <DD>Self-explanatory. 
 
-<DT><I>Fix srd simulation box must be periodic</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Fix store/state compute array is accessed out-of-range</I> 
 
 <DD>Self-explanatory. 
@@ -2930,6 +3140,11 @@ details.
 
 <DD>Self-explanatory. 
 
+<DT><I>Fix used in compute atom/molecule not computed at compatible time</I> 
+
+<DD>The fix must produce per-atom quantities on timesteps that the compute
+needs them. 
+
 <DT><I>Fix used in compute reduce not computed at compatible time</I> 
 
 <DD>Fixes generate their values on specific timesteps.  Compute sum is
@@ -3008,6 +3223,14 @@ this fix.
 
 <DD>When using a "*" in the restart file name, no matching file was found. 
 
+<DT><I>GPU is not the first fix for this run</I> 
+
+<DD>This is the way the fix must be defined in your input script. 
+
+<DT><I>Gmask function in equal-style variable formula</I> 
+
+<DD>Gmask is per-atom operation. 
+
 <DT><I>Gravity changed since fix pour was created</I> 
 
 <DD>Gravity must be static and not dynamic for use with fix pour. 
@@ -3020,6 +3243,10 @@ this fix.
 
 <DD>Gravity must be pointing "down" in a 3d box, i.e. theta = 180.0. 
 
+<DT><I>Grmask function in equal-style variable formula</I> 
+
+<DD>Grmask is per-atom operation. 
+
 <DT><I>Group ID does not exist</I> 
 
 <DD>A group ID used in the group command does not exist. 
@@ -3062,6 +3289,10 @@ invalid.
 
 <DD>The name is too long to be a chemical element. 
 
+<DT><I>Illegal fix gpu command</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Illegal number of angle table entries</I> 
 
 <DD>There must be at least 2 table entries. 
@@ -3090,7 +3321,7 @@ or the atoms are too far apart to make a valid improper.
 on a particular processor.  The pairwise cutoff is too short or the
 atoms are too far apart to make a valid improper. 
 
-<DT><I>Improper atoms %d %d %d %d missing on proc %d at step %d</I> 
+<DT><I>Improper atoms %d %d %d %d missing on proc %d at step</I> 
 
 <DD>One or more of 4 atoms needed to compute a particular improper are
 missing on this processor.  Typically this is because the pairwise
@@ -3278,6 +3509,14 @@ simulation box.
 
 <DD>Eigensolve for rigid body was not sufficiently accurate. 
 
+<DT><I>Insufficient memory on accelerator (or no fix gpu)</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Invalid Boolean syntax in if command</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Invalid REAX atom type</I> 
 
 <DD>There is a mis-match between LAMMPS atom types and the elements
@@ -3403,18 +3642,10 @@ types.
 
 <DD>Self-explanatory.  Check the fix shake command in the input script. 
 
-<DT><I>Invalid coeffs for this angle style</I> 
-
-<DD>Cannot set class 2 coeffs in data file for this angle style. 
-
 <DT><I>Invalid coeffs for this dihedral style</I> 
 
 <DD>Cannot set class 2 coeffs in data file for this dihedral style. 
 
-<DT><I>Invalid coeffs for this improper style</I> 
-
-<DD>Cannot set class 2 coeffs in data file for this improper style. 
-
 <DT><I>Invalid command-line argument</I> 
 
 <DD>One or more command-line arguments is invalid.  Check the syntax of
@@ -3504,6 +3735,10 @@ the command you are using to launch LAMMPS.
 
 <DD>Atom style does not allow dihedrals. 
 
+<DT><I>Invalid delta_conf in tad command</I> 
+
+<DD>The value must be between 0 and 1 inclusive. 
+
 <DT><I>Invalid density in Atoms section of data file</I> 
 
 <DD>Density value cannot be <= 0.0. 
@@ -3707,15 +3942,6 @@ improper types.
 
 <DD>Self-explanatory. 
 
-<DT><I>Invalid natoms for dump dcd</I> 
-
-<DD>Natoms is initially 0 which is not valid for the dump dcd style.
-Natoms must be constant for the duration of the simulation. 
-
-<DT><I>Invalid natoms for dump xtc</I> 
-
-<DD>Natoms is initially 0 which is not valid for the dump xtc style. 
-
 <DT><I>Invalid option in lattice command for non-custom style</I> 
 
 <DD>Certain lattice keywords are not supported unless the
@@ -3752,10 +3978,6 @@ kspace, etc.
 
 <DD>Random number seed must be > 0. 
 
-<DT><I>Invalid region in group function in variable formula</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Invalid region style</I> 
 
 <DD>The choice of region style is unknown. 
@@ -3764,6 +3986,19 @@ kspace, etc.
 
 <DD>Self-explanatory. 
 
+<DT><I>Invalid run command N value</I> 
+
+<DD>The number of timesteps must fit in a 32-bit integer.  If you want to
+run for more steps than this, perform multiple shorter runs. 
+
+<DT><I>Invalid run command start/stop value</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Invalid run command upto value</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Invalid seed for Marsaglia random # generator</I> 
 
 <DD>The initial seed for this random number generator must be a positive
@@ -3806,10 +4041,18 @@ integer.
 
 <DD>Self-explanatory. 
 
+<DT><I>Invalid t_event in tad command</I> 
+
+<DD>The value must be greater than 0. 
+
 <DT><I>Invalid thermo keyword in variable formula</I> 
 
 <DD>The keyword is not recognized. 
 
+<DT><I>Invalid tmax in tad command</I> 
+
+<DD>The value must be greater than 0.0. 
+
 <DT><I>Invalid type for dipole set</I> 
 
 <DD>Dipole command must set a type from 1-N where N is the number of atom
@@ -3930,21 +4173,17 @@ sc, bcc, or fcc lattice.
 
 <DD>Self-explanatory. 
 
-<DT><I>Lost atoms via displace_atoms: original %.15g current %.15g</I> 
-
-<DD>The displace_atoms command lost one or more atoms. 
+<DT><I>MEAM library error %d</I> 
 
-<DT><I>Lost atoms via displace_box: original %.15g current %.15g</I> 
+<DD>A call to the MEAM Fortran library returned an error. 
 
-<DD>The displace_box command lost one or more atoms. 
+<DT><I>MPI_LMP_BIGINT and bigint in lmptype.h are not compatible</I> 
 
-<DT><I>Lost atoms: original %.15g current %.15g</I> 
+<DD>The size of the MPI datatype does not match the size of a bigint. 
 
-<DD>A thermodynamic computation has detected lost atoms. 
+<DT><I>MPI_LMP_TAGINT and tagint in lmptype.h are not compatible</I> 
 
-<DT><I>MEAM library error %d</I> 
-
-<DD>A call to the MEAM Fortran library returned an error. 
+<DD>The size of the MPI datatype does not match the size of a tagint. 
 
 <DT><I>Mass command before simulation box is defined</I> 
 
@@ -3986,6 +4225,15 @@ values is used in an equal-style variable formula.
 produces per-atom values is used in an equal-style variable
 formula. 
 
+<DT><I>Molecular data file has too many atoms</I> 
+
+<DD>These kids of data files are currently limited to a number
+of atoms that fits in a 32-bit integer. 
+
+<DT><I>Molecule count changed in compute atom/molecule</I> 
+
+<DD>Number of molecules must remain constant over time. 
+
 <DT><I>Molecule count changed in compute com/molecule</I> 
 
 <DD>Number of molecules must remain constant over time. 
@@ -4142,10 +4390,6 @@ by a fix shake command.
 
 <DD>Self-explanatory. 
 
-<DT><I>Must use a molecular atom style with fix rigid molecule</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Must use a z-axis cylinder with fix pour</I> 
 
 <DD>The axis of the cylinder region used with the fix pour command must
@@ -4160,17 +4404,6 @@ command.
 
 <DD>Self-explanatory. 
 
-<DT><I>Must use charged atom style with fix efield</I> 
-
-<DD>The atom style being used does not allow atoms to have assigned
-charges.  Hence it will not work with this fix which generates a force
-due to an E-field acting on charge. 
-
-<DT><I>Must use molecular atom style with neigh_modify exclude molecule</I> 
-
-<DD>The atom style must define a molecule ID to use the exclude
-option. 
-
 <DT><I>Must use pair_style comb with fix qeq/comb</I> 
 
 <DD>Self-explanatory. 
@@ -4197,6 +4430,10 @@ force during minimization.
 <DD>The header of the data file indicated that bonds or angles or
 dihedrals or impropers would be included, but they were not present. 
 
+<DT><I>Neigh_modify exclude molecule requires atom attribute molecule</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Neigh_modify include group != atom_modify first group</I> 
 
 <DD>Self-explanatory. 
@@ -4207,12 +4444,20 @@ dihedrals or impropers would be included, but they were not present.
 inconsistent.  If the delay setting is non-zero, then it must be a
 multiple of the every setting. 
 
+<DT><I>Neighbor include group not allowed with ghost neighbors</I> 
+
+<DD>This is a current restriction within LAMMPS. 
+
 <DT><I>Neighbor list overflow, boost neigh_modify one or page</I> 
 
 <DD>There are too many neighbors of a single atom.  Use the neigh_modify
 command to increase the neighbor page size and the max number of
 neighbors allowed for one atom. 
 
+<DT><I>Neighbor multi not yet enabled for ghost neighbors</I> 
+
+<DD>This is a current restriction within LAMMPS. 
+
 <DT><I>Neighbor multi not yet enabled for granular</I> 
 
 <DD>Self-explanatory. 
@@ -4225,6 +4470,10 @@ neighbors allowed for one atom.
 
 <DD>This is required to prevent wasting too much memory. 
 
+<DT><I>Neighbors of ghost atoms only allowed for full neighbor lists</I> 
+
+<DD>This is a current restriction within LAMMPS. 
+
 <DT><I>New bond exceeded bonds per atom in fix bond/create</I> 
 
 <DD>See the read_data command for info on setting the "extra bond per
@@ -4299,6 +4548,10 @@ output to dump file.
 <DD>The EAM potential file does not contain elements that match the
 requested elements. 
 
+<DT><I>No pair hbond/dreiding coefficients set</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>No pair style defined for compute group/group</I> 
 
 <DD>Cannot calculate group interactions without a pair style defined. 
@@ -4623,6 +4876,22 @@ does not support them.
 <DD>Atoms in the simulation do not have IDs, so history effects
 cannot be tracked by the granular pair potential. 
 
+<DT><I>Pair style hbond/dreiding requires an atom map, see atom_modify</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Pair style hbond/dreiding requires atom IDs</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Pair style hbond/dreiding requires molecular system</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Pair style hbond/dreiding requires newton pair on</I> 
+
+<DD>See the newton command for details. 
+
 <DT><I>Pair style hybrid cannot have hybrid as an argument</I> 
 
 <DD>Self-explanatory. 
@@ -4749,7 +5018,7 @@ read_restart, or create_box command.
 <DD>Particles must be "exterior" to the wall in order for energy/force to
 be calculated. 
 
-<DT><I>Particle on or inside fix wall/region surface</I> 
+<DT><I>Particle on or inside surface of region used in fix wall/region</I> 
 
 <DD>Particles must be "exterior" to the region surface in order for
 energy/force to be calculated. 
@@ -4768,16 +5037,17 @@ variable doc page for ideas on how to make this work.
 
 <DD>Equal-style variables cannot use per-atom quantities. 
 
-<DT><I>Per-atom virial not available with GPU Gay-Berne</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Per-atom virial was not tallied on needed timestep</I> 
 
 <DD>You are using a thermo keyword that requires potentials to have
 tallied the virial, but they didn't on this timestep.  See the
 variable doc page for ideas on how to make this work. 
 
+<DT><I>Per-processor system is too big</I> 
+
+<DD>The number of owned atoms plus ghost atoms on a single
+processor must fit in 32-bit integer. 
+
 <DT><I>Potential energy ID for fix neb does not exist</I> 
 
 <DD>Self-explanatory. 
@@ -4896,10 +5166,6 @@ library and re-build LAMMPS.
 
 <DD>Self-explanatory. 
 
-<DT><I>Region ID for compute temp reduce/region does not exist</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Region ID for compute temp/region does not exist</I> 
 
 <DD>Self-explanatory. 
@@ -4916,6 +5182,10 @@ library and re-build LAMMPS.
 
 <DD>Self-explanatory. 
 
+<DT><I>Region ID for fix ave/spatial does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Region ID for fix aveforce does not exist</I> 
 
 <DD>Self-explanatory. 
@@ -4940,6 +5210,10 @@ library and re-build LAMMPS.
 
 <DD>Self-explanatory. 
 
+<DT><I>Region ID in variable formula does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Region cannot have 0 length rotation vector</I> 
 
 <DD>Self-explanatory. 
@@ -4975,6 +5249,19 @@ or create_box command.
 to processors.  This is likely due to some atom coordinates being
 outside a non-periodic simulation box. 
 
+<DT><I>Replicated molecular system atom IDs are too big</I> 
+
+<DD>See the setting for the allowed atom ID size in the src/lmptype.h
+file. 
+
+<DT><I>Replicated system is too big</I> 
+
+<DD>See the setting for bigint in the src/lmptype.h file. 
+
+<DT><I>Resetting timestep is not allowed with fix move</I> 
+
+<DD>This is because fix move is moving atoms based on elapsed time. 
+
 <DT><I>Respa inner cutoffs are invalid</I> 
 
 <DD>The first cutoff must be <= the second cutoff. 
@@ -5011,6 +5298,10 @@ more non-collinear atoms, even with joint atoms removed.
 else the rigid fix contribution to the pressure virial is
 incorrect. 
 
+<DT><I>Rmask function in equal-style variable formula</I> 
+
+<DD>Rmask is per-atom operation. 
+
 <DT><I>Run command before simulation box is defined</I> 
 
 <DD>The run command cannot be used before a read_data, read_restart, or
@@ -5024,10 +5315,6 @@ create_box command.
 
 <DD>Self-explanatory. 
 
-<DT><I>Run command upto value is before current timestep</I> 
-
-<DD>Self-explanatory. 
-
 <DT><I>Run_style command before simulation box is defined</I> 
 
 <DD>The run_style command cannot be used before a read_data,
@@ -5041,10 +5328,9 @@ read_restart, or create_box command.
 
 <DD>The bin shape is not within tolerance of cubic. 
 
-<DT><I>SRD particle %d started inside big particle %d on step %d bounce %d</I> 
+<DT><I>Same dimension twice in fix ave/spatial</I> 
 
-<DD>This may not be a problem, but indicates one or more SRD particles are
-being left inside solute particles. 
+<DD>Self-explanatory. 
 
 <DT><I>Set command before simulation box is defined</I> 
 
@@ -5065,19 +5351,19 @@ or create_box command.
 command that are the same angle type, must also have the same bond
 types for the 2 bonds in the angle. 
 
-<DT><I>Shake atoms %d %d %d %d missing on proc %d at step %d</I> 
+<DT><I>Shake atoms %d %d %d %d missing on proc %d at step</I> 
 
 <DD>The 4 atoms in a single shake cluster specified by the fix shake
 command are not all accessible to a processor.  This probably means
 an atom has moved too far. 
 
-<DT><I>Shake atoms %d %d %d missing on proc %d at step %d</I> 
+<DT><I>Shake atoms %d %d %d missing on proc %d at step</I> 
 
 <DD>The 3 atoms in a single shake cluster specified by the fix shake
 command are not all accessible to a processor.  This probably means
 an atom has moved too far. 
 
-<DT><I>Shake atoms %d %d missing on proc %d at step %d</I> 
+<DT><I>Shake atoms %d %d missing on proc %d at step</I> 
 
 <DD>The 2 atoms in a single shake cluster specified by the fix shake
 command are not all accessible to a processor.  This probably means
@@ -5107,6 +5393,15 @@ SHAKE fix contribution to the pressure virial is incorrect.
 
 <DD>Self-explanatory. 
 
+<DT><I>Smallint setting in lmptype.h is invalid</I> 
+
+<DD>It has to be the size of an integer. 
+
+<DT><I>Smallint setting in lmptype.h is not compatible</I> 
+
+<DD>Smallint stored in restart file is not consistent with LAMMPS version
+you are running. 
+
 <DT><I>Sqrt of negative value in variable formula</I> 
 
 <DD>Self-explanatory. 
@@ -5116,6 +5411,14 @@ SHAKE fix contribution to the pressure virial is incorrect.
 <DD>Input script line contained a variable that could not be substituted
 for. 
 
+<DT><I>System in data file is too big</I> 
+
+<DD>See the setting for bigint in the src/lmptype.h file. 
+
+<DT><I>TAD nsteps must be multiple of t_event</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>TIP4P hydrogen has incorrect atom type</I> 
 
 <DD>The TIP4P pairwise computation found an H atom whose type does not
@@ -5131,6 +5434,19 @@ within a water molecule.
 <DD>The target file for the fix tmd command did not list all atoms in the
 fix group. 
 
+<DT><I>Tad command before simulation box is defined</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Tagint setting in lmptype.h is invalid</I> 
+
+<DD>Tagint must be as large or larger than smallint. 
+
+<DT><I>Tagint setting in lmptype.h is not compatible</I> 
+
+<DD>Smallint stored in restart file is not consistent with LAMMPS version
+you are running. 
+
 <DT><I>Target temperature for fix nvt/npt/nph cannot be 0.0</I> 
 
 <DD>Self-explanatory. 
@@ -5320,6 +5636,10 @@ is not computing this quantity.
 <DD>Cannot use thermo_modify to set this parameter since the thermo_style
 is not computing this quantity. 
 
+<DT><I>Thermo_modify int format does not contain d character</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Thermo_modify pressure ID does not compute pressure</I> 
 
 <DD>The specified compute ID does not compute pressure. 
@@ -5347,11 +5667,17 @@ not defined by the atom style used in this simulation.
 
 <DD>Specified timestep size is invalid. 
 
-<DT><I>Too big a problem to replicate with molecular atom style</I> 
+<DT><I>Too big a problem to use velocity create loop all</I> 
+
+<DD>The system size must fit in a 32-bit integer to use this option. 
 
-<DD>Molecular problems cannot become bigger than 2^31 atoms (or bonds,
-etc) when replicated, else the atom IDs and other quantities cannot be
-stored in 32-bit quantities. 
+<DT><I>Too big a timestep for dump dcd</I> 
+
+<DD>The timestep must fit in a 32-bit integer to use this dump style. 
+
+<DT><I>Too big a timestep for dump xtc</I> 
+
+<DD>The timestep must fit in a 32-bit integer to use this dump style. 
 
 <DT><I>Too few bits for lookup table</I> 
 
@@ -5363,6 +5689,16 @@ machine's floating point representation.
 <DD>This is likely due to an immense simulation box that has blown up
 to a large size. 
 
+<DT><I>Too many atoms for dump dcd</I> 
+
+<DD>The system size must fit in a 32-bit integer to use this dump
+style. 
+
+<DT><I>Too many atoms for dump xtc</I> 
+
+<DD>The system size must fit in a 32-bit integer to use this dump
+style. 
+
 <DT><I>Too many atoms to dump sort</I> 
 
 <DD>Cannot sort when running with more than 2^31 atoms. 
@@ -5377,6 +5713,11 @@ machine's floating point representation.
 <DD>The maximum number of atom groups (including the "all" group) is 
 given by MAX_GROUP in group.cpp and is 32. 
 
+<DT><I>Too many iterations</I> 
+
+<DD>You must use a number of iterations that fit in a 32-bit integer 
+for minimization. 
+
 <DT><I>Too many mantissa bits for lookup table</I> 
 
 <DD>Table size specified via pair_modify command does not work with your
@@ -5392,6 +5733,15 @@ types.
 <DD>This is likely due to an immense simulation box that has blown up
 to a large size. 
 
+<DT><I>Too many timesteps for NEB</I> 
+
+<DD>You must use a number of timesteps that fit in a 32-bit integer 
+for NEB. 
+
+<DT><I>Too many total atoms</I> 
+
+<DD>See the setting for bigint in the src/lmptype.h file. 
+
 <DT><I>Too many total bits for bitmapped lookup table</I> 
 
 <DD>Table size specified via pair_modify command is too large.  Note that
@@ -5403,6 +5753,11 @@ a value of N generates a 2^N size table.
 MAXTOUCH parameter in fix_shear_history.cpp must be set larger and
 LAMMPS must be re-built. 
 
+<DT><I>Too much per-proc info for dump</I> 
+
+<DD>Number of local atoms times number of columns must fit in a 32-bit
+integer for dump. 
+
 <DT><I>Tree structure in joint connections</I> 
 
 <DD>Fix poems cannot (yet) work with coupled bodies whose joints connect
@@ -5477,6 +5832,10 @@ valid.
 <DD>The lattice type in an entry of the MEAM parameter file is not
 valid. 
 
+<DT><I>Unrecognized pair style in compute pair command</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Use of compute temp/ramp with undefined lattice</I> 
 
 <DD>Must use lattice command with compute temp/ramp command if units
@@ -5530,11 +5889,6 @@ set to lattice.
 <DD>Must use lattice command with fix wall command if units option is set
 to lattice. 
 
-<DT><I>Use of fix wall/reflect with undefined lattice</I> 
-
-<DD>If scale = lattice (the default) for the fix wall/reflect command,
-then a lattice must first be defined via the lattice command. 
-
 <DT><I>Use of region with undefined lattice</I> 
 
 <DD>If scale = lattice (the default) for the region command, then a
@@ -5564,6 +5918,10 @@ deform needs to be used.
 <DD>Cannot evaluate a compute or fix or atom-based value in a variable
 before the simulation has been setup. 
 
+<DT><I>Variable for compute ti is invalid style</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Variable for dump every is invalid style</I> 
 
 <DD>Only equal-style variables can be used. 
@@ -5572,6 +5930,10 @@ before the simulation has been setup.
 
 <DD>Only equal-style variables can be used. 
 
+<DT><I>Variable for fix addforce is invalid style</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Variable for fix aveforce is invalid style</I> 
 
 <DD>Only equal-style variables can be used. 
@@ -5596,14 +5958,34 @@ before the simulation has been setup.
 
 <DD>Only equal-style variables can be used. 
 
+<DT><I>Variable for fix wall is invalid style</I> 
+
+<DD>Only equal-style variables can be used. 
+
 <DT><I>Variable for fix wall/reflect is invalid style</I> 
 
 <DD>Only equal-style variables can be used. 
 
+<DT><I>Variable for fix wall/srd is invalid style</I> 
+
+<DD>Only equal-style variables can be used. 
+
+<DT><I>Variable for region is invalid style</I> 
+
+<DD>Only equal-style variables can be used. 
+
+<DT><I>Variable for region is not equal style</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Variable for thermo every is invalid style</I> 
 
 <DD>Only equal-style variables can be used. 
 
+<DT><I>Variable for velocity set is invalid style</I> 
+
+<DD>Only atom-style variables can be used. 
+
 <DT><I>Variable formula compute array is accessed out-of-range</I> 
 
 <DD>Self-explanatory. 
@@ -5620,10 +6002,18 @@ before the simulation has been setup.
 
 <DD>Self-explanatory. 
 
+<DT><I>Variable name for compute atom/molecule does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Variable name for compute reduce does not exist</I> 
 
 <DD>Self-explanatory. 
 
+<DT><I>Variable name for compute ti does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Variable name for dump every does not exist</I> 
 
 <DD>Self-explanatory. 
@@ -5680,7 +6070,19 @@ before the simulation has been setup.
 
 <DD>Self-explanatory. 
 
-<DT><I>Variable name for fix wall/relect does not exist</I> 
+<DT><I>Variable name for fix wall does not exist</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Variable name for fix wall/reflect does not exist</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Variable name for fix wall/srd does not exist</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Variable name for region does not exist</I> 
 
 <DD>Self-explanatory. 
 
@@ -5688,6 +6090,10 @@ before the simulation has been setup.
 
 <DD>Self-explanatory. 
 
+<DT><I>Variable name for velocity set does not exist</I> 
+
+<DD>Self-explanatory. 
+
 <DT><I>Variable name must be alphanumeric or underscore characters</I> 
 
 <DD>Self-explanatory. 
@@ -5716,6 +6122,23 @@ temperature.
 have tallied the virial, but they didn't on this timestep.  See the
 variable doc page for ideas on how to make this work. 
 
+<DT><I>Wall defined twice in fix wall command</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Wall defined twice in fix wall/reflect command</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Wall defined twice in fix wall/srd command</I> 
+
+<DD>Self-explanatory. 
+
+<DT><I>Weighted neighbor list values are too big</I> 
+
+<DD>You must have less atoms per processor to use this
+style neighbor list. 
+
 <DT><I>World variable count doesn't match # of partitions</I> 
 
 <DD>A world-style variable must specify a number of values equal to the
@@ -5751,6 +6174,12 @@ want.
 <DD>See the doc page for fix bond/break for more info on this
 restriction. 
 
+<DT><I>Building an occasional neighobr list when atoms may have moved too far</I> 
+
+<DD>This can cause LAMMPS to crash when the neighbor list is built.
+The solution is to check for building the regular neighbor lists
+more frequently. 
+
 <DT><I>Compute cna/atom cutoff may be too large to find ghost atom neighbors</I> 
 
 <DD>The neighbor cutoff used may not encompass enough ghost atoms
@@ -5788,6 +6217,10 @@ will be truncated to attempt to prevent the bond from blowing up.
 <DD>A FENE bond has stretched dangerously far.  It's interaction strength
 will be truncated to attempt to prevent the bond from blowing up. 
 
+<DT><I>Fix SRD walls overlap but fix srd overlap not set</I> 
+
+<DD>You likely want to set this in your input script. 
+
 <DT><I>Fix bond/swap will ignore defined angles</I> 
 
 <DD>See the doc page for fix bond/swap for more info on this
@@ -5814,6 +6247,10 @@ fix recenter should come last.
 
 <DD>This may cause accuracy problems. 
 
+<DT><I>Fix srd no-slip wall collisions with bin shifting</I> 
+
+<DD>This is an inconsistent setting in your input script. 
+
 <DT><I>Fix srd particle moved outside valid domain</I> 
 
 <DD>This may indicate a problem with your simulation parameters. 
@@ -5879,6 +6316,10 @@ on the same group of atoms that velocities are being set for.
 
 <DD>It is not efficient to use compute centro/atom  more than once. 
 
+<DT><I>More than one compute cluster/atom</I> 
+
+<DD>It is not efficient to use compute cluster/atom  more than once. 
+
 <DT><I>More than one compute cna/atom defined</I> 
 
 <DD>It is not efficient to use compute cna/atom  more than once. 
@@ -5988,6 +6429,13 @@ every = 1, check = yes.  Since these settings were not in place,
 LAMMPS changed them and will restore them to their original values
 after the PRD simulation. 
 
+<DT><I>Resetting reneighboring criteria during TAD</I> 
+
+<DD>A TAD simulation requires that neigh_modify settings be delay = 0,
+every = 1, check = yes.  Since these settings were not in place,
+LAMMPS changed them and will restore them to their original values
+after the PRD simulation. 
+
 <DT><I>Resetting reneighboring criteria during minimization</I> 
 
 <DD>Minimization requires that neigh_modify settings be delay = 0, every =
diff --git a/doc/Section_errors.txt b/doc/Section_errors.txt
index 8706782413..d94e8a9be7 100644
--- a/doc/Section_errors.txt
+++ b/doc/Section_errors.txt
@@ -233,7 +233,7 @@ The set command cannot find one or more atoms in a particular angle on
 a particular processor.  The pairwise cutoff is too short or the atoms
 are too far apart to make a valid angle. :dd
 
-{Angle atoms %d %d %d missing on proc %d at step %d} :dt
+{Angle atoms %d %d %d missing on proc %d at step} :dt
 
 One or more of 3 atoms needed to compute a particular angle are
 missing on this processor.  Typically this is because the pairwise
@@ -316,14 +316,6 @@ Argument of arccos() must be between -1 and 1. :dd
 
 Argument of arcsin() must be between -1 and 1. :dd
 
-{At least 1 proc could not allocate a CUDA gpu or memory} :dt
-
-You are not setup correctly to use a GPU from your CPU. :dd
-
-{At least one process could not allocate a CUDA-enabled gpu} :dt
-
-Self-explanatory. :dd
-
 {Atom IDs must be consecutive for velocity create loop all} :dt
 
 Self-explanatory. :dd
@@ -403,6 +395,14 @@ Cannot rescale a temperature that is already 0.0. :dd
 Two atoms in a FENE bond have become so far apart that the bond cannot
 be computed. :dd
 
+{Bad TIP4P angle type for PPPM/TIP4P} :dt
+
+Specified angle type is not valid. :dd
+
+{Bad TIP4P bond type for PPPM/TIP4P} :dt
+
+Specified bond type is not valid. :dd
+
 {Bad grid of processors} :dt
 
 The 3d grid of processors defined by the processors command does not
@@ -434,6 +434,15 @@ compute. :dd
 
 Big particles must be extended spheriods or ellipsoids. :dd
 
+{Bigint setting in lmptype.h is invalid} :dt
+
+Size of bigint is less than size of tagint. :dd
+
+{Bigint setting in lmptype.h is not compatible} :dt
+
+Bigint stored in restart file is not consistent with LAMMPS version
+you are running. :dd
+
 {Bitmapped lookup tables require int/float be same size} :dt
 
 Cannot use pair tables on this machine, because of word sizes.  Use
@@ -465,7 +474,7 @@ The set command cannot find one or more atoms in a particular bond on
 a particular processor.  The pairwise cutoff is too short or the atoms
 are too far apart to make a valid bond. :dd
 
-{Bond atoms %d %d missing on proc %d at step %d} :dt
+{Bond atoms %d %d missing on proc %d at step} :dt
 
 One or both of 2 atoms needed to compute a particular bond are
 missing on this processor.  Typically this is because the pairwise
@@ -572,10 +581,18 @@ See the region prism command for details. :dd
 
 This is current restriction for NEB as implemented in LAMMPS. :dd
 
+{Can only use TAD with 1-processor replicas for NEB} :dt
+
+This is current restriction for NEB as implemented in LAMMPS. :dd
+
 {Cannot (yet) use PPPM with triclinic box} :dt
 
 This feature is not yet supported. :dd
 
+{Cannot add atoms to fix move variable} :dt
+
+Atoms can not be added afterwards to this fix option. :dd
+
 {Cannot change box to orthogonal when tilt is non-zero} :dt
 
 Self-explanatory :dd
@@ -622,6 +639,11 @@ but the atoms that have been defined have no IDs. :dd
 Must use the lattice command before using the create_atoms
 command. :dd
 
+{Cannot create/grow a vector/array of pointers for %s} :dt
+
+LAMMPS code is making an illegal call to the templated memory
+allocaters, to create a vector or array of pointers. :dd
+
 {Cannot create_atoms after reading restart file with per-atom info} :dt
 
 The per-atom info was stored to be used when by a fix that you
@@ -633,6 +655,10 @@ there will not be a correct amount of per-atom info. :dd
 The create_box command cannot be used after a read_data, read_restart,
 or create_box command. :dd
 
+{Cannot currently use pair reax with pair hybrid} :dt
+
+This is not yet supported. :dd
+
 {Cannot delete group all} :dt
 
 Self-explanatory. :dd
@@ -901,10 +927,6 @@ In the rRESPA integrator, you must compute pairwise potentials either
 all together (pair), or in pieces (inner/middle/outer).  You can't do
 both. :dd
 
-{Cannot set both vel and wiggle in fix wall command} :dt
-
-Self-explantory. :dd
-
 {Cannot set dipole for this atom style} :dt
 
 This atom style does not support dipole settings for each atom type. :dd
@@ -918,6 +940,14 @@ Self-explanatory. :dd
 This atom style does not support mass settings for each atom type.
 Instead they are defined on a per-atom basis in the data file. :dd
 
+{Cannot set non-zero image flag for non-periodic dimension} :dt
+
+Self-explanatory. :dd
+
+{Cannot set non-zero z velocity for 2d simulation} :dt
+
+Self-explanatory. :dd
+
 {Cannot set respa middle without inner/outer} :dt
 
 In the rRESPA integrator, you must define both a inner and outer
@@ -931,6 +961,10 @@ The atom style does not support this setting. :dd
 
 The attribute being set does not exist for the defined atom style. :dd
 
+{Cannot set variable z velocity for 2d simulation} :dt
+
+Self-explanatory. :dd
+
 {Cannot skew triclinic box in z for 2d simulation} :dt
 
 Self-explanatory. :dd
@@ -978,6 +1012,18 @@ which is enabled by default, via the atom_modify command. :dd
 
 Use the atom_modify command to create an atom map. :dd
 
+{Cannot use TAD unless atom map exists for NEB} :dt
+
+See atom_modify map command to set this. :dd
+
+{Cannot use TAD with a single replica for NEB} :dt
+
+NEB requires multiple replicas. :dd
+
+{Cannot use TAD with atom_modify sort enabled for NEB} :dt
+
+This is a current restriction of NEB. :dd
+
 {Cannot use a damped dynamics min style with fix box/relax} :dt
 
 This is a current restriction in LAMMPS.  Use another minimizer
@@ -988,6 +1034,14 @@ style. :dd
 This is a current restriction in LAMMPS.  Use another minimizer
 style. :dd
 
+{Cannot use compute cluster/atom unless atoms have IDs} :dt
+
+Atom IDs are used to identify clusters. :dd
+
+{Cannot use cwiggle in variable formula between runs} :dt
+
+This is a function of elapsed time. :dd
+
 {Cannot use delete_atoms unless atoms have IDs} :dt
 
 Your atoms do not have IDs, so the delete_atoms command cannot be
@@ -1004,6 +1058,10 @@ provided by an atom map.  An atom map does not exist (by default) for
 non-molecular problems.  Using the atom_modify map command will force
 an atom map to be created. :dd
 
+{Cannot use fix ave/spatial z for 2 dimensional model} :dt
+
+Self-explanatory. :dd
+
 {Cannot use fix bond/break with non-molecular systems} :dt
 
 Self-explanatory. :dd
@@ -1102,6 +1160,36 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Cannot use fix wall/reflect in periodic dimension} :dt
+
+Self-explanatory. :dd
+
+{Cannot use fix wall/reflect zlo/zhi for a 2d simulation} :dt
+
+Self-explanatory. :dd
+
+{Cannot use fix wall/srd in periodic dimension} :dt
+
+Self-explanatory. :dd
+
+{Cannot use fix wall/srd more than once} :dt
+
+Nor is their a need to since multiple walls can be specified
+in one command. :dd
+
+{Cannot use fix wall/srd without fix srd} :dt
+
+Self-explanatory. :dd
+
+{Cannot use fix wall/srd zlo/zhi for a 2d simulation} :dt
+
+Self-explanatory. :dd
+
+{Cannot use force/neigh with triclinic box} :dt
+
+This is a current limitation of the GPU implementation
+in LAMMPS. :dd
+
 {Cannot use kspace solver on system with no charge} :dt
 
 No atoms in system have a non-zero charge. :dd
@@ -1112,13 +1200,26 @@ Too many neighbor bins will be created.  This typically happens when
 the simulation box is very small in some dimension, compared to the
 neighbor cutoff.  Use the "nsq" style instead of "bin" style. :dd
 
-{Cannot use newton pair with GPU GayBerne pair style} :dt
+{Cannot use newton pair with GPU CHARMM pair style} :dt
 
-Self-explanatory. :dd
+See the newton command to change the setting. :dd
 
-{Cannot use newton pair with GPU lj/cut pair style} :dt
+{Cannot use newton pair with GPU Gay-Berne pair style} :dt
 
-Self-explanatory. :dd
+See the newton command to change the setting. :dd
+
+{Cannot use newton pair with GPU LJ pair style} :dt
+
+See the newton command to change the setting. :dd
+
+{Cannot use newton pair with GPU LJ96 pair style} :dt
+
+See the newton command to change the setting. :dd
+
+{Cannot use non-zero forces in an energy minimization} :dt
+
+Fix setforce cannot be used in this manner.  Use fix addforce
+instead. :dd
 
 {Cannot use nonperiodic boundares with fix ttm} :dt
 
@@ -1157,6 +1258,10 @@ create_box command has been used. :dd
 
 Atom IDs are not defined, so they cannot be used to identify an atom. :dd
 
+{Cannot use swiggle in variable formula between runs} :dt
+
+This is a function of elapsed time. :dd
+
 {Cannot use variable energy with constant force in fix addforce} :dt
 
 This is because for constant force, LAMMPS can compute the change
@@ -1167,6 +1272,14 @@ in energy directly. :dd
 The format of DCD dump files requires snapshots be output
 at a constant frequency. :dd
 
+{Cannot use variable every setting for dump xtc} :dt
+
+The format of this file requires snapshots at regular intervals. :dd
+
+{Cannot use vdisplace in variable formula between runs} :dt
+
+This is a function of elapsed time. :dd
+
 {Cannot use velocity create loop all unless atoms have IDs} :dt
 
 Atoms in the simulation to do not have IDs, so this style
@@ -1198,6 +1311,10 @@ triclinic. :dd
 
 Self-explanatory. :dd
 
+{Compute ID for compute atom/molecule does not exist} :dt
+
+Self-explanatory. :dd
+
 {Compute ID for compute reduce does not exist} :dt
 
 Self-explanatory. :dd
@@ -1234,6 +1351,46 @@ Self-explanatory. :dd
 
 The atom style does not support angles. :dd
 
+{Compute atom/molecule compute array is accessed out-of-range} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule compute does not calculate a per-atom array} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule compute does not calculate a per-atom vector} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule compute does not calculate per-atom values} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule fix array is accessed out-of-range} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule fix does not calculate a per-atom array} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule fix does not calculate a per-atom vector} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule fix does not calculate per-atom values} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule requires molecular atom style} :dt
+
+Self-explanatory. :dd
+
+{Compute atom/molecule variable is not atom-style variable} :dt
+
+Self-explanatory. :dd
+
 {Compute bond/local used when bonds are not allowed} :dt
 
 The atom style does not support bonds. :dd
@@ -1243,6 +1400,15 @@ The atom style does not support bonds. :dd
 This is because the computation of the centro-symmetry values
 uses a pairwise neighbor list. :dd
 
+{Compute cluster/atom cutoff is longer than pairwise cutoff} :dt
+
+Cannot identify clusters beyond cutoff. :dd
+
+{Compute cluster/atom requires a pair style be defined} :dt
+
+This is so that the pair style defines a cutoff distance which
+is used to find clusters. :dd
+
 {Compute cna/atom cutoff is longer than pairwise cutoff} :dt
 
 Self-explantory. :dd
@@ -1336,6 +1502,10 @@ The atom style does not support impropers. :dd
 
 Self-explanatory. :dd
 
+{Compute pair must use group all} :dt
+
+Pair styles accumlate energy on all atoms. :dd
+
 {Compute pe must use group all} :dt
 
 Energies computed by potentials (pair, bond, etc) are computed on all
@@ -1465,6 +1635,18 @@ An atom style that defines these attributes must be used. :dd
 
 Self-explanatory. :dd
 
+{Compute ti kspace style does not exist} :dt
+
+Self-explanatory. :dd
+
+{Compute ti pair style does not exist} :dt
+
+Self-explanatory. :dd
+
+{Compute ti tail when pair style does not compute tail corrections} :dt
+
+Self-explanatory. :dd
+
 {Compute used in variable between runs is not current} :dt
 
 Computes cannot be invoked by a variable in between runs.  Thus they
@@ -1509,6 +1691,10 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Could not find compute ID for TAD} :dt
+
+Self-explanatory. :dd
+
 {Could not find compute ID for temperature bias} :dt
 
 Self-explanatory. :dd
@@ -1654,6 +1840,10 @@ The compute ID for computing temperature does not exist. :dd
 
 Self-explanatory. :dd
 
+{Could not find or initialize a specified accelerator device} :dt
+
+Your GPU setup is invalid. :dd
+
 {Could not find set group ID} :dt
 
 Group ID specified in set command does not exist. :dd
@@ -1824,7 +2014,7 @@ The set command cannot find one or more atoms in a particular dihedral
 on a particular processor.  The pairwise cutoff is too short or the
 atoms are too far apart to make a valid dihedral. :dd
 
-{Dihedral atoms %d %d %d %d missing on proc %d at step %d} :dt
+{Dihedral atoms %d %d %d %d missing on proc %d at step} :dt
 
 One or more of 4 atoms needed to compute a particular dihedral are
 missing on this processor.  Typically this is because the pairwise
@@ -1939,6 +2129,10 @@ needs them. :dd
 
 This is a requirement of the CFG output format. :dd
 
+{Dump cfg requires one snapshot per file} :dt
+
+Use the wildcard "*" character in the filename. :dd
+
 {Dump custom and fix not computed at compatible times} :dt
 
 The fix must produce per-atom quantities on timesteps that dump custom
@@ -1993,10 +2187,6 @@ Use the dump_modify sort command to enable this. :dd
 
 The variable must return a timestep greater than the current timestep. :dd
 
-{Dump in CFG format requires one snapshot per file} :dt
-
-Self-explanatory. :dd
-
 {Dump local and fix not computed at compatible times} :dt
 
 The fix must produce per-atom quantities on timesteps that dump local
@@ -2108,6 +2298,11 @@ dumped. :dd
 Only per-atom quantities that are defined for the atom style being
 used are allowed. :dd
 
+{Duplicate particle in PeriDynamic bond - simulation box is too small} :dt
+
+This is likely because your box length is shorter than 2 times
+the bond length. :dd
+
 {Electronic temperature dropped below zero} :dt
 
 Something has gone wrong with the fix ttm electron temperature model. :dd
@@ -2157,6 +2352,10 @@ This is not allowed.  Make your SRD bin size smaller. :dd
 
 Self-explanatory. :dd
 
+{Fix ID for compute atom/molecule does not exist} :dt
+
+Self-explanatory. :dd
+
 {Fix ID for compute reduce does not exist} :dt
 
 Self-explanatory. :dd
@@ -2229,27 +2428,30 @@ conservative settings. :dd
 Reset the ATOMPERBIN parameter at the top of fix_srd.cpp
 to a larger value, and re-compile the code. :dd
 
-{Fix adapt atom attribute is not recognized} :dt
+{Fix SRD: too many walls in bin} :dt
 
-Self-explanatory :dd
+This should not happen unless your system has been setup incorrectly. :dd
 
-{Fix adapt pair parameter is not recognized} :dt
+{Fix adapt kspace style does not exist} :dt
 
-Self-explanatory :dd
+Self-explanatory. :dd
 
 {Fix adapt pair style does not exist} :dt
 
 Self-explanatory :dd
 
-{Fix adapt pair types are not valid} :dt
+{Fix adapt pair style param not supported} :dt
 
-The specified types must be between 1 and Ntypes and be
-used by the pair style. :dd
+The pair style does not know about the parameter you specified. :dd
 
 {Fix adapt requires atom attribute diameter} :dt
 
 The atom style being used does not specify an atom diameter. :dd
 
+{Fix adapt type pair range is not valid for pair hybrid sub-style} :dt
+
+Self-explanatory. :dd
+
 {Fix ave/atom compute array is accessed out-of-range} :dt
 
 Self-explanatory. :dd
@@ -2463,10 +2665,6 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
-{Fix ave/time compute does not calculate a array} :dt
-
-Self-explanatory. :dd
-
 {Fix ave/time compute does not calculate a scalar} :dt
 
 Only computes that calculate a scalar or vector quantity (not a
@@ -2477,6 +2675,10 @@ per-atom quantity) can be used with fix ave/time. :dd
 Only computes that calculate a scalar or vector quantity (not a
 per-atom quantity) can be used with fix ave/time. :dd
 
+{Fix ave/time compute does not calculate an array} :dt
+
+Self-explanatory. :dd
+
 {Fix ave/time compute vector is accessed out-of-range} :dt
 
 The index for the vector is out of bounds. :dd
@@ -2485,10 +2687,6 @@ The index for the vector is out of bounds. :dd
 
 Self-explanatory. :dd
 
-{Fix ave/time fix does not calculate a array} :dt
-
-Self-explanatory. :dd
-
 {Fix ave/time fix does not calculate a scalar} :dt
 
 A fix used by fix ave/time must generate global values. :dd
@@ -2497,6 +2695,10 @@ A fix used by fix ave/time must generate global values. :dd
 
 A fix used by fix ave/time must generate global values. :dd
 
+{Fix ave/time fix does not calculate an array} :dt
+
+Self-explanatory. :dd
+
 {Fix ave/time fix vector is accessed out-of-range} :dt
 
 The index for the vector is out of bounds. :dd
@@ -2568,6 +2770,10 @@ Only static regions can be used with fix deposit. :dd
 Not all regions represent bounded volumes.  You cannot use
 such a region with the fix deposit command. :dd
 
+{Fix efield requires atom attribute q} :dt
+
+Self-explanatory. :dd
+
 {Fix evaporate molecule requires atom attribute molecule} :dt
 
 The atom style being used does not define a molecule ID. :dd
@@ -2801,6 +3007,14 @@ was exceeded. :dd
 
 Self-explanatory. :dd
 
+{Fix rigid atom has non-zero image flag in a non-periodic dimension} :dt
+
+You cannot set image flags for non-periodic dimensions. :dd
+
+{Fix rigid molecule requires atom attribute molecule} :dt
+
+Self-explanatory. :dd
+
 {Fix rigid/nvt period must be > 0.0} :dt
 
 Self-explanatory :dd
@@ -2835,10 +3049,6 @@ Use the communicate vel yes command to enable this. :dd
 
 Self-explanatory. :dd
 
-{Fix srd simulation box must be periodic} :dt
-
-Self-explanatory. :dd
-
 {Fix store/state compute array is accessed out-of-range} :dt
 
 Self-explanatory. :dd
@@ -2927,6 +3137,11 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Fix used in compute atom/molecule not computed at compatible time} :dt
+
+The fix must produce per-atom quantities on timesteps that the compute
+needs them. :dd
+
 {Fix used in compute reduce not computed at compatible time} :dt
 
 Fixes generate their values on specific timesteps.  Compute sum is
@@ -3005,6 +3220,14 @@ The compute ID assigned to the fix must compute temperature. :dd
 
 When using a "*" in the restart file name, no matching file was found. :dd
 
+{GPU is not the first fix for this run} :dt
+
+This is the way the fix must be defined in your input script. :dd
+
+{Gmask function in equal-style variable formula} :dt
+
+Gmask is per-atom operation. :dd
+
 {Gravity changed since fix pour was created} :dt
 
 Gravity must be static and not dynamic for use with fix pour. :dd
@@ -3017,6 +3240,10 @@ Gravity must be pointing "down" in a 2d box. :dd
 
 Gravity must be pointing "down" in a 3d box, i.e. theta = 180.0. :dd
 
+{Grmask function in equal-style variable formula} :dt
+
+Grmask is per-atom operation. :dd
+
 {Group ID does not exist} :dt
 
 A group ID used in the group command does not exist. :dd
@@ -3059,6 +3286,10 @@ invalid. :dd
 
 The name is too long to be a chemical element. :dd
 
+{Illegal fix gpu command} :dt
+
+Self-explanatory. :dd
+
 {Illegal number of angle table entries} :dt
 
 There must be at least 2 table entries. :dd
@@ -3087,7 +3318,7 @@ The set command cannot find one or more atoms in a particular improper
 on a particular processor.  The pairwise cutoff is too short or the
 atoms are too far apart to make a valid improper. :dd
 
-{Improper atoms %d %d %d %d missing on proc %d at step %d} :dt
+{Improper atoms %d %d %d %d missing on proc %d at step} :dt
 
 One or more of 4 atoms needed to compute a particular improper are
 missing on this processor.  Typically this is because the pairwise
@@ -3275,6 +3506,14 @@ Eigensolve for rigid body was not sufficiently accurate. :dd
 
 Eigensolve for rigid body was not sufficiently accurate. :dd
 
+{Insufficient memory on accelerator (or no fix gpu)} :dt
+
+Self-explanatory. :dd
+
+{Invalid Boolean syntax in if command} :dt
+
+Self-explanatory. :dd
+
 {Invalid REAX atom type} :dt
 
 There is a mis-match between LAMMPS atom types and the elements
@@ -3400,18 +3639,10 @@ Self-explanatory. :dd
 
 Self-explanatory.  Check the fix shake command in the input script. :dd
 
-{Invalid coeffs for this angle style} :dt
-
-Cannot set class 2 coeffs in data file for this angle style. :dd
-
 {Invalid coeffs for this dihedral style} :dt
 
 Cannot set class 2 coeffs in data file for this dihedral style. :dd
 
-{Invalid coeffs for this improper style} :dt
-
-Cannot set class 2 coeffs in data file for this improper style. :dd
-
 {Invalid command-line argument} :dt
 
 One or more command-line arguments is invalid.  Check the syntax of
@@ -3501,6 +3732,10 @@ Atom style does not allow impropers. :dd
 
 Atom style does not allow dihedrals. :dd
 
+{Invalid delta_conf in tad command} :dt
+
+The value must be between 0 and 1 inclusive. :dd
+
 {Invalid density in Atoms section of data file} :dt
 
 Density value cannot be <= 0.0. :dd
@@ -3704,15 +3939,6 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
-{Invalid natoms for dump dcd} :dt
-
-Natoms is initially 0 which is not valid for the dump dcd style.
-Natoms must be constant for the duration of the simulation. :dd
-
-{Invalid natoms for dump xtc} :dt
-
-Natoms is initially 0 which is not valid for the dump xtc style. :dd
-
 {Invalid option in lattice command for non-custom style} :dt
 
 Certain lattice keywords are not supported unless the
@@ -3749,10 +3975,6 @@ Random number seed must be > 0. :dd
 
 Random number seed must be > 0. :dd
 
-{Invalid region in group function in variable formula} :dt
-
-Self-explanatory. :dd
-
 {Invalid region style} :dt
 
 The choice of region style is unknown. :dd
@@ -3761,6 +3983,19 @@ The choice of region style is unknown. :dd
 
 Self-explanatory. :dd
 
+{Invalid run command N value} :dt
+
+The number of timesteps must fit in a 32-bit integer.  If you want to
+run for more steps than this, perform multiple shorter runs. :dd
+
+{Invalid run command start/stop value} :dt
+
+Self-explanatory. :dd
+
+{Invalid run command upto value} :dt
+
+Self-explanatory. :dd
+
 {Invalid seed for Marsaglia random # generator} :dt
 
 The initial seed for this random number generator must be a positive
@@ -3803,10 +4038,18 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Invalid t_event in tad command} :dt
+
+The value must be greater than 0. :dd
+
 {Invalid thermo keyword in variable formula} :dt
 
 The keyword is not recognized. :dd
 
+{Invalid tmax in tad command} :dt
+
+The value must be greater than 0.0. :dd
+
 {Invalid type for dipole set} :dt
 
 Dipole command must set a type from 1-N where N is the number of atom
@@ -3927,21 +4170,17 @@ sc, bcc, or fcc lattice. :dd
 
 Self-explanatory. :dd
 
-{Lost atoms via displace_atoms: original %.15g current %.15g} :dt
-
-The displace_atoms command lost one or more atoms. :dd
+{MEAM library error %d} :dt
 
-{Lost atoms via displace_box: original %.15g current %.15g} :dt
+A call to the MEAM Fortran library returned an error. :dd
 
-The displace_box command lost one or more atoms. :dd
+{MPI_LMP_BIGINT and bigint in lmptype.h are not compatible} :dt
 
-{Lost atoms: original %.15g current %.15g} :dt
+The size of the MPI datatype does not match the size of a bigint. :dd
 
-A thermodynamic computation has detected lost atoms. :dd
+{MPI_LMP_TAGINT and tagint in lmptype.h are not compatible} :dt
 
-{MEAM library error %d} :dt
-
-A call to the MEAM Fortran library returned an error. :dd
+The size of the MPI datatype does not match the size of a tagint. :dd
 
 {Mass command before simulation box is defined} :dt
 
@@ -3983,6 +4222,15 @@ A variable is referenced incorrectly or an atom-style variable that
 produces per-atom values is used in an equal-style variable
 formula. :dd
 
+{Molecular data file has too many atoms} :dt
+
+These kids of data files are currently limited to a number
+of atoms that fits in a 32-bit integer. :dd
+
+{Molecule count changed in compute atom/molecule} :dt
+
+Number of molecules must remain constant over time. :dd
+
 {Molecule count changed in compute com/molecule} :dt
 
 Number of molecules must remain constant over time. :dd
@@ -4139,10 +4387,6 @@ by a fix shake command. :dd
 
 Self-explanatory. :dd
 
-{Must use a molecular atom style with fix rigid molecule} :dt
-
-Self-explanatory. :dd
-
 {Must use a z-axis cylinder with fix pour} :dt
 
 The axis of the cylinder region used with the fix pour command must
@@ -4157,17 +4401,6 @@ command. :dd
 
 Self-explanatory. :dd
 
-{Must use charged atom style with fix efield} :dt
-
-The atom style being used does not allow atoms to have assigned
-charges.  Hence it will not work with this fix which generates a force
-due to an E-field acting on charge. :dd
-
-{Must use molecular atom style with neigh_modify exclude molecule} :dt
-
-The atom style must define a molecule ID to use the exclude
-option. :dd
-
 {Must use pair_style comb with fix qeq/comb} :dt
 
 Self-explanatory. :dd
@@ -4194,6 +4427,10 @@ Self-explanatory. :dd
 The header of the data file indicated that bonds or angles or
 dihedrals or impropers would be included, but they were not present. :dd
 
+{Neigh_modify exclude molecule requires atom attribute molecule} :dt
+
+Self-explanatory. :dd
+
 {Neigh_modify include group != atom_modify first group} :dt
 
 Self-explanatory. :dd
@@ -4204,12 +4441,20 @@ The delay and every parameters set via the neigh_modify command are
 inconsistent.  If the delay setting is non-zero, then it must be a
 multiple of the every setting. :dd
 
+{Neighbor include group not allowed with ghost neighbors} :dt
+
+This is a current restriction within LAMMPS. :dd
+
 {Neighbor list overflow, boost neigh_modify one or page} :dt
 
 There are too many neighbors of a single atom.  Use the neigh_modify
 command to increase the neighbor page size and the max number of
 neighbors allowed for one atom. :dd
 
+{Neighbor multi not yet enabled for ghost neighbors} :dt
+
+This is a current restriction within LAMMPS. :dd
+
 {Neighbor multi not yet enabled for granular} :dt
 
 Self-explanatory. :dd
@@ -4222,6 +4467,10 @@ Self-explanatory. :dd
 
 This is required to prevent wasting too much memory. :dd
 
+{Neighbors of ghost atoms only allowed for full neighbor lists} :dt
+
+This is a current restriction within LAMMPS. :dd
+
 {New bond exceeded bonds per atom in fix bond/create} :dt
 
 See the read_data command for info on setting the "extra bond per
@@ -4296,6 +4545,10 @@ Self-explanatory.  Check data file. :dd
 The EAM potential file does not contain elements that match the
 requested elements. :dd
 
+{No pair hbond/dreiding coefficients set} :dt
+
+Self-explanatory. :dd
+
 {No pair style defined for compute group/group} :dt
 
 Cannot calculate group interactions without a pair style defined. :dd
@@ -4620,6 +4873,22 @@ does not support them. :dd
 Atoms in the simulation do not have IDs, so history effects
 cannot be tracked by the granular pair potential. :dd
 
+{Pair style hbond/dreiding requires an atom map, see atom_modify} :dt
+
+Self-explanatory. :dd
+
+{Pair style hbond/dreiding requires atom IDs} :dt
+
+Self-explanatory. :dd
+
+{Pair style hbond/dreiding requires molecular system} :dt
+
+Self-explanatory. :dd
+
+{Pair style hbond/dreiding requires newton pair on} :dt
+
+See the newton command for details. :dd
+
 {Pair style hybrid cannot have hybrid as an argument} :dt
 
 Self-explanatory. :dd
@@ -4746,7 +5015,7 @@ Self-explanatory. :dd
 Particles must be "exterior" to the wall in order for energy/force to
 be calculated. :dd
 
-{Particle on or inside fix wall/region surface} :dt
+{Particle on or inside surface of region used in fix wall/region} :dt
 
 Particles must be "exterior" to the region surface in order for
 energy/force to be calculated. :dd
@@ -4765,16 +5034,17 @@ variable doc page for ideas on how to make this work. :dd
 
 Equal-style variables cannot use per-atom quantities. :dd
 
-{Per-atom virial not available with GPU Gay-Berne} :dt
-
-Self-explanatory. :dd
-
 {Per-atom virial was not tallied on needed timestep} :dt
 
 You are using a thermo keyword that requires potentials to have
 tallied the virial, but they didn't on this timestep.  See the
 variable doc page for ideas on how to make this work. :dd
 
+{Per-processor system is too big} :dt
+
+The number of owned atoms plus ghost atoms on a single
+processor must fit in 32-bit integer. :dd
+
 {Potential energy ID for fix neb does not exist} :dt
 
 Self-explanatory. :dd
@@ -4893,10 +5163,6 @@ library and re-build LAMMPS. :dd
 
 Self-explanatory. :dd
 
-{Region ID for compute temp reduce/region does not exist} :dt
-
-Self-explanatory. :dd
-
 {Region ID for compute temp/region does not exist} :dt
 
 Self-explanatory. :dd
@@ -4913,6 +5179,10 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Region ID for fix ave/spatial does not exist} :dt
+
+Self-explanatory. :dd
+
 {Region ID for fix aveforce does not exist} :dt
 
 Self-explanatory. :dd
@@ -4937,6 +5207,10 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Region ID in variable formula does not exist} :dt
+
+Self-explanatory. :dd
+
 {Region cannot have 0 length rotation vector} :dt
 
 Self-explanatory. :dd
@@ -4972,6 +5246,19 @@ Atoms replicated by the replicate command were not assigned correctly
 to processors.  This is likely due to some atom coordinates being
 outside a non-periodic simulation box. :dd
 
+{Replicated molecular system atom IDs are too big} :dt
+
+See the setting for the allowed atom ID size in the src/lmptype.h
+file. :dd
+
+{Replicated system is too big} :dt
+
+See the setting for bigint in the src/lmptype.h file. :dd
+
+{Resetting timestep is not allowed with fix move} :dt
+
+This is because fix move is moving atoms based on elapsed time. :dd
+
 {Respa inner cutoffs are invalid} :dt
 
 The first cutoff must be <= the second cutoff. :dd
@@ -5008,6 +5295,10 @@ NPT/NPH fix must be defined in input script after all rigid fixes,
 else the rigid fix contribution to the pressure virial is
 incorrect. :dd
 
+{Rmask function in equal-style variable formula} :dt
+
+Rmask is per-atom operation. :dd
+
 {Run command before simulation box is defined} :dt
 
 The run command cannot be used before a read_data, read_restart, or
@@ -5021,10 +5312,6 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
-{Run command upto value is before current timestep} :dt
-
-Self-explanatory. :dd
-
 {Run_style command before simulation box is defined} :dt
 
 The run_style command cannot be used before a read_data,
@@ -5038,10 +5325,9 @@ Fix SRD had to adjust the bin size to fit the simulation box. :dd
 
 The bin shape is not within tolerance of cubic. :dd
 
-{SRD particle %d started inside big particle %d on step %d bounce %d} :dt
+{Same dimension twice in fix ave/spatial} :dt
 
-This may not be a problem, but indicates one or more SRD particles are
-being left inside solute particles. :dd
+Self-explanatory. :dd
 
 {Set command before simulation box is defined} :dt
 
@@ -5062,19 +5348,19 @@ All 3-atom angle-constrained SHAKE clusters specified by the fix shake
 command that are the same angle type, must also have the same bond
 types for the 2 bonds in the angle. :dd
 
-{Shake atoms %d %d %d %d missing on proc %d at step %d} :dt
+{Shake atoms %d %d %d %d missing on proc %d at step} :dt
 
 The 4 atoms in a single shake cluster specified by the fix shake
 command are not all accessible to a processor.  This probably means
 an atom has moved too far. :dd
 
-{Shake atoms %d %d %d missing on proc %d at step %d} :dt
+{Shake atoms %d %d %d missing on proc %d at step} :dt
 
 The 3 atoms in a single shake cluster specified by the fix shake
 command are not all accessible to a processor.  This probably means
 an atom has moved too far. :dd
 
-{Shake atoms %d %d missing on proc %d at step %d} :dt
+{Shake atoms %d %d missing on proc %d at step} :dt
 
 The 2 atoms in a single shake cluster specified by the fix shake
 command are not all accessible to a processor.  This probably means
@@ -5104,6 +5390,15 @@ SHAKE fix contribution to the pressure virial is incorrect. :dd
 
 Self-explanatory. :dd
 
+{Smallint setting in lmptype.h is invalid} :dt
+
+It has to be the size of an integer. :dd
+
+{Smallint setting in lmptype.h is not compatible} :dt
+
+Smallint stored in restart file is not consistent with LAMMPS version
+you are running. :dd
+
 {Sqrt of negative value in variable formula} :dt
 
 Self-explanatory. :dd
@@ -5113,6 +5408,14 @@ Self-explanatory. :dd
 Input script line contained a variable that could not be substituted
 for. :dd
 
+{System in data file is too big} :dt
+
+See the setting for bigint in the src/lmptype.h file. :dd
+
+{TAD nsteps must be multiple of t_event} :dt
+
+Self-explanatory. :dd
+
 {TIP4P hydrogen has incorrect atom type} :dt
 
 The TIP4P pairwise computation found an H atom whose type does not
@@ -5128,6 +5431,19 @@ within a water molecule. :dd
 The target file for the fix tmd command did not list all atoms in the
 fix group. :dd
 
+{Tad command before simulation box is defined} :dt
+
+Self-explanatory. :dd
+
+{Tagint setting in lmptype.h is invalid} :dt
+
+Tagint must be as large or larger than smallint. :dd
+
+{Tagint setting in lmptype.h is not compatible} :dt
+
+Smallint stored in restart file is not consistent with LAMMPS version
+you are running. :dd
+
 {Target temperature for fix nvt/npt/nph cannot be 0.0} :dt
 
 Self-explanatory. :dd
@@ -5317,6 +5633,10 @@ is not computing this quantity. :dd
 Cannot use thermo_modify to set this parameter since the thermo_style
 is not computing this quantity. :dd
 
+{Thermo_modify int format does not contain d character} :dt
+
+Self-explanatory. :dd
+
 {Thermo_modify pressure ID does not compute pressure} :dt
 
 The specified compute ID does not compute pressure. :dd
@@ -5344,11 +5664,17 @@ not defined by the atom style used in this simulation. :dd
 
 Specified timestep size is invalid. :dd
 
-{Too big a problem to replicate with molecular atom style} :dt
+{Too big a problem to use velocity create loop all} :dt
+
+The system size must fit in a 32-bit integer to use this option. :dd
 
-Molecular problems cannot become bigger than 2^31 atoms (or bonds,
-etc) when replicated, else the atom IDs and other quantities cannot be
-stored in 32-bit quantities. :dd
+{Too big a timestep for dump dcd} :dt
+
+The timestep must fit in a 32-bit integer to use this dump style. :dd
+
+{Too big a timestep for dump xtc} :dt
+
+The timestep must fit in a 32-bit integer to use this dump style. :dd
 
 {Too few bits for lookup table} :dt
 
@@ -5360,6 +5686,16 @@ machine's floating point representation. :dd
 This is likely due to an immense simulation box that has blown up
 to a large size. :dd
 
+{Too many atoms for dump dcd} :dt
+
+The system size must fit in a 32-bit integer to use this dump
+style. :dd
+
+{Too many atoms for dump xtc} :dt
+
+The system size must fit in a 32-bit integer to use this dump
+style. :dd
+
 {Too many atoms to dump sort} :dt
 
 Cannot sort when running with more than 2^31 atoms. :dd
@@ -5374,6 +5710,11 @@ machine's floating point representation. :dd
 The maximum number of atom groups (including the "all" group) is 
 given by MAX_GROUP in group.cpp and is 32. :dd
 
+{Too many iterations} :dt
+
+You must use a number of iterations that fit in a 32-bit integer 
+for minimization. :dd
+
 {Too many mantissa bits for lookup table} :dt
 
 Table size specified via pair_modify command does not work with your
@@ -5389,6 +5730,15 @@ types. :dd
 This is likely due to an immense simulation box that has blown up
 to a large size. :dd
 
+{Too many timesteps for NEB} :dt
+
+You must use a number of timesteps that fit in a 32-bit integer 
+for NEB. :dd
+
+{Too many total atoms} :dt
+
+See the setting for bigint in the src/lmptype.h file. :dd
+
 {Too many total bits for bitmapped lookup table} :dt
 
 Table size specified via pair_modify command is too large.  Note that
@@ -5400,6 +5750,11 @@ A granular simulation has too many neighbors touching one atom.  The
 MAXTOUCH parameter in fix_shear_history.cpp must be set larger and
 LAMMPS must be re-built. :dd
 
+{Too much per-proc info for dump} :dt
+
+Number of local atoms times number of columns must fit in a 32-bit
+integer for dump. :dd
+
 {Tree structure in joint connections} :dt
 
 Fix poems cannot (yet) work with coupled bodies whose joints connect
@@ -5474,6 +5829,10 @@ valid. :dd
 The lattice type in an entry of the MEAM parameter file is not
 valid. :dd
 
+{Unrecognized pair style in compute pair command} :dt
+
+Self-explanatory. :dd
+
 {Use of compute temp/ramp with undefined lattice} :dt
 
 Must use lattice command with compute temp/ramp command if units
@@ -5527,11 +5886,6 @@ set to lattice. :dd
 Must use lattice command with fix wall command if units option is set
 to lattice. :dd
 
-{Use of fix wall/reflect with undefined lattice} :dt
-
-If scale = lattice (the default) for the fix wall/reflect command,
-then a lattice must first be defined via the lattice command. :dd
-
 {Use of region with undefined lattice} :dt
 
 If scale = lattice (the default) for the region command, then a
@@ -5561,6 +5915,10 @@ deform needs to be used. :dd
 Cannot evaluate a compute or fix or atom-based value in a variable
 before the simulation has been setup. :dd
 
+{Variable for compute ti is invalid style} :dt
+
+Self-explanatory. :dd
+
 {Variable for dump every is invalid style} :dt
 
 Only equal-style variables can be used. :dd
@@ -5569,6 +5927,10 @@ Only equal-style variables can be used. :dd
 
 Only equal-style variables can be used. :dd
 
+{Variable for fix addforce is invalid style} :dt
+
+Self-explanatory. :dd
+
 {Variable for fix aveforce is invalid style} :dt
 
 Only equal-style variables can be used. :dd
@@ -5593,14 +5955,34 @@ Only equal-style variables can be used. :dd
 
 Only equal-style variables can be used. :dd
 
+{Variable for fix wall is invalid style} :dt
+
+Only equal-style variables can be used. :dd
+
 {Variable for fix wall/reflect is invalid style} :dt
 
 Only equal-style variables can be used. :dd
 
+{Variable for fix wall/srd is invalid style} :dt
+
+Only equal-style variables can be used. :dd
+
+{Variable for region is invalid style} :dt
+
+Only equal-style variables can be used. :dd
+
+{Variable for region is not equal style} :dt
+
+Self-explanatory. :dd
+
 {Variable for thermo every is invalid style} :dt
 
 Only equal-style variables can be used. :dd
 
+{Variable for velocity set is invalid style} :dt
+
+Only atom-style variables can be used. :dd
+
 {Variable formula compute array is accessed out-of-range} :dt
 
 Self-explanatory. :dd
@@ -5617,10 +5999,18 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Variable name for compute atom/molecule does not exist} :dt
+
+Self-explanatory. :dd
+
 {Variable name for compute reduce does not exist} :dt
 
 Self-explanatory. :dd
 
+{Variable name for compute ti does not exist} :dt
+
+Self-explanatory. :dd
+
 {Variable name for dump every does not exist} :dt
 
 Self-explanatory. :dd
@@ -5677,7 +6067,19 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
-{Variable name for fix wall/relect does not exist} :dt
+{Variable name for fix wall does not exist} :dt
+
+Self-explanatory. :dd
+
+{Variable name for fix wall/reflect does not exist} :dt
+
+Self-explanatory. :dd
+
+{Variable name for fix wall/srd does not exist} :dt
+
+Self-explanatory. :dd
+
+{Variable name for region does not exist} :dt
 
 Self-explanatory. :dd
 
@@ -5685,6 +6087,10 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Variable name for velocity set does not exist} :dt
+
+Self-explanatory. :dd
+
 {Variable name must be alphanumeric or underscore characters} :dt
 
 Self-explanatory. :dd
@@ -5713,6 +6119,23 @@ You are using a thermo keyword that requires potentials to
 have tallied the virial, but they didn't on this timestep.  See the
 variable doc page for ideas on how to make this work. :dd
 
+{Wall defined twice in fix wall command} :dt
+
+Self-explanatory. :dd
+
+{Wall defined twice in fix wall/reflect command} :dt
+
+Self-explanatory. :dd
+
+{Wall defined twice in fix wall/srd command} :dt
+
+Self-explanatory. :dd
+
+{Weighted neighbor list values are too big} :dt
+
+You must have less atoms per processor to use this
+style neighbor list. :dd
+
 {World variable count doesn't match # of partitions} :dt
 
 A world-style variable must specify a number of values equal to the
@@ -5748,6 +6171,12 @@ want. :dd
 See the doc page for fix bond/break for more info on this
 restriction. :dd
 
+{Building an occasional neighobr list when atoms may have moved too far} :dt
+
+This can cause LAMMPS to crash when the neighbor list is built.
+The solution is to check for building the regular neighbor lists
+more frequently. :dd
+
 {Compute cna/atom cutoff may be too large to find ghost atom neighbors} :dt
 
 The neighbor cutoff used may not encompass enough ghost atoms
@@ -5785,6 +6214,10 @@ will be truncated to attempt to prevent the bond from blowing up. :dd
 A FENE bond has stretched dangerously far.  It's interaction strength
 will be truncated to attempt to prevent the bond from blowing up. :dd
 
+{Fix SRD walls overlap but fix srd overlap not set} :dt
+
+You likely want to set this in your input script. :dd
+
 {Fix bond/swap will ignore defined angles} :dt
 
 See the doc page for fix bond/swap for more info on this
@@ -5811,6 +6244,10 @@ This is because the SRD particles may move long distances. :dd
 
 This may cause accuracy problems. :dd
 
+{Fix srd no-slip wall collisions with bin shifting} :dt
+
+This is an inconsistent setting in your input script. :dd
+
 {Fix srd particle moved outside valid domain} :dt
 
 This may indicate a problem with your simulation parameters. :dd
@@ -5876,6 +6313,10 @@ on the same group of atoms that velocities are being set for. :dd
 
 It is not efficient to use compute centro/atom  more than once. :dd
 
+{More than one compute cluster/atom} :dt
+
+It is not efficient to use compute cluster/atom  more than once. :dd
+
 {More than one compute cna/atom defined} :dt
 
 It is not efficient to use compute cna/atom  more than once. :dd
@@ -5985,6 +6426,13 @@ every = 1, check = yes.  Since these settings were not in place,
 LAMMPS changed them and will restore them to their original values
 after the PRD simulation. :dd
 
+{Resetting reneighboring criteria during TAD} :dt
+
+A TAD simulation requires that neigh_modify settings be delay = 0,
+every = 1, check = yes.  Since these settings were not in place,
+LAMMPS changed them and will restore them to their original values
+after the PRD simulation. :dd
+
 {Resetting reneighboring criteria during minimization} :dt
 
 Minimization requires that neigh_modify settings be delay = 0, every =
diff --git a/doc/pair_coeff.html b/doc/pair_coeff.html
index 36f8c74033..fa98d3addd 100644
--- a/doc/pair_coeff.html
+++ b/doc/pair_coeff.html
@@ -40,7 +40,7 @@ can be used for each, as in the 1st example above.  I <= J is
 required.  LAMMPS sets the coefficients for the symmetric J,I
 interaction to the same values.
 </P>
-<P>A wild-card asterisk can be used in place of or in conjunction with the
+<P>A wildcard asterisk can be used in place of or in conjunction with the
 I,J arguments to set the coefficients for multiple pairs of atom
 types.  This takes the form "*" or "*n" or "n*" or "m*n".  If N = the
 number of atom types, then an asterisk with no numeric values means all
diff --git a/doc/pair_coeff.txt b/doc/pair_coeff.txt
index 09c2dc401a..baf95341db 100644
--- a/doc/pair_coeff.txt
+++ b/doc/pair_coeff.txt
@@ -37,7 +37,7 @@ can be used for each, as in the 1st example above.  I <= J is
 required.  LAMMPS sets the coefficients for the symmetric J,I
 interaction to the same values.
 
-A wild-card asterisk can be used in place of or in conjunction with the
+A wildcard asterisk can be used in place of or in conjunction with the
 I,J arguments to set the coefficients for multiple pairs of atom
 types.  This takes the form "*" or "*n" or "n*" or "m*n".  If N = the
 number of atom types, then an asterisk with no numeric values means all
-- 
GitLab