git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@16053 f3b2605a-c512-4ea7-a41b-209d697bcdaa

git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@16051 f3b2605a-c512-4ea7-a41b-209d697bcdaa

.github/CODEOWNERS

@@ -1,21 +0,0 @@
-# This file contains file patterns that triggers automatic
-# code review requests from users that are owners of these files
-# Order matters, the last match has the highest precedence
-
-# library folders
-lib/colvars/*         @giacomofiorin
-lib/compress/*        @akohlmey
-lib/kokkos/*          @stanmoore1
-lib/molfile/*         @akohlmey
-lib/qmmm/*            @akohlmey
-lib/vtk/*             @rbberger
-
-# packages
-src/KOKKOS            @stanmoore1
-src/USER-CGSDK        @akohlmey
-src/USER-COLVARS      @giacomofiorin
-src/USER-OMP          @akohlmey
-src/USER-QMMM         @akohlmey
-
-# tools
-tools/msi2lmp/*       @akohlmey

.github/CONTRIBUTING.md

@@ -1,112 +0,0 @@
-# Contributing to LAMMPS via GitHub
-
-Thank your for considering to contribute to the LAMMPS software project.
-
-The following is a set of guidelines as well as explanations of policies and workflows for contributing to the LAMMPS molecular dynamics software project. These guidelines focus on submitting issues or pull requests on the LAMMPS GitHub project.
-
-Thus please also have a look at:
-* [The Section on submitting new features for inclusion in LAMMPS of the Manual](http://lammps.sandia.gov/doc/Section_modify.html#mod-15)
-* [The LAMMPS GitHub Tutorial in the Manual](http://lammps.sandia.gov/doc/tutorial_github.html)
-
-## Table of Contents
-
-[I don't want to read this whole thing, I just have a question!](#i-dont-want-to-read-this-whole-thing-i-just-have-a-question)
-
-[How Can I Contribute?](#how-can-i-contribute)
-* [Discussing How To Use LAMMPS](#discussing-how-to-use-lammps)
-* [Reporting Bugs](#reporting-bugs)
-* [Suggesting Enhancements](#suggesting-enhancements)
-* [Contributing Code](#contributing-code)
-
-[GitHub Workflows](#github-workflows)
-* [Issues](#issues)
-* [Pull Requests](#pull-requests)
-
-__
-
-## I don't want to read this whole thing I just have a question!
-
-> **Note:** Please do not file an issue to ask a general question about LAMMPS, its features, how to use specific commands, or how perform simulations or analysis in LAMMPS. Instead post your question to the ['lammps-users' mailing list](http://lammps.sandia.gov/mail.html). You do not need to be subscribed to post to the list (but a mailing list subscription avoids having your post delayed until it is approved by a mailing list moderator). Most posts to the mailing list receive a response within less than 24 hours. Before posting to the mailing list, please read the [mailing list guidelines](http://lammps.sandia.gov/guidelines.html). Following those guidelines will help greatly to get a helpful response. Always mention which LAMMPS version you are using.
-
-## How Can I Contribute?
-
-There are several ways how you can actively contribute to the LAMMPS project: you can discuss compiling and using LAMMPS, and solving LAMMPS related problems with other LAMMPS users on the lammps-users mailing list, you can report bugs or suggest enhancements by creating issues on GitHub (or posting them to the lammps-users mailing list), and you can contribute by submitting pull requests on GitHub or e-mail your code
-to one of the [LAMMPS core developers](http://lammps.sandia.gov/authors.html). As you may see from the aforementioned developer page, the LAMMPS software package includes the efforts of a very large number of contributors beyond the principal authors and maintainers.
-
-### Discussing How To Use LAMMPS
-
-The LAMMPS mailing list is hosted at SourceForge. The mailing list began in 2005, and now includes tens of thousands of messages in thousands of threads. LAMMPS developers try to respond to posted questions in a timely manner, but there are no guarantees. Please consider that people live in different timezone and may not have time to answer e-mails outside of their work hours.
-You can post to list by sending your email to lammps-users at lists.sourceforge.net (no subscription required), but before posting, please read the [mailing list guidelines](http://lammps.sandia.gov/guidelines.html) to maximize your chances to receive a helpful response.
-
-Anyone can browse/search previous questions/answers in the archives. You do not have to subscribe to the list to post questions, receive answers (to your questions), or browse/search the archives. You **do** need to subscribe to the list if you want emails for **all** the posts (as individual messages or in digest form), or to answer questions yourself. Feel free to sign up and help us out! Answering questions from fellow LAMMPS users is a great way to pay back the community for providing you a useful tool for free, and to pass on the advice you have received yourself to others. It improves your karma and helps you understand your own research better.
-
-If you post a message and you are a subscriber, your message will appear immediately. If you are not a subscriber, your message will be moderated, which typically takes one business day. Either way, when someone replies the reply will usually be sent to both, your personal email address and the mailing list. When replying to people, that responded to your post to the list, please always included the mailing list in your replies (i.e. use "Reply All" and **not** "Reply"). Responses will appear on the list in a few minutes, but it can take a few hours for postings and replies to show up in the SourceForge archive. Sending replies also to the mailing list is important, so that responses are archived and people with a similar issue can search for possible solutions in the mailing list archive.
-
-### Reporting Bugs
-
-While developers writing code for LAMMPS are careful to test their code, LAMMPS is such a large and complex software, that it is impossible to test for all combinations of features under all normal and not so normal circumstances. Thus bugs do happen, and if you suspect, that you have encountered one, please try to document it and report it as an [Issue](https://github.com/lammps/lammps/issues) on the LAMMPS GitHub project web page. However, before reporting a bug, you need to check whether this is something that may have already been corrected. The [Latest Features and Bug Fixes in LAMMPS](http://lammps.sandia.gov/bug.html) web page lists all significant changes to LAMMPS over the years. It also tells you what the current latest development version of LAMMPS is, and you should test whether your issue still applies to that version.
-
-When you click on the green "New Issue" button, you will be provided with a text field, where you can enter your message. That text field with contain a template with several headlines and some descriptions. Keep the headlines that are relevant to your reported potential bug and replace the descriptions with the information as suggested by the descriptions.
-You can also attach small text files (please add the file name extension `.txt` or it will be rejected), images, or small compressed text files (using gzip, do not use RAR or 7-ZIP or similar tools that are uncommon outside of Windows machines). In many cases, bugs are best illustrated by providing a small input deck (do **not** attach your entire production input, but remove everything that is not required to reproduce the issue, and scale down your system size, that the resulting calculation runs fast and can be run on small desktop quickly).
-
-To be able to submit an issue on GitHub, you have to register for an account (for GitHub in general). If you do not want to do that, or have other reservations against submitting an issue there, you can - as an alternative and in decreasing preference - either send an e-mail to the lammps-users mailing list, the original authors of the feature that you suspect to be affected, or one or more of the core LAMMPS developers.
-
-### Suggesting Enhancements
-
-The LAMMPS developers welcome suggestions for enhancements or new features. These should be submitted using the [GitHub Issue Tracker](https://github.com/lammps/lammps/issues) of the LAMMPS project. This is particularly recommended, when you plan to implement the feature or enhancement yourself, as this allows to coordinate in case there are other similar or conflicting ongoing developments.
-The LAMMPS developers will review your submission and consider implementing it. Whether this will actually happen depends on many factors: how difficult it would be, how much effort it would take, how many users would benefit from it, how well the individual developer would understand the underlying physics of the feature, and whether this is a feature that would fit into a software like LAMMPS, or would be better implemented as a separate tool. Because of these factors, it matters how well the suggested enhancement is formulated and the overall benefit is argued convincingly.
-
-To be able to submit an issue on GitHub, you have to register for an account (for GitHub in general). If you do not want to do that, or have other reservations against submitting an issue there, you can - as an alternative - send an e-mail to the lammps-users mailing list.
-
-### Contributing Code
-
-We encourage users to submit new features or modifications for LAMMPS to the core developers so they can be added to the LAMMPS distribution. The preferred way to manage and coordinate this is by submitting a pull request at the LAMMPS project on GitHub. For any larger modifications or programming project, you are encouraged to contact the LAMMPS developers ahead of time, in order to discuss implementation strategies and coding guidelines, that will make it easier to integrate your contribution and result in less work for everybody involved. You are also encouraged to search through the list of open issues on GitHub and submit a new issue for a planned feature, so you would not duplicate the work of others (and possibly get scooped by them) or have your work duplicated by others.
-
-How quickly your contribution will be integrated depends largely on how much effort it will cause to integrate and test it, how much it requires changes to the core code base, and of how much interest it is to the larger LAMMPS community. Please see below for a checklist of typical requirements. Once you have prepared everything, see [this tutorial](http://lammps.sandia.gov/doc/tutorial_github.html)
- for instructions on how to submit your changes or new files through a GitHub pull request
-
-Here is a checklist of steps you need to follow to submit a single file or user package for our consideration. Following these steps will save both you and us time. See existing files in packages in the source directory for examples. If you are uncertain, please ask on the lammps-users mailing list.
-
-* All source files you provide must compile with the most current version of LAMMPS with multiple configurations. In particular you need to test compiling LAMMPS from scratch with `-DLAMMPS_BIGBIG` set in addition to the default `-DLAMMPS_SMALLBIG` setting. Your code will need to work correctly in serial and in parallel using MPI.
-* For consistency with the rest of LAMMPS and especially, if you want your contribution(s) to be added to main LAMMPS code or one of its standard packages, it needs to be written in a style compatible with other LAMMPS source files. This means: 2-character indentation per level, no tabs, no lines over 80 characters. I/O is done via the C-style stdio library, class header files should not import any system headers outside <stdio.h>, STL containers should be avoided in headers, and forward declarations used where possible or needed. All added code should be placed into the LAMMPS_NS namespace or a sub-namespace; global or static variables should be avoided, as they conflict with the modular nature of LAMMPS and the C++ class structure. Header files must not import namespaces with using. This all is so the developers can more easily understand, integrate, and maintain your contribution and reduce conflicts with other parts of LAMMPS. This basically means that the code accesses data structures, performs its operations, and is formatted similar to other LAMMPS source files, including the use of the error class for error and warning messages.
-* If you want your contribution to be added as a user-contributed feature, and it is a single file (actually a `<name>.cpp` and `<name>.h` file) it can be rapidly added to the USER-MISC directory. Include the one-line entry to add to the USER-MISC/README file in that directory, along with the 2 source files. You can do this multiple times if you wish to contribute several individual features.
-* If you want your contribution to be added as a user-contribution and it is several related features, it is probably best to make it a user package directory with a name like USER-FOO. In addition to your new files, the directory should contain a README text file. The README should contain your name and contact information and a brief description of what your new package does. If your files depend on other LAMMPS style files also being installed (e.g. because your file is a derived class from the other LAMMPS class), then an Install.sh file is also needed to check for those dependencies. See other README and Install.sh files in other USER directories as examples. Send us a tarball of this USER-FOO directory.
-* Your new source files need to have the LAMMPS copyright, GPL notice, and your name and email address at the top, like other user-contributed LAMMPS source files. They need to create a class that is inside the LAMMPS namespace. If the file is for one of the USER packages, including USER-MISC, then we are not as picky about the coding style (see above). I.e. the files do not need to be in the same stylistic format and syntax as other LAMMPS files, though that would be nice for developers as well as users who try to read your code.
-* You **must** also create or extend a documentation file for each new command or style you are adding to LAMMPS. For simplicity and convenience, the documentation of groups of closely related commands or styles may be combined into a single file. This will be one file for a single-file feature. For a package, it might be several files. These are simple text files with a specific markup language, that are then auto-converted to HTML and PDF. The tools for this conversion are included in the source distribution, and the translation can be as simple as doing "make html pdf" in the doc folder. Thus the documentation source files must be in the same format and style as other `<name>.txt` files in the lammps/doc/src directory for similar commands and styles; use one or more of them as a starting point. A description of the markup can also be found in `lammps/doc/utils/txt2html/README.html` As appropriate, the text files can include links to equations (see doc/Eqs/*.tex for examples, we auto-create the associated JPG files), or figures (see doc/JPG for examples), or even additional PDF files with further details (see doc/PDF for examples). The doc page should also include literature citations as appropriate; see the bottom of doc/fix_nh.txt for examples and the earlier part of the same file for how to format the cite itself. The "Restrictions" section of the doc page should indicate that your command is only available if LAMMPS is built with the appropriate USER-MISC or USER-FOO package. See other user package doc files for examples of how to do this. The prerequisite for building the HTML format files are Python 3.x and virtualenv, the requirement for generating the PDF format manual is the htmldoc software. Please run at least "make html" and carefully inspect and proofread the resulting HTML format doc page before submitting your code.
-* For a new package (or even a single command) you should include one or more example scripts demonstrating its use. These should run in no more than a couple minutes, even on a single processor, and not require large data files as input. See directories under examples/USER for examples of input scripts other users provided for their packages. These example inputs are also required for validating memory accesses and testing for memory leaks with valgrind
-* If there is a paper of yours describing your feature (either the algorithm/science behind the feature itself, or its initial usage, or its implementation in LAMMPS), you can add the citation to the *.cpp source file. See src/USER-EFF/atom_vec_electron.cpp for an example. A LaTeX citation is stored in a variable at the top of the file and a single line of code that references the variable is added to the constructor of the class. Whenever a user invokes your feature from their input script, this will cause LAMMPS to output the citation to a log.cite file and prompt the user to examine the file. Note that you should only use this for a paper you or your group authored. E.g. adding a cite in the code for a paper by Nose and Hoover if you write a fix that implements their integrator is not the intended usage. That kind of citation should just be in the doc page you provide.
-
-Finally, as a general rule-of-thumb, the more clear and self-explanatory you make your documentation and README files, and the easier you make it for people to get started, e.g. by providing example scripts, the more likely it is that users will try out your new feature.
-
-If the new features/files are broadly useful we may add them as core files to LAMMPS or as part of a standard package. Else we will add them as a user-contributed file or package. Examples of user packages are in src sub-directories that start with USER. The USER-MISC package is simply a collection of (mostly) unrelated single files, which is the simplest way to have your contribution quickly added to the LAMMPS distribution. You can see a list of the both standard and user packages by typing "make package" in the LAMMPS src directory.
-
-Note that by providing us files to release, you are agreeing to make them open-source, i.e. we can release them under the terms of the GPL, used as a license for the rest of LAMMPS. See Section 1.4 for details.
-
-With user packages and files, all we are really providing (aside from the fame and fortune that accompanies having your name in the source code and on the Authors page of the LAMMPS WWW site), is a means for you to distribute your work to the LAMMPS user community, and a mechanism for others to easily try out your new feature. This may help you find bugs or make contact with new collaborators. Note that you are also implicitly agreeing to support your code which means answer questions, fix bugs, and maintain it if LAMMPS changes in some way that breaks it (an unusual event).
-
-To be able to submit an issue on GitHub, you have to register for an account (for GitHub in general). If you do not want to do that, or have other reservations or difficulties to submit a pull request, you can - as an alternative - contact one or more of the core LAMMPS developers and ask if one of them would be interested in manually merging your code into LAMMPS and send them your source code. Since the effort to merge a pull request is a small fraction of the effort of integrating source code manually (which would usually be done by converting the contribution into a pull request), your chances to have your new code included quickly are the best with a pull request.
-
-If you prefer to submit patches or full files, you should first make certain, that your code works correctly with the latest patch-level version of LAMMPS and contains all bug fixes from it. Then create a gzipped tar file of all changed or added files or a corresponding patch file using 'diff -u' or 'diff -c' and compress it with gzip. Please only use gzip compression, as this works well on all platforms.
-
-## GitHub Workflows
-
-This section briefly summarizes the steps that will happen **after** you have submitted either an issue or a pull request on the LAMMPS GitHub project page. 
-
-### Issues
-
-After submitting an issue, one or more of the LAMMPS developers will review it and categorize it by assigning labels. Confirmed bug reports will be labeled `bug`; if the bug report also contains a suggestion for how to fix it, it will be labeled `bugfix`; if the issue is a feature request, it will be labeled `enhancement`. Other labels may be attached as well, depending on which parts of the LAMMPS code are affected. If the assessment is, that the issue does not warrant any changes, the `wontfix` label will be applied and if the submission is incorrect or something that should not be submitted as an issue, the `invalid` label will be applied. In both of the last two cases, the issue will then be closed without further action.
-
-For feature requests, what happens next is that developers may comment on the viability or relevance of the request, discuss and make suggestions for how to implement it. If a LAMMPS developer or user is planning to implement the feature, the issue will be assigned to that developer. For developers, that are not yet listed as LAMMPS project collaborators, they will receive an invitation to be added to the LAMMPS project as a collaborator so they can get assigned. If the requested feature or enhancement is implemented, it will usually be submitted as a pull request, which will contain a reference to the issue number. And once the pull request is reviewed and accepted for inclusion into LAMMPS, the issue will be closed. For details on how pull requests are processed, please see below.
-
-For bug reports, the next step is that one of the core LAMMPS developers will self-assign to the issue and try to confirm the bug. If confirmed, the `bug` label and potentially other labels are added to classify the issue and its impact to LAMMPS. Before confirming, further questions may be asked or requests for providing additional input files or details about the steps required to reproduce the issue. Any bugfix is likely to be submitted as a pull request (more about that below) and since most bugs require only local changes, the bugfix may be included in a pull request specifically set up to collect such local bugfixes or small enhancements. Once the bugfix is included in the master branch, the issue will be closed.
-
-### Pull Requests
-
-For submitting pull requests, there is a [detailed tutorial](http://lammps.sandia.gov/doc/tutorial_github.html) in the LAMMPS manual. Thus only a brief breakdown of the steps is presented here.
-Immediately after the submission, the LAMMPS continuing integration server at ci.lammps.org will download your submitted branch and perform a simple compilation test, i.e. will test whether your submitted code can be compiled under various conditions. It will also do a check on whether your included documentation translates cleanly. Whether these tests are successful or fail will be recorded. If a test fails, please inspect the corresponding output on the CI server and take the necessary steps, if needed, so that the code can compile cleanly again. The test will be re-run each the pull request is updated with a push to the remote branch on GitHub.
-Next a LAMMPS core developer will self-assign and do an overall technical assessment of the submission. If you are not yet registered as a LAMMPS collaborator, you will receive an invitation for that.
-You may also receive comments and suggestions on the overall submission or specific details. If permitted, additional changes may be pushed into your pull request branch or a pull request may be filed in your LAMMPS fork on GitHub to include those changes.
-The LAMMPS developer may then decide to assign the pull request to another developer (e.g. when that developer is more knowledgeable about the submitted feature or enhancement or has written the modified code). It may also happen, that additional developers are requested to provide a review and approve the changes. For submissions, that may change the general behavior of LAMMPS, or where a possibility of unwanted side effects exists, additional tests may be requested by the assigned developer.
-If the assigned developer is satisfied and considers the submission ready for inclusion into LAMMPS, the pull request will be assigned to the LAMMPS lead developer, Steve Plimpton (@sjplimp), who will then have the final decision on whether the submission will be included, additional changes are required or it will be ultimately rejected. After the pull request is merged, you may delete the pull request branch in your personal LAMMPS fork.
-Since the learning curve for git is quite steep for efficiently managing remote repositories, local and remote branches, pull requests and more, do not hesitate to ask questions, if you are not sure about how to do certain steps that are asked of you. Even if the changes asked of you do not make sense to you, they may be important for the LAMMPS developers. Please also note, that these all are guidelines and not set in stone.
-

.github/ISSUE_TEMPLATE.md

@@ -1,31 +0,0 @@
-## Summary
-
-_Please provide a brief description of the issue_
-
-## Type of Issue
-
-_Is this a 'Bug Report' or a 'Suggestion for an Enhancement'?_
-
-## Detailed Description (Enhancement Suggestion)
-
-_Explain how you would like to see LAMMPS enhanced, what feature(s) you are looking for, provide references to relevant background information, and whether you are willing to implement the enhancement yourself or would like to participate in the implementation_
-
-## LAMMPS Version (Bug Report)
-
-_Please specify which LAMMPS version this issue was detected with. If this is not the latest development version, please stop and test that version, too, and report it here if the bug persists_
-
-## Expected Behavior (Bug Report)
-
-_Describe the expected behavior. Quote from the LAMMPS manual where needed or explain why the expected behavior is meaningful, especially when it differs from the manual_
-
-## Actual Behavior (Bug Report)
-
-_Describe the actual behavior, how it differs from the expected behavior, and how this can be observed. Try to be specific and do **not* use vague terms like "doesn't work" or "wrong result". Do not assume that the person reading this has any experience with or knowledge of your specific research._
-
-## Steps to Reproduce (Bug Report)
-
-_Describe the steps required to quickly reproduce the issue. You can attach (small) files to the section below or add URLs where to download an archive with all necessary files. Please try to create input that are as small as possible and run as fast as possible. NOTE: the less effort and time it takes to reproduce your issue, the more likely, that somebody will look into it._
-
-## Further Information, Files, and Links
-
-_Put any additional information here, attach relevant text or image files and URLs to external sites, e.g. relevant publications_

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,29 +0,0 @@
-## Purpose
-
-_Briefly describe the new feature(s), enhancement(s), or bugfix(es) included in this pull request. If this addresses an open GitHub Issue, mention the issue number, e.g. with `fixes #221` or `closes #135`, so that issue will be automatically closed when the pull request is merged_
-
-## Author(s)
-
-_Please state name and affiliation of the author or authors that should be credited with the changes in this pull request_
-
-## Backward Compatibility
-
-_Please state whether any changes in the pull request break backward compatibility for inputs, and - if yes - explain what has been changed and why_
-
-## Implementation Notes
-
-_Provide any relevant details about how the changes are implemented, how correctness was verified, how other features - if any - in LAMMPS are affected_
-
-## Post Submission Checklist
-
-_Please check the fields below as they are completed_
-- [ ] The feature or features in this pull request is complete
-- [ ] Suitable new documentation files and/or updates to the existing docs are included
-- [ ] One or more example input decks are included
-- [ ] The source code follows the LAMMPS formatting guidelines
-
-## Further Information, Files, and Links
-
-_Put any additional information here, attach relevant text or image files, and URLs to external sites (e.g. DOIs or webpages)_
-
-

.gitignore

@@ -1,34 +0,0 @@
-*~
-*.o
-*.so
-*.cu_o
-*.ptx
-*_ptx.h
-*.a
-*.d
-*.x
-*.exe
-*.dll
-*.pyc
-__pycache__
-
-Obj_*
-log.lammps
-log.cite
-*.bz2
-*.gz
-*.tar
-.*.swp
-*.orig
-*.rej
-.vagrant
-\#*#
-.#*
-
-.DS_Store
-.DS_Store?
-._*
-.Spotlight-V100
-.Trashes
-ehthumbs.db
-Thumbs.db

LICENSE

@@ -3,7 +3,7 @@ GNU GENERAL PUBLIC LICENSE
 Version 2, June 1991 
 
 Copyright (C) 1989, 1991 Free Software Foundation, Inc.  
-51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+59 Temple Place - Suite 330, Boston, MA  02111-1307, USA
 
 Everyone is permitted to copy and distribute verbatim copies of this
 license document, but changing it is not allowed.

bench/FERMI/README

@@ -1,21 +1,55 @@
 These are input scripts used to run versions of several of the
-benchmarks in the top-level bench directory using the GPU accelerator
-package.  The results of running these scripts on two different machines
-(a desktop with 2 Tesla GPUs and the ORNL Titan supercomputer) are shown
-on the "GPU (Fermi)" section of the Benchmark page of the LAMMPS WWW
-site: lammps.sandia.gov/bench.
+benchmarks in the top-level bench directory using the GPU and
+USER-CUDA accelerator packages.  The results of running these scripts
+on two different machines (a desktop with 2 Tesla GPUs and the ORNL
+Titan supercomputer) are shown on the "GPU (Fermi)" section of the
+Benchmark page of the LAMMPS WWW site: lammps.sandia.gov/bench.
 
 Examples are shown below of how to run these scripts.  This assumes
-you have built 3 executables with the GPU package
+you have built 3 executables with both the GPU and USER-CUDA packages
 installed, e.g.
 
 lmp_linux_single
 lmp_linux_mixed
 lmp_linux_double
 
+The precision (single, mixed, double) refers to the GPU and USER-CUDA
+pacakge precision.  See the README files in the lib/gpu and lib/cuda
+directories for instructions on how to build the packages with
+different precisions.  The GPU and USER-CUDA sub-sections of the
+doc/Section_accelerate.html file also describes this process.
+
+Make.py -d ~/lammps -j 16 -p #all orig -m linux -o cpu -a exe
+Make.py -d ~/lammps -j 16 -p #all opt orig -m linux -o opt -a exe
+Make.py -d ~/lammps -j 16 -p #all omp orig -m linux -o omp -a exe
+Make.py -d ~/lammps -j 16 -p #all gpu orig -m linux \
+        -gpu mode=double arch=20 -o gpu_double -a libs exe
+Make.py -d ~/lammps -j 16 -p #all gpu orig -m linux \
+        -gpu mode=mixed arch=20 -o gpu_mixed -a libs exe
+Make.py -d ~/lammps -j 16 -p #all gpu orig -m linux \
+        -gpu mode=single arch=20 -o gpu_single -a libs exe
+Make.py -d ~/lammps -j 16 -p #all cuda orig -m linux \
+        -cuda mode=double arch=20 -o cuda_double -a libs exe
+Make.py -d ~/lammps -j 16 -p #all cuda orig -m linux \
+        -cuda mode=mixed arch=20 -o cuda_mixed -a libs exe
+Make.py -d ~/lammps -j 16 -p #all cuda orig -m linux \
+        -cuda mode=single arch=20 -o cuda_single -a libs exe
+Make.py -d ~/lammps -j 16 -p #all intel orig -m linux -o intel_cpu -a exe
+Make.py -d ~/lammps -j 16 -p #all kokkos orig -m linux -o kokkos_omp -a exe
+Make.py -d ~/lammps -j 16 -p #all kokkos orig -kokkos cuda arch=20 \
+        -m cuda -o kokkos_cuda -a exe
+
+Make.py -d ~/lammps -j 16 -p #all opt omp gpu cuda intel kokkos orig \
+        -gpu mode=double arch=20 -cuda mode=double arch=20 -m linux \
+        -o all -a libs exe
+
+Make.py -d ~/lammps -j 16 -p #all opt omp gpu cuda intel kokkos orig \
+        -kokkos cuda arch=20 -gpu mode=double arch=20 \
+        -cuda mode=double arch=20 -m cuda -o all_cuda -a libs exe
+
 ------------------------------------------------------------------------
 
-To run on just CPUs (without using the GPU styles),
+To run on just CPUs (without using the GPU or USER-CUDA styles),
 do something like the following:
 
 mpirun -np 1 lmp_linux_double -v x 8 -v y 8 -v z 8 -v t 100 < in.lj
@@ -47,5 +81,23 @@ node via a "-ppn" setting.
 
 ------------------------------------------------------------------------
 
+To run with the USER-CUDA package, do something like the following:
+
+mpirun -np 1 lmp_linux_single -c on -sf cuda -v x 16 -v y 16 -v z 16 -v t 100 < in.lj
+mpirun -np 2 lmp_linux_double -c on -sf cuda -pk cuda 2 -v x 32 -v y 64 -v z 64 -v t 100 < in.eam
+
+The "xyz" settings determine the problem size.  The "t" setting
+determines the number of timesteps.  The "np" setting determines how
+many MPI tasks (per node) the problem will run on.  The numeric
+argument to the "-pk" setting is the number of GPUs (per node); 1 GPU
+is the default.  Note that the number of MPI tasks must equal the
+number of GPUs (both per node) with the USER-CUDA package.
+
+These mpirun commands run on a single node.  To run on multiple nodes,
+scale up the "-np" setting, and control the number of MPI tasks per
+node via a "-ppn" setting.
+
+------------------------------------------------------------------------
+
 If the script has "titan" in its name, it was run on the Titan
 supercomputer at ORNL.

bench/README

@@ -71,33 +71,49 @@ integration
 
 ----------------------------------------------------------------------
 
+Here is a src/Make.py command which will perform a parallel build of a
+LAMMPS executable "lmp_mpi" with all the packages needed by all the
+examples.  This assumes you have an MPI installed on your machine so
+that "mpicxx" can be used as the wrapper compiler.  It also assumes
+you have an Intel compiler to use as the base compiler.  You can leave
+off the "-cc mpi wrap=icc" switch if that is not the case.  You can
+also leave off the "-fft fftw3" switch if you do not have the FFTW
+(v3) installed as an FFT package, in which case the default KISS FFT
+library will be used.
+
+cd src
+Make.py -j 16 -p none molecule manybody kspace granular rigid orig \
+  -cc mpi wrap=icc -fft fftw3 -a file mpi
+
+----------------------------------------------------------------------
+
 Here is how to run each problem, assuming the LAMMPS executable is
 named lmp_mpi, and you are using the mpirun command to launch parallel
 runs:
 
 Serial (one processor runs):
 
-lmp_mpi -in in.lj
-lmp_mpi -in in.chain
-lmp_mpi -in in.eam
-lmp_mpi -in in.chute
-lmp_mpi -in in.rhodo
+lmp_mpi < in.lj
+lmp_mpi < in.chain
+lmp_mpi < in.eam
+lmp_mpi < in.chute
+lmp_mpi < in.rhodo
 
 Parallel fixed-size runs (on 8 procs in this case):
 
-mpirun -np 8 lmp_mpi -in in.lj
-mpirun -np 8 lmp_mpi -in in.chain
-mpirun -np 8 lmp_mpi -in in.eam
-mpirun -np 8 lmp_mpi -in in.chute
-mpirun -np 8 lmp_mpi -in in.rhodo
+mpirun -np 8 lmp_mpi < in.lj
+mpirun -np 8 lmp_mpi < in.chain
+mpirun -np 8 lmp_mpi < in.eam
+mpirun -np 8 lmp_mpi < in.chute
+mpirun -np 8 lmp_mpi < in.rhodo
 
 Parallel scaled-size runs (on 16 procs in this case):
 
-mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 -in in.lj
-mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 -in in.chain.scaled
-mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 -in in.eam
-mpirun -np 16 lmp_mpi -var x 4 -var y 4 -in in.chute.scaled
-mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 -in in.rhodo.scaled
+mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 < in.lj
+mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 < in.chain.scaled
+mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 < in.eam
+mpirun -np 16 lmp_mpi -var x 4 -var y 4 < in.chute.scaled
+mpirun -np 16 lmp_mpi -var x 2 -var y 2 -var z 4 < in.rhodo.scaled
 
 For each of the scaled-size runs you must set 3 variables as -var
 command line switches.  The variables x,y,z are used in the input

doc/.gitignore

@@ -1,6 +0,0 @@
-/html
-/spelling
-/LAMMPS.epub
-/LAMMPS.mobi
-/Manual.pdf
-/Developer.pdf

doc/Makefile

@@ -6,7 +6,6 @@ BUILDDIR      = /tmp/lammps-docs-$(SHA1)
 RSTDIR        = $(BUILDDIR)/rst
 VENV          = $(BUILDDIR)/docenv
 TXT2RST       = $(VENV)/bin/txt2rst
-ANCHORCHECK   = $(VENV)/bin/doc_anchor_check
 
 PYTHON        = $(shell which python3)
 HAS_PYTHON3    = NO
@@ -23,7 +22,7 @@ endif
 SOURCES=$(wildcard src/*.txt)
 OBJECTS=$(SOURCES:src/%.txt=$(RSTDIR)/%.rst)
 
-.PHONY: help clean-all clean epub html pdf old venv spelling anchor_check
+.PHONY: help clean-all clean epub html pdf old venv
 
 # ------------------------------------------
 
@@ -37,7 +36,6 @@ help:
 	@echo "  clean      remove all intermediate RST files"
 	@echo "  clean-all  reset the entire build environment"
 	@echo "  txt2html   build txt2html tool"
-	@echo "  anchor_check  scan for duplicate anchor labels"
 
 # ------------------------------------------
 
@@ -46,19 +44,12 @@ clean-all:
 
 clean:
 	rm -rf $(RSTDIR) html
-	rm -rf spelling
 
-clean-spelling:
-	rm -rf spelling
-
-html: $(OBJECTS) $(ANCHORCHECK)
+html: $(OBJECTS)
 	@(\
 		. $(VENV)/bin/activate ;\
 		cp -r src/* $(RSTDIR)/ ;\
 		sphinx-build -j 8 -b html -c utils/sphinx-config -d $(BUILDDIR)/doctrees $(RSTDIR) html ;\
-		echo "############################################" ;\
-		doc_anchor_check src/*.txt ;\
-		echo "############################################" ;\
 		deactivate ;\
 	)
 	-rm html/searchindex.js
@@ -73,17 +64,6 @@ html: $(OBJECTS) $(ANCHORCHECK)
 	@rm -rf html/USER/*/*.[sg]*
 	@echo "Build finished. The HTML pages are in doc/html."
 
