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

patch 17Jan17

Browse Source
This commit is contained in:
Steve Plimpton
2017-01-17 10:14:53 -07:00
parent c52a26382f
commit d2fc88a626
3 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/Manual.txt
View File

@ -1,7 +1,7 @@
<!-- HTML_ONLY --> <!-- HTML_ONLY -->
<HEAD> <HEAD>
<TITLE>LAMMPS Users Manual</TITLE> <TITLE>LAMMPS Users Manual</TITLE>
<META NAME="docnumber" CONTENT="9 Jan 2017 version"> <META NAME="docnumber" CONTENT="17 Jan 2017 version">
<META NAME="author" CONTENT="http://lammps.sandia.gov - Sandia National Laboratories"> <META NAME="author" CONTENT="http://lammps.sandia.gov - Sandia National Laboratories">
<META NAME="copyright" CONTENT="Copyright (2003) Sandia Corporation. This software and manual is distributed under the GNU General Public License."> <META NAME="copyright" CONTENT="Copyright (2003) Sandia Corporation. This software and manual is distributed under the GNU General Public License.">
</HEAD> </HEAD>
@ -21,7 +21,7 @@
<H1></H1> <H1></H1>
LAMMPS Documentation :c,h3 LAMMPS Documentation :c,h3
9 Jan 2017 version :c,h4 17 Jan 2017 version :c,h4
Version info: :h4 Version info: :h4

13
doc/src/Section_errors.txt
View File

@ -55,12 +55,13 @@ LAMMPS errors are detected at setup time; others like a bond
stretching too far may not occur until the middle of a run. stretching too far may not occur until the middle of a run.
LAMMPS tries to flag errors and print informative error messages so LAMMPS tries to flag errors and print informative error messages so
you can fix the problem. Of course, LAMMPS cannot figure out your you can fix the problem. For most errors it will also print the last
physics or numerical mistakes, like choosing too big a timestep, input script command that it was processing. Of course, LAMMPS cannot
specifying erroneous force field coefficients, or putting 2 atoms on figure out your physics or numerical mistakes, like choosing too big a
top of each other! If you run into errors that LAMMPS doesn't catch timestep, specifying erroneous force field coefficients, or putting 2
that you think it should flag, please send an email to the atoms on top of each other! If you run into errors that LAMMPS
"developers"_http://lammps.sandia.gov/authors.html. doesn't catch that you think it should flag, please send an email to
the "developers"_http://lammps.sandia.gov/authors.html.
If you get an error message about an invalid command in your input If you get an error message about an invalid command in your input
script, you can determine what command is causing the problem by script, you can determine what command is causing the problem by

2
src/version.h
View File

@ -1 +1 @@
#define LAMMPS_VERSION "9 Jan 2017" #define LAMMPS_VERSION "17 Jan 2017"