-spelling: $(OBJECTS) utils/sphinx-config/false_positives.txt
-	@(\
-		. $(VENV)/bin/activate ;\
-		pip install sphinxcontrib-spelling ;\
-		cp -r src/* $(RSTDIR)/ ;\
-        cp utils/sphinx-config/false_positives.txt $(RSTDIR)/ ;\
-		sphinx-build -b spelling -c utils/sphinx-config -d $(BUILDDIR)/doctrees $(RSTDIR) spelling ;\
-		deactivate ;\
-	)
-	@echo "Spell check finished."
-
 epub: $(OBJECTS)
 	@mkdir -p epub
 	@rm -f LAMMPS.epub
@@ -100,7 +80,6 @@ epub: $(OBJECTS)
 
 pdf: utils/txt2html/txt2html.exe
 	@(\
-		set -e; \
 		cd src; \
 		../utils/txt2html/txt2html.exe -b *.txt; \
 		htmldoc --batch lammps.book;          \
@@ -133,13 +112,6 @@ fetch:
 
 txt2html: utils/txt2html/txt2html.exe
 
-anchor_check : $(ANCHORCHECK)
-	@(\
-		. $(VENV)/bin/activate ;\
-		doc_anchor_check src/*.txt ;\
-		deactivate ;\
-	)
-
 # ------------------------------------------
 
 utils/txt2html/txt2html.exe: utils/txt2html/txt2html.cpp
@@ -159,12 +131,12 @@ $(VENV):
 	@( \
 		virtualenv -p $(PYTHON) $(VENV); \
 		. $(VENV)/bin/activate; \
-		pip install Sphinx==1.5.6; \
+		pip install Sphinx; \
 		pip install sphinxcontrib-images; \
 		deactivate;\
 	)
 
-$(TXT2RST) $(ANCHORCHECK): $(VENV)
+$(TXT2RST): $(VENV)
 	@( \
 		. $(VENV)/bin/activate; \
 		(cd utils/converters;\

doc/src/2001/input_commands.html

@@ -464,7 +464,7 @@ the angletype option can only be assigned to a "fix style" of "shake",
   entirely rigid (e.g. water)
 the angletype option enables an additional check when SHAKE constraints
   are computed: if a cluster is of size 3 and both bonds in
-  the cluster are of a bondtype specified by the 2nd parameter of
+  the cluster are of a bondtype specified by the 2nd paramter of
   angletype, then the cluster is SHAKEn with an additional angle
   constraint that makes it rigid, using the equilibrium angle appropriate
   to the specified angletype
@@ -476,7 +476,7 @@ IMPORTANT NOTE: the angletype option has one additional affect, namely
   since they will not be SHAKEn but neither will the angle force by computed
 for style region, a coeff of INF means + or - infinity (all the way 
   to the boundary)
-an atom can be assigned to multiple constraints, the constraints will be
+an atom can be assigned to multiple constraints, the contraints will be
   applied in the reverse order they are assigned to that atom
   (e.g. each timestep, the last fix assigned to an atom will be applied 
   to it first, then the next-to-last applied second, etc)
@@ -689,7 +689,7 @@ coeffs:  types
          remainder
                no other parameters required
        
-used with "create temp" command to initialize velocities of atoms
+used with "create temp" commmand to initialize velocities of atoms
 by default, the "create temp" command initializes the velocities of all atoms,
   this command limits the initialization to a group of atoms
 this command is only in force for the next "create temp" command, any
@@ -1263,7 +1263,7 @@ when using constraints with the minimizer, fixes are
   applied when atoms move except for the following
 fixes associated with temperature control are not allowed
   (rescale, hoover/drag, langevin)
-the minimizer does not invoke the "fix style shake" constraints on
+the minimizer does not invoke the "fix style shake" contraints on
   bond lengths
 the minimizer does not invoke pressure control or volume control settings
 for good convergence, should specify use of smooth nonbond force fields 
@@ -1566,7 +1566,7 @@ mesh dimensions that are power-of-two are fastest for FFTs, but any sizes
   can be used that are supported by native machine libraries
 this command is optional - if not used, a default
   mesh size will be chosen to satisfy accuracy criterion - if used, the
-  specified mesh size will override the default
+  specifed mesh size will override the default
 </PRE>
 <HR>
 <H3>
@@ -1788,7 +1788,7 @@ if the style is 2, restart information will be written alternately to files
 when the minimizer is invoked this command means create a restart file
   at the end of the minimization with the filename filename.timestep.min
 a restart file stores atom and force-field information in binary form
-allows program to restart from where it left off (see &quot;read restart&quot; command)
+allows program to restart from where it left off (see &quot;read restart&quot; commmand)
 
 Default = 0
 </PRE>

doc/src/99/basics.html

@@ -167,7 +167,7 @@ tool on the small-system data file.</P>
 <P>
 (6) flow</P>
 <P>
-2-d flow of Lennard-Jones atoms in a channel using various constraint
+2-d flow of Lennard-Jones atoms in a channel using various contraint 
 options.</P>
 <P>
 (7) polymer</P>
@@ -201,7 +201,7 @@ The tools directory also has a F77 program called setup_chain.f
 (compile and link with print.c) which can be used to generate random 
 initial polymer configurations for bead-spring models like those used 
 in examples/polymer. It uses an input polymer definition file (see 
-examples/polymer for two sample def files) that specifies how many
+examples/polymer for two sample def files) that specfies how many 
 chains of what length, a random number seed, etc.</P>
 </BODY>
 </HTML>

doc/src/99/crib.html

@@ -40,7 +40,7 @@ Note: this file is somewhat out-of-date for LAMMPS 99.</P>
     <LI>
     maxtype = max # of atom types 
     <LI>
-    maxbond = max # of bonds to compute on one processor
+    maxbond = max # of bonds to compute on one procesor 
     <LI>
     maxangle = max # of angles to compute on one processor 
     <LI>

doc/src/99/input_commands.html

@@ -294,7 +294,7 @@ assign a group of atoms to a particular constraint
 use appropriate number of coeffs for a particular style
 the constraint itself is defined by the "fix style" command
 multiple groups of atoms can be assigned to the same constraint
-an atom can be assigned to multiple constraints, the constraints will be
+an atom can be assigned to multiple constraints, the contraints will be
   applied in the reverse order they are assigned to that atom
   (e.g. each timestep, the last fix assigned to an atom will be applied 
   to it first, then the next-to-last applied second, etc)
@@ -477,7 +477,7 @@ coeffs:  types
          remainder
                no other parameters required
        
-used with "create temp" command to initialize velocities of atoms
+used with "create temp" commmand to initialize velocities of atoms
 by default, the "create temp" command initializes the velocities of all atoms,
   this command limits the initialization to a group of atoms
 this command is only in force for the next "create temp" command, any
@@ -1124,7 +1124,7 @@ mesh dimensions that are power-of-two are fastest for FFTs, but any size
   can be used that are supported by native machine libraries
 this command is optional - if not used, a default
   mesh size will be chosen to satisfy accuracy criterion - if used, the
-  specified mesh size will override the default
+  specifed mesh size will override the default
 
 Default = none
 </PRE>
@@ -1343,7 +1343,7 @@ value of 0 means never create one
 program will toggle between 2 filenames as the run progresses
   so always have at least one good file even if the program dies in mid-write
 restart file stores atom positions and velocities in binary form
-allows program to restart from where it left off (see &quot;read restart&quot; command)
+allows program to restart from where it left off (see &quot;read restart&quot; commmand)
 
 Default = 0
 </PRE>

doc/src/Eqs/cnp_cutoff.tex

@@ -1,14 +0,0 @@
-\documentclass[12pt,article]{article}
-
-\usepackage{indentfirst}
-\usepackage{amsmath}
-
-\begin{document}
-
-\begin{eqnarray*}
-  r_{c}^{fcc} & = & \frac{1}{2} \left(\frac{\sqrt{2}}{2} + 1\right) \mathrm{a} \simeq 0.8536 \:\mathrm{a} \\
-  r_{c}^{bcc} & = & \frac{1}{2}(\sqrt{2} + 1) \mathrm{a} \simeq 1.207 \:\mathrm{a} \\
-  r_{c}^{hcp} & = & \frac{1}{2}\left(1+\sqrt{\frac{4+2x^{2}}{3}}\right) \mathrm{a}
-\end{eqnarray*}
-
-\end{document}

doc/src/Eqs/cnp_cutoff2.tex

@@ -1,12 +0,0 @@
-\documentclass[12pt,article]{article}
-
-\usepackage{indentfirst}
-\usepackage{amsmath}
-
-\begin{document}
-
-$$
-  Rc + Rs > 2*{\rm cutoff}
-$$
-
-\end{document}

doc/src/Eqs/cnp_eq.tex

@@ -1,9 +0,0 @@
-\documentclass[12pt]{article}
-
-\begin{document}
-
-$$
-   Q_{i} = \frac{1}{n_i}\sum_{j = 1}^{n_i} | \sum_{k = 1}^{n_{ij}}  \vec{R}_{ik} + \vec{R}_{jk} |^2
-$$
-
-\end{document}

doc/src/Eqs/fix_gcmc1.tex

@@ -1,9 +0,0 @@
-\documentclass[12pt]{article}
-
-\begin{document}
-
-\begin{eqnarray*}
-\mu &=&\mu^{id} + \mu^{ex}
-\end{eqnarray*}
-
-\end{document}

doc/src/Eqs/fix_gcmc2.tex

@@ -1,10 +0,0 @@
-\documentclass[12pt]{article}
-
-\begin{document}
-
-\begin{eqnarray*}
-\mu^{id} &=& k T \ln{\rho \Lambda^3} \\
-&=& k T \ln{\frac{\phi P \Lambda^3}{k T}} 
-\end{eqnarray*}
-
-\end{document}

doc/src/Eqs/fix_gcmc3.tex

@@ -1,9 +0,0 @@
-\documentclass[12pt]{article}
-
-\begin{document}
-
-\begin{eqnarray*}
-\Lambda &=& \sqrt{ \frac{h^2}{2 \pi m k T}}
-\end{eqnarray*}
-
-\end{document}

doc/src/Eqs/fix_wall_ees.tex

@@ -1,10 +0,0 @@
-\documentclass[12pt]{article}
-
-\begin{document}
-
-$$ 
-E = \epsilon \left[ \frac{2  \sigma_{LJ}^{12} \left(7 r^5+14 r^3 \sigma_{n}^2+3 r \sigma_{n}^4\right) }{945 \left(r^2-\sigma_{n}^2\right)^7} -\frac{ \sigma_{LJ}^6 \left(2 r \sigma_{n}^3+\sigma_{n}^2 \left(r^2-\sigma_{n}^2\right)\log{ \left[\frac{r-\sigma_{n}}{r+\sigma_{n}}\right]}\right) }{12 \sigma_{n}^5 \left(r^2-\sigma_{n}^2\right)} \right]\qquad \sigma_n < r < r_c
-$$
-
-
-\end{document}

doc/src/Eqs/pair_kolmogorov_crespi_z.tex

@@ -1,13 +0,0 @@
-\documentclass[12pt]{article}
-\thispagestyle{empty}
-
-\begin{document}
-
-\begin{eqnarray*}
-  E & = & \frac{1}{2} \sum_i \sum_{j \neq i} V_{ij} \\
-  V_{ij} & = & e^{-\lambda(r_{ij} -z_0}) \left[ C + f(\rho_{ij}) + f(\rho_{ji}) \right] - A \left( \frac{r_{ij}}{z_0}\right)^{-6} + A \left( \frac{\textrm{cutoff}}{z_0}\right)^{-6} \\
-  \rho_{ij}^2 = \rho_{ji}^2 & = &  x_{ij}^2 + y_{ij}^2 ~\hspace{2cm} (\mathbf{n_i}\equiv\hat \mathbf{z})\\
-  f(\rho) & = &  e^{-(\rho/\delta)^2} \sum_{n=0}^2 C_{2n} \left( \rho/\delta \right) ^{2n}
-\end{eqnarray*}
-
-\end{document}

doc/src/Eqs/pair_lj_sf.tex

@@ -0,0 +1,11 @@
+\documentclass[12pt]{article}
+
+\begin{document}
+
+\begin{eqnarray*}
+ F & = & F_{\mathrm{LJ}}(r) - F_{\mathrm{LJ}}(r_{\mathrm{c}}) \qquad r < r_{\mathrm{c}} \\
+ E & = & E_{\mathrm{LJ}}(r) - E_{\mathrm{LJ}}(r_{\mathrm{c}}) + (r - r_{\mathrm{c}}) F_{\mathrm{LJ}}(r_{\mathrm{c}}) \qquad r < r_{\mathrm{c}} \\
+ \mathrm{with} \qquad E_{\mathrm{LJ}}(r) & = & 4 \epsilon \left[ \left(\frac{\sigma}{r}\right)^{12} - \left(\frac{\sigma}{r}\right)^6 \right] \qquad \mathrm{and} \qquad F_{\mathrm{LJ}}(r) = - E^\prime_{\mathrm{LJ}}(r)
+\end{eqnarray*}                           
+
+\end{document}

doc/src/Eqs/pair_meam_spline.tex

@@ -1,14 +1,13 @@
 \documentclass[12pt]{article}
-\usepackage{amsmath}
 
 \begin{document}
 
 $$
-   E=\sum_{i<j}\phi(r_{ij})+\sum_{i}U(n_{i}),
+   E=\sum_{ij}\phi(r_{ij})+\sum_{i}U(\rho_{i}),
 $$
 
 $$
-   n_{i}=\sum_{j}\rho(r_{ij})+\sum_{\substack{j<k,\\j,k\neq i}}f(r_{ij})f(r_{ik})g[\cos(\theta_{jik})]
+   \rho_{i}=\sum_{j}\rho(r_{ij})+\sum_{jk}f(r_{ij})f(r_{ik})g[\cos(\theta_{jik})]
 $$
 
 \end{document}

doc/src/Eqs/pair_meam_spline_multicomponent.tex

@@ -1,14 +0,0 @@
-\documentclass[12pt]{article}
-\usepackage{amsmath}
-
-\begin{document}
-
-$$
-   E=\sum_{i<j}\phi_{ij}(r_{ij})+\sum_{i}U_i(n_{i}),
-$$
-
-$$
-   n_{i}=\sum_{j\ne i}\rho_j(r_{ij})+\sum_{\substack{j<k,\\j,k\neq i}}f_{j}(r_{ij})f_{k}(r_{ik})g_{jk}[\cos(\theta_{jik})]
-$$
-
-\end{document}

doc/src/Eqs/pair_momb.tex

@@ -1,13 +0,0 @@
-\documentclass[12pt,fleqn]{article}
-\usepackage{amsmath}
-\thispagestyle{empty}
-
-\begin{document}
-
-\setlength{\jot}{2ex}
-\begin{gather*}
-  E = D_0 [\exp^{-2 \alpha (r-r_0)} - 2\exp^{-\alpha (r-r_0)}] - s_6 \frac{C_6}{r^6} f_{damp}(r,R_r) \\
-  f_{damp}(r,R_r) = \frac{1}{1 + \exp^{-d(r/R_r - 1)}}
-\end{gather*}
-
-\end{document}

doc/src/Manual.txt

@@ -1,7 +1,7 @@
 <!-- HTML_ONLY -->
 <HEAD>
 <TITLE>LAMMPS Users Manual</TITLE>
-<META NAME="docnumber" CONTENT="17 Aug 2017 version">
+<META NAME="docnumber" CONTENT="26 Jan 2017 version">
 <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.">
 </HEAD>
@@ -21,7 +21,7 @@
 <H1></H1>
 
 LAMMPS Documentation :c,h3
-17 Aug 2017 version :c,h4
+26 Jan 2017 version :c,h4
 
 Version info: :h4
 
@@ -39,7 +39,7 @@ directory name created when you unpack a tarball, and at the top of
 the first page of the manual (this page).
 
 If you browse the HTML doc pages on the LAMMPS WWW site, they always
-describe the most current [development] version of LAMMPS. :ulb,l
+describe the most current version of LAMMPS. :ulb,l
 
 If you browse the HTML doc pages included in your tarball, they
 describe the version you have. :l
@@ -67,7 +67,7 @@ Labs and Temple University:
 
 "Steve Plimpton"_sjp, sjplimp at sandia.gov :ulb,l
 Aidan Thompson, athomps at sandia.gov :l
-Stan Moore, stamoor at sandia.gov :l
+Stan Moore, stamoore at sandia.gov :l
 "Axel Kohlmeyer"_ako, akohlmey at gmail.com :l
 :ule
 
@@ -79,7 +79,7 @@ bug reports and feature requests are mainly coordinated through the
 "LAMMPS project on GitHub."_https://github.com/lammps/lammps
 The lammps.org domain, currently hosting "public continuous integration
 testing"_https://ci.lammps.org/job/lammps/ and "precompiled Linux
-RPM and Windows installer packages"_http://packages.lammps.org is located
+RPM and Windows installer packages"_http://rpm.lammps.org is located
 at Temple University and managed by Richard Berger,
 richard.berger at temple.edu.
 
@@ -158,11 +158,12 @@ END_RST -->
   2.1 "What's in the LAMMPS distribution"_start_1 :ulb,b
   2.2 "Making LAMMPS"_start_2 :b
   2.3 "Making LAMMPS with optional packages"_start_3 :b
-  2.4 "Building LAMMPS as a library"_start_4 :b
-  2.5 "Running LAMMPS"_start_5 :b
-  2.6 "Command-line options"_start_6 :b
-  2.7 "Screen output"_start_7 :b
-  2.8 "Tips for users of previous versions"_start_8 :ule,b
+  2.4 "Building LAMMPS via the Make.py script"_start_4 :b
+  2.5 "Building LAMMPS as a library"_start_5 :b
+  2.6 "Running LAMMPS"_start_6 :b
+  2.7 "Command-line options"_start_7 :b
+  2.8 "Screen output"_start_8 :b
+  2.9 "Tips for users of previous versions"_start_9 :ule,b
 "Commands"_Section_commands.html :l
   3.1 "LAMMPS input script"_cmd_1 :ulb,b
   3.2 "Parsing rules"_cmd_2 :b
@@ -261,6 +262,7 @@ END_RST -->
 :link(start_6,Section_start.html#start_6)
 :link(start_7,Section_start.html#start_7)
 :link(start_8,Section_start.html#start_8)
+:link(start_9,Section_start.html#start_9)
 
 :link(cmd_1,Section_commands.html#cmd_1)
 :link(cmd_2,Section_commands.html#cmd_2)

doc/src/Section_accelerate.txt

@@ -56,7 +56,7 @@ timings; you can simply extrapolate from short runs.
 
 For the set of runs, look at the timing data printed to the screen and
 log file at the end of each LAMMPS run.  "This
-section"_Section_start.html#start_7 of the manual has an overview.
+section"_Section_start.html#start_8 of the manual has an overview.
 
 Running on one (or a few processors) should give a good estimate of
 the serial performance and what portions of the timestep are taking
@@ -226,16 +226,16 @@ re-build LAMMPS |
   make machine |
 prepare and test a regular LAMMPS simulation |
   lmp_machine -in in.script; mpirun -np 32 lmp_machine -in in.script |
-enable specific accelerator support via '-k on' "command-line switch"_Section_start.html#start_6, |
+enable specific accelerator support via '-k on' "command-line switch"_Section_start.html#start_7, |
   only needed for KOKKOS package |
-set any needed options for the package via "-pk" "command-line switch"_Section_start.html#start_6 or "package"_package.html command, |
+set any needed options for the package via "-pk" "command-line switch"_Section_start.html#start_7 or "package"_package.html command, |
   only if defaults need to be changed |
-use accelerated styles in your input via "-sf" "command-line switch"_Section_start.html#start_6 or "suffix"_suffix.html command | lmp_machine -in in.script -sf gpu
+use accelerated styles in your input via "-sf" "command-line switch"_Section_start.html#start_7 or "suffix"_suffix.html command | lmp_machine -in in.script -sf gpu
 :tb(c=2,s=|)
 
-Note that the first 4 steps can be done as a single command with
-suitable make command invocations. This is discussed in "Section
-4"_Section_packages.html of the manual, and its use is
+Note that the first 4 steps can be done as a single command, using the
+src/Make.py tool.  This tool is discussed in "Section
+2.4"_Section_start.html#start_4 of the manual, and its use is
 illustrated in the individual accelerator sections.  Typically these
 steps only need to be done once, to create an executable that uses one
 or more accelerator packages.

doc/src/Section_commands.txt

@@ -281,12 +281,12 @@ the "minimize"_minimize.html command.  A parallel tempering
 
 3.4 Commands listed by category :link(cmd_4),h4
 
-This section lists core LAMMPS commands, grouped by category.
-The "next section"_#cmd_5 lists all commands alphabetically.  The
+This section lists all LAMMPS commands, grouped by category.  The
+"next section"_#cmd_5 lists the same commands alphabetically.  The
 next section also includes (long) lists of style options for entries
 that appear in the following categories as a single command (fix,
 compute, pair, etc).  Commands that are added by user packages are not
-included in the categories here, but they are in the next section.
+included in these categories, but they are in the next section.
 
 Initialization:
 
@@ -361,7 +361,7 @@ Settings:
 "timer"_timer.html,
 "timestep"_timestep.html
 
-Operations within timestepping (fixes) and diagnostics (computes):
+Operations within timestepping (fixes) and diagnositics (computes):
 
 "compute"_compute.html,
 "compute_modify"_compute_modify.html,
@@ -527,9 +527,9 @@ These are additional commands in USER packages, which can be used if
 "LAMMPS is built with the appropriate
 package"_Section_start.html#start_3.
 
-"dump netcdf"_dump_netcdf.html,
-"dump netcdf/mpiio"_dump_netcdf.html,
-"dump vtk"_dump_vtk.html,
+"dump custom/vtk"_dump_custom_vtk.html,
+"dump nc"_dump_nc.html,
+"dump nc/mpiio"_dump_nc.html,
 "group2ndx"_group2ndx.html,
 "ndx2group"_group2ndx.html,
 "temper/grem"_temper_grem.html :tb(c=3,ea=c)
@@ -618,7 +618,6 @@ USER-INTEL, k = KOKKOS, o = USER-OMP, t = OPT.
 "press/berendsen"_fix_press_berendsen.html,
 "print"_fix_print.html,
 "property/atom"_fix_property_atom.html,
-"python"_fix_python.html,
 "qeq/comb (o)"_fix_qeq_comb.html,
 "qeq/dynamic"_fix_qeq.html,
 "qeq/fire"_fix_qeq.html,
@@ -688,7 +687,6 @@ package"_Section_start.html#start_3.
 "eos/cv"_fix_eos_cv.html,
 "eos/table"_fix_eos_table.html,
 "eos/table/rx"_fix_eos_table_rx.html,
-"filter/corotate"_fix_filter_corotate.html,
 "flow/gauss"_fix_flow_gauss.html,
 "gle"_fix_gle.html,
 "grem"_fix_grem.html,
@@ -717,7 +715,7 @@ package"_Section_start.html#start_3.
 "phonon"_fix_phonon.html,
 "pimd"_fix_pimd.html,
 "qbmsst"_fix_qbmsst.html,
-"qeq/reax (ko)"_fix_qeq_reax.html,
+"qeq/reax"_fix_qeq_reax.html,
 "qmmm"_fix_qmmm.html,
 "qtb"_fix_qtb.html,
 "reax/c/bonds"_fix_reax_bonds.html,
@@ -734,9 +732,7 @@ package"_Section_start.html#start_3.
 "smd/wall/surface"_fix_smd_wall_surface.html,
 "temp/rescale/eff"_fix_temp_rescale_eff.html,
 "ti/spring"_fix_ti_spring.html,
-"ttm/mod"_fix_ttm.html,
-"wall/ees"_fix_wall_ees.html,
-"wall/region/ees"_fix_wall_ees.html :tb(c=6,ea=c)
+"ttm/mod"_fix_ttm.html :tb(c=6,ea=c)
 
 :line
 
@@ -833,7 +829,6 @@ package"_Section_start.html#start_3.
 
 "ackland/atom"_compute_ackland_atom.html,
 "basal/atom"_compute_basal_atom.html,
-"cnp/atom"_compute_cnp_atom.html,
 "dpd"_compute_dpd.html,
 "dpd/atom"_compute_dpd_atom.html,
 "fep"_compute_fep.html,
@@ -892,8 +887,8 @@ KOKKOS, o = USER-OMP, t = OPT.
 "hybrid"_pair_hybrid.html,
 "hybrid/overlay"_pair_hybrid.html,
 "adp (o)"_pair_adp.html,
-"airebo (oi)"_pair_airebo.html,
-"airebo/morse (oi)"_pair_airebo.html,
+"airebo (o)"_pair_airebo.html,
+"airebo/morse (o)"_pair_airebo.html,
 "beck (go)"_pair_beck.html,
 "body"_pair_body.html,
 "bop"_pair_bop.html,
@@ -927,27 +922,23 @@ KOKKOS, o = USER-OMP, t = OPT.
 "dpd/tstat (go)"_pair_dpd.html,
 "dsmc"_pair_dsmc.html,
 "eam (gkiot)"_pair_eam.html,
-"eam/alloy (gkiot)"_pair_eam.html,
-"eam/fs (gkiot)"_pair_eam.html,
+"eam/alloy (gkot)"_pair_eam.html,
+"eam/fs (gkot)"_pair_eam.html,
 "eim (o)"_pair_eim.html,
 "gauss (go)"_pair_gauss.html,
 "gayberne (gio)"_pair_gayberne.html,
 "gran/hertz/history (o)"_pair_gran.html,
 "gran/hooke (o)"_pair_gran.html,
 "gran/hooke/history (o)"_pair_gran.html,
-"gw"_pair_gw.html,
-"gw/zbl"_pair_gw.html,
 "hbond/dreiding/lj (o)"_pair_hbond_dreiding.html,
 "hbond/dreiding/morse (o)"_pair_hbond_dreiding.html,
 "kim"_pair_kim.html,
 "lcbop"_pair_lcbop.html,
 "line/lj"_pair_line_lj.html,
-"lj/charmm/coul/charmm (kio)"_pair_charmm.html,
+"lj/charmm/coul/charmm (ko)"_pair_charmm.html,
 "lj/charmm/coul/charmm/implicit (ko)"_pair_charmm.html,
-"lj/charmm/coul/long (gkio)"_pair_charmm.html,
+"lj/charmm/coul/long (giko)"_pair_charmm.html,
 "lj/charmm/coul/msm"_pair_charmm.html,
-"lj/charmmfsw/coul/charmmfsh"_pair_charmm.html,
-"lj/charmmfsw/coul/long"_pair_charmm.html,
 "lj/class2 (gko)"_pair_class2.html,
 "lj/class2/coul/cut (ko)"_pair_class2.html,
 "lj/class2/coul/long (gko)"_pair_class2.html,
@@ -966,7 +957,7 @@ KOKKOS, o = USER-OMP, t = OPT.
 "lj/expand (gko)"_pair_lj_expand.html,
 "lj/gromacs (gko)"_pair_gromacs.html,
 "lj/gromacs/coul/gromacs (ko)"_pair_gromacs.html,
-"lj/long/coul/long (io)"_pair_lj_long.html,
+"lj/long/coul/long (o)"_pair_lj_long.html,
 "lj/long/dipole/long"_pair_dipole.html,
 "lj/long/tip4p/long"_pair_lj_long.html,
 "lj/smooth (o)"_pair_lj_smooth.html,
@@ -978,7 +969,7 @@ KOKKOS, o = USER-OMP, t = OPT.
 "lubricateU/poly"_pair_lubricateU.html,
 "meam"_pair_meam.html,
 "mie/cut (o)"_pair_mie.html,
-"morse (gkot)"_pair_morse.html,
+"morse (got)"_pair_morse.html,
 "nb3b/harmonic (o)"_pair_nb3b_harmonic.html,
 "nm/cut (o)"_pair_nm.html,
 "nm/cut/coul/cut (o)"_pair_nm.html,
@@ -988,9 +979,8 @@ KOKKOS, o = USER-OMP, t = OPT.
 "peri/pmb (o)"_pair_peri.html,
 "peri/ves"_pair_peri.html,
 "polymorphic"_pair_polymorphic.html,
-"python"_pair_python.html,
 "reax"_pair_reax.html,
-"rebo (oi)"_pair_airebo.html,
+"rebo (o)"_pair_airebo.html,
 "resquared (go)"_pair_resquared.html,
 "snap"_pair_snap.html,
 "soft (go)"_pair_soft.html,
@@ -1023,11 +1013,9 @@ package"_Section_start.html#start_3.
 "dpd/fdt/energy"_pair_dpd_fdt.html,
 "eam/cd (o)"_pair_eam.html,
 "edip (o)"_pair_edip.html,
-"edip/multi"_pair_edip.html,
 "eff/cut"_pair_eff.html,
 "exp6/rx"_pair_exp6_rx.html,
 "gauss/cut"_pair_gauss.html,
-"kolmogorov/crespi/z"_pair_kolmogorov_crespi_z.html,
 "lennard/mdf"_pair_mdf.html,
 "list"_pair_list.html,
 "lj/charmm/coul/long/soft (o)"_pair_charmm.html,
@@ -1041,11 +1029,10 @@ package"_Section_start.html#start_3.
 "lj/sdk (gko)"_pair_sdk.html,
 "lj/sdk/coul/long (go)"_pair_sdk.html,
 "lj/sdk/coul/msm (o)"_pair_sdk.html,
-"meam/c"_pair_meam.html,
+"lj/sf (o)"_pair_lj_sf.html,
 "meam/spline (o)"_pair_meam_spline.html,
 "meam/sw/spline"_pair_meam_sw_spline.html,
 "mgpt"_pair_mgpt.html,
-"momb"_pair_momb.html,
 "morse/smooth/linear"_pair_morse.html,
 "morse/soft"_pair_morse.html,
 "multi/lucy"_pair_multi_lucy.html,
@@ -1055,12 +1042,8 @@ package"_Section_start.html#start_3.
 "oxdna/hbond"_pair_oxdna.html,
 "oxdna/stk"_pair_oxdna.html,
 "oxdna/xstk"_pair_oxdna.html,
-"oxdna2/coaxstk"_pair_oxdna2.html,
-"oxdna2/dh"_pair_oxdna2.html,
-"oxdna2/excv"_pair_oxdna2.html,
-"oxdna2/stk"_pair_oxdna2.html,
 "quip"_pair_quip.html,
-"reax/c (ko)"_pair_reaxc.html,
+"reax/c (k)"_pair_reax_c.html,
 "smd/hertz"_pair_smd_hertz.html,
 "smd/tlsph"_pair_smd_tlsph.html,
 "smd/triangulated/surface"_pair_smd_triangulated_surface.html,
@@ -1093,7 +1076,7 @@ KOKKOS, o = USER-OMP, t = OPT.
 "none"_bond_none.html,
 "zero"_bond_zero.html,
 "hybrid"_bond_hybrid.html,
-"class2 (ko)"_bond_class2.html,
+"class2 (o)"_bond_class2.html,
 "fene (iko)"_bond_fene.html,
 "fene/expand (o)"_bond_fene_expand.html,
 "harmonic (ko)"_bond_harmonic.html,
@@ -1108,8 +1091,7 @@ package"_Section_start.html#start_3.
 
 "harmonic/shift (o)"_bond_harmonic_shift.html,
 "harmonic/shift/cut (o)"_bond_harmonic_shift_cut.html,
-"oxdna/fene"_bond_oxdna.html,
-"oxdna2/fene"_bond_oxdna.html :tb(c=4,ea=c)
+"oxdna/fene"_bond_oxdna_fene.html :tb(c=4,ea=c)
 
 :line
 
@@ -1127,7 +1109,7 @@ USER-OMP, t = OPT.
 "zero"_angle_zero.html,
 "hybrid"_angle_hybrid.html,
 "charmm (ko)"_angle_charmm.html,
-"class2 (ko)"_angle_class2.html,
+"class2 (o)"_angle_class2.html,
 "cosine (o)"_angle_cosine.html,
 "cosine/delta (o)"_angle_cosine_delta.html,
 "cosine/periodic (o)"_angle_cosine_periodic.html,
@@ -1163,8 +1145,7 @@ USER-OMP, t = OPT.
 "zero"_dihedral_zero.html,
 "hybrid"_dihedral_hybrid.html,
 "charmm (ko)"_dihedral_charmm.html,
-"charmmfsw"_dihedral_charmm.html,
-"class2 (ko)"_dihedral_class2.html,
+"class2 (o)"_dihedral_class2.html,
 "harmonic (io)"_dihedral_harmonic.html,
 "helix (o)"_dihedral_helix.html,
 "multi/harmonic (o)"_dihedral_multi_harmonic.html,
@@ -1196,7 +1177,7 @@ USER-OMP, t = OPT.
 "none"_improper_none.html,
 "zero"_improper_zero.html,
 "hybrid"_improper_hybrid.html,
-"class2 (ko)"_improper_class2.html,
+"class2 (o)"_improper_class2.html,
 "cvff (io)"_improper_cvff.html,
 "harmonic (ko)"_improper_harmonic.html,
 "umbrella (o)"_improper_umbrella.html :tb(c=4,ea=c)
@@ -1228,7 +1209,7 @@ USER-OMP, t = OPT.
 "msm/cg (o)"_kspace_style.html,
 "pppm (go)"_kspace_style.html,
 "pppm/cg (o)"_kspace_style.html,
-"pppm/disp (i)"_kspace_style.html,
+"pppm/disp"_kspace_style.html,
 "pppm/disp/tip4p"_kspace_style.html,
 "pppm/stagger"_kspace_style.html,
 "pppm/tip4p (o)"_kspace_style.html :tb(c=4,ea=c)

doc/src/Section_errors.txt

@@ -22,7 +22,7 @@ either conceptually, or as printed out by the program.
 
 12.1 Common problems :link(err_1),h4
 
-If two LAMMPS runs do not produce the exact same answer on different
+If two LAMMPS runs do not produce the same answer on different
 machines or different numbers of processors, this is typically not a
 bug.  In theory you should get identical answers on any number of
 processors and on any machine.  In practice, numerical round-off can
@@ -71,7 +71,7 @@ style", with ... being fix, compute, pair, etc, it means that you
 mistyped the style name or that the command is part of an optional
 package which was not compiled into your executable.  The list of
 available styles in your executable can be listed by using "the -h
-command-line argument"_Section_start.html#start_6.  The installation
+command-line argument"_Section_start.html#start_7.  The installation
 and compilation of optional packages is explained in the "installation
 instructions"_Section_start.html#start_3.
 
@@ -80,24 +80,12 @@ order.  If you mess this up, LAMMPS will often flag the error, but it
 may also simply read a bogus argument and assign a value that is
 valid, but not what you wanted.  E.g. trying to read the string "abc"
 as an integer value of 0.  Careful reading of the associated doc page
-for the command should allow you to fix these problems. In most cases,
-where LAMMPS expects to read a number, either integer or floating point,
-it performs a stringent test on whether the provided input actually
-is an integer or floating-point number, respectively, and reject the
-input with an error message (for instance, when an integer is required,
-but a floating-point number 1.0 is provided):
-
-ERROR: Expected integer parameter in input script or data file :pre
-
-Some commands allow for using variable references in place of numeric
-constants so that the value can be evaluated and may change over the
-course of a run.  This is typically done with the syntax {v_name} for a
-parameter, where name is the name of the variable. On the other hand,
-immediate variable expansion with the syntax ${name} is performed while
-reading the input and before parsing commands,
-
-NOTE: Using a variable reference (i.e. {v_name}) is only allowed if
-the documentation of the corresponding command explicitly says it is.
+for the command should allow you to fix these problems.  Note that
+some commands allow for variables to be specified in place of numeric
+constants so that the value can be evaluated and change over the
+course of a run.  This is typically done with the syntax {v_name} for
+a parameter, where name is the name of the variable.  This is only
+allowed if the command documentation says it is.
 
 Generally, LAMMPS will print a message to the screen and logfile and
 exit gracefully when it encounters a fatal error.  Sometimes it will
@@ -574,11 +562,11 @@ group of atoms correctly. :dd
 
 {Bad quadratic solve for particle/line collision} :dt
 
-This is an internal error.  It should normally not occur. :dd
+This is an internal error.  It should nornally not occur. :dd
 
 {Bad quadratic solve for particle/tri collision} :dt
 
-This is an internal error.  It should normally not occur. :dd
+This is an internal error.  It should nornally not occur. :dd
 
 {Bad real space Coulomb cutoff in fix tune/kspace} :dt
 
@@ -912,7 +900,7 @@ Atoms can not be added afterwards to this fix option. :dd
 
 {Cannot append atoms to a triclinic box} :dt
 
-The simulation box must be defined with edges aligned with the
+The simulation box must be defined with edges alligned with the
 Cartesian axes. :dd
 
 {Cannot balance in z dimension for 2d simulation} :dt
@@ -992,7 +980,7 @@ file. :dd
 
 LAMMPS failed to compute an initial guess for the PPPM_disp g_ewald_6
 factor that partitions the computation between real space and k-space
-for Dispersion interactions. :dd
+for Disptersion interactions. :dd
 
 {Cannot create an atom map unless atoms have IDs} :dt
 
@@ -1327,7 +1315,7 @@ Self-explanatory. :dd
 
 This file is created when you use some LAMMPS features, to indicate
 what paper you should cite on behalf of those who implemented
-the feature.  Check that you have write privileges into the directory
+the feature.  Check that you have write priveleges into the directory
 you are running in. :dd
 
 {Cannot open log.lammps for writing} :dt
@@ -2005,7 +1993,7 @@ Self-explanatory. :dd
 
 {Cannot use fix reax/bonds without pair_style reax} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Cannot use fix rigid npt/nph and fix deform on same component of stress tensor} :dt
 
@@ -2088,7 +2076,7 @@ Self-explanatory. :dd
 
 {Cannot use lines with fix srd unless overlap is set} :dt
 
-This is because line segments are connected to each other. :dd
+This is because line segements are connected to each other. :dd
 
 {Cannot use multiple fix wall commands with pair brownian} :dt
 
@@ -2131,7 +2119,7 @@ Self-explanatory. :dd
 
 {Cannot use newton pair with born/gpu pair style} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Cannot use newton pair with buck/coul/cut/gpu pair style} :dt
 
@@ -2291,7 +2279,7 @@ Self-explanatory. :dd
 
 {Cannot use newton pair with zbl/gpu pair style} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Cannot use non-zero forces in an energy minimization} :dt
 
@@ -2641,11 +2629,11 @@ uses a pairwise neighbor list. :dd
 
 {Compute chunk/atom bin/cylinder radius is too large for periodic box} :dt
 
-Radius cannot be bigger than 1/2 of a non-axis  periodic dimension. :dd
+Radius cannot be bigger than 1/2 of a non-axis  periodic dimention. :dd
 
 {Compute chunk/atom bin/sphere radius is too large for periodic box} :dt
 
-Radius cannot be bigger than 1/2 of any periodic dimension. :dd
+Radius cannot be bigger than 1/2 of any periodic dimention. :dd
 
 {Compute chunk/atom compute array is accessed out-of-range} :dt
 
@@ -2706,15 +2694,15 @@ It will only store IDs if its compress option is enabled. :dd
 
 {Compute chunk/atom stores no coord1 for compute property/chunk} :dt
 
-Only certain binning options for compute chunk/atom store coordinates. :dd
+Only certain binning options for comptue chunk/atom store coordinates. :dd
 
 {Compute chunk/atom stores no coord2 for compute property/chunk} :dt
 
-Only certain binning options for compute chunk/atom store coordinates. :dd
+Only certain binning options for comptue chunk/atom store coordinates. :dd
 
 {Compute chunk/atom stores no coord3 for compute property/chunk} :dt
 
-Only certain binning options for compute chunk/atom store coordinates. :dd
+Only certain binning options for comptue chunk/atom store coordinates. :dd
 
 {Compute chunk/atom variable is not atom-style variable} :dt
 
@@ -2735,11 +2723,11 @@ is used to find clusters. :dd
 
 {Compute cna/atom cutoff is longer than pairwise cutoff} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Compute cna/atom requires a pair style be defined} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Compute com/chunk does not use chunk/atom compute} :dt
 
@@ -2747,7 +2735,7 @@ The style of the specified compute is not chunk/atom. :dd
 
 {Compute contact/atom requires a pair style be defined} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Compute contact/atom requires atom style sphere} :dt
 
@@ -2760,7 +2748,7 @@ since those atoms are not in the neighbor list. :dd
 
 {Compute coord/atom requires a pair style be defined} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Compute damage/atom requires peridynamic potential} :dt
 
@@ -2790,7 +2778,7 @@ Self-explanatory. :dd
 
 {Compute erotate/asphere requires extended particles} :dt
 
-This compute cannot be used with point particles. :dd
+This compute cannot be used with point paritlces. :dd
 
 {Compute erotate/rigid with non-rigid fix-ID} :dt
 
@@ -2835,7 +2823,7 @@ Cannot compute order parameter beyond cutoff. :dd
 
 {Compute hexorder/atom requires a pair style be defined} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Compute improper/local used when impropers are not allowed} :dt
 
@@ -2881,11 +2869,11 @@ Cannot compute order parameter beyond cutoff. :dd
 
 {Compute orientorder/atom requires a pair style be defined} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Compute pair must use group all} :dt
 
-Pair styles accumulate energy on all atoms. :dd
+Pair styles accumlate energy on all atoms. :dd
 
 {Compute pe must use group all} :dt
 
@@ -2935,7 +2923,7 @@ The style of the specified compute is not chunk/atom. :dd
 {Compute property/local cannot use these inputs together} :dt
 
 Only inputs that generate the same number of datums can be used
-together.  E.g. bond and angle quantities cannot be mixed. :dd
+togther.  E.g. bond and angle quantities cannot be mixed. :dd
 
 {Compute property/local does not (yet) work with atom_style template} :dt
 
@@ -3079,7 +3067,7 @@ Self-explanatory. :dd
 
 {Compute temp/asphere requires extended particles} :dt
 
-This compute cannot be used with point particles. :dd
+This compute cannot be used with point paritlces. :dd
 
 {Compute temp/body requires atom style body} :dt
 
@@ -3524,12 +3512,12 @@ path and name are correct. :dd
 
 {Could not process Python file} :dt
 
-The Python code in the specified file was not run successfully by
+The Python code in the specified file was not run sucessfully by
 Python, probably due to errors in the Python code. :dd
 
 {Could not process Python string} :dt
 
-The Python code in the here string was not run successfully by Python,
+The Python code in the here string was not run sucessfully by Python,
 probably due to errors in the Python code. :dd
 
 {Coulomb PPPMDisp order has been reduced below minorder} :dt
@@ -3638,7 +3626,7 @@ Self-explanatory. :dd
 
 {Cutoffs missing in pair_style buck/long/coul/long} :dt
 
-Self-explanatory. :dd
+Self-exlanatory. :dd
 
 {Cutoffs missing in pair_style lj/long/coul/long} :dt
 
@@ -4385,7 +4373,7 @@ Self-explanatory. :dd
 
 {Fix ave/chunk does not use chunk/atom compute} :dt
 
-The specified compute is not for a compute chunk/atom command. :dd
+The specified conpute is not for a compute chunk/atom command. :dd
 
 {Fix ave/chunk fix does not calculate a per-atom array} :dt
 
@@ -4617,11 +4605,11 @@ An index for the array is out of bounds. :dd
 
 {Fix ave/time compute does not calculate a scalar} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Fix ave/time compute does not calculate a vector} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Fix ave/time compute does not calculate an array} :dt
 
@@ -4696,9 +4684,9 @@ Self-explanatory. :dd
 
 {Fix bond/create induced too many angles/dihedrals/impropers per atom} :dt
 
-See the read_data command for info on using the "extra/angle/per/atom",
-(or dihedral, improper) keywords to allow for additional
-angles, dihedrals, and impropers to be formed. :dd
+See the read_data command for info on setting the "extra angle per
+atom", etc header values to allow for additional angles, etc to be
+formed. :dd
 
 {Fix bond/create needs ghost atoms from further away} :dt
 
@@ -4970,7 +4958,7 @@ Self-explanatory. :dd
 
 {Fix langevin angmom requires extended particles} :dt
 
-This fix option cannot be used with point particles. :dd
+This fix option cannot be used with point paritlces. :dd
 
 {Fix langevin omega is not yet implemented with kokkos} :dt
 
@@ -6171,7 +6159,7 @@ map command will force an atom map to be created. :dd
 
 {Initial temperatures not all set in fix ttm} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Input line quote not followed by whitespace} :dt
 
@@ -6199,7 +6187,7 @@ Eigensolve for rigid body was not sufficiently accurate. :dd
 
 {Insufficient Jacobi rotations for triangle} :dt
 
-The calculation of the inertia tensor of the triangle failed.  This
+The calculation of the intertia tensor of the triangle failed.  This
 should not happen if it is a reasonably shaped triangle. :dd
 
 {Insufficient memory on accelerator} :dt
@@ -6463,15 +6451,15 @@ Self-explanatory. :dd
 
 {Invalid attribute in dump custom command} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Invalid attribute in dump local command} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Invalid attribute in dump modify command} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Invalid basis setting in create_atoms command} :dt
 
@@ -6737,7 +6725,7 @@ or cause multiple files to be written. :dd
 Filenames used with the dump xyz style cannot be binary or cause files
 to be written by each processor. :dd
 
-{Invalid dump_modify threshold operator} :dt
+{Invalid dump_modify threshhold operator} :dt
 
 Operator keyword used for threshold specification in not recognized. :dd
 
@@ -6751,7 +6739,7 @@ The fix is not recognized. :dd
 
 {Invalid fix ave/time off column} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Invalid fix box/relax command for a 2d simulation} :dt
 
@@ -7313,7 +7301,7 @@ Self-explanatory. Check the input script or data file. :dd
 
 {LJ6 off not supported in pair_style buck/long/coul/long} :dt
 
-Self-explanatory. :dd
+Self-exlanatory. :dd
 
 {Label wasn't found in input script} :dt
 
@@ -7361,7 +7349,7 @@ This should not occur.  Report the problem to the developers. :dd
 Lost atoms are checked for each time thermo output is done.  See the
 thermo_modify lost command for options.  Lost atoms usually indicate
 bad dynamics, e.g. atoms have been blown far out of the simulation
-box, or moved further than one processor's sub-domain away before
+box, or moved futher than one processor's sub-domain away before
 reneighboring. :dd
 
 {MEAM library error %d} :dt
@@ -7526,7 +7514,7 @@ Self-explanatory. :dd
 
 {Molecule template ID for create_atoms does not exist} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Molecule template ID for fix deposit does not exist} :dt
 
@@ -7552,7 +7540,7 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
-{Molecule topology/atom exceeds system topology/atom} :dt
+{Molecule toplogy/atom exceeds system topology/atom} :dt
 
 The number of bonds, angles, etc per-atom in the molecule exceeds the
 system setting.  See the create_box command for how to specify these
@@ -7792,7 +7780,7 @@ Self-explanatory. :dd
 
 {Must use variable energy with fix addforce} :dt
 
-Must define an energy variable when applying a dynamic
+Must define an energy vartiable when applyting a dynamic
 force during minimization. :dd
 
 {Must use variable energy with fix efield} :dt
@@ -7876,20 +7864,18 @@ See the setting for tagint in the src/lmptype.h file. :dd
 
 {New bond exceeded bonds per atom in create_bonds} :dt
 
-See the read_data command for info on using the "extra/bond/per/atom"
-keyword to allow for additional bonds to be formed
+See the read_data command for info on setting the "extra bond per
+atom" header value to allow for additional bonds to be formed. :dd
 
 {New bond exceeded bonds per atom in fix bond/create} :dt
 
-See the read_data command for info on using the "extra/bond/per/atom"
-keyword to allow for additional bonds to be formed :dd
+See the read_data command for info on setting the "extra bond per
+atom" header value to allow for additional bonds to be formed. :dd
 
 {New bond exceeded special list size in fix bond/create} :dt
 
-See the "read_data extra/special/per/atom" command
-(or the "create_box extra/special/per/atom" command)
-for info on how to leave space in the special bonds
-list to allow for additional bonds to be formed. :dd
+See the special_bonds extra command for info on how to leave space in
+the special bonds list to allow for additional bonds to be formed. :dd
 
 {Newton bond change after simulation box is defined} :dt
 
@@ -8044,7 +8030,7 @@ Self-explanatory. :dd
 
 {Non digit character between brackets in variable} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Non integer # of swaps in temper command} :dt
 
@@ -8665,7 +8651,7 @@ not be invoked by bond_style quartic. :dd
 {Pair style does not support compute group/group} :dt
 
 The pair_style does not have a single() function, so it cannot be
-invoked by the compute group/group command. :dd
+invokded by the compute group/group command. :dd
 
 {Pair style does not support compute pair/local} :dt
 
@@ -8892,14 +8878,6 @@ This is a requirement to use this potential. :dd
 
 See the newton command.  This is a restriction to use this potential. :dd
 
-{Pair style vashishta/gpu requires atom IDs} :dt
-
-This is a requirement to use this potential. :dd
-
-{Pair style vashishta/gpu requires newton pair off} :dt
-
-See the newton command.  This is a restriction to use this potential. :dd
-
 {Pair style tersoff/gpu requires atom IDs} :dt
 
 This is a requirement to use the tersoff/gpu potential. :dd
@@ -8958,11 +8936,11 @@ Self-explanatory. :dd
 
 {Pair yukawa/colloid requires atom style sphere} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Pair yukawa/colloid requires atoms with same type have same radius} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Pair yukawa/colloid/gpu requires atom style sphere} :dt
 
@@ -9176,7 +9154,7 @@ Self-explanatory. :dd
 
 {Python function evaluation failed} :dt
 
-The Python function did not run successfully and/or did not return a
+The Python function did not run succesfully and/or did not return a
 value (if it is supposed to return a value).  This is probably due to
 some error condition in the function. :dd
 
@@ -9666,10 +9644,9 @@ you are running. :dd
 
 {Special list size exceeded in fix bond/create} :dt
 
-See the "read_data extra/special/per/atom" command
-(or the "create_box extra/special/per/atom" command)
-for info on how to leave space in the special bonds
-list to allow for additional bonds to be formed. :dd
+See the read_data command for info on setting the "extra special per
+atom" header value to allow for additional special values to be
+stored. :dd
 
 {Specified processors != physical processors} :dt
 
@@ -9686,23 +9663,23 @@ Self-explanatory. :dd
 
 {Subsequent read data induced too many angles per atom} :dt
 
-See the extra/angle/per/atom keyword for the create_box
-or the read_data command to set this limit larger :dd
+See the create_box extra/angle/per/atom or read_data "extra angle per
+atom" header value to set this limit larger. :dd
 
 {Subsequent read data induced too many bonds per atom} :dt
 
-See the extra/bond/per/atom keyword for the create_box
-or the read_data command to set this limit larger :dd
+See the create_box extra/bond/per/atom or read_data "extra bond per
+atom" header value to set this limit larger. :dd
 
 {Subsequent read data induced too many dihedrals per atom} :dt
 
-See the extra/dihedral/per/atom keyword for the create_box
-or the read_data command to set this limit larger :dd
+See the create_box extra/dihedral/per/atom or read_data "extra
+dihedral per atom" header value to set this limit larger. :dd
 
 {Subsequent read data induced too many impropers per atom} :dt
 
-See the extra/improper/per/atom keyword for the create_box
-or the read_data command to set this limit larger :dd
+See the create_box extra/improper/per/atom or read_data "extra
+improper per atom" header value to set this limit larger. :dd
 
 {Substitution for illegal variable} :dt
 
@@ -10036,7 +10013,7 @@ make sense in between runs. :dd
 
 {Threshhold for an atom property that isn't allocated} :dt
 
-A dump threshold has been requested on a quantity that is
+A dump threshhold has been requested on a quantity that is
 not defined by the atom style used in this simulation. :dd
 
 {Timestep must be >= 0} :dt
@@ -10098,7 +10075,7 @@ to a large size. :dd
 {Too many atom triplets for pair bop} :dt
 
 The number of three atom groups for angle determinations exceeds the
-expected number.  Check your atomic structure to ensure that it is
+expected number.  Check your atomic structrure to ensure that it is
 realistic. :dd
 
 {Too many atoms for dump dcd} :dt
@@ -10166,7 +10143,7 @@ to a large size. :dd
 
 {Too many timesteps} :dt
 
-The cumulative timesteps must fit in a 64-bit integer. :dd
+The cummulative timesteps must fit in a 64-bit integer. :dd
 
 {Too many timesteps for NEB} :dt
 
@@ -10665,7 +10642,7 @@ Only atom-style variables can be used. :dd
 
 {Variable for region cylinder is invalid style} :dt
 
-Only equal-style variables are allowed. :dd
+Only equal-style varaibles are allowed. :dd
 
 {Variable for region is invalid style} :dt
 
@@ -10677,7 +10654,7 @@ Self-explanatory. :dd
 
 {Variable for region sphere is invalid style} :dt
 
-Only equal-style variables are allowed. :dd
+Only equal-style varaibles are allowed. :dd
 
 {Variable for restart is invalid style} :dt
 
@@ -10718,7 +10695,7 @@ Self-explanatory. :dd
 {Variable has circular dependency} :dt
 
 A circular dependency is when variable "a" in used by variable "b" and
-variable "b" is also used by variable "a".  Circular dependencies with
+variable "b" is also used by varaible "a".  Circular dependencies with
 longer chains of dependence are also not allowed. :dd
 
 {Variable name between brackets must be alphanumeric or underscore characters} :dt
@@ -10807,7 +10784,7 @@ Self-explanatory. :dd
 
 {Variable name for fix deform does not exist} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Variable name for fix efield does not exist} :dt
 
@@ -11094,7 +11071,7 @@ for a dihedral) and adding a small amount of stretch. :dd
 
 {Both groups in compute group/group have a net charge; the Kspace boundary correction to energy will be non-zero} :dt
 
-Self-explanatory. :dd
+Self-explantory. :dd
 
 {Calling write_dump before a full system init.} :dt
 
@@ -11182,12 +11159,6 @@ Self-explanatory. :dd
 If the fix changes the timestep, the dump dcd file will not
 reflect the change. :dd
 
-{Energy due to X extra global DOFs will be included in minimizer energies} :dt
-
-When using fixes like box/relax, the potential energy used by the minimizer
-is augmented by an additional energy provided by the fix. Thus the printed
-converged energy may be different from the total potential energy. :dd
-
 {Energy tally does not account for 'zero yes'} :dt
 
 The energy removed by using the 'zero yes' flag is not accounted
@@ -11431,7 +11402,7 @@ The command options you have used caused atoms to be lost. :dd
 Lost atoms are checked for each time thermo output is done.  See the
 thermo_modify lost command for options.  Lost atoms usually indicate
 bad dynamics, e.g. atoms have been blown far out of the simulation
-box, or moved further than one processor's sub-domain away before
+box, or moved futher than one processor's sub-domain away before
 reneighboring. :dd
 
 {MSM mesh too small, increasing to 2 points in each direction} :dt
@@ -11469,7 +11440,7 @@ i.e. the first molecule in the template. :dd
 
 {Molecule template for fix shake has multiple molecules} :dt
 
-The fix shake command will only recognize molecules of a single
+The fix shake command will only recoginze molecules of a single
 type, i.e. the first molecule in the template. :dd
 
 {More than one compute centro/atom} :dt
@@ -11554,7 +11525,7 @@ neigh_modify exclude command. :dd
 
 If a thermo_style command is used after a thermo_modify command, the
 settings changed by the thermo_modify command will be reset to their
-default values.  This is because the thermo_modify command acts on
+default values.  This is because the thermo_modify commmand acts on
 the currently defined thermo style, and a thermo_style command creates
 a new style. :dd
 
@@ -11606,7 +11577,7 @@ This may not be what you intended. :dd
 
 {One or more dynamic groups may not be updated at correct point in timestep} :dt
 
-If there are other fixes that act immediately after the initial stage
+If there are other fixes that act immediately after the intitial stage
 of time integration within a timestep (i.e. after atoms move), then
 the command that sets up the dynamic group should appear after those
 fixes.  This will insure that dynamic group assignments are made
@@ -11903,7 +11874,7 @@ Self-explanatory. :dd
 
 {Using largest cutoff for buck/long/coul/long} :dt
 
-Self-explanatory. :dd
+Self-exlanatory. :dd
 
 {Using largest cutoff for lj/long/coul/long} :dt
 

doc/src/Section_example.txt

@@ -25,7 +25,9 @@ files and image files.
 
 If you uncomment the "dump"_dump.html command in the input script, a
 text dump file will be produced, which can be animated by various
-"visualization programs"_http://lammps.sandia.gov/viz.html.
+"visualization programs"_http://lammps.sandia.gov/viz.html.  It can
+also be animated using the xmovie tool described in the "Additional
+Tools"_Section_tools.html section of the LAMMPS documentation.
 
 If you uncomment the "dump image"_dump.html command in the input
 script, and assuming you have built LAMMPS with a JPG library, JPG
@@ -49,14 +51,11 @@ Lists of both kinds of directories are given below.
 Lowercase directories :h4
 
 accelerate: run with various acceleration options (OpenMP, GPU, Phi)
-airebo:   polyethylene with AIREBO potential
 balance:  dynamic load balancing, 2d system
 body:     body particles, 2d system
-cmap:     CMAP 5-body contributions to CHARMM force field
 colloid:  big colloid particles in a small particle solvent, 2d system
 comb:     models using the COMB potential
 coreshell: core/shell model using CORESHELL package
-controller: use of fix controller as a thermostat
 crack:    crack propagation in a 2d solid
 deposit:  deposit atoms and molecules on a surface
 dipole:   point dipolar particles, 2d system
@@ -65,8 +64,6 @@ eim:      NaCl using the EIM potential
 ellipse:  ellipsoidal particles in spherical solvent, 2d system
 flow:     Couette and Poiseuille flow in a 2d channel
 friction: frictional contact of spherical asperities between 2d surfaces
-gcmc:     Grand Canonical Monte Carlo (GCMC) via the fix gcmc command
-granregion: use of fix wall/region/gran as boundary on granular particles
 hugoniostat: Hugoniostat shock dynamics
 indent:   spherical indenter into a 2d solid
 kim:      use of potentials in Knowledge Base for Interatomic Models (KIM)
@@ -74,7 +71,6 @@ meam:     MEAM test for SiC and shear (same as shear examples)
 melt:     rapid melt of 3d LJ system
 micelle:  self-assembly of small lipid-like molecules into 2d bilayers
 min:      energy minimization of 2d LJ melt
-mscg:     parameterize a multi-scale coarse-graining (MSCG) model
 msst:     MSST shock dynamics
 nb3b:     use of nonbonded 3-body harmonic pair style
 neb:      nudged elastic band (NEB) calculation for barrier finding
@@ -93,8 +89,7 @@ snap:     NVE dynamics for BCC tantalum crystal using SNAP potential
 srd:      stochastic rotation dynamics (SRD) particles as solvent
 streitz:  use of Streitz/Mintmire potential with charge equilibration
 tad:      temperature-accelerated dynamics of vacancy diffusion in bulk Si
-vashishta: use of the Vashishta potential
-voronoi:  Voronoi tesselation via compute voronoi/atom command :tb(s=:)
+vashishta: use of the Vashishta potential :tb(s=:)
 
 Here is how you can run and visualize one of the sample problems:
 

doc/src/Section_history.txt

@@ -37,7 +37,7 @@ pitfalls or alternatives.
 
 Please see some of the closed issues for examples of how to
 suggest code enhancements, submit proposed changes, or report
-possible bugs and how they are resolved.
+possible bugs and how they are resoved.
 
 As an alternative to using GitHub, you may e-mail the
 "core developers"_http://lammps.sandia.gov/authors.html or send

doc/src/Section_howto.txt

@@ -54,7 +54,7 @@ restart files can be saved to disk using the "restart"_restart.html
 command.  At a later time, these binary files can be read via a
 "read_restart"_read_restart.html command in a new script.  Or they can
 be converted to text data files using the "-r command-line
-switch"_Section_start.html#start_6 and read by a
+switch"_Section_start.html#start_7 and read by a
 "read_data"_read_data.html command in a new script.
 
 Here we give examples of 2 scripts that read either a binary restart
@@ -165,16 +165,9 @@ Many of the example input scripts included in the LAMMPS distribution
 are for 2d models.
 
 NOTE: Some models in LAMMPS treat particles as finite-size spheres, as
-opposed to point particles.  See the "atom_style
-sphere"_atom_style.html and "fix nve/sphere"_fix_nve_sphere.html
-commands for details.  By default, for 2d simulations, such particles
-will still be modeled as 3d spheres, not 2d discs (circles), meaning
-their moment of inertia will be that of a sphere.  If you wish to
-model them as 2d discs, see the "set density/disc"_set.html command
-and the {disc} option for the "fix nve/sphere"_fix_nve_sphere.html,
-"fix nvt/sphere"_fix_nvt_sphere.html, "fix
-nph/sphere"_fix_nph_sphere.html, "fix npt/sphere"_fix_npt_sphere.html
-commands.
+opposed to point particles.  In 2d, the particles will still be
+spheres, not disks, meaning their moment of inertia will be the same
+as in 3d.
 
 :line
 
@@ -204,10 +197,7 @@ documentation for the formula it computes.
 
 "bond_style"_bond_harmonic.html harmonic
 "angle_style"_angle_charmm.html charmm
-"dihedral_style"_dihedral_charmm.html charmmfsh
 "dihedral_style"_dihedral_charmm.html charmm
-"pair_style"_pair_charmm.html lj/charmmfsw/coul/charmmfsh
-"pair_style"_pair_charmm.html lj/charmmfsw/coul/long
 "pair_style"_pair_charmm.html lj/charmm/coul/charmm
 "pair_style"_pair_charmm.html lj/charmm/coul/charmm/implicit
 "pair_style"_pair_charmm.html lj/charmm/coul/long :ul
@@ -215,12 +205,6 @@ documentation for the formula it computes.
 "special_bonds"_special_bonds.html charmm
 "special_bonds"_special_bonds.html amber :ul
 
-NOTE: For CHARMM, newer {charmmfsw} or {charmmfsh} styles were
-released in March 2017.  We recommend they be used instead of the
-older {charmm} styles.  See discussion of the differences on the "pair
-charmm"_pair_charmm.html and "dihedral charmm"_dihedral_charmm.html
-doc pages.
-
 DREIDING is a generic force field developed by the "Goddard
 group"_http://www.wag.caltech.edu at Caltech and is useful for
 predicting structures and dynamics of organic, biological and
@@ -337,7 +321,7 @@ All of the above examples work whether you are running on 1 or
 multiple processors, but assumed you are running LAMMPS on a single
 partition of processors.  LAMMPS can be run on multiple partitions via
 the "-partition" command-line switch as described in "this
-section"_Section_start.html#start_6 of the manual.
+section"_Section_start.html#start_7 of the manual.
 
 In the last 2 examples, if LAMMPS were run on 3 partitions, the same
 scripts could be used if the "index" and "loop" variables were
@@ -387,7 +371,7 @@ for more info on packages.
 In all these cases, you must run with one or more processors per
 replica.  The processors assigned to each replica are determined at
 run-time by using the "-partition command-line
-switch"_Section_start.html#start_6 to launch LAMMPS on multiple
+switch"_Section_start.html#start_7 to launch LAMMPS on multiple
 partitions, which in this context are the same as replicas.  E.g.
 these commands:
 
@@ -395,7 +379,7 @@ mpirun -np 16 lmp_linux -partition 8x2 -in in.temper
 mpirun -np 8 lmp_linux -partition 8x1 -in in.neb :pre
 
 would each run 8 replicas, on either 16 or 8 processors.  Note the use
-of the "-in command-line switch"_Section_start.html#start_6 to specify
+of the "-in command-line switch"_Section_start.html#start_7 to specify
 the input script which is required when running in multi-replica mode.
 
 Also note that with MPI installed on a machine (e.g. your desktop),
@@ -450,12 +434,6 @@ computations between frozen atoms by using this command:
 
 "neigh_modify"_neigh_modify.html exclude :ul
 
-NOTE: By default, for 2d systems, granular particles are still modeled
-as 3d spheres, not 2d discs (circles), meaning their moment of inertia
-will be the same as in 3d.  If you wish to model granular particles in
-2d as 2d discs, see the note on this topic in "Section
-6.2"_Section_howto.html#howto_2, where 2d simulations are disussed.
-
 :line
 
 6.7 TIP3P water model :link(howto_7),h4
@@ -473,7 +451,7 @@ atoms and the water molecule to run a rigid TIP3P-CHARMM model with a
 cutoff.  The K values can be used if a flexible TIP3P model (without
 fix shake) is desired.  If the LJ epsilon and sigma for HH and OH are
 set to 0.0, it corresponds to the original 1983 TIP3P model
-"(Jorgensen)"_#Jorgensen1.
+"(Jorgensen)"_#Jorgensen.
 
 O mass = 15.9994
 H mass = 1.008
@@ -491,7 +469,7 @@ K of HOH angle = 55
 theta of HOH angle = 104.52 :all(b),p
 
 These are the parameters to use for TIP3P with a long-range Coulombic
-solver (e.g. Ewald or PPPM in LAMMPS), see "(Price)"_#Price1 for
+solver (e.g. Ewald or PPPM in LAMMPS), see "(Price)"_#Price for
 details:
 
 O mass = 15.9994
@@ -535,7 +513,7 @@ using the "fix shake"_fix_shake.html command.
 
 These are the additional parameters (in real units) to set for O and H
 atoms and the water molecule to run a rigid TIP4P model with a cutoff
-"(Jorgensen)"_#Jorgensen1.  Note that the OM distance is specified in
+"(Jorgensen)"_#Jorgensen.  Note that the OM distance is specified in
 the "pair_style"_pair_style.html command, not as part of the pair
 coefficients.
 
@@ -595,7 +573,7 @@ LJ epsilon of O-O = 0.16275
 LJ sigma of O-O = 3.16435
 LJ epsilon, sigma of OH, HH = 0.0 :all(b),p
 
-Note that the when using the TIP4P pair style, the neighbor list
+Note that the when using the TIP4P pair style, the neighobr list
 cutoff for Coulomb interactions is effectively extended by a distance
 2 * (OM distance), to account for the offset distance of the
 fictitious charges on O atoms in water molecules.  Thus it is
@@ -640,7 +618,7 @@ any of the parameters above, though it becomes a different model in
 that mode of usage.
 
 The SPC/E (extended) water model is the same, except
-the partial charge assignments change:
+the partial charge assignemnts change:
 
 O charge = -0.8476
 H charge = 0.4238 :all(b),p
@@ -759,14 +737,23 @@ LAMMPS itself does not do visualization, but snapshots from LAMMPS
 simulations can be visualized (and analyzed) in a variety of ways.
 
 LAMMPS snapshots are created by the "dump"_dump.html command which can
-create files in several formats. The native LAMMPS dump format is a
+create files in several formats.  The native LAMMPS dump format is a
 text file (see "dump atom" or "dump custom") which can be visualized
-by several popular visualization tools. The "dump image"_dump_image.html
-and "dump movie"_dump_image.html styles can output internally rendered
-images and convert a sequence of them to a movie during the MD run.
+by the "xmovie"_Section_tools.html#xmovie program, included with the
+LAMMPS package.  This produces simple, fast 2d projections of 3d
+systems, and can be useful for rapid debugging of simulation geometry
+and atom trajectories.
+
 Several programs included with LAMMPS as auxiliary tools can convert
-between LAMMPS format files and other formats.
-See the "Section 9"_Section_tools.html doc page for details.
+native LAMMPS dump files to other formats.  See the
+"Section 9"_Section_tools.html doc page for details.  The first is
+the "ch2lmp tool"_Section_tools.html#charmm, which contains a
+lammps2pdb Perl script which converts LAMMPS dump files into PDB
+files.  The second is the "lmp2arc tool"_Section_tools.html#arc which
+converts LAMMPS dump files into Accelrys' Insight MD program files.
+The third is the "lmp2cfg tool"_Section_tools.html#cfg which converts
+LAMMPS dump files into CFG files which can be read into the
+"AtomEye"_atomeye visualizer.
 
 A Python-based toolkit distributed by our group can read native LAMMPS
 dump files, including custom dump files with additional columns of
@@ -779,7 +766,22 @@ RasMol visualization programs.  Pizza.py has tools that do interactive
 3d OpenGL visualization and one that creates SVG images of dump file
 snapshots.
 
+LAMMPS can create XYZ files directly (via "dump xyz") which is a
+simple text-based file format used by many visualization programs
+including "VMD"_vmd.
+
+LAMMPS can create DCD files directly (via "dump dcd") which can be
+read by "VMD"_vmd in conjunction with a CHARMM PSF file.  Using this
+form of output avoids the need to convert LAMMPS snapshots to PDB
+files.  See the "dump"_dump.html command for more information on DCD
+files.
+
+LAMMPS can create XTC files directly (via "dump xtc") which is GROMACS
+file format which can also be read by "VMD"_vmd for visualization.
+See the "dump"_dump.html command for more information on XTC files.
+
 :link(pizza,http://www.sandia.gov/~sjplimp/pizza.html)
+:link(vmd,http://www.ks.uiuc.edu/Research/vmd)
 :link(ensight,http://www.ensight.com)
 :link(atomeye,http://mt.seas.upenn.edu/Archive/Graphics/A)
 
@@ -861,7 +863,7 @@ boundary conditions in specific dimensions.  See the command doc pages
 for details.
 
 The 9 parameters (xlo,xhi,ylo,yhi,zlo,zhi,xy,xz,yz) are defined at the
-time the simulation box is created.  This happens in one of 3 ways.
+time the simluation box is created.  This happens in one of 3 ways.
 If the "create_box"_create_box.html command is used with a region of
 style {prism}, then a triclinic box is setup.  See the
 "region"_region.html command for details.  If the
@@ -980,10 +982,10 @@ used with non-orthogonal basis vectors to define a lattice that will
 tile a triclinic simulation box via the
 "create_atoms"_create_atoms.html command.
 
-A second use is to run Parinello-Rahman dynamics via the "fix
+A second use is to run Parinello-Rahman dyanamics via the "fix
 npt"_fix_nh.html command, which will adjust the xy, xz, yz tilt
 factors to compensate for off-diagonal components of the pressure
-tensor.  The analog for an "energy minimization"_minimize.html is
+tensor.  The analalog for an "energy minimization"_minimize.html is
 the "fix box/relax"_fix_box_relax.html command.
 
 A third use is to shear a bulk solid to study the response of the
@@ -1030,10 +1032,6 @@ profile consistent with the applied shear strain rate.
 An alternative method for calculating viscosities is provided via the
 "fix viscosity"_fix_viscosity.html command.
 
-NEMD simulations can also be used to measure transport properties of a fluid
-through a pore or channel. Simulations of steady-state flow can be performed
-using the "fix flow/gauss"_fix_flow_gauss.html command.
-
 :line
 
 6.14 Finite-size spherical and aspherical particles :link(howto_14),h4
@@ -1394,7 +1392,7 @@ custom"_dump.html command.
 
 There is also a "dump local"_dump.html format where the user specifies
 what local values to output.  A pre-defined index keyword can be
-specified to enumerate the local values.  Two additional kinds of
+specified to enumuerate the local values.  Two additional kinds of
 keywords can also be specified (c_ID, f_ID), where a
 "compute"_compute.html or "fix"_fix.html or "variable"_variable.html
 provides the values to be output.  In each case, the compute or fix
@@ -1527,7 +1525,7 @@ Variables that generate values to output :h5,link(variable)
 "Variables"_variable.html defined in an input script can store one or
 more strings.  But equal-style, vector-style, and atom-style or
 atomfile-style variables generate a global scalar value, global vector
-or values, or a per-atom vector, respectively, when accessed.  The
+or values, or a per-atom vector, resepctively, when accessed.  The
 formulas used to define these variables can contain references to the
 thermodynamic keywords and to global and per-atom data generated by
 computes, fixes, and other variables.  The values generated by
@@ -1587,7 +1585,7 @@ Temperature is computed as kinetic energy divided by some number of
 degrees of freedom (and the Boltzmann constant).  Since kinetic energy
 is a function of particle velocity, there is often a need to
 distinguish between a particle's advection velocity (due to some
-aggregate motion of particles) and its thermal velocity.  The sum of
+aggregate motiion of particles) and its thermal velocity.  The sum of
 the two is the particle's total velocity, but the latter is often what
 is wanted to compute a temperature.
 
@@ -1642,14 +1640,14 @@ nvt/asphere"_fix_nvt_asphere.html thermostat not only translation
 velocities but also rotational velocities for spherical and aspherical
 particles.
 
-DPD thermostatting alters pairwise interactions in a manner analogous
+DPD thermostatting alters pairwise interactions in a manner analagous
 to the per-particle thermostatting of "fix
 langevin"_fix_langevin.html.
 
 Any of the thermostatting fixes can use temperature computes that
 remove bias which has two effects.  First, the current calculated
 temperature, which is compared to the requested target temperature, is
-calculated with the velocity bias removed.  Second, the thermostat
+caluclated with the velocity bias removed.  Second, the thermostat
 adjusts only the thermal temperature component of the particle's
 velocities, which are the velocities with the bias removed.  The
 removed bias is then added back to the adjusted velocities.  See the
@@ -1686,7 +1684,7 @@ nph) and Berendsen:
 The "fix npt"_fix_nh.html commands include a Nose-Hoover thermostat
 and barostat.  "Fix nph"_fix_nh.html is just a Nose/Hoover barostat;
 it does no thermostatting.  Both "fix nph"_fix_nh.html and "fix
-press/berendsen"_fix_press_berendsen.html can be used in conjunction
+press/bernendsen"_fix_press_berendsen.html can be used in conjunction
 with any of the thermostatting fixes.
 
 As with the thermostats, "fix npt"_fix_nh.html and "fix
@@ -1836,7 +1834,7 @@ the deformation must be chosen judiciously, and care must be taken to
 fully equilibrate the deformed cell before sampling the stress
 tensor. Another approach is to sample the triclinic cell fluctuations
 that occur in an NPT simulation. This method can also be slow to
-converge and requires careful post-processing "(Shinoda)"_#Shinoda1
+converge and requires careful post-processing "(Shinoda)"_#Shinoda
 
 :line
 
@@ -1872,7 +1870,7 @@ void lammps_free(void *) :pre
 
 The lammps_open() function is used to initialize LAMMPS, passing in a
 list of strings as if they were "command-line
-arguments"_Section_start.html#start_6 when LAMMPS is run in
+arguments"_Section_start.html#start_7 when LAMMPS is run in
 stand-alone mode from the command line, and a MPI communicator for
 LAMMPS to run under.  It returns a ptr to the LAMMPS object that is
 created, and which is used in subsequent library calls.  The
@@ -1890,7 +1888,7 @@ instances of LAMMPS to perform different calculations.
 
 The lammps_open_no_mpi() function is similar except that no MPI
 communicator is passed from the caller.  Instead, MPI_COMM_WORLD is
-used to instantiate LAMMPS, and MPI is initialized if necessary.
+used to instantiate LAMMPS, and MPI is initialzed if necessary.
 
 The lammps_close() function is used to shut down an instance of LAMMPS
 and free all its memory.
@@ -1938,7 +1936,7 @@ documentation in the src/library.cpp file for details, including
 which quantities can be queried by name:
 
 void *lammps_extract_global(void *, char *)
-void lammps_extract_box(void *, double *, double *,
+void lammps_extract_box(void *, double *, double *, 
                         double *, double *, double *, int *, int *)
 void *lammps_extract_atom(void *, char *)
 void *lammps_extract_compute(void *, char *, int, int)
@@ -1959,12 +1957,9 @@ The extract functions return a pointer to various global or per-atom
 quantities stored in LAMMPS or to values calculated by a compute, fix,
 or variable.  The pointer returned by the extract_global() function
 can be used as a permanent reference to a value which may change.  For
-the extract_atom() method, see the extract() method in the
-src/atom.cpp file for a list of valid per-atom properties.  New names
-could easily be added if the property you want is not listed.  For the
-other extract functions, the underlying storage may be reallocated as
-LAMMPS runs, so you need to re-call the function to assure a current
-pointer or returned value(s).
+the other extract functions, the underlying storage may be reallocated
+as LAMMPS runs, so you need to re-call the function to assure a
+current pointer or returned value(s).
 
 The lammps_reset_box() function resets the size and shape of the
 simulation box, e.g. as part of restoring a previously extracted and
@@ -1980,20 +1975,11 @@ keyword as a double precision value.
 The lammps_get_natoms() function returns the total number of atoms in
 the system and can be used by the caller to allocate space for the
 lammps_gather_atoms() and lammps_scatter_atoms() functions.  The
-gather function collects peratom info of the requested type (atom
-coords, types, forces, etc) from all processors, orders them by atom
-ID, and returns a full list to each calling processor.  The scatter
-function does the inverse.  It distributes the same peratom values,
+gather function collects atom info of the requested type (atom coords,
+types, forces, etc) from all procsesors, orders them by atom ID, and
+returns a full list to each calling processor.  The scatter function
+does the inverse.  It distributes the same kinds of values, 
 passed by the caller, to each atom owned by individual processors.
-Both methods are thus a means to extract or assign (overwrite) any
-peratom quantities within LAMMPS.  See the extract() method in the
-src/atom.cpp file for a list of valid per-atom properties.  New names
-could easily be added if the property you want is not listed.
-A special treatment is applied for accessing image flags via the
-"image" property. Image flags are stored in a packed format with all
-three image flags stored in a single integer. When signaling to access
-the image flags as 3 individual values per atom instead of 1, the data
-is transparently packed or unpacked by the library interface.
 
 The lammps_create_atoms() function takes a list of N atoms as input
 with atom types and coords (required), an optionally atom IDs and
@@ -2027,7 +2013,7 @@ a simple Lennard-Jones fluid model.  Also, see "this
 section"_Section_howto.html#howto_21 of the manual for an analogous
 discussion for viscosity.
 
-The thermal conductivity tensor kappa is a measure of the propensity
+The thermal conducitivity tensor kappa is a measure of the propensity
 of a material to transmit heat energy in a diffusive manner as given
 by Fourier's law
 
@@ -2113,7 +2099,7 @@ and grad(Vstream) is the spatial gradient of the velocity of the fluid
 moving in another direction, normal to the area through which the
 momentum flows.  Viscosity thus has units of pressure-time.
 
-The first method is to perform a non-equilibrium MD (NEMD) simulation
+The first method is to perform a non-equlibrium MD (NEMD) simulation
 by shearing the simulation box via the "fix deform"_fix_deform.html
 command, and using the "fix nvt/sllod"_fix_nvt_sllod.html command to
 thermostat the fluid via the SLLOD equations of motion.
@@ -2139,7 +2125,7 @@ the rNEMD algorithm of Muller-Plathe.  Momentum in one dimension is
 swapped between atoms in two different layers of the simulation box in
 a different dimension.  This induces a velocity gradient which can be
 monitored with the "fix ave/chunk"_fix_ave_chunk.html command.
-The fix tallies the cumulative momentum transfer that it performs.
+The fix tallies the cummulative momentum transfer that it performs.
 See the "fix viscosity"_fix_viscosity.html command for details.
 
 The fourth method is based on the Green-Kubo (GK) formula which
@@ -2282,7 +2268,7 @@ atoms with same local defect structure | chunk ID = output of "compute centro/at
 Note that chunk IDs are integer values, so for atom properties or
 computes that produce a floating point value, they will be truncated
 to an integer.  You could also use the compute in a variable that
-scales the floating point value to spread it across multiple integers.
+scales the floating point value to spread it across multiple intergers.
 
 Spatial bins can be of various kinds, e.g. 1d bins = slabs, 2d bins =
 pencils, 3d bins = boxes, spherical bins, cylindrical bins.
@@ -2367,7 +2353,7 @@ largest cluster or fastest diffusing molecule. :l
 
 Example calculations with chunks :h5
 
-Here are examples using chunk commands to calculate various
+Here are eaxmples using chunk commands to calculate various
 properties:
 
 (1) Average velocity in each of 1000 2d spatial bins:
@@ -2438,7 +2424,7 @@ which both have their up- and downsides.
 The first approach is to set desired real-space an kspace accuracies
 via the {kspace_modify force/disp/real} and {kspace_modify
 force/disp/kspace} commands. Note that the accuracies have to be
-specified in force units and are thus dependent on the chosen unit
+specified in force units and are thus dependend on the chosen unit
 settings. For real units, 0.0001 and 0.002 seem to provide reasonable
 accurate and efficient computations for the real-space and kspace
 accuracies.  0.002 and 0.05 work well for most systems using lj
@@ -2458,7 +2444,7 @@ performance. This approach provides a fast initialization of the
 simulation. However, it is sensitive to errors: A combination of
 parameters that will perform well for one system might result in
 far-from-optimal conditions for other simulations. For example,
-parameters that provide accurate and fast computations for
+parametes that provide accurate and fast computations for
 all-atomistic force fields can provide insufficient accuracy or
 united-atomistic force fields (which is related to that the latter
 typically have larger dispersion coefficients).
@@ -2492,7 +2478,7 @@ arithmetic mixing rule substantially increases the computational cost.
 The computational overhead can be reduced using the {kspace_modify
 mix/disp geom} and {kspace_modify splittol} commands. The first
 command simply enforces geometric mixing of the dispersion
-coefficients in kspace computations.  This introduces some error in
+coeffiecients in kspace computations.  This introduces some error in
 the computations but will also significantly speed-up the
 simulations. The second keyword sets the accuracy with which the
 dispersion coefficients are approximated using a matrix factorization
@@ -2511,7 +2497,7 @@ to specify this command explicitly.
 6.25 Polarizable models :link(howto_25),h4
 
 In polarizable force fields the charge distributions in molecules and
-materials respond to their electrostatic environments. Polarizable
+materials respond to their electrostatic environements. Polarizable
 systems can be simulated in LAMMPS using three methods:
 
 the fluctuating charge method, implemented in the "QEQ"_fix_qeq.html
@@ -2565,7 +2551,7 @@ this is done by "fix qeq/dynamic"_fix_qeq.html, and for the
 charge-on-spring models by the methods outlined in the next two
 sections. The assignment of masses to the additional degrees of
 freedom can lead to unphysical trajectories if care is not exerted in
-choosing the parameters of the polarizable models and the simulation
+choosing the parameters of the poarizable models and the simulation
 conditions.
 
 In the core-shell model the vibration of the shells is kept faster
@@ -2587,7 +2573,7 @@ well.
 6.26 Adiabatic core/shell model :link(howto_26),h4
 
 The adiabatic core-shell model by "Mitchell and
-Fincham"_#MitchellFincham is a simple method for adding
+Finchham"_#MitchellFinchham is a simple method for adding
 polarizability to a system.  In order to mimic the electron shell of
 an ion, a satellite particle is attached to it. This way the ions are
 split into a core and a shell where the latter is meant to react to
@@ -2681,16 +2667,13 @@ bond_coeff      1 63.014 0.0
 bond_coeff      2 25.724 0.0 :pre
 
 When running dynamics with the adiabatic core/shell model, the
-following issues should be considered.  The relative motion of
-the core and shell particles corresponds to the polarization,
-hereby an instantaneous relaxation of the shells is approximated
-and a fast core/shell spring frequency ensures a nearly constant
-internal kinetic energy during the simulation.
-Thermostats can alter this polarization behaviour, by scaling the
-internal kinetic energy, meaning the shell will not react freely to
-its electrostatic environment.
-Therefore it is typically desirable to decouple the relative motion of
-the core/shell pair, which is an imaginary degree of freedom, from the
+following issues should be considered.  Since the relative motion of
+the core and shell particles corresponds to the polarization, typical
+thermostats can alter the polarization behaviour, meaning the shell
+will not react freely to its electrostatic environment.  This is
+critical during the equilibration of the system. Therefore
+it's typically desirable to decouple the relative motion of the
+core/shell pair, which is an imaginary degree of freedom, from the
 real physical system.  To do that, the "compute
 temp/cs"_compute_temp_cs.html command can be used, in conjunction with
 any of the thermostat fixes, such as "fix nvt"_fix_nh.html or "fix
@@ -2721,54 +2704,44 @@ fix thermostatequ all nve                               # integrator as needed f
 fix_modify thermoberendsen temp CSequ
 thermo_modify temp CSequ                                # output of center-of-mass derived temperature :pre
 
-The pressure for the core/shell system is computed via the regular
-LAMMPS convention by "treating the cores and shells as individual
-particles"_#MitchellFincham2. For the thermo output of the pressure
-as well as for the application of a barostat, it is necessary to
-use an additional "pressure"_compute_pressure compute based on the
-default "temperature"_compute_temp and specifying it as a second
-argument in "fix modify"_fix_modify.html and
-"thermo_modify"_thermo_modify.html resulting in:
-
-(...)
-compute CSequ all temp/cs cores shells
-compute thermo_press_lmp all pressure thermo_temp       # pressure for individual particles
-thermo_modify temp CSequ press thermo_press_lmp         # modify thermo to regular pressure
-fix press_bar all npt temp 300 300 0.04 iso 0 0 0.4
-fix_modify press_bar temp CSequ press thermo_press_lmp  # pressure modification for correct kinetic scalar :pre
-
 If "compute temp/cs"_compute_temp_cs.html is used, the decoupled
 relative motion of the core and the shell should in theory be
 stable.  However numerical fluctuation can introduce a small
 momentum to the system, which is noticable over long trajectories.
-Therefore it is recommendable to use the "fix
+Therefore it is recomendable to use the "fix
 momentum"_fix_momentum.html command in combination with "compute
 temp/cs"_compute_temp_cs.html when equilibrating the system to
 prevent any drift.
 
-When initializing the velocities of a system with core/shell pairs, it
+When intializing the velocities of a system with core/shell pairs, it
 is also desirable to not introduce energy into the relative motion of
 the core/shell particles, but only assign a center-of-mass velocity to
 the pairs.  This can be done by using the {bias} keyword of the
 "velocity create"_velocity.html command and assigning the "compute
 temp/cs"_compute_temp_cs.html command to the {temp} keyword of the
-"velocity"_velocity.html command, e.g.
+"velocity"_velocity.html commmand, e.g.
 
 velocity all create 1427 134 bias yes temp CSequ
 velocity all scale 1427 temp CSequ :pre
 
-To maintain the correct polarizability of the core/shell pairs, the
-kinetic energy of the internal motion shall remain nearly constant.
-Therefore the choice of spring force and mass ratio need to ensure
-much faster relative motion of the 2 atoms within the core/shell pair
-than their center-of-mass velocity. This allows the shells to
-effectively react instantaneously to the electrostatic environment and
-limits energy transfer to or from the core/shell oscillators.
-This fast movement also dictates the timestep that can be used.
+It is important to note that the polarizability of the core/shell
+pairs is based on their relative motion. Therefore the choice of
+spring force and mass ratio need to ensure much faster relative motion
+of the 2 atoms within the core/shell pair than their center-of-mass
+velocity. This allow the shells to effectively react instantaneously
+to the electrostatic environment.  This fast movement also limits the
+timestep size that can be used.
 
 The primary literature of the adiabatic core/shell model suggests that
 the fast relative motion of the core/shell pairs only allows negligible
-energy transfer to the environment.
+energy transfer to the environment. Therefore it is not intended to
+decouple the core/shell degree of freedom from the physical system
+during production runs. In other words, the "compute
+temp/cs"_compute_temp_cs.html command should not be used during
+production runs and is only required during equilibration. This way one
+is consistent with literature (based on the code packages DL_POLY or
+GULP for instance).
+
 The mentioned energy transfer will typically lead to a small drift
 in total energy over time.  This internal energy can be monitored
 using the "compute chunk/atom"_compute_chunk_atom.html and "compute
@@ -2788,20 +2761,14 @@ command, to use as input to the "compute
 chunk/atom"_compute_chunk_atom.html command to define the core/shell
 pairs as chunks.
 
-For example if core/shell pairs are the only molecules:
-
-read_data NaCl_CS_x0.1_prop.data
-compute prop all property/atom molecule
-compute cs_chunk all chunk/atom c_prop
-compute cstherm all temp/chunk cs_chunk temp internal com yes cdof 3.0     # note the chosen degrees of freedom for the core/shell pairs
-fix ave_chunk all ave/time 10 1 10 c_cstherm file chunk.dump mode vector :pre
-
-For example if core/shell pairs and other molecules are present:
+For example,
 
 fix csinfo all property/atom i_CSID                       # property/atom command
 read_data NaCl_CS_x0.1_prop.data fix csinfo NULL CS-Info  # atom property added in the data-file
 compute prop all property/atom i_CSID
-(...) :pre
+compute cs_chunk all chunk/atom c_prop
+compute cstherm all temp/chunk cs_chunk temp internal com yes cdof 3.0     # note the chosen degrees of freedom for the core/shell pairs
+fix ave_chunk all ave/time 10 1 10 c_cstherm file chunk.dump mode vector :pre
 
 The additional section in the date file would be formatted like this:
 
@@ -2822,7 +2789,7 @@ CS-Info         # header of additional section :pre
 6.27 Drude induced dipoles :link(howto_27),h4
 
 The thermalized Drude model, similarly to the "core-shell"_#howto_26
-model, represents induced dipoles by a pair of charges (the core atom
+model, representes induced dipoles by a pair of charges (the core atom
 and the Drude particle) connected by a harmonic spring. The Drude
 model has a number of features aimed at its use in molecular systems
 ("Lamoureux and Roux"_#howto-Lamoureux):
@@ -2913,23 +2880,19 @@ Fischer, Gao, Guo, Ha, et al, J Phys Chem, 102, 3586 (1998).
 [(Mayo)] Mayo, Olfason, Goddard III, J Phys Chem, 94, 8897-8909
 (1990).
 
-:link(Jorgensen1)
+:link(Jorgensen)
 [(Jorgensen)] Jorgensen, Chandrasekhar, Madura, Impey, Klein, J Chem
 Phys, 79, 926 (1983).
 
-:link(Price1)
+:link(Price)
 [(Price)] Price and Brooks, J Chem Phys, 121, 10096 (2004).
 
-:link(Shinoda1)
+:link(Shinoda)
 [(Shinoda)] Shinoda, Shiga, and Mikami, Phys Rev B, 69, 134103 (2004).
 
-:link(MitchellFincham)
-[(Mitchell and Fincham)] Mitchell, Fincham, J Phys Condensed Matter,
+:link(MitchellFinchham)
+[(Mitchell and Finchham)] Mitchell, Finchham, J Phys Condensed Matter,
 5, 1031-1038 (1993).
 
-:link(MitchellFincham2)
-[(Fincham)] Fincham, Mackrodt and Mitchell, J Phys Condensed Matter,
-6, 393-404 (1994).
-
 :link(howto-Lamoureux)
 [(Lamoureux and Roux)] G. Lamoureux, B. Roux, J. Chem. Phys 119, 3025 (2003)

doc/src/Section_intro.txt

@@ -249,12 +249,8 @@ Pizza.py WWW site"_pizza. :l
 
 Specialized features :h5
 
-LAMMPS can be built with optional packages which implement a variety
-of additional capabilities.  An overview of all the packages is "given
-here"_Section_packages.html.
-
-These are some LAMMPS capabilities which you may not think of as
-typical classical molecular dynamics options:
+These are LAMMPS capabilities which you may not think of as typical
+molecular dynamics options:
 
 "static"_balance.html and "dynamic load-balancing"_fix_balance.html
 "generalized aspherical particles"_body.html
@@ -342,13 +338,15 @@ dynamics timestepping, particularly if the computations are not
 parallel, so it is often better to leave such analysis to
 post-processing codes.
 
-For high-quality visualization we recommend the
+A very simple (yet fast) visualizer is provided with the LAMMPS
+package - see the "xmovie"_Section_tools.html#xmovie tool in "this
+section"_Section_tools.html.  It creates xyz projection views of
+atomic coordinates and animates them.  We find it very useful for
+debugging purposes.  For high-quality visualization we recommend the
 following packages:
 
 "VMD"_http://www.ks.uiuc.edu/Research/vmd
 "AtomEye"_http://mt.seas.upenn.edu/Archive/Graphics/A
-"OVITO"_http://www.ovito.org/
-"ParaView"_http://www.paraview.org/
 "PyMol"_http://www.pymol.org
 "Raster3d"_http://www.bmsc.washington.edu/raster3d/raster3d.html
 "RasMol"_http://www.openrasmol.org :ul
@@ -519,7 +517,7 @@ the packages they have written are somewhat unique to LAMMPS and the
 code would not be as general-purpose as it is without their expertise
 and efforts.
 
-Axel Kohlmeyer (Temple U), akohlmey at gmail.com, SVN and Git repositories, indefatigable mail list responder, USER-CGSDK and USER-OMP packages
+Axel Kohlmeyer (Temple U), akohlmey at gmail.com, SVN and Git repositories, indefatigable mail list responder, USER-CG-CMM and USER-OMP packages
 Roy Pollock (LLNL), Ewald and PPPM solvers
 Mike Brown (ORNL), brownw at ornl.gov, GPU package
 Greg Wagner (Sandia), gjwagne at sandia.gov, MEAM package for MEAM potential

doc/src/Section_modify.txt

@@ -159,17 +159,17 @@ pack_comm_vel: add velocity info to communication buffer (required)
 pack_comm_hybrid: store extra info unique to this atom style (optional)
 unpack_comm: retrieve an atom's info from the buffer (required)
 unpack_comm_vel: also retrieve velocity info (required)
-unpack_comm_hybrid: retrieve extra info unique to this atom style (optional)
+unpack_comm_hybrid: retreive extra info unique to this atom style (optional)
 pack_reverse: store an atom's info in a buffer communicating partial forces  (required)
 pack_reverse_hybrid: store extra info unique to this atom style (optional)
 unpack_reverse: retrieve an atom's info from the buffer (required)
-unpack_reverse_hybrid: retrieve extra info unique to this atom style (optional)
+unpack_reverse_hybrid: retreive extra info unique to this atom style (optional)
 pack_border: store an atom's info in a buffer communicated on neighbor re-builds (required)
 pack_border_vel: add velocity info to buffer (required)
 pack_border_hybrid: store extra info unique to this atom style (optional)
 unpack_border: retrieve an atom's info from the buffer (required)
 unpack_border_vel: also retrieve velocity info (required)
-unpack_border_hybrid: retrieve extra info unique to this atom style (optional)
+unpack_border_hybrid: retreive extra info unique to this atom style (optional)
 pack_exchange: store all an atom's info to migrate to another processor (required)
 unpack_exchange: retrieve an atom's info from the buffer (required)
 size_restart: number of restart quantities associated with proc's atoms (required)
@@ -369,7 +369,7 @@ pre_force_respa: same as pre_force, but for rRESPA (optional)
 post_force_respa: same as post_force, but for rRESPA (optional)
 final_integrate_respa: same as final_integrate, but for rRESPA (optional)
 min_pre_force: called after pair & molecular forces are computed in minimizer (optional)
-min_post_force: called after pair & molecular forces are computed and communicated in minimizer (optional)
+min_post_force: called after pair & molecular forces are computed and communicated in minmizer (optional)
 min_store: store extra data for linesearch based minimization on a LIFO stack (optional)
 min_pushstore: push the minimization LIFO stack one element down (optional)
 min_popstore: pop the minimization LIFO stack one element up (optional)
@@ -517,7 +517,7 @@ class.  See region.h for details.
 inside: determine whether a point is in the region
 surface_interior: determine if a point is within a cutoff distance inside of surc
 surface_exterior: determine if a point is within a cutoff distance outside of surf
-shape_update : change region shape if set by time-dependent variable :tb(s=:)
+shape_update : change region shape if set by time-depedent variable :tb(s=:)
 
 :line
 
@@ -601,16 +601,16 @@ Adding keywords for the "thermo_style custom"_thermo_style.html command
 "here"_Section_modify.html#mod_13 on this page.
 
 Adding a new math function of one or two arguments can be done by
-editing one section of the Variable::evaluate() method.  Search for
+editing one section of the Variable::evaulate() method.  Search for
 the word "customize" to find the appropriate location.
 
 Adding a new group function can be done by editing one section of the
-Variable::evaluate() method.  Search for the word "customize" to find
+Variable::evaulate() method.  Search for the word "customize" to find
 the appropriate location.  You may need to add a new method to the
 Group class as well (see the group.cpp file).
 
 Accessing a new atom-based vector can be done by editing one section
-of the Variable::evaluate() method.  Search for the word "customize"
+of the Variable::evaulate() method.  Search for the word "customize"
 to find the appropriate location.
 
 Adding new "compute styles"_compute.html (whose calculated values can
@@ -740,7 +740,7 @@ entry to add to the USER-MISC/README file in that dir, along with the
 contribute several individual features.  :l
 
 If you want your contribution to be added as a user-contribution and
-it is several related features, it is probably best to make it a user
+it is several related featues, it is probably best to make it a user
 package directory with a name like USER-FOO.  In addition to your new
 files, the directory should contain a README text file.  The README
 should contain your name and contact information and a brief
@@ -785,10 +785,10 @@ file for how to format the cite itself.  The "Restrictions" section of
 the doc page should indicate that your command is only available if
 LAMMPS is built with the appropriate USER-MISC or USER-FOO package.
 See other user package doc files for examples of how to do this. The
-prerequisite for building the HTML format files are Python 3.x and
+prerequiste for building the HTML format files are Python 3.x and
 virtualenv, the requirement for generating the PDF format manual
 is the "htmldoc"_http://www.htmldoc.org/ software. Please run at least
-"make html" and carefully inspect and proofread the resulting HTML format
+"make html" and carefully inspect and proofread the resuling HTML format
 doc page before submitting your code. :l
 
 For a new package (or even a single command) you should include one or

doc/src/Section_perf.txt

@@ -69,7 +69,7 @@ bench/in.lj input script.
 
 For all the benchmarks, a useful metric is the CPU cost per atom per
 timestep.  Since performance scales roughly linearly with problem size
-and timesteps for all LAMMPS models (i.e. interatomic or coarse-grained
+and timesteps for all LAMMPS models (i.e. inteatomic or coarse-grained
 potentials), the run time of any problem using the same model (atom
 style, force field, cutoff, etc) can then be estimated.
 

doc/src/Section_python.txt

@@ -97,7 +97,7 @@ current LAMMPS library interface and how to call them from Python.
 Section 11.8 gives some examples of coupling LAMMPS to other tools via
 Python.  For example, LAMMPS can easily be coupled to a GUI or other
 visualization tools that display graphs or animations in real time as
-LAMMPS runs.  Examples of such scripts are included in the python
+LAMMPS runs.  Examples of such scripts are inlcluded in the python
 directory.
 
 Two advantages of using Python to run LAMMPS are how concise the
@@ -118,21 +118,18 @@ check which version of Python you have installed, by simply typing
 
 11.2 Overview of using Python from a LAMMPS script :link(py_2),h4
 
-LAMMPS has several commands which can be used to invoke Python
-code directly from an input script:
+NOTE: It is not currently possible to use the "python"_python.html
+command described in this section with Python 3, only with Python 2.
+The C API changed from Python 2 to 3 and the LAMMPS code is not
+compatible with both.
 
-"python"_python.html
-"variable python"_variable.html
-"fix python"_fix_python.html
-"pair_style python"_pair_python.html :ul
-
-The "python"_python.html command which can be used to define and
-execute a Python function that you write the code for.  The Python
-function can also be assigned to a LAMMPS python-style variable via
-the "variable"_variable.html command.  Each time the variable is
-evaluated, either in the LAMMPS input script itself, or by another
-LAMMPS command that uses the variable, this will trigger the Python
-function to be invoked.
+LAMMPS has a "python"_python.html command which can be used in an
+input script to define and execute a Python function that you write
+the code for.  The Python function can also be assigned to a LAMMPS
+python-style variable via the "variable"_variable.html command.  Each
+time the variable is evaluated, either in the LAMMPS input script
+itself, or by another LAMMPS command that uses the variable, this will
+trigger the Python function to be invoked.
 
 The Python code for the function can be included directly in the input
 script or in an auxiliary file.  The function can have arguments which
@@ -165,16 +162,8 @@ doc page for its python-style variables for more info, including
 examples of Python code you can write for both pure Python operations
 and callbacks to LAMMPS.
 
-The "fix python"_fix_python.html command can execute
-Python code at selected timesteps during a simulation run.
-
-The "pair_style python"_pair_python command allows you to define
-pairwise potentials as python code which encodes a single pairwise
-interaction.  This is useful for rapid-developement and debugging of a
-new potential.
-
-To use any of these commands, you only need to build LAMMPS with the
-PYTHON package installed:
+To run pure Python code from LAMMPS, you only need to build LAMMPS
+with the PYTHON package installed:
 
 make yes-python
 make machine :pre
@@ -188,7 +177,7 @@ of Python and your machine to successfully build LAMMPS.  See the
 lib/python/README file for more info.
 
 If you want to write Python code with callbacks to LAMMPS, then you
-must also follow the steps overviewed in the preceding section (11.1)
+must also follow the steps overviewed in the preceeding section (11.1)
 for running LAMMPS from Python.  I.e. you must build LAMMPS as a
 shared library and insure that Python can find the python/lammps.py
 file and the shared library.
@@ -198,7 +187,7 @@ file and the shared library.
 11.3 Building LAMMPS as a shared library :link(py_3),h4
 
 Instructions on how to build LAMMPS as a shared library are given in
-"Section 2.4"_Section_start.html#start_4.  A shared library is one
+"Section 2.5"_Section_start.html#start_5.  A shared library is one
 that is dynamically loadable, which is what Python requires to wrap
 LAMMPS.  On Linux this is a library file that ends in ".so", not ".a".
 
@@ -217,7 +206,7 @@ NOTE: If you are building LAMMPS with an MPI or FFT library or other
 auxiliary libraries (used by various packages), then all of these
 extra libraries must also be shared libraries.  If the LAMMPS
 shared-library build fails with an error complaining about this, see
-"Section 2.4"_Section_start.html#start_4 for more details.
+"Section 2.5"_Section_start.html#start_5 for more details.
 
 :line
 
@@ -336,7 +325,7 @@ sudo python setup.py install :pre
 Again, the "sudo" is only needed if required to copy PyPar files into
 your Python distribution's site-packages directory.
 
-If you have successfully installed PyPar, you should be able to run
+If you have successully installed PyPar, you should be able to run
 Python and type
 
 import pypar :pre
@@ -380,7 +369,7 @@ user privilege into the user local directory type
 
 python setup.py install --user :pre
 
-If you have successfully installed mpi4py, you should be able to run
+If you have successully installed mpi4py, you should be able to run
 Python and type
 
 from mpi4py import MPI :pre
@@ -439,7 +428,7 @@ first importing from the lammps.py file:
 >>> CDLL("liblammps.so") :pre
 
 If an error occurs, carefully go thru the steps in "Section
-2.4"_Section_start.html#start_4 and above about building a shared
+2.5"_Section_start.html#start_5 and above about building a shared
 library and about insuring Python can find the necessary two files
 it needs.
 
@@ -605,10 +594,10 @@ flag = lmp.set_variable(name,value)       # set existing named string-style vari
 value = lmp.get_thermo(name)              # return current value of a thermo keyword
 
 natoms = lmp.get_natoms()                 # total # of atoms as int
-data = lmp.gather_atoms(name,type,count)  # return per-atom property of all atoms gathered into data, ordered by atom ID
+data = lmp.gather_atoms(name,type,count)  # return atom attribute of all atoms gathered into data, ordered by atom ID
                                           # name = "x", "charge", "type", etc
                                           # count = # of per-atom values, 1 or 3, etc
-lmp.scatter_atoms(name,type,count,data)   # scatter per-atom property to all atoms from data, ordered by atom ID
+lmp.scatter_atoms(name,type,count,data)   # scatter atom attribute of all atoms from data, ordered by atom ID
                                           # name = "x", "charge", "type", etc
                                           # count = # of per-atom values, 1 or 3, etc :pre
 
@@ -621,7 +610,7 @@ lmp = lammps() :pre
 
 create an instance of LAMMPS, wrapped in a Python class by the lammps
 Python module, and return an instance of the Python class as lmp.  It
-is used to make all subsequent calls to the LAMMPS library.
+is used to make all subequent calls to the LAMMPS library.
 
 Additional arguments to lammps() can be used to tell Python the name
 of the shared library to load or to pass arguments to the LAMMPS
@@ -667,13 +656,13 @@ argument.
 For extract_atom(), a pointer to internal LAMMPS atom-based data is
 returned, which you can use via normal Python subscripting.  See the
 extract() method in the src/atom.cpp file for a list of valid names.
-Again, new names could easily be added if the property you want is not
-listed.  A pointer to a vector of doubles or integers, or a pointer to
-an array of doubles (double **) or integers (int **) is returned.  You
-need to specify the appropriate data type via the type argument.
+Again, new names could easily be added.  A pointer to a vector of
+doubles or integers, or a pointer to an array of doubles (double **)
+or integers (int **) is returned.  You need to specify the appropriate
+data type via the type argument.
 
 For extract_compute() and extract_fix(), the global, per-atom, or
-local data calculated by the compute or fix can be accessed.  What is
+local data calulated by the compute or fix can be accessed.  What is
 returned depends on whether the compute or fix calculates a scalar or
 vector or array.  For a scalar, a single double value is returned.  If
 the compute or fix calculates a vector or array, a pointer to the
@@ -700,21 +689,12 @@ specified group.
 The get_natoms() method returns the total number of atoms in the
 simulation, as an int.
 
-The gather_atoms() method allows any per-atom property (coordinates,
-velocities, etc) to be extracted from LAMMPS.  It returns a ctypes
-vector of ints or doubles as specified by type, of length
-count*natoms, for the named property for all atoms in the simulation.
-The data is ordered by count and then by atom ID.  See the extract()
-method in the src/atom.cpp file for a list of valid names.  Again, new
-names could easily be added if the property you want is missing.  The
-vector can be used via normal Python subscripting.  If atom IDs are
-not consecutively ordered within LAMMPS, a None is returned as
-indication of an error. A special treatment is applied for image flags
-stored in the "image" property. All three image flags are stored in
-a packed format in a single integer, so count would be 1 to retrieve
-that integer, however also a count value of 3 can be used and then
-the image flags will be unpacked into 3 individual integers, ordered
-in a similar fashion as coordinates.
+The gather_atoms() method returns a ctypes vector of ints or doubles
+as specified by type, of length count*natoms, for the property of all
+the atoms in the simulation specified by name, ordered by count and
+then by atom ID.  The vector can be used via normal Python
+subscripting.  If atom IDs are not consecutively ordered within
+LAMMPS, a None is returned as indication of an error.
 
 Note that the data structure gather_atoms("x") returns is different
 from the data structure returned by extract_atom("x") in four ways.
@@ -731,22 +711,14 @@ assigning a new values to the extract_atom() array.  To do this with
 the gather_atoms() vector, you need to change values in the vector,
 then invoke the scatter_atoms() method.
 
-The scatter_atoms() method allows any per-atom property (coordinates,
-velocities, etc) to be inserted into LAMMPS, overwriting the current
-property.  It takes a vector of ints or doubles as specified by type,
-of length count*natoms, for the named property for all atoms in the
-simulation.  The data should be ordered by count and then by atom ID.
-See the extract() method in the src/atom.cpp file for a list of valid
-names.  Again, new names could easily be added if the property you
-want is missing.  It uses the vector of data to overwrite the
-corresponding properties for each atom inside LAMMPS.  This requires
-LAMMPS to have its "map" option enabled; see the
-"atom_modify"_atom_modify.html command for details.  If it is not, or
-if atom IDs are not consecutively ordered, no coordinates are reset.
-Similar as for gather_atoms() a special treatment is applied for image
-flags, which can be provided in packed (count = 1) or unpacked (count = 3)
-format and in the latter case, they will be packed before applied to
-atoms.
+The scatter_atoms() method takes a vector of ints or doubles as
+specified by type, of length count*natoms, for the property of all the
+atoms in the simulation specified by name, ordered by bount and then
+by atom ID.  It uses the vector of data to overwrite the corresponding
+properties for each atom inside LAMMPS.  This requires LAMMPS to have
+its "map" option enabled; see the "atom_modify"_atom_modify.html
+command for details.  If it is not, or if atom IDs are not
+consecutively ordered, no coordinates are reset.
 
 The array of coordinates passed to scatter_atoms() must be a ctypes
 vector of ints or doubles, allocated and initialized something like
@@ -762,7 +734,7 @@ x\[2\] = z coord of atom with ID 1
 x\[3\] = x coord of atom with ID 2
 ...
 x\[n3-1\] = z coord of atom with ID natoms
-lmp.scatter_atoms("x",1,3,x) :pre
+lmp.scatter_coords("x",1,3,x) :pre
 
 Alternatively, you can just change values in the vector returned by
 gather_atoms("x",1,3), since it is a ctypes vector of doubles.
@@ -802,7 +774,7 @@ demo.py, invoke various LAMMPS library interface routines,
 simple.py, run in parallel, similar to examples/COUPLE/simple/simple.cpp,
 split.py, same as simple.py but running in parallel on a subset of procs,
 gui.py, GUI go/stop/temperature-slider to control LAMMPS,
-plot.py, real-time temperature plot with GnuPlot via Pizza.py,
+plot.py, real-time temeperature plot with GnuPlot via Pizza.py,
 viz_tool.py, real-time viz via some viz package,
 vizplotgui_tool.py, combination of viz_tool.py and plot.py and gui.py :tb(c=2)
 

doc/src/Section_start.txt

@@ -14,11 +14,12 @@ experienced users.
 2.1 "What's in the LAMMPS distribution"_#start_1
 2.2 "Making LAMMPS"_#start_2
 2.3 "Making LAMMPS with optional packages"_#start_3
-2.4 "Building LAMMPS as a library"_#start_4
-2.5 "Running LAMMPS"_#start_5
-2.6 "Command-line options"_#start_6
-2.7 "Screen output"_#start_7
-2.8 "Tips for users of previous versions"_#start_8 :all(b)
+2.4 "Building LAMMPS via the Make.py script"_#start_4
+2.5 "Building LAMMPS as a library"_#start_5
+2.6 "Running LAMMPS"_#start_6
+2.7 "Command-line options"_#start_7
+2.8 "Screen output"_#start_8
+2.9 "Tips for users of previous versions"_#start_9 :all(b)
 
 :line
 
@@ -95,7 +96,7 @@ make serial :pre
 Note that on a facility supercomputer, there are often "modules"
 loaded in your environment that provide the compilers and MPI you
 should use.  In this case, the "mpicxx" compile/link command in
-Makefile.mpi should simply work by accessing those modules.
+Makefile.mpi should just work by accessing those modules.
 
 It may be the case that one of the other Makefile.machine files in the
 src/MAKE sub-directories is a better match to your system (type "make"
@@ -106,35 +107,33 @@ make stampede :pre
 If any of these builds (with an existing Makefile.machine) works on
 your system, then you're done!
 
-If you need to install an optional package with a LAMMPS command you
-want to use, and the package does not depend on an extra library, you
-can simply type
-
-make name :pre
-
-before invoking (or re-invoking) the above steps.  "Name" is the
-lower-case name of the package, e.g. replica or user-misc.
-
 If you want to do one of the following:
 
-use a LAMMPS command that requires an extra library (e.g. "dump image"_dump_image.html)
-build with a package that requires an extra library
-build with an accelerator package that requires special compiler/linker settings
-run on a machine that has its own compilers, settings, or libraries :ul
+use optional LAMMPS features that require additional libraries
+use optional packages that require additional libraries
+use optional accelerator packages that require special compiler/linker settings
+run on a specialized platform that has its own compilers, settings, or other libs to use :ul
 
 then building LAMMPS is more complicated.  You may need to find where
-extra libraries exist on your machine or install them if they don't.
-You may need to build extra libraries that are included in the LAMMPS
-distribution, before building LAMMPS itself.  You may need to edit a
+auxiliary libraries exist on your machine or install them if they
+don't.  You may need to build additional libraries that are part of
+the LAMMPS package, before building LAMMPS.  You may need to edit a
 Makefile.machine file to make it compatible with your system.
 
+Note that there is a Make.py tool in the src directory that automates
+several of these steps, but you still have to know what you are doing.
+"Section 2.4"_#start_4 below describes the tool.  It is a convenient
+way to work with installing/un-installing various packages, the
+Makefile.machine changes required by some packages, and the auxiliary
+libraries some of them use.
+
 Please read the following sections carefully.  If you are not
 comfortable with makefiles, or building codes on a Unix platform, or
 running an MPI job on your machine, please find a local expert to help
-you.  Many compilation, linking, and run problems users experience are
-often not LAMMPS issues - they are peculiar to the user's system,
-compilers, libraries, etc.  Such questions are better answered by a
-local expert.
+you.  Many compilation, linking, and run problems that users have are
+often not really LAMMPS issues - they are peculiar to the user's
+system, compilers, libraries, etc.  Such questions are better answered
+by a local expert.
 
 If you have a build problem that you are convinced is a LAMMPS issue
 (e.g. the compiler complains about a line of LAMMPS source code), then
@@ -414,7 +413,7 @@ uses (for performing 1d FFTs) when running the particle-particle
 particle-mesh (PPPM) option for long-range Coulombics via the
 "kspace_style"_kspace_style.html command.
 
-LAMMPS supports common open-source or vendor-supplied FFT libraries
+LAMMPS supports various open-source or vendor-supplied FFT libraries
 for this purpose.  If you leave these 3 variables blank, LAMMPS will
 use the open-source "KISS FFT library"_http://kissfft.sf.net, which is
 included in the LAMMPS distribution.  This library is portable to all
@@ -424,9 +423,10 @@ package in your build, you can also leave the 3 variables blank.
 
 Otherwise, select which kinds of FFTs to use as part of the FFT_INC
 setting by a switch of the form -DFFT_XXX.  Recommended values for XXX
-are: MKL or FFTW3.  FFTW2 and NONE are supported as legacy options.
-Selecting -DFFT_FFTW will use the FFTW3 library and -DFFT_NONE will
-use the KISS library described above.
+are: MKL, SCSL, FFTW2, and FFTW3.  Legacy options are: INTEL, SGI,
+ACML, and T3E.  For backward compatability, using -DFFT_FFTW will use
+the FFTW2 library.  Using -DFFT_NONE will use the KISS library
+described above.
 
 You may also need to set the FFT_INC, FFT_PATH, and FFT_LIB variables,
 so the compiler and linker can find the needed FFT header and library
@@ -434,39 +434,20 @@ files.  Note that on some large parallel machines which use "modules"
 for their compile/link environements, you may simply need to include
 the correct module in your build environment.  Or the parallel machine
 may have a vendor-provided FFT library which the compiler has no
-trouble finding.  See the src/MAKE/OPTIONS/Makefile.fftw file for an
-example of how to specify these variables to use the FFTW3 library.
+trouble finding.
 
-FFTW is fast, portable library that should also work on any platform
-and typically be faster than KISS FFT.  You can download it from
+FFTW is a fast, portable library that should also work on any
+platform.  You can download it from
 "www.fftw.org"_http://www.fftw.org.  Both the legacy version 2.1.X and
 the newer 3.X versions are supported as -DFFT_FFTW2 or -DFFT_FFTW3.
-Building FFTW for your box should be as simple as ./configure; make;
-make install.  The install command typically requires root privileges
-(e.g. invoke it via sudo), unless you specify a local directory with
-the "--prefix" option of configure.  Type "./configure --help" to see
-various options.
-
-If you wish to have FFTW support for single-precision FFTs (see below
-about -DFFT_SINGLE) in addition to the default double-precision FFTs,
-you will need to build FFTW a second time for single-precision.  For
-FFTW3, do this via:
-
-make clean
-./configure --enable-single; make; make install :pre
-
-which should produce the additional library libfftw3f.a.
-
-For FFTW2, do this:
-
-make clean
-./configure --enable-float --enable-type-prefix; make; make install :pre
-
-which should produce the additional library libsfftw.a and additional
-include file sfttw.a.  Note that on some platforms FFTW2 has been
-pre-installed for both single- and double-precision, and may already
-have these files as well as libdfftw.a and dfftw.h for double
-precision.
+Building FFTW for your box should be as simple as ./configure; make.
+Note that on some platforms FFTW2 has been pre-installed, and uses
+renamed files indicating the precision it was compiled with,
+e.g. sfftw.h, or dfftw.h instead of fftw.h.  In this case, you can
+specify an additional define variable for FFT_INC called -DFFTW_SIZE,
+which will select the correct include file.  In this case, for FFT_LIB
+you must also manually specify the correct library, namely -lsfftw or
+-ldfftw.
 
 The FFT_INC variable also allows for a -DFFT_SINGLE setting that will
 use single-precision FFTs with PPPM, which can speed-up long-range
@@ -478,16 +459,6 @@ accuracy for reduced memory use and parallel communication costs for
 transposing 3d FFT data.  Note that single precision FFTs have only
 been tested with the FFTW3, FFTW2, MKL, and KISS FFT options.
 
-When using -DFFT_SINGLE with FFTW3 or FFTW2, you need to build FFTW
-with support for single-precision, as explained above.  For FFTW3 you
-also need to include -lfftw3f with the FFT_LIB setting, in addition to
--lfftw3.  For FFTW2, you also need to specify -DFFT_SIZE with the
-FFT_INC setting and -lsfftw with the FFT_LIB setting (in place of
--lfftw).  Similarly, if FFTW2 has been preinstalled with an explicit
-double-precision library (libdfftw.a and not the default libfftw.a),
-then you can specify -DFFT_SIZE (and not -DFFT_SINGLE), and specify
--ldfftw to use double-precision FFTs.
-
 Step 7 :h6
 
 The 3 JPG variables allow you to specify a JPEG and/or PNG library
@@ -538,13 +509,13 @@ You should get the executable lmp_foo when the build is complete.
 
 Errors that can occur when making LAMMPS: h5 :link(start_2_3)
 
-If an error occurs when building LAMMPS, the compiler or linker will
-state very explicitly what the problem is.  The error message should
-give you a hint as to which of the steps above has failed, and what
-you need to do in order to fix it.  Building a code with a Makefile is
-a very logical process.  The compiler and linker need to find the
-appropriate files and those files need to be compatible with LAMMPS
-settings and source files.  When a make fails, there is usually a very
+NOTE: If an error occurs when building LAMMPS, the compiler or linker
+will state very explicitly what the problem is.  The error message
+should give you a hint as to which of the steps above has failed, and
+what you need to do in order to fix it.  Building a code with a
+Makefile is a very logical process.  The compiler and linker need to
+find the appropriate files and those files need to be compatible with
+LAMMPS source files.  When a make fails, there is usually a very
 simple reason, which you or a local expert will need to fix.
 
 Here are two non-obvious errors that can occur:
@@ -658,29 +629,22 @@ utilities.
 For Cygwin and the MinGW cross-compilers, suitable makefiles are
 provided in src/MAKE/MACHINES. When using other compilers, like
 Visual C++ or Intel compilers for Windows, you may have to implement
-your own build system. Due to differences between the Windows OS
-and Windows system libraries to Unix-like environments like Linux
-or MacOS, when compiling for Windows a few adjustments may be needed:
-
-Do [not] set the -DLAMMPS_MEMALIGN define (see LMP_INC makefile variable)
-Add -lwsock32 -lpsapi to the linker flags (see LIB makefile variable)
-Try adding -static-libgcc or -static or both to the linker flags when your LAMMPS executable complains about missing .dll files  :ul
-
-Since none of the current LAMMPS core developers has significant
-experience building executables on Windows, we are happy to distribute
-contributed instructions and modifications to improve the situation,
-but we cannot provide support for those.
+your own build system. Since none of the current LAMMPS core developers
+has significant experience building executables on Windows, we are
+happy to distribute contributed instructions and modifications, but
+we cannot provide support for those.
 
 With the so-called "Anniversary Update" to Windows 10, there is a
 Ubuntu Linux subsystem available for Windows, that can be installed
 and then used to compile/install LAMMPS as if you are running on a
 Ubuntu Linux system instead of Windows.
 
-As an alternative, you can download pre-compiled installer packages from
-"packages.lammps.org/windows.html"_http://packages.lammps.org/windows.html.
-These executables are built with most optional packages included and the
-download includes documentation, potential files, some tools and many
-examples, but no source code.
+As an alternative, you can download "daily builds" (and some older
+versions) of the installer packages from
+"rpm.lammps.org/windows.html"_http://rpm.lammps.org/windows.html.
+These executables are built with most optional packages and the
+download includes documentation, potential files, some tools and
+many examples, but no source code.
 
 :line
 
@@ -690,7 +654,13 @@ This section has the following sub-sections:
 
 2.3.1 "Package basics"_#start_3_1
 2.3.2 "Including/excluding packages"_#start_3_2
-2.3.3 "Packages that require extra libraries"_#start_3_3 :all(b)
+2.3.3 "Packages that require extra libraries"_#start_3_3
+2.3.4 "Packages that require Makefile.machine settings"_#start_3_4 :all(b)
+
+Note that the following "Section 2.4"_#start_4 describes the Make.py
+tool which can be used to install/un-install packages and build the
+auxiliary libraries which some of them use.  It can also auto-edit a
+Makefile.machine to add settings needed by some packages.
 
 :line
 
@@ -701,221 +671,235 @@ are always included, plus optional packages.  Packages are groups of
 files that enable a specific set of features.  For example, force
 fields for molecular systems or granular systems are in packages.
 
-"Section 4"_Section_packages.html in the manual has details about all
-the packages, which come in two flavors: [standard] and [user]
-packages. It also has specific instructions for building LAMMPS with
-any package which requires an extra library.  General instructions are
+"Section 4"_Section_packages.html in the manual has details
+about all the packages, including specific instructions for building
+LAMMPS with each package, which are covered in a more general manner
 below.
 
 You can see the list of all packages by typing "make package" from
-within the src directory of the LAMMPS distribution.  It will also
-list various make commands that can be used to manage packages.
+within the src directory of the LAMMPS distribution.  This also lists
+various make commands that can be used to manipulate packages.
 
 If you use a command in a LAMMPS input script that is part of a
 package, you must have built LAMMPS with that package, else you will
 get an error that the style is invalid or the command is unknown.
 Every command's doc page specfies if it is part of a package.  You can
-type
+also type
 
 lmp_machine -h :pre
 
 to run your executable with the optional "-h command-line
-switch"_#start_6 for "help", which will list the styles and commands
-known to your executable, and immediately exit.
+switch"_#start_7 for "help", which will simply list the styles and
+commands known to your executable, and immediately exit.
+
+There are two kinds of packages in LAMMPS, standard and user packages.
+More information about the contents of standard and user packages is
+given in "Section 4"_Section_packages.html of the manual.  The
+difference between standard and user packages is as follows:
+
+Standard packages, such as molecule or kspace, are supported by the
+LAMMPS developers and are written in a syntax and style consistent
+with the rest of LAMMPS.  This means we will answer questions about
+them, debug and fix them if necessary, and keep them compatible with
+future changes to LAMMPS.
+
+User packages, such as user-atc or user-omp, have been contributed by
+users, and always begin with the user prefix.  If they are a single
+command (single file), they are typically in the user-misc package.
+Otherwise, they are a set of files grouped together which add a
+specific functionality to the code.
+
+User packages don't necessarily meet the requirements of the standard
+packages.  If you have problems using a feature provided in a user
+package, you may need to contact the contributor directly to get help.
+Information on how to submit additions you make to LAMMPS as single
+files or either a standard or user-contributed package are given in
+"this section"_Section_modify.html#mod_15 of the documentation.
 
 :line
 
 Including/excluding packages :h5,link(start_3_2)
 
-To use (or not use) a package you must install it (or un-install it)
-before building LAMMPS.  From the src directory, this is as simple as:
+To use (or not use) a package you must include it (or exclude it)
+before building LAMMPS.  From the src directory, this is typically as
+simple as:
 
 make yes-colloid
 make mpi :pre
 
 or
 
-make no-user-omp
+make no-manybody
 make mpi :pre
 
-NOTE: You should NOT install/un-install packages and build LAMMPS in a
+NOTE: You should NOT include/exclude packages and build LAMMPS in a
 single make command using multiple targets, e.g. make yes-colloid mpi.
 This is because the make procedure creates a list of source files that
 will be out-of-date for the build if the package configuration changes
 within the same command.
 
-Any package can be installed or not in a LAMMPS build, independent of
-all other packages.  However, some packages include files derived from
-files in other packages.  LAMMPS checks for this and does the right
-thing.  I.e. individual files are only included if their dependencies
-are already included.  Likewise, if a package is excluded, other files
+Some packages have individual files that depend on other packages
+being included.  LAMMPS checks for this and does the right thing.
+I.e. individual files are only included if their dependencies are
+already included.  Likewise, if a package is excluded, other files
 dependent on that package are also excluded.
 
-NOTE: The one exception is that we do not recommend building with both
-the KOKKOS package installed and any of the other acceleration
-packages (GPU, OPT, USER-INTEL, USER-OMP) also installed.  This is
-because of how Kokkos sometimes builds using a wrapper compiler which
-can make it difficult to invoke all the compile/link flags correctly
-for both Kokkos and non-Kokkos files.
-
 If you will never run simulations that use the features in a
 particular packages, there is no reason to include it in your build.
-For some packages, this will keep you from having to build extra
-libraries, and will also produce a smaller executable which may run a
-bit faster.
+For some packages, this will keep you from having to build auxiliary
+libraries (see below), and will also produce a smaller executable
+which may run a bit faster.
 
-When you download a LAMMPS tarball, three packages are pre-installed
-in the src directory -- KSPACE, MANYBODY, MOLECULE -- because they are
-so commonly used.  When you download LAMMPS source files from the SVN
-or Git repositories, no packages are pre-installed.
+When you download a LAMMPS tarball, these packages are pre-installed
+in the src directory: KSPACE, MANYBODY,MOLECULE, because they are so
+commonly used.  When you download LAMMPS source files from the SVN or
+Git repositories, no packages are pre-installed.
 
-Packages are installed or un-installed by typing
+Packages are included or excluded by typing "make yes-name" or "make
+no-name", where "name" is the name of the package in lower-case, e.g.
+name = kspace for the KSPACE package or name = user-atc for the
+USER-ATC package.  You can also type "make yes-standard", "make
+no-standard", "make yes-std", "make no-std", "make yes-user", "make
+no-user", "make yes-lib", "make no-lib", "make yes-all", or "make
+no-all" to include/exclude various sets of packages.  Type "make
+package" to see all of the package-related make options.
 
-make yes-name
-make no-name :pre
+NOTE: Inclusion/exclusion of a package works by simply moving files
+back and forth between the main src directory and sub-directories with
+the package name (e.g. src/KSPACE, src/USER-ATC), so that the files
+are seen or not seen when LAMMPS is built.  After you have included or
+excluded a package, you must re-build LAMMPS.
 
-where "name" is the name of the package in lower-case, e.g.  name =
-kspace for the KSPACE package or name = user-atc for the USER-ATC
-package.  You can also type any of these commands:
-
-make yes-all | install all packages
-make no-all | un-install all packages
-make yes-standard or make yes-std | install standard packages
-make no-standard or make no-std| un-install standard packages
-make yes-user | install user packages
-make no-user | un-install user packages
-make yes-lib | install packages that require extra libraries
-make no-lib | un-install packages that require extra libraries
-make yes-ext | install packages that require external libraries
-make no-ext | un-install packages that require external libraries :tb(s=|)
-
-which install/un-install various sets of packages.  Typing "make
-package" will list all the these commands.
-
-NOTE: Installing or un-installing a package works by simply moving
-files back and forth between the main src directory and
-sub-directories with the package name (e.g. src/KSPACE, src/USER-ATC),
-so that the files are included or excluded when LAMMPS is built.
-After you have installed or un-installed a package, you must re-build
-LAMMPS for the action to take effect.
-
-The following make commands help manage files that exist in both the
-src directory and in package sub-directories.  You do not normally
-need to use these commands unless you are editing LAMMPS files or have
-downloaded a patch from the LAMMPS web site.
-
-Typing "make package-status" or "make ps" will show which packages are
-currently installed. For those that are installed, it will list any
-files that are different in the src directory and package
-sub-directory.
+Additional package-related make options exist to help manage LAMMPS
+files that exist in both the src directory and in package
+sub-directories.  You do not normally need to use these commands
+unless you are editing LAMMPS files or have downloaded a patch from
+the LAMMPS WWW site.
 
 Typing "make package-update" or "make pu" will overwrite src files
-with files from the package sub-directories if the package is
-installed.  It should be used after a patch has been applied, since
-patches only update the files in the package sub-directory, but not
-the src files.
+with files from the package sub-directories if the package has been
+included.  It should be used after a patch is installed, since patches
+only update the files in the package sub-directory, but not the src
+files.  Typing "make package-overwrite" will overwrite files in the
+package sub-directories with src files.
 
-Typing "make package-overwrite" will overwrite files in the package
-sub-directories with src files.
-
-Typing "make package-diff" lists all differences between these files.
-
-Again, just type "make package" to see all of the package-related make
-options.
+Typing "make package-status" or "make ps" will show which packages are
+currently included. For those that are included, it will list any
+files that are different in the src directory and package
+sub-directory.  Typing "make package-diff" lists all differences
+between these files.  Again, type "make package" to see all of the
+package-related make options.
 
 :line
 
 Packages that require extra libraries :h5,link(start_3_3)
 
-A few of the standard and user packages require extra libraries.  See
-"Section 4"_Section_packages.html for two tables of packages which
-indicate which ones require libraries.  For each such package, the
-Section 4 doc page gives details on how to build the extra library,
-including how to download it if necessary.  The basic ideas are
-summarized here.
+A few of the standard and user packages require additional auxiliary
+libraries.  Many of them are provided with LAMMPS, in which case they
+must be compiled first, before LAMMPS is built, if you wish to include
+that package.  If you get a LAMMPS build error about a missing
+library, this is likely the reason.  See the
+"Section 4"_Section_packages.html doc page for a list of
+packages that have these kinds of auxiliary libraries.
 
-[System libraries:]
+The lib directory in the distribution has sub-directories with package
+names that correspond to the needed auxiliary libs, e.g. lib/gpu.
+Each sub-directory has a README file that gives more details.  Code
+for most of the auxiliary libraries is included in that directory.
+Examples are the USER-ATC and MEAM packages.
 
-Packages in the tables "Section 4"_Section_packages.html with a "sys"
-in the last column link to system libraries that typically already
-exist on your machine.  E.g. the python package links to a system
-Python library.  If your machine does not have the required library,
-you will have to download and install it on your machine, in either
-the system or user space.
+A few of the lib sub-directories do not include code, but do include
+instructions (and sometimes scripts) that automate the process of
+downloading the auxiliary library and installing it so LAMMPS can link
+to it.  Examples are the KIM, VORONOI, USER-MOLFILE, and USER-SMD
+packages.
 
-[Internal libraries:]
+The lib/python directory (for the PYTHON package) contains only a
+choice of Makefile.lammps.* files.  This is because no auxiliary code
+or libraries are needed, only the Python library and other system libs
+that should already available on your system.  However, the
+Makefile.lammps file is needed to tell LAMMPS which libs to use and
+where to find them.
 
-Packages in the tables "Section 4"_Section_packages.html with an "int"
-in the last column link to internal libraries whose source code is
-included with LAMMPS, in the lib/name directory where name is the
-package name.  You must first build the library in that directory
-before building LAMMPS with that package installed.  E.g. the gpu
-package links to a library you build in the lib/gpu dir.  You can
-often do the build in one step by typing "make lib-name args=..."
-from the src dir, with appropriate arguments.  You can leave off the
-args to see a help message.  See "Section 4"_Section_packages.html for
-details for each package.
+For libraries with provided code, the sub-directory README file
+(e.g. lib/atc/README) has instructions on how to build that library.
+This information is also summarized in "Section
+4"_Section_packages.html.  Typically this is done by typing
+something like:
 
-[External libraries:]
+make -f Makefile.g++ :pre
 
-Packages in the tables "Section 4"_Section_packages.html with an "ext"
-in the last column link to exernal libraries whose source code is not
-included with LAMMPS.  You must first download and install the library
-before building LAMMPS with that package installed.  E.g. the voronoi
-package links to the freely available "Voro++ library"_voro_home2.  You
-can often do the download/build in one step by typing "make lib-name
-args=..." from the src dir, with appropriate arguments.  You can leave
-off the args to see a help message.  See "Section
-4"_Section_packages.html for details for each package.
+If one of the provided Makefiles is not appropriate for your system
+you will need to edit or add one.  Note that all the Makefiles have a
+setting for EXTRAMAKE at the top that specifies a Makefile.lammps.*
+file.
 
-:link(voro_home2,http://math.lbl.gov/voro++)
+If the library build is successful, it will produce 2 files in the lib
+directory:
 
-[Possible errors:]
+libpackage.a
+Makefile.lammps :pre
 
-There are various common errors which can occur when building extra
-libraries or when building LAMMPS with packages that require the extra
-libraries.
+The Makefile.lammps file will typically be a copy of one of the
+Makefile.lammps.* files in the library directory.
 
-If you cannot build the extra library itself successfully, you may
-need to edit or create an appropriate Makefile for your machine, e.g.
-with appropriate compiler or system settings.  Provided makefiles are
-typically in the lib/name directory.  E.g. see the Makefile.* files in
-lib/gpu.
+Note that you must insure that the settings in Makefile.lammps are
+appropriate for your system.  If they are not, the LAMMPS build may
+fail.  To fix this, you can edit or create a new Makefile.lammps.*
+file for your system, and copy it to Makefile.lammps.
 
-The LAMMPS build often uses settings in a lib/name/Makefile.lammps
-file which either exists in the LAMMPS distribution or is created or
-copied from a lib/name/Makefile.lammps.* file when the library is
-built.  If those settings are not correct for your machine you will
-need to edit or create an appropriate Makefile.lammps file.
+As explained in the lib/package/README files, the settings in
+Makefile.lammps are used to specify additional system libraries and
+their locations so that LAMMPS can build with the auxiliary library.
+For example, if the MEAM package is used, the auxiliary library
+consists of F90 code, built with a Fortran complier.  To link that
+library with LAMMPS (a C++ code) via whatever C++ compiler LAMMPS is
+built with, typically requires additional Fortran-to-C libraries be
+included in the link.  Another example are the BLAS and LAPACK
+libraries needed to use the USER-ATC or USER-AWPMD packages.
 
-Package-specific details for these steps are given in "Section
-4"_Section_packages.html an in README files in the lib/name
-directories.
+For libraries without provided code, the sub-directory README file has
+information on where to download the library and how to build it,
+e.g. lib/voronoi/README and lib/smd/README.  The README files also
+describe how you must either (a) create soft links, via the "ln"
+command, in those directories to point to where you built or installed
+the packages, or (b) check or edit the Makefile.lammps file in the
+same directory to provide that information.
 
-[Compiler options needed for accelerator packages:]
+Some of the sub-directories, e.g. lib/voronoi, also have an install.py
+script which can be used to automate the process of
+downloading/building/installing the auxiliary library, and setting the
+needed soft links.  Type "python install.py" for further instructions.
 
-Several packages contain code that is optimized for specific hardware,
-e.g. CPU, KNL, or GPU.  These are the OPT, GPU, KOKKOS, USER-INTEL,
-and USER-OMP packages.  Compiling and linking the source files in
-these accelerator packages for optimal performance requires specific
-settings in the Makefile.machine file you use.
+As with the sub-directories containing library code, if the soft links
+or settings in the lib/package/Makefile.lammps files are not correct,
+the LAMMPS build will typically fail.
 
-A summary of the Makefile.machine settings needed for each of these
-packages is given in "Section 4"_Section_packages.html.  More info is
-given on the doc pages that describe each package in detail:
+:line
+
+Packages that require Makefile.machine settings :h5,link(start_3_4)
+
+A few packages require specific settings in Makefile.machine, to
+either build or use the package effectively.  These are the
+USER-INTEL, KOKKOS, USER-OMP, and OPT packages, used for accelerating
+code performance on CPUs or other hardware, as discussed in "Section
+5.3"_Section_accelerate.html#acc_3.
+
+A summary of what Makefile.machine changes are needed for each of
+these packages is given in "Section 4"_Section_packages.html.
+The details are given on the doc pages that describe each of these
+accelerator packages in detail:
 
 5.3.1 "USER-INTEL package"_accelerate_intel.html
-5.3.2 "GPU package"_accelerate_intel.html
 5.3.3 "KOKKOS package"_accelerate_kokkos.html
 5.3.4 "USER-OMP package"_accelerate_omp.html
 5.3.5 "OPT package"_accelerate_opt.html :all(b)
 
-You can also use or examine the following machine Makefiles in
-src/MAKE/OPTIONS, which include the settings.  Note that the
-USER-INTEL and KOKKOS packages can use settings that build LAMMPS for
-different hardware.  The USER-INTEL package can be compiled for Intel
-CPUs and KNLs; the KOKKOS package builds for CPUs (OpenMP), GPUs
-(CUDA), and Intel KNLs.
+You can also look at the following machine Makefiles in
+src/MAKE/OPTIONS, which include the changes.  Note that the USER-INTEL
+and KOKKOS packages allow for settings that build LAMMPS for different
+hardware.  The USER-INTEL package builds for CPU and the Xeon Phi, the
+KOKKOS package builds for OpenMP, GPUs (Cuda), and the Xeon Phi.
 
 Makefile.intel_cpu
 Makefile.intel_phi
@@ -925,9 +909,127 @@ Makefile.kokkos_phi
 Makefile.omp
 Makefile.opt :ul
 
+Also note that the Make.py tool, described in the next "Section
+2.4"_#start_4 can automatically add the needed info to an existing
+machine Makefile, using simple command-line arguments.
+
 :line
 
-2.4 Building LAMMPS as a library :h4,link(start_4)
+2.4 Building LAMMPS via the Make.py tool :h4,link(start_4)
+
+The src directory includes a Make.py script, written in Python, which
+can be used to automate various steps of the build process.  It is
+particularly useful for working with the accelerator packages, as well
+as other packages which require auxiliary libraries to be built.
+
+The goal of the Make.py tool is to allow any complex multi-step LAMMPS
+build to be performed as a single Make.py command.  And you can
+archive the commands, so they can be re-invoked later via the -r
+(redo) switch.  If you find some LAMMPS build procedure that can't be
+done in a single Make.py command, let the developers know, and we'll
+see if we can augment the tool.
+
+You can run Make.py from the src directory by typing either:
+
+Make.py -h
+python Make.py -h :pre
+
+which will give you help info about the tool.  For the former to work,
+you may need to edit the first line of Make.py to point to your local
+Python.  And you may need to insure the script is executable:
+
+chmod +x Make.py :pre
+
+Here are examples of build tasks you can perform with Make.py:
+
+Install/uninstall packages: Make.py -p no-lib kokkos omp intel
+Build specific auxiliary libs: Make.py -a lib-atc lib-meam
+Build libs for all installed packages: Make.py -p cuda gpu -gpu mode=double arch=31 -a lib-all
+Create a Makefile from scratch with compiler and MPI settings: Make.py -m none -cc g++ -mpi mpich -a file
+Augment Makefile.serial with settings for installed packages: Make.py -p intel -intel cpu -m serial -a file
+Add JPG and FFTW support to Makefile.mpi: Make.py -m mpi -jpg -fft fftw -a file
+Build LAMMPS with a parallel make using Makefile.mpi: Make.py -j 16 -m mpi -a exe
+Build LAMMPS and libs it needs using Makefile.serial with accelerator settings: Make.py -p gpu intel -intel cpu -a lib-all file serial :tb(s=:)
+
+The bench and examples directories give Make.py commands that can be
+used to build LAMMPS with the various packages and options needed to
+run all the benchmark and example input scripts.  See these files for
+more details:
+
+bench/README
+bench/FERMI/README
+bench/KEPLER/README
+bench/PHI/README
+examples/README
+examples/accelerate/README
+examples/accelerate/make.list :ul
+
+All of the Make.py options and syntax help can be accessed by using
+the "-h" switch.
+
+E.g. typing "Make.py -h" gives
+
+Syntax: Make.py switch args ...
+  switches can be listed in any order
+  help switch:
+    -h prints help and syntax for all other specified switches
+  switch for actions:
+    -a lib-all, lib-dir, clean, file, exe or machine
+    list one or more actions, in any order
+    machine is a Makefile.machine suffix, must be last if used
+  one-letter switches:
+    -d (dir), -j (jmake), -m (makefile), -o (output),
+    -p (packages), -r (redo), -s (settings), -v (verbose)
+  switches for libs:
+    -atc, -awpmd, -colvars, -cuda
+    -gpu, -meam, -poems, -qmmm, -reax
+  switches for build and makefile options:
+    -intel, -kokkos, -cc, -mpi, -fft, -jpg, -png :pre
+
+Using the "-h" switch with other switches and actions gives additional
+info on all the other specified switches or actions.  The "-h" can be
+anywhere in the command-line and the other switches do not need their
+arguments.  E.g. type "Make.py -h -d -atc -intel" will print:
+
+-d dir
+  dir = LAMMPS home dir
+  if -d not specified, working dir must be lammps/src :pre
+
+-atc make=suffix lammps=suffix2
+  all args are optional and can be in any order
+  make = use Makefile.suffix (def = g++)
+  lammps = use Makefile.lammps.suffix2 (def = EXTRAMAKE in makefile) :pre
+
+-intel mode
+  mode = cpu or phi (def = cpu)
+    build Intel package for CPU or Xeon Phi :pre
+
+Note that Make.py never overwrites an existing Makefile.machine.
+Instead, it creates src/MAKE/MINE/Makefile.auto, which you can save or
+rename if desired.  Likewise it creates an executable named
+src/lmp_auto, which you can rename using the -o switch if desired.
+
+The most recently executed Make.py commmand is saved in
+src/Make.py.last.  You can use the "-r" switch (for redo) to re-invoke
+the last command, or you can save a sequence of one or more Make.py
+commands to a file and invoke the file of commands using "-r".  You
+can also label the commands in the file and invoke one or more of them
+by name.
+
+A typical use of Make.py is to start with a valid Makefile.machine for
+your system, that works for a vanilla LAMMPS build, i.e. when optional
+packages are not installed.  You can then use Make.py to add various
+settings (FFT, JPG, PNG) to the Makefile.machine as well as change its
+compiler and MPI options.  You can also add additional packages to the
+build, as well as build the needed supporting libraries.
+
+You can also use Make.py to create a new Makefile.machine from
+scratch, using the "-m none" switch, if you also specify what compiler
+and MPI options to use, via the "-cc" and "-mpi" switches.
+
+:line
+
+2.5 Building LAMMPS as a library :h4,link(start_5)
 
 LAMMPS can be built as either a static or shared library, which can
 then be called from another application or a scripting language.  See
@@ -1049,7 +1151,7 @@ interface and how to extend it for your needs.
 
 :line
 
-2.5 Running LAMMPS :h4,link(start_5)
+2.6 Running LAMMPS :h4,link(start_6)
 
 By default, LAMMPS runs by reading commands from standard input.  Thus
 if you run the LAMMPS executable by itself, e.g.
@@ -1093,7 +1195,7 @@ LAMMPS to be built with one or more of its optional packages.
 :line
 
 On a Windows box, you can skip making LAMMPS and simply download an
-installer package from "here"_http://packages.lammps.org/windows.html
+installer package from "here"_http://rpm.lammps.org/windows.html
 
 For running the non-MPI executable, follow these steps:
 
@@ -1105,27 +1207,18 @@ the [in.lj] input from the bench folder. (e.g. by typing: cd "Documents"). :l
 
 At the command prompt, type "lmp_serial -in in.lj", replacing [in.lj]
 with the name of your LAMMPS input script. :l
-
-The serial executable includes support for multi-threading
-parallelization from the styles in the USER-OMP packages.
-
-To run with, e.g. 4 threads, type "lmp_serial -in in.lj -pk omp 4 -sf omp"
 :ule
 
-For the MPI version, which allows you to run LAMMPS under Windows with
-the more general message passing parallel library (LAMMPS has been
-designed from ground up to use MPI efficiently), follow these steps:
+For the MPI version, which allows you to run LAMMPS under Windows on
+multiple processors, follow these steps:
 
-Download and install a compatible MPI library binary package:
-for 32-bit Windows
-"mpich2-1.4.1p1-win-ia32.msi"_download.lammps.org/thirdparty/mpich2-1.4.1p1-win-ia32.msi
-and for 64-bit Windows
-"mpich2-1.4.1p1-win-x86-64.msi"_download.lammps.org/thirdparty/mpich2-1.4.1p1-win-x86-64.msi
-:ulb,l
+Download and install
+"MPICH2"_http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads
+for Windows. :ulb,l
 
 The LAMMPS Windows installer packages will automatically adjust your
 path for the default location of this MPI package. After the installation
-of the MPICH2 software, it needs to be integrated into the system.
+of the MPICH software, it needs to be integrated into the system.
 For this you need to start a Command Prompt in {Administrator Mode}
 (right click on the icon and select it). Change into the MPICH2
 installation directory, then into the subdirectory [bin] and execute
@@ -1144,7 +1237,7 @@ or
 
 mpiexec -np 4 lmp_mpi -in in.lj :pre
 
-replacing [in.lj] with the name of your LAMMPS input script. For the latter
+replacing in.lj with the name of your LAMMPS input script. For the latter
 case, you may be prompted to enter your password. :l
 
 In this mode, output may not immediately show up on the screen, so if
@@ -1156,11 +1249,6 @@ something like:
 
 lmp_mpi -in in.lj :pre
 
-And the parallel executable also includes OpenMP multi-threading, which
-can be combined with MPI using something like:
-
-mpiexec -localonly 2 lmp_mpi -in in.lj -pk omp 2 -sf omp :pre
-
 :ule
 
 :line
@@ -1195,7 +1283,7 @@ more processors or setup a smaller problem.
 
 :line
 
-2.6 Command-line options :h4,link(start_6)
+2.7 Command-line options :h4,link(start_7)
 
 At run time, LAMMPS recognizes several optional command-line switches
 which may be used in any order.  Either the full word or a one-or-two
@@ -1625,7 +1713,7 @@ negative numeric value.  It is OK if the first value1 starts with a
 
 :line
 
-2.7 LAMMPS screen output :h4,link(start_7)
+2.8 LAMMPS screen output :h4,link(start_8)
 
 As LAMMPS reads an input script, it prints information to both the
 screen and a log file about significant actions it takes to setup a
@@ -1781,7 +1869,7 @@ communication, roughly 75% in the example above.
 
 :line
 
-2.8 Tips for users of previous LAMMPS versions :h4,link(start_8)
+2.9 Tips for users of previous LAMMPS versions :h4,link(start_9)
 
 The current C++ began with a complete rewrite of LAMMPS 2001, which
 was written in F90.  Features of earlier versions of LAMMPS are listed

doc/src/Section_tools.txt

@@ -12,12 +12,9 @@ Section"_Section_modify.html :c
 
 LAMMPS is designed to be a computational kernel for performing
 molecular dynamics computations.  Additional pre- and post-processing
-steps are often necessary to setup and analyze a simulation. A
-list of such tools can be found on the LAMMPS home page
-at "http://lammps.sandia.gov/prepost.html"_http://lammps.sandia.gov/prepost.html
-
-A few additional tools are provided with the LAMMPS distribution
-and are described in this section.
+steps are often necessary to setup and analyze a simulation.  A few
+additional tools are provided with the LAMMPS distribution and are
+described in this section.
 
 Our group has also written and released a separate toolkit called
 "Pizza.py"_pizza which provides tools for doing setup, analysis,
@@ -39,16 +36,16 @@ authors.
 The source code for each of these codes is in the tools sub-directory
 of the LAMMPS distribution.  There is a Makefile (which you may need
 to edit for your platform) which will build several of the tools which
-reside in that directory.  Most of them are larger packages in their
-own sub-directories with their own Makefiles and/or README files.
+reside in that directory.  Some of them are larger packages in their
+own sub-directories with their own Makefiles.
 
 "amber2lmp"_#amber
 "binary2txt"_#binary
 "ch2lmp"_#charmm
 "chain"_#chain
 "colvars"_#colvars
-"createatoms"_#createatoms
-"drude"_#drude
+"createatoms"_#create
+"data2xmovie"_#data
 "eam database"_#eamdb
 "eam generate"_#eamgn
 "eff"_#eff
@@ -59,18 +56,20 @@ own sub-directories with their own Makefiles and/or README files.
 "kate"_#kate
 "lmp2arc"_#arc
 "lmp2cfg"_#cfg
+"lmp2vmd"_#vmd
 "matlab"_#matlab
 "micelle2d"_#micelle
 "moltemplate"_#moltemplate
 "msi2lmp"_#msi
 "phonon"_#phonon
-"polybond"_#polybond
+"polymer bonding"_#polybond
 "pymol_asphere"_#pymol
 "python"_#pythontools
 "reax"_#reax_tool
-"smd"_#smd
+"restart2data"_#restart
 "vim"_#vim
 "xmgrace"_#xmgrace
+"xmovie"_#xmovie :ul
 
 :line
 
@@ -159,7 +158,7 @@ gmail.com) at ICTP, Italy.
 
 :line
 
-createatoms tool :h4,link(createatoms)
+createatoms tool :h4,link(create)
 
 The tools/createatoms directory contains a Fortran program called
 createAtoms.f which can generate a variety of interesting crystal
@@ -172,16 +171,16 @@ The tool is authored by Xiaowang Zhou (Sandia), xzhou at sandia.gov.
 
 :line
 
-drude tool :h4,link(drude)
+data2xmovie tool :h4,link(data)
 
-The tools/drude directory contains a Python script called
-polarizer.py which can add Drude oscillators to a LAMMPS
-data file in the required format.
+The file data2xmovie.c converts a LAMMPS data file into a snapshot
+suitable for visualizing with the "xmovie"_#xmovie tool, as if it had
+been output with a dump command from LAMMPS itself.  The syntax for
+running the tool is
 
-See the header of the polarizer.py file for details.
+data2xmovie \[options\] < infile > outfile :pre
 
-The tool is authored by Agilio Padua and Alain Dequidt: agilio.padua
-at univ-bpclermont.fr, alain.dequidt at univ-bpclermont.fr
+See the top of the data2xmovie.c file for a discussion of the options.
 
 :line
 
@@ -318,6 +317,18 @@ This tool was written by Ara Kooser at Sandia (askoose at sandia.gov).
 
 :line
 
+lmp2vmd tool :h4,link(vmd)
+
+The lmp2vmd sub-directory contains a README.txt file that describes
+details of scripts and plugin support within the "VMD
+package"_http://www.ks.uiuc.edu/Research/vmd for visualizing LAMMPS
+dump files.
+
+The VMD plugins and other supporting scripts were written by Axel
+Kohlmeyer (akohlmey at cmm.chem.upenn.edu) at U Penn.
+
+:line
+
 matlab tool :h4,link(matlab)
 
 The matlab sub-directory contains several "MATLAB"_matlabhome scripts for
@@ -369,18 +380,17 @@ supports it.  It has its own WWW page at
 
 msi2lmp tool :h4,link(msi)
 
-The msi2lmp sub-directory contains a tool for creating LAMMPS template
-input and data files from BIOVIA's Materias Studio files (formerly Accelrys'
-Insight MD code, formerly MSI/Biosym and its Discover MD code).
+The msi2lmp sub-directory contains a tool for creating LAMMPS input
+data files from Accelrys' Insight MD code (formerly MSI/Biosym and
+its Discover MD code).  See the README file for more information.
 
 This tool was written by John Carpenter (Cray), Michael Peachey
-(Cray), and Steve Lustig (Dupont). Several people contributed changes
-to remove bugs and adapt its output to changes in LAMMPS.
+(Cray), and Steve Lustig (Dupont).  John is now at the Mayo Clinic
+(jec at mayo.edu), but still fields questions about the tool.
 
-This tool has several known limitations and is no longer under active
-development, so there are no changes except for the occasional bugfix.
-
-See the README file in the tools/msi2lmp folder for more information.
+This tool may be out-of-date with respect to the current LAMMPS and
+Insight versions.  Since we don't use it at Sandia, you'll need to
+experiment with it yourself.
 
 :line
 
@@ -399,7 +409,7 @@ University.
 
 :line
 
-polybond tool :h4,link(polybond)
+polymer bonding tool :h4,link(polybond)
 
 The polybond sub-directory contains a Python-based tool useful for
 performing "programmable polymer bonding".  The Python file
@@ -458,19 +468,48 @@ These tools were written by Aidan Thompson at Sandia.
 
 :line
 
-smd tool :h4,link(smd)
+restart2data tool :h4,link(restart)
 
-The smd sub-directory contains a C++ file dump2vtk_tris.cpp and
-Makefile which can be compiled and used to convert triangle output
-files created by the Smooth-Mach Dynamics (USER-SMD) package into a
-VTK-compatible unstructured grid file.  It could then be read in and
-visualized by VTK.
+NOTE: This tool is now obsolete and is not included in the current
+LAMMPS distribution.  This is becaues there is now a
+"write_data"_write_data.html command, which can create a data file
+from within an input script.  Running LAMMPS with the "-r"
+"command-line switch"_Section_start.html#start_7 as follows:
 
-See the header of dump2vtk.cpp for more details.
+lmp_g++ -r restartfile datafile
 
-This tool was written by the USER-SMD package author, Georg
-Ganzenmuller at the Fraunhofer-Institute for High-Speed Dynamics,
-Ernst Mach Institute in Germany (georg.ganzenmueller at emi.fhg.de).
+is the same as running a 2-line input script:
+
+read_restart restartfile
+write_data datafile
+
+which will produce the same data file that the restart2data tool used
+to create.  The following information is included in case you have an
+older version of LAMMPS which still includes the restart2data tool.
+
+The file restart2data.cpp converts a binary LAMMPS restart file into
+an ASCII data file.  The syntax for running the tool is
+
+restart2data restart-file data-file (input-file) :pre
+
+Input-file is optional and if specified will contain LAMMPS input
+commands for the masses and force field parameters, instead of putting
+those in the data-file.  Only a few force field styles currently
+support this option.
+
+This tool must be compiled on a platform that can read the binary file
+created by a LAMMPS run, since binary files are not compatible across
+all platforms.
+
+Note that a text data file has less precision than a binary restart
+file.  Hence, continuing a run from a converted data file will
+typically not conform as closely to a previous run as will restarting
+from a binary restart file.
+
+If a "%" appears in the specified restart-file, the tool expects a set
+of multiple files to exist.  See the "restart"_restart.html and
+"write_restart"_write_restart.html commands for info on how such sets
+of files are written by LAMMPS, and how the files are named.
 
 :line
 
@@ -498,3 +537,32 @@ See the README file for details.
 
 These files were provided by Vikas Varshney (vv0210 at gmail.com)
 
+:line
+
+xmovie tool :h4,link(xmovie)
+
+The xmovie tool is an X-based visualization package that can read
+LAMMPS dump files and animate them.  It is in its own sub-directory
+with the tools directory.  You may need to modify its Makefile so that
+it can find the appropriate X libraries to link against.
+
+The syntax for running xmovie is
+
+xmovie \[options\] dump.file1 dump.file2 ... :pre
+
+If you just type "xmovie" you will see a list of options.  Note that
+by default, LAMMPS dump files are in scaled coordinates, so you
+typically need to use the -scale option with xmovie.  When xmovie runs
+it opens a visualization window and a control window.  The control
+options are straightforward to use.
+
+Xmovie was mostly written by Mike Uttormark (U Wisconsin) while he
+spent a summer at Sandia.  It displays 2d projections of a 3d domain.
+While simple in design, it is an amazingly fast program that can
+render large numbers of atoms very quickly.  It's a useful tool for
+debugging LAMMPS input and output and making sure your simulation is
+doing what you think it should.  The animations on the Examples page
+of the "LAMMPS WWW site"_lws were created with xmovie.
+
+I've lost contact with Mike, so I hope he's comfortable with us
+distributing his great tool!

doc/src/USER/atc/man_consistent_fe_initialization.html

@@ -27,7 +27,7 @@
 syntax</a></h2>
 <p>fix_modify AtC consistent_fe_initialization &lt;on | off&gt;</p>
 <ul>
-<li>&lt;on|off&gt; = switch to activiate/deactiviate the initial setting of FE intrinsic field to match the projected MD field </li>
+<li>&lt;on|off&gt; = switch to activiate/deactiviate the intial setting of FE intrinsic field to match the projected MD field </li>
 </ul>
 <h2><a class="anchor" id="examples">
 examples</a></h2>

doc/src/accelerate_gpu.txt

@@ -54,7 +54,7 @@ specify the # of GPUs per node
 use GPU styles in your input script :ul
 
 The latter two steps can be done using the "-pk gpu" and "-sf gpu"
-"command-line switches"_Section_start.html#start_6 respectively.  Or
+"command-line switches"_Section_start.html#start_7 respectively.  Or
 the effect of the "-pk" or "-sf" switches can be duplicated by adding
 the "package gpu"_package.html or "suffix gpu"_suffix.html commands
 respectively to your input script.
@@ -62,7 +62,7 @@ respectively to your input script.
 [Required hardware/software:]
 
 To use this package, you currently need to have an NVIDIA GPU and
-install the NVIDIA CUDA software on your system:
+install the NVIDIA Cuda software on your system:
 
 Check if you have an NVIDIA GPU: cat /proc/driver/nvidia/gpus/0/information
 Go to http://www.nvidia.com/object/cuda_get.html
@@ -74,8 +74,13 @@ Run lammps/lib/gpu/nvc_get_devices (after building the GPU library, see below) t
 This requires two steps (a,b): build the GPU library, then build
 LAMMPS with the GPU package.
 
-You can do both these steps in one line as described in
-"Section 4"_Section_packages.html of the manual.
+You can do both these steps in one line, using the src/Make.py script,
+described in "Section 2.4"_Section_start.html#start_4 of the manual.
+Type "Make.py -h" for help.  If run from the src directory, this
+command will create src/lmp_gpu using src/MAKE/Makefile.mpi as the
+starting Makefile.machine:
+
+Make.py -p gpu -gpu mode=single arch=31 -o gpu -a lib-gpu file mpi :pre
 
 Or you can follow these two (a,b) steps:
 
@@ -85,7 +90,7 @@ The GPU library is in lammps/lib/gpu.  Select a Makefile.machine (in
 lib/gpu) appropriate for your system.  You should pay special
 attention to 3 settings in this makefile.
 
-CUDA_HOME = needs to be where NVIDIA CUDA software is installed on your system
+CUDA_HOME = needs to be where NVIDIA Cuda software is installed on your system
 CUDA_ARCH = needs to be appropriate to your GPUs
 CUDA_PREC = precision (double, mixed, single) you desire :ul
 
@@ -146,9 +151,9 @@ automatically if you create more MPI tasks/node than there are
 GPUs/mode.  E.g. with 8 MPI tasks/node and 2 GPUs, each GPU will be
 shared by 4 MPI tasks.
 
-Use the "-sf gpu" "command-line switch"_Section_start.html#start_6,
+Use the "-sf gpu" "command-line switch"_Section_start.html#start_7,
 which will automatically append "gpu" to styles that support it.  Use
-the "-pk gpu Ng" "command-line switch"_Section_start.html#start_6 to
+the "-pk gpu Ng" "command-line switch"_Section_start.html#start_7 to
 set Ng = # of GPUs/node to use.
 
 lmp_machine -sf gpu -pk gpu 1 -in in.script                         # 1 MPI task uses 1 GPU
@@ -183,7 +188,7 @@ pair_style lj/cut/gpu 2.5 :pre
 
 You must also use the "package gpu"_package.html command to enable the
 GPU package, unless the "-sf gpu" or "-pk gpu" "command-line
-switches"_Section_start.html#start_6 were used.  It specifies the
+switches"_Section_start.html#start_7 were used.  It specifies the
 number of GPUs/node to use, as well as other options.
 
 [Speed-ups to expect:]

doc/src/accelerate_intel.txt

@@ -20,7 +20,7 @@ coprocessors via offloading neighbor list and non-bonded force
 calculations to the Phi.  The same C++ code is used in both cases.
 When offloading to a coprocessor from a CPU, the same routine is run
 twice, once on the CPU and once with an offload flag. This allows
-LAMMPS to run on the CPU cores and coprocessor cores simultaneously.
+LAMMPS to run on the CPU cores and coprocessor cores simulataneously.
 
 [Currently Available USER-INTEL Styles:]
 
@@ -29,11 +29,9 @@ Bond Styles: fene, harmonic :l
 Dihedral Styles: charmm, harmonic, opls :l
 Fixes: nve, npt, nvt, nvt/sllod :l
 Improper Styles: cvff, harmonic :l
-Pair Styles: airebo, airebo/morse, buck/coul/cut, buck/coul/long, 
-buck, eam, eam/alloy, eam/fs, gayberne, lj/charmm/coul/charmm, 
-lj/charmm/coul/long, lj/cut, lj/cut/coul/long, lj/long/coul/long, rebo,
-sw, tersoff :l
-K-Space Styles: pppm, pppm/disp :l
+Pair Styles: buck/coul/cut, buck/coul/long, buck, eam, gayberne,
+charmm/coul/long, lj/cut, lj/cut/coul/long, sw, tersoff :l
+K-Space Styles: pppm :l
 :ule
 
 [Speed-ups to expect:]
@@ -44,90 +42,61 @@ precision mode. Performance improvements are shown compared to
 LAMMPS {without using other acceleration packages} as these are
 under active development (and subject to performance changes). The
 measurements were performed using the input files available in
-the src/USER-INTEL/TEST directory with the provided run script.
-These are scalable in size; the results given are with 512K
-particles (524K for Liquid Crystal). Most of the simulations are
-standard LAMMPS benchmarks (indicated by the filename extension in
-parenthesis) with modifications to the run length and to add a
-warmup run (for use with offload benchmarks).
+the src/USER-INTEL/TEST directory. These are scalable in size; the
+results given are with 512K particles (524K for Liquid Crystal).
+Most of the simulations are standard LAMMPS benchmarks (indicated
+by the filename extension in parenthesis) with modifications to the
+run length and to add a warmup run (for use with offload
+benchmarks).
 
 :c,image(JPG/user_intel.png)
 
 Results are speedups obtained on Intel Xeon E5-2697v4 processors
 (code-named Broadwell) and Intel Xeon Phi 7250 processors
-(code-named Knights Landing) with "June 2017" LAMMPS built with
-Intel Parallel Studio 2017 update 2. Results are with 1 MPI task
+(code-named Knights Landing) with "18 Jun 2016" LAMMPS built with
+Intel Parallel Studio 2016 update 3. Results are with 1 MPI task
 per physical core. See {src/USER-INTEL/TEST/README} for the raw
 simulation rates and instructions to reproduce.
 
 :line
 
-[Accuracy and order of operations:]
-
-In most molecular dynamics software, parallelization parameters
-(# of MPI, OpenMP, and vectorization) can change the results due
-to changing the order of operations with finite-precision
-calculations. The USER-INTEL package is deterministic. This means
-that the results should be reproducible from run to run with the
-{same} parallel configurations and when using determinstic
-libraries or library settings (MPI, OpenMP, FFT). However, there
-are differences in the USER-INTEL package that can change the
-order of operations compared to LAMMPS without acceleration:
-
-Neighbor lists can be created in a different order :ulb,l
-Bins used for sorting atoms can be oriented differently :l
-The default stencil order for PPPM is 7. By default, LAMMPS will
-calculate other PPPM parameters to fit the desired acuracy with
-this order :l
-The {newton} setting applies to all atoms, not just atoms shared
-between MPI tasks :l
-Vectorization can change the order for adding pairwise forces :l
-:ule
-
-The precision mode (described below) used with the USER-INTEL
-package can change the {accuracy} of the calculations. For the
-default {mixed} precision option, calculations between pairs or
-triplets of atoms are performed in single precision, intended to
-be within the inherent error of MD simulations. All accumulation
-is performed in double precision to prevent the error from growing
-with the number of atoms in the simulation. {Single} precision
-mode should not be used without appropriate validation.
-
-:line
-
 [Quick Start for Experienced Users:]
 
 LAMMPS should be built with the USER-INTEL package installed.
 Simulations should be run with 1 MPI task per physical {core},
 not {hardware thread}.
 
+For Intel Xeon CPUs:
+
 Edit src/MAKE/OPTIONS/Makefile.intel_cpu_intelmpi as necessary. :ulb,l
-Set the environment variable KMP_BLOCKTIME=0 :l
-"-pk intel 0 omp $t -sf intel" added to LAMMPS command-line :l
-$t should be 2 for Intel Xeon CPUs and 2 or 4 for Intel Xeon Phi :l
-For some of the simple 2-body potentials without long-range
-electrostatics, performance and scalability can be better with
-the "newton off" setting added to the input script :l
-For simulations on higher node counts, add "processors * * * grid 
-numa" to the beginning of the input script for better scalability :l
-If using {kspace_style pppm} in the input script, add
-"kspace_modify diff ad" for better performance :l
+If using {kspace_style pppm} in the input script, add "neigh_modify binsize 3" and "kspace_modify diff ad" to the input script for better
+performance. :l
+"-pk intel 0 omp 2 -sf intel" added to LAMMPS command-line :l
 :ule
 
-For Intel Xeon Phi CPUs:
+For Intel Xeon Phi CPUs for simulations without {kspace_style
+pppm} in the input script :
 
-Runs should be performed using MCDRAM. :ulb,l
+Edit src/MAKE/OPTIONS/Makefile.knl as necessary. :ulb,l
+Runs should be performed using MCDRAM. :l
+"-pk intel 0 omp 2 -sf intel" {or} "-pk intel 0 omp 4 -sf intel"
+should be added to the LAMMPS command-line. Choice for best
+performance will depend on the simulation. :l
 :ule
 
-For simulations using {kspace_style pppm} on Intel CPUs
-supporting AVX-512:
+For Intel Xeon Phi CPUs for simulations with {kspace_style
+pppm} in the input script:
 
-Add "kspace_modify diff ad" to the input script :ulb,l
-The command-line option should be changed to
-"-pk intel 0 omp $r lrt yes -sf intel" where $r is the number of
-threads minus 1. :l
-Do not use thread affinity (set KMP_AFFINITY=none) :l
-The "newton off" setting may provide better scalability :l
+Edit src/MAKE/OPTIONS/Makefile.knl as necessary. :ulb,l
+Runs should be performed using MCDRAM. :l
+Add "neigh_modify binsize 3" to the input script for better
+performance. :l
+Add "kspace_modify diff ad" to the input script for better
+performance. :l
+export KMP_AFFINITY=none :l
+"-pk intel 0 omp 3 lrt yes -sf intel" or "-pk intel 0 omp 1 lrt yes
+-sf intel" added to LAMMPS command-line. Choice for best performance
+will depend on the simulation. :l
 :ule
 
 For Intel Xeon Phi coprocessors (Offload):
@@ -146,7 +115,7 @@ coprocessor and an Intel compiler are required. For this, the
 recommended version of the Intel compiler is 14.0.1.106 or
 versions 15.0.2.044 and higher.
 
-Although any compiler can be used with the USER-INTEL package,
+Although any compiler can be used with the USER-INTEL pacakge,
 currently, vectorization directives are disabled by default when
 not using Intel compilers due to lack of standard support and
 observations of decreased performance. The OpenMP standard now
@@ -199,10 +168,6 @@ cat /proc/cpuinfo :pre
 
 [Building LAMMPS with the USER-INTEL package:]
 
-NOTE: See the src/USER-INTEL/README file for additional flags that
-might be needed for best performance on Intel server processors
-code-named "Skylake".
-
 The USER-INTEL package must be installed into the source directory:
 
 make yes-user-intel :pre
@@ -227,9 +192,11 @@ source /opt/intel/parallel_studio_xe_2016.3.067/psxevars.sh
 # or psxevars.csh for C-shell
 make intel_cpu_intelmpi :pre
 
-Alternatively this can be done as a single command with
-suitable make command invocations. This is discussed in "Section
-4"_Section_packages.html of the manual.
+Alternatively, the build can be accomplished with the src/Make.py
+script, described in "Section 2.4"_Section_start.html#start_4 of the
+manual. Type "Make.py -h" for help. For an example:
+
+Make.py -v -p intel omp -intel cpu -a file intel_cpu_intelmpi :pre
 
 Note that if you build with support for a Phi coprocessor, the same
 binary can be used on nodes with or without coprocessors installed.
@@ -244,7 +211,8 @@ highly recommended for CCFLAGS and LINKFLAGS. LIB should include
 is required for CCFLAGS and "-qoffload" is required for LINKFLAGS.
 Other recommended CCFLAG options for best performance are
 "-O2 -fno-alias -ansi-alias -qoverride-limits fp-model fast=2
--no-prec-div".
+-no-prec-div". The Make.py command will add all of these
+automatically.
 
 NOTE: The vectorization and math capabilities can differ depending on
 the CPU. For Intel compilers, the "-x" flag specifies the type of
@@ -300,7 +268,7 @@ Hyper-Threading technology disabled.
 
 To enable USER-INTEL optimizations for all available styles used in
 the input script, the "-sf intel"
-"command-line switch"_Section_start.html#start_6 can be used without
+"command-line switch"_Section_start.html#start_7 can be used without
 any requirement for editing the input script. This switch will
 automatically append "intel" to styles that support it. It also
 invokes a default command: "package intel 1"_package.html. This
@@ -313,7 +281,7 @@ support, that 1 coprocessor per node will be used with automatic
 balancing of work between the CPU and the coprocessor.
 
 You can specify different options for the USER-INTEL package by using
-the "-pk intel Nphi" "command-line switch"_Section_start.html#start_6
+the "-pk intel Nphi" "command-line switch"_Section_start.html#start_7
 with keyword/value pairs as specified in the documentation. Here,
 Nphi = # of Xeon Phi coprocessors/node (ignored without offload
 support). Common options to the USER-INTEL package include {omp} to
@@ -353,8 +321,8 @@ follow in the input script.
 
 NOTE: The USER-INTEL package will perform better with modifications
 to the input script when "PPPM"_kspace_style.html is used:
-"kspace_modify diff ad"_kspace_modify.html should be added to the
-input script.
+"kspace_modify diff ad"_kspace_modify.html and "neigh_modify binsize
+3"_neigh_modify.html should be added to the input script.
 
 Long-Range Thread (LRT) mode is an option to the "package
 intel"_package.html command that can improve performance when using
@@ -373,10 +341,6 @@ would normally perform best with "-pk intel 0 omp 4", instead use
 environment variable "KMP_AFFINITY=none". LRT mode is not supported
 when using offload.
 
-NOTE: Changing the "newton"_newton.html setting to off can improve
-performance and/or scalability for simple 2-body potentials such as
-lj/cut or when using LRT mode on processors supporting AVX-512.
-
 Not all styles are supported in the USER-INTEL package. You can mix
 the USER-INTEL package with styles from the "OPT"_accelerate_opt.html
 package or the "USER-OMP package"_accelerate_omp.html. Of course,
@@ -386,17 +350,13 @@ can performed automatically by using "-sf hybrid intel opt" or
 and "omp" suffixes can be appended manually in the input script. For
 the latter, the "package omp"_package.html command must be in the
 input script or the "-pk omp Nt" "command-line
-switch"_Section_start.html#start_6 must be used where Nt is the
+switch"_Section_start.html#start_7 must be used where Nt is the
 number of OpenMP threads. The number of OpenMP threads should not be
 set differently for the different packages. Note that the "suffix
 hybrid intel omp"_suffix.html command can also be used within the
 input script to automatically append the "omp" suffix to styles when
 USER-INTEL styles are not available.
 
-NOTE: For simulations on higher node counts, add "processors * * * 
-grid numa"_processors.html" to the beginning of the input script for
-better scalability.
-
 When running on many nodes, performance might be better when using
 fewer OpenMP threads and more MPI tasks. This will depend on the
 simulation and the machine. Using the "verlet/split"_run_style.html
@@ -468,7 +428,7 @@ to the card.  This allows for overlap of MPI communication of forces
 with computation on the coprocessor when the "newton"_newton.html
 setting is "on".  The default is dependent on the style being used,
 however, better performance may be achieved by setting this option
-explicitly.
+explictly.
 
 When using offload with CPU Hyper-Threading disabled, it may help
 performance to use fewer MPI tasks and OpenMP threads than available
@@ -485,7 +445,7 @@ sorting"_atom_modify.html is changed to 1 so that the per-atom data is
 effectively sorted at every rebuild of the neighbor lists. All the
 available coprocessor threads on each Phi will be divided among MPI
 tasks, unless the {tptask} option of the "-pk intel" "command-line
-switch"_Section_start.html#start_6 is used to limit the coprocessor
+switch"_Section_start.html#start_7 is used to limit the coprocessor
 threads per MPI task.
 
 [Restrictions:]
@@ -504,9 +464,9 @@ supported.
 
 [References:]
 
-Brown, W.M., Carrillo, J.-M.Y., Mishra, B., Gavhane, N., Thakker, F.M., De Kraker, A.R., Yamada, M., Ang, J.A., Plimpton, S.J., "Optimizing Classical Molecular Dynamics in LAMMPS," in Intel Xeon Phi Processor High Performance Programming: Knights Landing Edition, J. Jeffers, J. Reinders, A. Sodani, Eds. Morgan Kaufmann. :ulb,l
+Brown, W.M., Carrillo, J.-M.Y., Mishra, B., Gavhane, N., Thakker, F.M., De Kraker, A.R., Yamada, M., Ang, J.A., Plimpton, S.J., “Optimizing Classical Molecular Dynamics in LAMMPS,” in Intel Xeon Phi Processor High Performance Programming: Knights Landing Edition, J. Jeffers, J. Reinders, A. Sodani, Eds. Morgan Kaufmann. :ulb,l
 
-Brown, W. M., Semin, A., Hebenstreit, M., Khvostov, S., Raman, K., Plimpton, S.J. "Increasing Molecular Dynamics Simulation Rates with an 8-Fold Increase in Electrical Power Efficiency."_http://dl.acm.org/citation.cfm?id=3014915 2016 High Performance Computing, Networking, Storage and Analysis, SC16: International Conference (pp. 82-95). :l
+Brown, W. M., Semin, A., Hebenstreit, M., Khvostov, S., Raman, K., Plimpton, S.J. Increasing Molecular Dynamics Simulation Rates with an 8-Fold Increase in Electrical Power Efficiency. 2016 International Conference for High Performance Computing. In press. :l
 
 Brown, W.M., Carrillo, J.-M.Y., Gavhane, N., Thakkar, F.M., Plimpton, S.J. Optimizing Legacy Molecular Dynamics Software with Directive-Based Offload. Computer Physics Communications. 2015. 195: p. 95-101. :l
 :ule

doc/src/accelerate_kokkos.txt

@@ -60,7 +60,8 @@ More details follow.
 use a C++11 compatible compiler
 make yes-kokkos
 make mpi KOKKOS_DEVICES=OpenMP                 # build with the KOKKOS package
-make kokkos_omp                                # or Makefile.kokkos_omp already has variable set :pre
+make kokkos_omp                                # or Makefile.kokkos_omp already has variable set
+Make.py -v -p kokkos -kokkos omp -o mpi -a file mpi   # or one-line build via Make.py :pre
 
 mpirun -np 16 lmp_mpi -k on -sf kk -in in.lj              # 1 node, 16 MPI tasks/node, no threads
 mpirun -np 2 -ppn 1 lmp_mpi -k on t 16 -sf kk -in in.lj   # 2 nodes, 1 MPI task/node, 16 threads/task
@@ -81,7 +82,8 @@ use a C++11 compatible compiler
 KOKKOS_DEVICES = Cuda, OpenMP
 KOKKOS_ARCH = Kepler35
 make yes-kokkos
-make machine :pre
+make machine
+Make.py -p kokkos -kokkos cuda arch=31 -o kokkos_cuda -a file kokkos_cuda :pre
 
 mpirun -np 1 lmp_cuda -k on t 6 -sf kk -in in.lj          # one MPI task, 6 threads on CPU
 mpirun -np 4 -ppn 1 lmp_cuda -k on t 6 -sf kk -in in.lj   # ditto on 4 nodes :pre
@@ -96,7 +98,8 @@ use a C++11 compatible compiler
 KOKKOS_DEVICES = OpenMP
 KOKKOS_ARCH = KNC
 make yes-kokkos
-make machine :pre
+make machine
+Make.py -p kokkos -kokkos phi -o kokkos_phi -a file mpi :pre
 
 host=MIC, Intel Phi with 61 cores (240 threads/phi via 4x hardware threading):
 mpirun -np 1 lmp_g++ -k on t 240 -sf kk -in in.lj           # 1 MPI task on 1 Phi, 1*240 = 240
@@ -113,7 +116,7 @@ To build with Kokkos support for CPUs, your compiler must support the
 OpenMP interface.  You should have one or more multi-core CPUs so that
 multiple threads can be launched by each MPI task running on a CPU.
 
-To build with Kokkos support for NVIDIA GPUs, NVIDIA CUDA software
+To build with Kokkos support for NVIDIA GPUs, NVIDIA Cuda software
 version 7.5 or later must be installed on your system.  See the
 discussion for the "GPU"_accelerate_gpu.html package for details of
 how to check and do this.
@@ -132,16 +135,16 @@ mode like the USER-INTEL package supports.
 You must choose at build time whether to build for CPUs (OpenMP),
 GPUs, or Phi.
 
-You can do any of these in one line, using the suitable make command
-line flags as described in "Section 4"_Section_packages.html of the
-manual. If run from the src directory, these
+You can do any of these in one line, using the src/Make.py script,
+described in "Section 2.4"_Section_start.html#start_4 of the manual.
+Type "Make.py -h" for help.  If run from the src directory, these
 commands will create src/lmp_kokkos_omp, lmp_kokkos_cuda, and
 lmp_kokkos_phi.  Note that the OMP and PHI options use
 src/MAKE/Makefile.mpi as the starting Makefile.machine.  The CUDA
 option uses src/MAKE/OPTIONS/Makefile.kokkos_cuda.
 
 The latter two steps can be done using the "-k on", "-pk kokkos" and
-"-sf kk" "command-line switches"_Section_start.html#start_6
+"-sf kk" "command-line switches"_Section_start.html#start_7
 respectively.  Or the effect of the "-pk" or "-sf" switches can be
 duplicated by adding the "package kokkos"_package.html or "suffix
 kk"_suffix.html commands respectively to your input script.
@@ -214,7 +217,7 @@ best performance its CCFLAGS setting should use -O3 and have a
 KOKKOS_ARCH setting that matches the compute capability of your NVIDIA
 hardware and software installation, e.g. KOKKOS_ARCH=Kepler30.  Note
 the minimal required compute capability is 2.0, but this will give
-significantly reduced performance compared to Kepler generation GPUs
+signicantly reduced performance compared to Kepler generation GPUs
 with compute capability 3.x.  For the LINK setting, "nvcc" should not
 be used; instead use g++ or another compiler suitable for linking C++
 applications.  Often you will want to use your MPI compiler wrapper
@@ -231,7 +234,7 @@ provides alternative methods via environment variables for binding
 threads to hardware cores.  More info on binding threads to cores is
 given in "Section 5.3"_Section_accelerate.html#acc_3.
 
-KOKKOS_ARCH=KNC enables compiler switches needed when compiling for an
+KOKKOS_ARCH=KNC enables compiler switches needed when compling for an
 Intel Phi processor.
 
 KOKKOS_USE_TPLS=librt enables use of a more accurate timer mechanism
@@ -269,7 +272,7 @@ coprocessor support you need to insure there are one or more MPI tasks
 per coprocessor, and choose the number of coprocessor threads to use
 per MPI task (via the "-k" command-line switch discussed below).  The
 product of MPI tasks * coprocessor threads/task should not exceed the
-maximum number of threads the coprocessor is designed to run,
+maximum number of threads the coproprocessor is designed to run,
 otherwise performance will suffer.  This value is 240 for current
 generation Xeon Phi(TM) chips, which is 60 physical cores * 4
 threads/core.  Note that with the KOKKOS package you do not need to
@@ -277,10 +280,10 @@ specify how many Phi coprocessors there are per node; each
 coprocessors is simply treated as running some number of MPI tasks.
 
 You must use the "-k on" "command-line
-switch"_Section_start.html#start_6 to enable the KOKKOS package.  It
+switch"_Section_start.html#start_7 to enable the KOKKOS package.  It
 takes additional arguments for hardware settings appropriate to your
 system.  Those arguments are "documented
-here"_Section_start.html#start_6.  The two most commonly used
+here"_Section_start.html#start_7.  The two most commonly used
 options are:
 
 -k on t Nt g Ng :pre
@@ -301,12 +304,12 @@ The "-k on" switch also issues a "package kokkos" command (with no
 additional arguments) which sets various KOKKOS options to default
 values, as discussed on the "package"_package.html command doc page.
 
-Use the "-sf kk" "command-line switch"_Section_start.html#start_6,
+Use the "-sf kk" "command-line switch"_Section_start.html#start_7,
 which will automatically append "kk" to styles that support it.  Use
-the "-pk kokkos" "command-line switch"_Section_start.html#start_6 if
+the "-pk kokkos" "command-line switch"_Section_start.html#start_7 if
 you wish to change any of the default "package kokkos"_package.html
 optionns set by the "-k on" "command-line
-switch"_Section_start.html#start_6.
+switch"_Section_start.html#start_7.
 
 
 
@@ -320,7 +323,7 @@ However, when running in MPI-only mode with 1 thread per MPI task, it
 will typically be faster to use "half" neighbor lists and set the
 Newton flag to "on", just as is the case for non-accelerated pair
 styles.  You can do this with the "-pk" "command-line
-switch"_Section_start.html#start_6.
+switch"_Section_start.html#start_7.
 
 [Or run with the KOKKOS package by editing an input script:]
 
@@ -329,8 +332,8 @@ appropriate thread and GPU values for host=OMP or host=MIC or
 device=CUDA are the same.
 
 You must still use the "-k on" "command-line
-switch"_Section_start.html#start_6 to enable the KOKKOS package, and
-specify its additional arguments for hardware options appropriate to
+switch"_Section_start.html#start_7 to enable the KOKKOS package, and
+specify its additional arguments for hardware options appopriate to
 your system, as documented above.
 
 Use the "suffix kk"_suffix.html command, or you can explicitly add a
@@ -340,7 +343,7 @@ pair_style lj/cut/kk 2.5 :pre
 
 You only need to use the "package kokkos"_package.html command if you
 wish to change any of its option defaults, as set by the "-k on"
-"command-line switch"_Section_start.html#start_6.
+"command-line switch"_Section_start.html#start_7.
 
 [Speed-ups to expect:]
 
@@ -386,7 +389,7 @@ If N is the number of physical cores/node, then the number of MPI
 tasks/node * number of threads/task should not exceed N, and should
 typically equal N.  Note that the default threads/task is 1, as set by
 the "t" keyword of the "-k" "command-line
-switch"_Section_start.html#start_6.  If you do not change this, no
+switch"_Section_start.html#start_7.  If you do not change this, no
 additional parallelism (beyond MPI) will be invoked on the host
 CPU(s).
 
@@ -412,21 +415,21 @@ For binding threads with the KOKKOS OMP option, use thread affinity
 environment variables to force binding.  With OpenMP 3.1 (gcc 4.7 or
 later, intel 12 or later) setting the environment variable
 OMP_PROC_BIND=true should be sufficient.  For binding threads with the
-KOKKOS pthreads option, compile LAMMPS the KOKKOS HWLOC=yes option
-(see "this section"_Section_packages.html#KOKKOS of the manual for
-details).
+KOKKOS pthreads option, compile LAMMPS the KOKKOS HWLOC=yes option, as
+discussed in "Section 2.3.4"_Sections_start.html#start_3_4 of the
+manual.
 
 [Running on GPUs:]
 
 Insure the -arch setting in the machine makefile you are using,
-e.g. src/MAKE/Makefile.cuda, is correct for your GPU hardware/software.
-(see "this section"_Section_packages.html#KOKKOS of the manual for
+e.g. src/MAKE/Makefile.cuda, is correct for your GPU hardware/software
+(see "this section"_Section_start.html#start_3_4 of the manual for
 details).
 
 The -np setting of the mpirun command should set the number of MPI
 tasks/node to be equal to the # of physical GPUs on the node.
 
-Use the "-k" "command-line switch"_Section_commands.html#start_6 to
+Use the "-k" "command-line switch"_Section_commands.html#start_7 to
 specify the number of GPUs per node, and the number of threads per MPI
 task.  As above for multi-core CPUs (and no GPU), if N is the number
 of physical cores/node, then the number of MPI tasks/node * number of

doc/src/accelerate_omp.txt

@@ -23,7 +23,8 @@ one or more 16-core nodes.  More details follow.
 use -fopenmp with CCFLAGS and LINKFLAGS in Makefile.machine
 make yes-user-omp
 make mpi                                   # build with USER-OMP package, if settings added to Makefile.mpi
-make omp                                   # or Makefile.omp already has settings :pre
+make omp                                   # or Makefile.omp already has settings
+Make.py -v -p omp -o mpi -a file mpi       # or one-line build via Make.py :pre
 
 lmp_mpi -sf omp -pk omp 16 < in.script                         # 1 MPI task, 16 threads
 mpirun -np 4 lmp_mpi -sf omp -pk omp 4 -in in.script           # 4 MPI tasks, 4 threads/task
@@ -39,11 +40,14 @@ each MPI task running on a CPU.
 
 The lines above illustrate how to include/build with the USER-OMP
 package in two steps, using the "make" command.  Or how to do it with
-one command as described in "Section 4"_Section_packages.html of the manual.
+one command via the src/Make.py script, described in "Section
+2.4"_Section_start.html#start_4 of the manual.  Type "Make.py -h" for
+help.
 
 Note that the CCFLAGS and LINKFLAGS settings in Makefile.machine must
 include "-fopenmp".  Likewise, if you use an Intel compiler, the
-CCFLAGS setting must include "-restrict".
+CCFLAGS setting must include "-restrict".  The Make.py command will
+add these automatically.
 
 [Run with the USER-OMP package from the command line:]
 
@@ -58,14 +62,14 @@ threads/task should not exceed the physical number of cores (on a
 node), otherwise performance will suffer.
 
 As in the lines above, use the "-sf omp" "command-line
-switch"_Section_start.html#start_6, which will automatically append
+switch"_Section_start.html#start_7, which will automatically append
 "omp" to styles that support it.  The "-sf omp" switch also issues a
 default "package omp 0"_package.html command, which will set the
 number of threads per MPI task via the OMP_NUM_THREADS environment
 variable.
 
 You can also use the "-pk omp Nt" "command-line
-switch"_Section_start.html#start_6, to explicitly set Nt = # of OpenMP
+switch"_Section_start.html#start_7, to explicitly set Nt = # of OpenMP
 threads per MPI task to use, as well as additional options.  Its
 syntax is the same as the "package omp"_package.html command whose doc
 page gives details, including the default values used if it is not

doc/src/accelerate_opt.txt

@@ -21,7 +21,8 @@ Here is a quick overview of how to use the OPT package.  More details
 follow.
 
 make yes-opt
-make mpi                               # build with the OPT package :pre
+make mpi                               # build with the OPT package
+Make.py -v -p opt -o mpi -a file mpi   # or one-line build via Make.py :pre
 
 lmp_mpi -sf opt -in in.script                # run in serial
 mpirun -np 4 lmp_mpi -sf opt -in in.script   # run in parallel :pre
@@ -34,15 +35,18 @@ None.
 
 The lines above illustrate how to build LAMMPS with the OPT package in
 two steps, using the "make" command.  Or how to do it with one command
-as described in "Section 4"_Section_packages.html of the manual.
+via the src/Make.py script, described in "Section
+2.4"_Section_start.html#start_4 of the manual.  Type "Make.py -h" for
+help.
 
 Note that if you use an Intel compiler to build with the OPT package,
 the CCFLAGS setting in your Makefile.machine must include "-restrict".
+The Make.py command will add this automatically.
 
 [Run with the OPT package from the command line:]
 
 As in the lines above, use the "-sf opt" "command-line
-switch"_Section_start.html#start_6, which will automatically append
+switch"_Section_start.html#start_7, which will automatically append
 "opt" to styles that support it.
 
 [Or run with the OPT package by editing an input script:]

doc/src/angle_charmm.txt

@@ -63,7 +63,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_class2.txt

@@ -8,7 +8,6 @@
 
 angle_style class2 command :h3
 angle_style class2/omp command :h3
-angle_style class2/kk command :h3
 
 [Syntax:]
 
@@ -94,7 +93,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_cosine.txt

@@ -50,7 +50,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_cosine_delta.txt

@@ -55,7 +55,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_cosine_periodic.txt

@@ -63,7 +63,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_cosine_shift.txt

@@ -53,7 +53,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_cosine_shift_exp.txt

@@ -65,7 +65,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_cosine_squared.txt

@@ -55,7 +55,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_dipole.txt

@@ -41,7 +41,7 @@ angle.
 
 The torque on the dipole can be obtained by differentiating the
 potential using the 'chain rule' as in appendix C.3 of
-"(Allen)"_#Allen1:
+"(Allen)"_#Allen:
 
 :c,image(Eqs/angle_dipole_torque.jpg)
 
@@ -121,6 +121,6 @@ This angle style should not be used with SHAKE.
 [(Orsi)] Orsi & Essex, The ELBA force field for coarse-grain modeling of
 lipid membranes, PloS ONE 6(12): e28637, 2011.
 
-:link(Allen1)
+:link(Allen)
 [(Allen)] Allen & Tildesley, Computer Simulation of Liquids,
 Clarendon Press, Oxford, 1987.

doc/src/angle_fourier.txt

@@ -51,7 +51,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_fourier_simple.txt

@@ -50,7 +50,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_harmonic.txt

@@ -57,7 +57,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_hybrid.txt

@@ -81,7 +81,7 @@ LAMMPS"_Section_start.html#start_3 section for more info on packages.
 
 Unlike other angle styles, the hybrid angle style does not store angle
 coefficient info for individual sub-styles in a "binary restart
-files"_restart.html.  Thus when restarting a simulation from a restart
+files"_restart.html.  Thus when retarting a simulation from a restart
 file, you need to re-specify angle_coeff commands.
 
 [Related commands:]

doc/src/angle_quartic.txt

@@ -57,7 +57,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/angle_sdk.txt

@@ -46,7 +46,7 @@ from the pair_style.
 [Restrictions:]
 
 This angle style can only be used if LAMMPS was built with the
-USER-CGSDK package.  See the "Making
+USER-CG-CMM package.  See the "Making
 LAMMPS"_Section_start.html#start_3 section for more info on packages.
 
 [Related commands:]

doc/src/angle_table.txt

@@ -136,7 +136,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/atom_modify.txt

@@ -103,7 +103,7 @@ turns off the {first} option.
 
 It is OK to use the {first} keyword with a group that has not yet been
 defined, e.g. to use the atom_modify first command at the beginning of
-your input script.  LAMMPS does not use the group until a simulation
+your input script.  LAMMPS does not use the group until a simullation
 is run.
 
 The {sort} keyword turns on a spatial sorting or reordering of atoms
@@ -116,7 +116,7 @@ various other factors.  As a general rule, sorting is typically more
 effective at speeding up simulations of liquids as opposed to solids.
 In tests we have done, the speed-up can range from zero to 3-4x.
 
-Reordering is performed every {Nfreq} timesteps during a dynamics run
+Reordering is peformed every {Nfreq} timesteps during a dynamics run
 or iterations during a minimization.  More precisely, reordering
 occurs at the first reneighboring that occurs after the target
 timestep.  The reordering is performed locally by each processor,
@@ -130,7 +130,7 @@ the processor's 1d list of atoms.
 The goal of this procedure is for atoms to put atoms close to each
 other in the processor's one-dimensional list of atoms that are also
 near to each other spatially.  This can improve cache performance when
-pairwise interactions and neighbor lists are computed.  Note that if
+pairwise intereractions and neighbor lists are computed.  Note that if
 bins are too small, there will be few atoms/bin.  Likewise if bins are
 too large, there will be many atoms/bin.  In both cases, the goal of
 cache locality will be undermined.
@@ -138,7 +138,7 @@ cache locality will be undermined.
 NOTE: Running a simulation with sorting on versus off should not
 change the simulation results in a statistical sense.  However, a
 different ordering will induce round-off differences, which will lead
-to diverging trajectories over time when comparing two simulations.
+to diverging trajectories over time when comparing two simluations.
 Various commands, particularly those which use random numbers
 (e.g. "velocity create"_velocity.html, and "fix
 langevin"_fix_langevin.html), may generate (statistically identical)

doc/src/atom_style.txt

@@ -110,17 +110,12 @@ basis.
 For the {sphere} style, the particles are spheres and each stores a
 per-particle diameter and mass.  If the diameter > 0.0, the particle
 is a finite-size sphere.  If the diameter = 0.0, it is a point
-particle.  Note that by use of the {disc} keyword with the "fix
-nve/sphere"_fix_nve_sphere.html, "fix nvt/sphere"_fix_nvt_sphere.html,
-"fix nph/sphere"_fix_nph_sphere.html, "fix
-npt/sphere"_fix_npt_sphere.html commands, spheres can be effectively
-treated as 2d discs for a 2d simulation if desired.  See also the "set
-density/disc"_set.html command.
+particle.
 
 For the {ellipsoid} style, the particles are ellipsoids and each
 stores a flag which indicates whether it is a finite-size ellipsoid or
 a point particle.  If it is an ellipsoid, it also stores a shape
-vector with the 3 diameters of the ellipsoid and a quaternion 4-vector
+vector with the 3 diamters of the ellipsoid and a quaternion 4-vector
 with its orientation.
 
 For the {dipole} style, a point dipole is defined for each point
@@ -154,7 +149,7 @@ Hydrodynamics.  Both fluids and solids can be modeled.  Particles
 store the mass and volume of an integration point, a kernel diameter
 used for calculating the field variables (e.g. stress and deformation)
 and a contact radius for calculating repulsive forces which prevent
-individual physical bodies from penetrating each other.
+individual physical bodies from penetretating each other.
 
 The {wavepacket} style is similar to {electron}, but the electrons may
 consist of several Gaussian wave packets, summed up with coefficients
@@ -170,7 +165,7 @@ For the {tri} style, the particles are planar triangles and each
 stores a per-particle mass and size and orientation (i.e. the corner
 points of the triangle).
 
-The {template} style allows molecular topology (bonds,angles,etc) to be
+The {template} style allows molecular topolgy (bonds,angles,etc) to be
 defined via a molecule template using the "molecule"_molecule.html
 command.  The template stores one or more molecules with a single copy
 of the topology info (bonds,angles,etc) of each.  Individual atoms
@@ -200,7 +195,7 @@ the {bstyle} argument.  Body particles can represent complex entities,
 such as surface meshes of discrete points, collections of
 sub-particles, deformable objects, etc.
 
-The "body"_body.html doc page describes the body styles LAMMPS
+The "body"_body.html doc page descibes the body styles LAMMPS
 currently supports, and provides more details as to the kind of body
 particles they represent.  For all styles, each body particle stores
 moments of inertia and a quaternion 4-vector, so that its orientation
@@ -285,7 +280,7 @@ The {dpd} style is part of the USER-DPD package for dissipative
 particle dynamics (DPD).
 
 The {meso} style is part of the USER-SPH package for smoothed particle
-hydrodynamics (SPH).  See "this PDF
+hydrodyanmics (SPH).  See "this PDF
 guide"_USER/sph/SPH_LAMMPS_userguide.pdf to using SPH in LAMMPS.
 
 The {wavepacket} style is part of the USER-AWPMD package for the

doc/src/balance.txt

@@ -12,7 +12,7 @@ balance command :h3
 
 balance thresh style args ... keyword args ... :pre
 
-thresh = imbalance threshold that must be exceeded to perform a re-balance :ulb,l
+thresh = imbalance threshhold that must be exceeded to perform a re-balance :ulb,l
 one style/arg pair can be used (or multiple for {x},{y},{z}) :l
 style = {x} or {y} or {z} or {shift} or {rcb} :l
   {x} args = {uniform} or Px-1 numbers between 0 and 1
@@ -30,7 +30,7 @@ style = {x} or {y} or {z} or {shift} or {rcb} :l
   {shift} args = dimstr Niter stopthresh
     dimstr = sequence of letters containing "x" or "y" or "z", each not more than once
     Niter = # of times to iterate within each dimension of dimstr sequence
-    stopthresh = stop balancing when this imbalance threshold is reached
+    stopthresh = stop balancing when this imbalance threshhold is reached
   {rcb} args = none :pre
 zero or more keyword/arg pairs may be appended :l
 keyword = {weight} or {out} :l
@@ -76,13 +76,13 @@ sub-domain sizes and shapes on-the-fly during a "run"_run.html.
 
 Load-balancing is typically most useful if the particles in the
 simulation box have a spatially-varying density distribution or when
-the computational cost varies significantly between different
+the computational cost varies signficantly between different
 particles.  E.g. a model of a vapor/liquid interface, or a solid with
 an irregular-shaped geometry containing void regions, or "hybrid pair
 style simulations"_pair_hybrid.html which combine pair styles with
 different computational cost.  In these cases, the LAMMPS default of
 dividing the simulation box volume into a regular-spaced grid of 3d
-bricks, with one equal-volume sub-domain per processor, may assign
+bricks, with one equal-volume sub-domain per procesor, may assign
 numbers of particles per processor in a way that the computational
 effort varies significantly.  This can lead to poor performance when
 the simulation is run in parallel.
@@ -91,7 +91,7 @@ The balancing can be performed with or without per-particle weighting.
 With no weighting, the balancing attempts to assign an equal number of
 particles to each processor.  With weighting, the balancing attempts
 to assign an equal aggregate computational weight to each processor,
-which typically induces a different number of atoms assigned to each
+which typically inducces a diffrent number of atoms assigned to each
 processor.  Details on the various weighting options and examples for
 how they can be used are "given below"_#weighted_balance.
 
@@ -222,7 +222,7 @@ listed in ascending order.  They represent the fractional position of
 the cutting place.  The left (or lower) edge of the box is 0.0, and
 the right (or upper) edge is 1.0.  Neither of these values is
 specified.  Only the interior Ps-1 positions are specified.  Thus is
-there are 2 processors in the x dimension, you specify a single value
+there are 2 procesors in the x dimension, you specify a single value
 such as 0.75, which would make the left processor's sub-domain 3x
 larger than the right processor's sub-domain.
 
@@ -266,7 +266,7 @@ assigned, particles are migrated to their new owning processor, and
 the balance procedure ends.
 
 NOTE: At each rebalance operation, the bisectioning for each cutting
-plane (line in 2d) typically starts with low and high bounds separated
+plane (line in 2d) typcially starts with low and high bounds separated
 by the extent of a processor's sub-domain in one dimension.  The size
 of this bracketing region shrinks by 1/2 every iteration.  Thus if
 {Niter} is specified as 10, the cutting plane will typically be
@@ -286,32 +286,24 @@ above.  It performs a recursive coordinate bisectioning (RCB) of the
 simulation domain. The basic idea is as follows.
 
 The simulation domain is cut into 2 boxes by an axis-aligned cut in
-one of the dimensions, leaving one new sub-box on either side of the
-cut.  Which dimension is chosen for the cut depends on the particle
-(weight) distribution within the parent box.  Normally the longest
-dimension of the box is cut, but if all (or most) of the particles are
-at one end of the box, a cut may be performed in another dimension to
-induce sub-boxes that are more cube-ish (3d) or square-ish (2d) in
-shape.
-
-After the cut is made, all the processors are also partitioned into 2
-groups, half assigned to the box on the lower side of the cut, and
-half to the box on the upper side.  (If the processor count is odd,
-one side gets an extra processor.)  The cut is positioned so that the
-number of (weighted) particles in the lower box is exactly the number
-that the processors assigned to that box should own for load balance
-to be perfect.  This also makes load balance for the upper box
-perfect.  The positioning of the cut is done iteratively, by a
-bisectioning method (median search).  Note that counting particles on
-either side of the cut requires communication between all processors
-at each iteration.
+the longest dimension, leaving one new box on either side of the cut.
+All the processors are also partitioned into 2 groups, half assigned
+to the box on the lower side of the cut, and half to the box on the
+upper side.  (If the processor count is odd, one side gets an extra
+processor.)  The cut is positioned so that the number of particles in
+the lower box is exactly the number that the processors assigned to
+that box should own for load balance to be perfect.  This also makes
+load balance for the upper box perfect.  The positioning is done
+iteratively, by a bisectioning method.  Note that counting particles
+on either side of the cut requires communication between all
+processors at each iteration.
 
 That is the procedure for the first cut.  Subsequent cuts are made
 recursively, in exactly the same manner.  The subset of processors
-assigned to each box make a new cut in one dimension of that box,
-splitting the box, the subset of processors, and the particles in the
-box in two.  The recursion continues until every processor is assigned
-a sub-box of the entire simulation domain, and owns the (weighted)
+assigned to each box make a new cut in the longest dimension of that
+box, splitting the box, the subset of processsors, and the particles
+in the box in two.  The recursion continues until every processor is
+assigned a sub-box of the entire simulation domain, and owns the
 particles in that sub-box.
 
 :line
@@ -376,7 +368,7 @@ of about 0.8 often results in the best performance, since the number
 of neighbors is likely to overestimate the ideal weight.
 
 This weight style is useful for systems where there are different
-cutoffs used for different pairs of interactions, or the density
+cutoffs used for different pairs of interations, or the density
 fluctuates, or a large number of particles are in the vicinity of a
 wall, or a combination of these effects.  If a simulation uses
 multiple neighbor lists, this weight style will use the first suitable
@@ -394,7 +386,7 @@ weights.  It assigns the same weight to each particle owned by a
 processor based on the total computational time spent by that
 processor.  See details below on what time window is used.  It uses
 the same timing information as is used for the "MPI task timing
-breakdown"_Section_start.html#start_7, namely, for sections {Pair},
+breakdown"_Section_start.html#start_8, namely, for sections {Pair},
 {Bond}, {Kspace}, and {Neigh}.  The time spent in those portions of
 the timestep are measured for each MPI rank, summed, then divided by
 the number of particles owned by that processor.  I.e. the weight is
@@ -410,7 +402,7 @@ decrease the weights so that the ratio of max weight to min weight
 decreases by {factor}.  In both cases the intermediate weight values
 increase/decrease proportionally as well.  A value = 1.0 has no effect
 on the {time} weights.  As a rule of thumb, effective values to use
-are typically between 0.5 and 1.2.  Note that the timer quantities
+are typicall between 0.5 and 1.2.  Note that the timer quantities
 mentioned above can be affected by communication which occurs in the
 middle of the operations, e.g. pair styles with intermediate exchange
 of data witin the force computation, and likewise for KSpace solves.

doc/src/body.txt

@@ -82,7 +82,7 @@ internal stress that induces fragmentation :ul
 then the interaction between pairs of particles is likely to be more
 complex than the summation of simple sub-particle interactions.  An
 example is contact or frictional forces between particles with planar
-surfaces that inter-penetrate.
+sufaces that inter-penetrate.
 
 These are additional LAMMPS commands that can be used with body
 particles of different styles
@@ -105,7 +105,7 @@ in the sections below.
 
 The {nparticle} body style represents body particles as a rigid body
 with a variable number N of sub-particles.  It is provided as a
-vanilla, prototypical example of a body particle, although as
+vanillia, prototypical example of a body particle, although as
 mentioned above, the "fix rigid"_fix_rigid.html command already
 duplicates its functionality.
 
@@ -140,7 +140,7 @@ for more details.
 The 6 moments of inertia (ixx,iyy,izz,ixy,ixz,iyz) should be the
 values consistent with the current orientation of the rigid body
 around its center of mass.  The values are with respect to the
-simulation box XYZ axes, not with respect to the principal axes of the
+simulation box XYZ axes, not with respect to the prinicpal axes of the
 rigid body itself.  LAMMPS performs the latter calculation internally.
 The coordinates of each sub-particle are specified as its x,y,z
 displacement from the center-of-mass of the body particle.  The
@@ -218,7 +218,7 @@ wish; see the "read_data"_read_data.html command for more details.
 The 6 moments of inertia (ixx,iyy,izz,ixy,ixz,iyz) should be the
 values consistent with the current orientation of the rigid body
 around its center of mass.  The values are with respect to the
-simulation box XYZ axes, not with respect to the principal axes of the
+simulation box XYZ axes, not with respect to the prinicpal axes of the
 rigid body itself.  LAMMPS performs the latter calculation internally.
 The coordinates of each vertex are specified as its x,y,z displacement
 from the center-of-mass of the body particle.  The center-of-mass

doc/src/bond_class2.txt

@@ -8,7 +8,6 @@
 
 bond_style class2 command :h3
 bond_style class2/omp command :h3
-bond_style class2/kk command :h3
 
 [Syntax:]
 
@@ -56,7 +55,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/bond_fene.txt

@@ -59,7 +59,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/bond_fene_expand.txt

@@ -62,7 +62,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for

doc/src/bond_harmonic.txt

@@ -54,7 +54,7 @@ LAMMPS"_Section_start.html#start_3 section for more info.
 
 You can specify the accelerated styles explicitly in your input script
 by including their suffix, or you can use the "-suffix command-line
-switch"_Section_start.html#start_6 when you invoke LAMMPS, or you can
+switch"_Section_start.html#start_7 when you invoke LAMMPS, or you can
 use the "suffix"_suffix.html command in your input script.
 
 See "Section 5"_Section_accelerate.html of the manual for