Merge pull request #1623 from akohlmey/next-version

Step version string for stable release

cmake/CMakeLists.txt

@@ -37,7 +37,7 @@ include(PreventInSourceBuilds)
 
 if(NOT CMAKE_BUILD_TYPE AND NOT CMAKE_CXX_FLAGS)
   #release comes with -O3 by default
-  set(CMAKE_BUILD_TYPE Release CACHE STRING "Choose the type of build, options are: None Debug Release RelWithDebInfo MinSizeRel." FORCE)
+  set(CMAKE_BUILD_TYPE RelWithDebInfo CACHE STRING "Choose the type of build, options are: None Debug Release RelWithDebInfo MinSizeRel." FORCE)
 endif(NOT CMAKE_BUILD_TYPE AND NOT CMAKE_CXX_FLAGS)
 string(TOUPPER "${CMAKE_BUILD_TYPE}" BTYPE)
 
@@ -133,6 +133,24 @@ foreach(PKG ${DEFAULT_PACKAGES} ${ACCEL_PACKAGES})
   option(PKG_${PKG} "Build ${PKG} Package" OFF)
 endforeach()
 
+######################################################
+# download and unpack support binaries for compilation
+# of windows binaries.
+######################################################
+if(${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
+  set(LAMMPS_THIRDPARTY_URL "http://download.lammps.org/thirdparty")
+  file(DOWNLOAD "${LAMMPS_THIRDPARTY_URL}/opencl-win-devel.tar.gz" "${CMAKE_CURRENT_BINARY_DIR}/opencl-win-devel.tar.gz"
+          EXPECTED_MD5 2c00364888d5671195598b44c2e0d44d)
+  execute_process(COMMAND ${CMAKE_COMMAND} -E tar xzf opencl-win-devel.tar.gz WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR})
+  if(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86")
+    set(OpenCL_LIBRARY "${CMAKE_CURRENT_BINARY_DIR}/OpenCL/lib_win32/libOpenCL.dll")
+  elseif(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64")
+    set(OpenCL_LIBRARY "${CMAKE_CURRENT_BINARY_DIR}/OpenCL/lib_win64/libOpenCL.dll")
+  endif()
+  set(OpenCL_INCLUDE_DIR "${CMAKE_CURRENT_BINARY_DIR}/OpenCL/include")
+endif()
+
+######################################################
 ######################################################
 # packages with special compiler needs or external libs
 ######################################################
@@ -148,6 +166,7 @@ if(PKG_USER-ADIOS)
 endif()
 
 # do MPI detection after language activation, if MPI for these language is required
+set(MPI_CXX_SKIP_MPICXX TRUE)
 find_package(MPI QUIET)
 option(BUILD_MPI "Build MPI version" ${MPI_FOUND})
 if(BUILD_MPI)
@@ -175,11 +194,13 @@ add_definitions(-DLAMMPS_${LAMMPS_SIZES})
 set(LAMMPS_API_DEFINES "${LAMMPS_API_DEFINES} -DLAMMPS_${LAMMPS_SIZES}")
 
 # posix_memalign is not available on Windows
-if(NOT ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
+if(${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
+  set(LAMMPS_MEMALIGN "0" CACHE STRING "posix_memalign() is not available on Windows" FORCE)
+else()
   set(LAMMPS_MEMALIGN "64" CACHE STRING "enables the use of the posix_memalign() call instead of malloc() when large chunks or memory are allocated by LAMMPS. Set to 0 to disable")
-  if(NOT ${LAMMPS_MEMALIGN} STREQUAL "0")
-    add_definitions(-DLAMMPS_MEMALIGN=${LAMMPS_MEMALIGN})
-  endif()
+endif()
+if(NOT ${LAMMPS_MEMALIGN} STREQUAL "0")
+  add_definitions(-DLAMMPS_MEMALIGN=${LAMMPS_MEMALIGN})
 endif()
 
 option(LAMMPS_EXCEPTIONS "enable the use of C++ exceptions for error messages (useful for library interface)" OFF)
@@ -219,8 +240,7 @@ if(BUILD_OMP)
   set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${OpenMP_CXX_FLAGS}")
 endif()
 
-
-if(PKG_MSCG OR PKG_USER-ATC OR PKG_USER-AWPMD OR PKG_USER-PLUMED OR PKG_USER-QUIP OR PKG_LATTE)
+if(PKG_MSCG OR PKG_USER-ATC OR PKG_USER-AWPMD OR PKG_USER-QUIP OR PKG_LATTE)
   find_package(LAPACK)
   find_package(BLAS)
   if(NOT LAPACK_FOUND OR NOT BLAS_FOUND)
@@ -230,6 +250,7 @@ if(PKG_MSCG OR PKG_USER-ATC OR PKG_USER-AWPMD OR PKG_USER-PLUMED OR PKG_USER-QUI
     enable_language(Fortran)
     file(GLOB LAPACK_SOURCES ${LAMMPS_LIB_SOURCE_DIR}/linalg/[^.]*.[fF])
     add_library(linalg STATIC ${LAPACK_SOURCES})
+    set(BLAS_LIBRARIES linalg)
     set(LAPACK_LIBRARIES linalg)
   else()
     list(APPEND LAPACK_LIBRARIES ${BLAS_LIBRARIES})
@@ -303,6 +324,7 @@ include(Packages/USER-QUIP)
 include(Packages/USER-QMMM)
 include(Packages/USER-VTK)
 include(Packages/KIM)
+include(Packages/LATTE)
 include(Packages/MESSAGE)
 include(Packages/MSCG)
 include(Packages/COMPRESS)
@@ -496,10 +518,43 @@ if(BUILD_LIB)
   if(LAMMPS_DEPS)
     add_dependencies(lammps ${LAMMPS_DEPS})
   endif()
+  set(LAMMPS_CXX_HEADERS
+    ${LAMMPS_SOURCE_DIR}/angle.h
+    ${LAMMPS_SOURCE_DIR}/atom.h
+    ${LAMMPS_SOURCE_DIR}/bond.h
+    ${LAMMPS_SOURCE_DIR}/citeme.h
+    ${LAMMPS_SOURCE_DIR}/comm.h
+    ${LAMMPS_SOURCE_DIR}/compute.h
+    ${LAMMPS_SOURCE_DIR}/dihedral.h
+    ${LAMMPS_SOURCE_DIR}/domain.h
+    ${LAMMPS_SOURCE_DIR}/error.h
+    ${LAMMPS_SOURCE_DIR}/fix.h
+    ${LAMMPS_SOURCE_DIR}/force.h
+    ${LAMMPS_SOURCE_DIR}/group.h
+    ${LAMMPS_SOURCE_DIR}/improper.h
+    ${LAMMPS_SOURCE_DIR}/input.h
+    ${LAMMPS_SOURCE_DIR}/kspace.h
+    ${LAMMPS_SOURCE_DIR}/lammps.h
+    ${LAMMPS_SOURCE_DIR}/lattice.h
+    ${LAMMPS_SOURCE_DIR}/lmppython.h
+    ${LAMMPS_SOURCE_DIR}/memory.h
+    ${LAMMPS_SOURCE_DIR}/modify.h
+    ${LAMMPS_SOURCE_DIR}/neighbor.h
+    ${LAMMPS_SOURCE_DIR}/neigh_list.h
+    ${LAMMPS_SOURCE_DIR}/output.h
+    ${LAMMPS_SOURCE_DIR}/pair.h
+    ${LAMMPS_SOURCE_DIR}/pointers.h
+    ${LAMMPS_SOURCE_DIR}/region.h
+    ${LAMMPS_SOURCE_DIR}/timer.h
+    ${LAMMPS_SOURCE_DIR}/universe.h
+    ${LAMMPS_SOURCE_DIR}/update.h
+    ${LAMMPS_SOURCE_DIR}/variable.h)
+
   set_target_properties(lammps PROPERTIES OUTPUT_NAME lammps${LAMMPS_LIB_SUFFIX})
   set_target_properties(lammps PROPERTIES SOVERSION ${SOVERSION})
   install(TARGETS lammps LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR})
   install(FILES ${LAMMPS_SOURCE_DIR}/library.h DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/lammps)
+  install(FILES ${LAMMPS_CXX_HEADERS} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/lammps)
   configure_file(pkgconfig/liblammps.pc.in ${CMAKE_CURRENT_BINARY_DIR}/liblammps${LAMMPS_LIB_SUFFIX}.pc @ONLY)
   install(FILES ${CMAKE_CURRENT_BINARY_DIR}/liblammps${LAMMPS_LIB_SUFFIX}.pc DESTINATION ${CMAKE_INSTALL_LIBDIR}/pkgconfig)
   configure_file(FindLAMMPS.cmake.in ${CMAKE_CURRENT_BINARY_DIR}/FindLAMMPS${LAMMPS_LIB_SUFFIX}.cmake @ONLY)
@@ -550,11 +605,11 @@ include(Documentation)
 ###############################################################################
 # Install potential and force field files in data directory
 ###############################################################################
-set(LAMMPS_INSTALL_POTENTIALS_DIR ${CMAKE_INSTALL_FULL_DATADIR}/lammps/potentials)
-install(DIRECTORY ${LAMMPS_POTENTIALS_DIR} DESTINATION ${LAMMPS_INSTALL_POTENTIALS_DIR})
-
-set(LAMMPS_INSTALL_FRC_FILES_DIR ${CMAKE_INSTALL_FULL_DATADIR}/lammps/frc_files)
-install(DIRECTORY ${LAMMPS_TOOLS_DIR}/msi2lmp/frc_files/ DESTINATION ${LAMMPS_INSTALL_FRC_FILES_DIR})
+set(LAMMPS_INSTALL_DATADIR ${CMAKE_INSTALL_FULL_DATADIR}/lammps)
+install(DIRECTORY ${LAMMPS_POTENTIALS_DIR} DESTINATION ${LAMMPS_INSTALL_DATADIR})
+if(BUILD_TOOLS)
+  install(DIRECTORY ${LAMMPS_TOOLS_DIR}/msi2lmp/frc_files DESTINATION ${LAMMPS_INSTALL_DATADIR})
+endif()
 
 configure_file(etc/profile.d/lammps.sh.in ${CMAKE_BINARY_DIR}/etc/profile.d/lammps.sh @ONLY)
 configure_file(etc/profile.d/lammps.csh.in ${CMAKE_BINARY_DIR}/etc/profile.d/lammps.csh @ONLY)
@@ -672,5 +727,10 @@ if(PKG_KOKKOS)
   message(STATUS "Kokkos Arch: ${KOKKOS_ARCH}")
 endif()
 if(PKG_KSPACE)
-  message(STATUS "Using ${FFT} as FFT")
+  message(STATUS "Using ${FFT} as primary FFT library")
+  if(FFT_SINGLE)
+    message(STATUS "Using single precision FFTs")
+  else()
+    message(STATUS "Using double precision FFTs")
+  endif()
 endif()

cmake/Modules/Packages/KIM.cmake

@@ -9,6 +9,9 @@ if(PKG_KIM)
   if(KIM-API_FOUND)
     set(DOWNLOAD_KIM_DEFAULT OFF)
   else()
+    if (NOT DOWNLOAD_KIM)
+      message(WARNING "KIM-API package not found.  We will download and build our own")
+    endif()
     set(DOWNLOAD_KIM_DEFAULT ON)
   endif()
   option(DOWNLOAD_KIM "Download KIM-API from OpenKIM instead of using an already installed one" ${DOWNLOAD_KIM_DEFAULT})
@@ -17,12 +20,16 @@ if(PKG_KIM)
       message(FATAL_ERROR "Cannot build downloaded KIM-API library with Ninja build tool")
     endif()
     message(STATUS "KIM-API download requested - we will build our own")
-    enable_language(C)
-    enable_language(Fortran)
+    include(CheckLanguage)
     include(ExternalProject)
+    enable_language(C)
+    check_language(Fortran)
+    if(NOT CMAKE_Fortran_COMPILER)
+      message(FATAL_ERROR "Compiling the KIM-API library requires a Fortran compiler")
+    endif()
     ExternalProject_Add(kim_build
-      URL https://s3.openkim.org/kim-api/kim-api-2.0.2.txz
-      URL_MD5 537d9c0abd30f85b875ebb584f9143fa
+      URL https://s3.openkim.org/kim-api/kim-api-2.1.2.txz
+      URL_MD5 6ac52e14ef52967fc7858220b208cba5
       BINARY_DIR build
       CMAKE_ARGS -DCMAKE_C_COMPILER=${CMAKE_C_COMPILER}
                  -DCMAKE_CXX_COMPILER=${CMAKE_CXX_COMPILER}

cmake/Modules/Packages/KSPACE.cmake

@@ -1,5 +1,5 @@
 if(PKG_KSPACE)
-  option(FFT_SINGLE "Use single precision FFT instead of double" OFF)
+  option(FFT_SINGLE "Use single precision FFTs instead of double precision FFTs" OFF)
   set(FFTW "FFTW3")
   if(FFT_SINGLE)
     set(FFTW "FFTW3F")
@@ -7,26 +7,30 @@ if(PKG_KSPACE)
   endif()
   find_package(${FFTW} QUIET)
   if(${FFTW}_FOUND)
-    set(FFT "${FFTW}" CACHE STRING "FFT library for KSPACE package")
+    set(FFT "FFTW3" CACHE STRING "FFT library for KSPACE package")
   else()
     set(FFT "KISS" CACHE STRING "FFT library for KSPACE package")
   endif()
-  set(FFT_VALUES KISS ${FFTW} MKL)
+  set(FFT_VALUES KISS FFTW3 MKL)
   set_property(CACHE FFT PROPERTY STRINGS ${FFT_VALUES})
   validate_option(FFT FFT_VALUES)
   string(TOUPPER ${FFT} FFT)
-  if(NOT FFT STREQUAL "KISS")
-    find_package(${FFT} REQUIRED)
-    if(NOT FFT STREQUAL "FFTW3F")
-      add_definitions(-DFFT_FFTW)
-    else()
-      add_definitions(-DFFT_${FFT})
-    endif()
-    include_directories(${${FFT}_INCLUDE_DIRS})
-    list(APPEND LAMMPS_LINK_LIBS ${${FFT}_LIBRARIES})
+
+  if(FFT STREQUAL "FFTW3")
+    find_package(${FFTW} REQUIRED)
+    add_definitions(-DFFT_FFTW3)
+    include_directories(${${FFTW}_INCLUDE_DIRS})
+    list(APPEND LAMMPS_LINK_LIBS ${${FFTW}_LIBRARIES})
+  elseif(FFT STREQUAL "MKL")
+    find_package(MKL REQUIRED)
+    add_definitions(-DFFT_MKL)
+    include_directories(${MKL_INCLUDE_DIRS})
+    list(APPEND LAMMPS_LINK_LIBS ${MKL_LIBRARIES})
   else()
+    # last option is KISSFFT
     add_definitions(-DFFT_KISS)
   endif()
+
   set(FFT_PACK "array" CACHE STRING "Optimization for FFT")
   set(FFT_PACK_VALUES array pointer memcpy)
   set_property(CACHE FFT_PACK PROPERTY STRINGS ${FFT_PACK_VALUES})

cmake/Modules/Packages/USER-PLUMED.cmake

@@ -1,11 +1,23 @@
 if(PKG_USER-PLUMED)
-  find_package(GSL REQUIRED)
   set(PLUMED_MODE "static" CACHE STRING "Linkage mode for Plumed2 library")
   set(PLUMED_MODE_VALUES static shared runtime)
   set_property(CACHE PLUMED_MODE PROPERTY STRINGS ${PLUMED_MODE_VALUES})
   validate_option(PLUMED_MODE PLUMED_MODE_VALUES)
   string(TOUPPER ${PLUMED_MODE} PLUMED_MODE)
 
+  set(PLUMED_LINK_LIBS "")
+  if(PLUMED_MODE STREQUAL "STATIC")
+    find_package(LAPACK REQUIRED)
+    find_package(BLAS REQUIRED)
+    find_package(GSL REQUIRED)
+    list(APPEND LAPACK_LIBRARIES ${BLAS_LIBRARIES})
+    list(APPEND PLUMED_LINK_LIBS ${LAPACK_LIBRARIES} ${GSL_LIBRARIES})
+    find_package(ZLIB QUIET)
+    if(ZLIB_FOUND)
+      list(APPEND PLUMED_LINK_LIBS ${ZLIB_LIBRARIES})
+    endif()
+  endif()
+
   find_package(PkgConfig QUIET)
   set(DOWNLOAD_PLUMED_DEFAULT ON)
   if(PKG_CONFIG_FOUND)
@@ -37,8 +49,8 @@ if(PKG_USER-PLUMED)
     message(STATUS "PLUMED download requested - we will build our own")
     include(ExternalProject)
     ExternalProject_Add(plumed_build
-      URL https://github.com/plumed/plumed2/releases/download/v2.5.1/plumed-src-2.5.1.tgz
-      URL_MD5 c2a7b519e32197a120cdf47e0f194f81
+      URL https://github.com/plumed/plumed2/releases/download/v2.5.2/plumed-src-2.5.2.tgz
+      URL_MD5 bd2f18346c788eb54e1e52f4f6acf41a
       BUILD_IN_SOURCE 1
       CONFIGURE_COMMAND <SOURCE_DIR>/configure --prefix=<INSTALL_DIR>
                                                ${CONFIGURE_REQUEST_PIC}
@@ -53,11 +65,11 @@ if(PKG_USER-PLUMED)
     list(APPEND LAMMPS_DEPS plumed_build)
     if(PLUMED_MODE STREQUAL "STATIC")
       add_definitions(-D__PLUMED_WRAPPER_CXX=1)
-      list(APPEND LAMMPS_LINK_LIBS ${PLUMED_INSTALL_DIR}/lib/libplumed.a ${GSL_LIBRARIES} ${LAPACK_LIBRARIES} ${CMAKE_DL_LIBS})
+      list(APPEND LAMMPS_LINK_LIBS ${PLUMED_INSTALL_DIR}/lib/libplumed.a ${PLUMED_LINK_LIBS} ${CMAKE_DL_LIBS})
     elseif(PLUMED_MODE STREQUAL "SHARED")
-      list(APPEND LAMMPS_LINK_LIBS ${PLUMED_INSTALL_DIR}/lib/libplumed.so ${PLUMED_INSTALL_DIR}/lib/libplumedKernel.so ${CMAKE_DL_LIBS})
+      list(APPEND LAMMPS_LINK_LIBS ${PLUMED_INSTALL_DIR}/lib/libplumed${CMAKE_SHARED_LIBRARY_SUFFIX} ${PLUMED_INSTALL_DIR}/lib/libplumedKernel${CMAKE_SHARED_LIBRARY_SUFFIX} ${CMAKE_DL_LIBS})
     elseif(PLUMED_MODE STREQUAL "RUNTIME")
-      add_definitions(-D__PLUMED_HAS_DLOPEN=1 -D__PLUMED_DEFAULT_KERNEL=${PLUMED_INSTALL_DIR}/lib/libplumedKernel.so)
+      add_definitions(-D__PLUMED_HAS_DLOPEN=1 -D__PLUMED_DEFAULT_KERNEL=${PLUMED_INSTALL_DIR}/lib/libplumedKernel${CMAKE_SHARED_LIBRARY_SUFFIX})
       list(APPEND LAMMPS_LINK_LIBS ${PLUMED_INSTALL_DIR}/lib/libplumedWrapper.a -rdynamic ${CMAKE_DL_LIBS})
     endif()
     set(PLUMED_INCLUDE_DIRS "${PLUMED_INSTALL_DIR}/include")
@@ -70,7 +82,7 @@ if(PKG_USER-PLUMED)
     elseif(PLUMED_MODE STREQUAL "SHARED")
       include(${PLUMED_LIBDIR}/plumed/src/lib/Plumed.cmake.shared)
     elseif(PLUMED_MODE STREQUAL "RUNTIME")
-      add_definitions(-D__PLUMED_HAS_DLOPEN=1 -D__PLUMED_DEFAULT_KERNEL=${PLUMED_LIBDIR}/libplumedKernel.so)
+      add_definitions(-D__PLUMED_HAS_DLOPEN=1 -D__PLUMED_DEFAULT_KERNEL=${PLUMED_LIBDIR}/libplumedKernel${CMAKE_SHARED_LIBRARY_SUFFIX})
       include(${PLUMED_LIBDIR}/plumed/src/lib/Plumed.cmake.runtime)
     endif()
     list(APPEND LAMMPS_LINK_LIBS ${PLUMED_LOAD})

cmake/Modules/Packages/VORONOI.cmake

@@ -18,8 +18,12 @@ if(PKG_VORONOI)
     else()
       set(VORO_BUILD_CFLAGS "${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_${BTYPE}}")
     endif()
-    string(APPEND VORO_BUILD_CFLAGS ${CMAKE_CXX_FLAGS})
-    set(VORO_BUILD_OPTIONS CXX=${CMAKE_CXX_COMPILER} CFLAGS=${VORO_BUILD_CFLAGS})
+    if(APPLE)
+      get_filename_component(VORO_CXX ${CMAKE_CXX_COMPILER} NAME_WE)
+      set(VORO_BUILD_OPTIONS CXX=${VORO_CXX} CFLAGS=${VORO_BUILD_CFLAGS})
+    else()
+      set(VORO_BUILD_OPTIONS CXX=${CMAKE_CXX_COMPILER} CFLAGS=${VORO_BUILD_CFLAGS})
+    endif()
 
     ExternalProject_Add(voro_build
       URL https://download.lammps.org/thirdparty/voro++-0.4.6.tar.gz

cmake/README.md

@@ -33,12 +33,17 @@ tasks, act as a reference and provide examples of typical use cases.
       * [Package-Specific Configuration Options](#package-specific-configuration-options)
          * [KSPACE Package](#kspace-package)
          * [MKL](#mkl)
-         * [FFTW2](#fftw2)
          * [FFTW3](#fftw3)
+         * [BLAS](#blas)
          * [LAPACK](#lapack)
          * [PYTHON Package](#python-package)
          * [GPU Package](#gpu-package)
+         * [MESSAGE Package](#message-package)
+         * [MSCG Package](#mscg-package)
          * [VORONOI Package](#voronoi-package)
+         * [USER-LATTE Package](#user-latte-package)
+         * [USER-PLUMED Package](#user-plumed-package)
+         * [USER-SCAFACOS Package](#user-scafacos-package)
          * [USER-SMD Package](#user-smd-package)
       * [Optional Features](#optional-features)
          * [zlib support](#zlib-support)
@@ -50,8 +55,6 @@ tasks, act as a reference and provide examples of typical use cases.
          * [Building with GNU Compilers](#building-with-gnu-compilers)
          * [Building with Intel Compilers](#building-with-intel-compilers)
          * [Building with LLVM/Clang Compilers](#building-with-llvmclang-compilers)
-      * [Examples](#examples)
-
 
 ## Quick Start for the Impatient
 If you want to skip ahead and just run the compilation using `cmake`, please
@@ -205,8 +208,10 @@ cmake -C ../cmake/presets/all_on.cmake -C ../cmake/presets/nolib.cmake -D PKG_GP
   <td>Controls if debugging symbols are added to the generated binaries</td>
   <td>
   <dl>
-  <dt><code>Release</code> (default)</dt>
+  <dt><code>RelWithDebInfo (default)</code></dt>
+  <dt><code>Release</code></dt>
   <dt><code>Debug</code></dt>
+  <dt><code>MinSizeRel</code></dt>
   </dl>
   </td>
 </tr>
@@ -249,6 +254,16 @@ cmake -C ../cmake/presets/all_on.cmake -C ../cmake/presets/nolib.cmake -D PKG_GP
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>LAMMPS_LONGLONG_TO_LONG</code></td>
+  <td>Workaround if your system or MPI version does not recognize <code>long long</code> data types</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>LAMMPS_MEMALIGN</code></td>
   <td>controls the alignment of blocks of memory allocated by LAMMPS</td>
@@ -271,7 +286,16 @@ cmake -C ../cmake/presets/all_on.cmake -C ../cmake/presets/nolib.cmake -D PKG_GP
 </tr>
 <tr>
   <td><code>LAMMPS_MACHINE</code></td>
-  <td>allows appending a machine suffix to the generate LAMMPS binary</td>
+  <td>allows appending a machine suffix to the generated LAMMPS binary</td>
+  <td>
+  <dl>
+    <dt>*none*  (default)</dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>LAMMPS_LIB_SUFFIX</code></td>
+  <td>allows appending a suffix to the generated LAMMPS library</td>
   <td>
   <dl>
     <dt>*none*  (default)</dt>
@@ -319,8 +343,8 @@ cmake -C ../cmake/presets/all_on.cmake -C ../cmake/presets/nolib.cmake -D PKG_GP
   </td>
 </tr>
 <tr>
-  <td><code>LAMMPS_LONGLONG_TO_LONG</code></td>
-  <td>Workaround if your system or MPI version does not recognize <code>long long</code> data types</td>
+  <td><code>BUILD_TOOLS</code></td>
+  <td>control whether to build LAMMPS tools</td>
   <td>
   <dl>
     <dt><code>off</code> (default)</dt>
@@ -561,23 +585,6 @@ cmake -C ../cmake/presets/all_on.cmake -C ../cmake/presets/nolib.cmake -D PKG_GP
   </dl>
   </td>
 </tr>
-<tr>
-  <td><code>PKG_MEAM</code></td>
-  <td>
-<p>A pair style for the modified embedded atom (MEAM) potential.</p>
-
-<p><strong>Please note that the MEAM package has been superseded by the USER-MEAMC package,
-which is a direct translation of the MEAM package to C++. USER-MEAMC contains
-additional optimizations making it run faster than MEAM on most machines, while
-providing the identical features and USER interface.</strong></p>
-  </td>
-  <td>
-  <dl>
-    <dt><code>off</code> (default)</dt>
-    <dt><code>on</code></dt>
-  </dl>
-  </td>
-</tr>
 <tr>
   <td><code>PKG_MISC</code></td>
   <td>
@@ -634,21 +641,6 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
-<tr>
-  <td><code>PKG_REAX</code></td>
-  <td>
-  A pair style which wraps a Fortran library which implements the ReaxFF
-  potential, which is a universal reactive force field. See the USER-REAXC
-  package for an alternate implementation in C/C++. Also a fix reax/bonds
-  command for monitoring molecules as bonds are created and destroyed.
-  </td>
-  <td>
-  <dl>
-    <dt><code>off</code> (default)</dt>
-    <dt><code>on</code></dt>
-  </dl>
-  </td>
-</tr>
 <tr>
   <td><code>PKG_REPLICA</code></td>
   <td>
@@ -695,6 +687,16 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_SPIN</code></td>
+  <td>Model atomic magnetic spins classically, coupled to atoms moving in the usual manner via MD. Various pair, fix, and compute styles.</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>PKG_SNAP</code></td>
   <td>
@@ -757,6 +759,16 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_MESSAGE</code></td>
+  <td>Commands to use LAMMPS as either a client or server and couple it to another application.</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>PKG_MSCG</code></td>
   <td>
@@ -811,6 +823,18 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_VORONOI</code></td>
+  <td>
+  A compute command which calculates the Voronoi tesselation of a collection of atoms by wrapping the Voro++ library. This can be used to calculate the local volume or each atoms or its near neighbors.
+  </td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 </tbody>
 </table>
 
@@ -825,6 +849,16 @@ providing the identical features and USER interface.</strong></p>
 </tr>
 </thead>
 <tbody>
+<tr>
+  <td><code>PKG_USER-ADIOS</code></td>
+  <td>ADIOS is a high-performance I/O library. This package implements the dump “atom/adios” and dump “custom/adios” commands to write data using the ADIOS library.</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>PKG_USER-ATC</code></td>
   <td>
@@ -853,6 +887,18 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_USER-BOCS</code></td>
+  <td>
+  This package provides fix bocs, a modified version of fix npt which includes the pressure correction to the barostat as outlined in: N. J. H. Dunn and W. G. Noid, “Bottom-up coarse-grained models that accurately describe the structure, pressure, and compressibility of molecular liquids,” J. Chem. Phys. 143, 243148 (2015).
+  </td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>PKG_USER-CGDNA</code></td>
   <td>
@@ -1142,6 +1188,30 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_USER-PLUMED</code></td>
+  <td>
+  The fix plumed command allows you to use the PLUMED free energy plugin for molecular dynamics to analyze and bias your LAMMPS trajectory on the fly. The PLUMED library is called from within the LAMMPS input script by using the <code>fix plumed</code> command.
+  </td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>PKG_USER-PTM</code></td>
+  <td>
+  A <code>compute ptm/atom</code> command that calculates local structure characterization using the Polyhedral Template Matching methodology.
+  </td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>PKG_USER-QTB</code></td>
   <td>
@@ -1197,6 +1267,33 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_USER-SCAFACOS</code></td>
+  <td>
+  A KSpace style which wraps the ScaFaCoS Coulomb solver library to compute long-range Coulombic interactions.
+  </td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>PKG_USER-SDPD</code></td>
+  <td>
+  A pair style for smoothed dissipative particle dynamics (SDPD), which is an
+  extension of smoothed particle hydrodynamics (SPH) to mesoscale where thermal
+  fluctuations are important (see the USER-SPH package). Also two fixes for
+  moving and rigid body integration of SPH/SDPD particles (particles of
+  <code>atom_style meso</code>).</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>PKG_USER-SMD</code></td>
   <td>
@@ -1280,6 +1377,23 @@ providing the identical features and USER interface.</strong></p>
   </dl>
   </td>
 </tr>
+<tr>
+  <td><code>PKG_USER-YAFF</code></td>
+  <td>
+  Some potentials that are also implemented in the Yet Another Force Field (YAFF) code.
+  The expressions and their use are discussed in the following papers:
+  <ul>
+    <li><a href="http://dx.doi.org/10.1002/jcc.23877" target="_blank">Vanduyfhuys et al., J. Comput. Chem., 36 (13), 1015-1027 (2015)</a></li>
+    <li><a href="http://dx.doi.org/10.1002/jcc.25173" target="_blank">Vanduyfhuys et al., J. Comput. Chem., 39 (16), 999-1011 (2018)</a></li>
+  </ul>
+  </td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 </tbody>
 </table>
 
@@ -1300,14 +1414,27 @@ providing the identical features and USER interface.</strong></p>
   <td><code>FFT</code></td>
   <td>
     <p>FFT library for KSPACE package</p>
-    <p>If either MKL or FFTW is selected <code>cmake</code> will try to locate these libraries automatically. To control which one should be used please see the options below for each FFT library.</p>
+    <p>If either MKL or FFTW is selected <code>cmake</code> will try to locate
+    these libraries automatically. To control which one should be used please see
+    the options below for each FFT library.  Otherwise it will default to KISS
+    FFT.</p>
   </td>
   <td>
   <dl>
-    <dt><code>KISS</code></dt>
     <dt><code>FFTW3</code></dt>
     <dt><code>FFTW2</code></dt>
     <dt><code>MKL</code></dt>
+    <dt><code>KISS</code> (default)</dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>FFT_SINGLE</code></td>
+  <td>Use single-precision floating-point in FFT</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default = double precision)</dt>
+    <dt><code>on</code></dt>
   </dl>
   </td>
 </tr>
@@ -1325,60 +1452,6 @@ providing the identical features and USER interface.</strong></p>
 </tbody>
 </table>
 
-### MKL
-
-<table>
-<thead>
-<tr>
-  <th>Option</th>
-  <th>Description</th>
-  <th>Values</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-  <td><code>MKL_INCLUDE_DIRS</code></td>
-  <td></td>
-  <td>
-  </td>
-</tr>
-<tr>
-  <td><code>MKL_LIBRARIES</code></td>
-  <td></td>
-  <td>
-  </td>
-</tr>
-</tbody>
-</table>
-
-TODO static vs dynamic linking
-
-### FFTW2
-
-<table>
-<thead>
-<tr>
-  <th>Option</th>
-  <th>Description</th>
-  <th>Values</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-  <td><code>FFTW2_INCLUDE_DIRS</code></td>
-  <td></td>
-  <td>
-  </td>
-</tr>
-<tr>
-  <td><code>FFTW2_LIBRARIES</code></td>
-  <td></td>
-  <td>
-  </td>
-</tr>
-</tbody>
-</table>
-
 ### FFTW3
 
 <table>
@@ -1392,24 +1465,57 @@ TODO static vs dynamic linking
 <tbody>
 <tr>
   <td><code>FFTW3_INCLUDE_DIRS</code></td>
-  <td></td>
+  <td>path to FFTW3 include files</td>
   <td>
   </td>
 </tr>
 <tr>
   <td><code>FFTW3_LIBRARIES</code></td>
-  <td></td>
+  <td>list of paths to FFTW3 libraries</td>
   <td>
   </td>
 </tr>
 </tbody>
 </table>
 
+### MKL
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>MKL_INCLUDE_DIRS</code></td>
+  <td>path to MKL include files</td>
+  <td>
+  </td>
+</tr>
+<tr>
+  <td><code>MKL_LIBRARIES</code></td>
+  <td>list of paths to MKL libraries</td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### BLAS
+
+See [FindBLAS documentation](https://cmake.org/cmake/help/latest/module/FindBLAS.html)
+
 ### LAPACK
-TODO
+
+See [FindLAPACK documentation](https://cmake.org/cmake/help/latest/module/FindLAPACK.html)
 
 ### PYTHON Package
 
+See [FindPYTHON documentation](https://cmake.org/cmake/help/latest/module/FindPython.html)
+
 ### USER-INTEL Package
 
 <table>
@@ -1499,10 +1605,11 @@ target API.
   <td>
   <dl>
     <dt><code>sm_20</code> (Fermi)</dt>
-    <dt><code>sm_30</code> (Kepler)</dt>
+    <dt><code>sm_30</code> (Kepler) (default)</dt>
     <dt><code>sm_50</code> (Maxwell)</dt>
     <dt><code>sm_60</code> (Pascal)</dt>
     <dt><code>sm_70</code> (Volta)</dt>
+    <dt><code>sm_75</code> (Turing)</dt>
   </dl>
   </td>
 </tr>
@@ -1534,13 +1641,14 @@ target API.
 </tbody>
 </table>
 
-### VORONOI Package
+### KIM Package
 
-TODO
+Requires installation of the KIM library with API v2
 
-### USER-SMD Package
-
-Requires a Eigen3 installation
+If `DOWNLOAD_KIM` is set, the KIM library will be downloaded and built inside
+the CMake build directory. If the KIM library is already on your system (in a
+location CMake cannot find it), set the `PKG_CONFIG_PATH` environment variable
+so that `libkim-api` can be found.
 
 <table>
 <thead>
@@ -1551,9 +1659,323 @@ Requires a Eigen3 installation
 </tr>
 </thead>
 <tbody>
+<tr>
+  <td><code>DOWNLOAD_KIM</code></td>
+  <td>Download KIM API v2 and compile it as part of the build.</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### MESSAGE Package
+
+This package can optionally include support for messaging via sockets, using the open-source [ZeroMQ library](http://zeromq.org/), which must be installed on your system.
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>MESSAGE_ZMQ</code></td>
+  <td>Build with ZeroMQ support</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>ZMQ_LIBRARY</code></td>
+  <td>
+    ZMQ library file (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+<tr>
+  <td><code>ZMG_INCLUDE_DIR</code></td>
+  <td>
+    Provide include directory of existing ZMQ installation (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### MSCG Package
+
+Requires installation of the MSCG library
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_MSCG</code></td>
+  <td>Download MSCG and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>MSCG_LIBRARY</code></td>
+  <td>
+    MSCG library file (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+<tr>
+  <td><code>MSCG_INCLUDE_DIR</code></td>
+  <td>
+    Provide include directory of existing MSCG installation (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### VORONOI Package
+
+Requires installation of the Voro++ library
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_VORO</code></td>
+  <td>Download Voro++ and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>VORO_LIBRARY</code></td>
+  <td>
+    Voro++ library file (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+<tr>
+  <td><code>VORO_INCLUDE_DIR</code></td>
+  <td>
+    Provide include directory of existing Voro++ installation (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### USER-LATTE Package
+
+Requires installation of the LATTE library
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_LATTE</code></td>
+  <td>Download LATTE and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>LATTE_LIBRARY</code></td>
+  <td>
+    LATTE library file (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### USER-PLUMED Package
+
+Requires installation of the PLUMED library
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_PLUMED</code></td>
+  <td>Download PLUMED and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>PLUMED_MODE</code></td>
+  <td>
+    Determines the linkage mode for the PLUMED library.
+  </td>
+  <td>
+  <dl>
+    <dt><code>static</code> (default)</dt>
+    <dt><code>shared</code></dt>
+    <dt><code>runtime</code></dt>
+  </dl>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### USER-LATTE Package
+
+Requires installation of the LATTE library
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_LATTE</code></td>
+  <td>Download LATTE and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>LATTE_LIBRARY</code></td>
+  <td>
+    LATTE library file (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+### USER-SMD Package
+
+Requires installation of the Eigen3 library
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_EIGEN3</code></td>
+  <td>Download Eigen3 and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
 <tr>
   <td><code>EIGEN3_INCLUDE_DIR</code></td>
-  <td></td>
+  <td>
+    Provide include directory of existing Eigen3 installation (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+</tbody>
+</table>
+
+
+### USER-SCAFACOS Package
+
+To build with this package, you must download and build the [ScaFaCoS Coulomb solver library](http://www.scafacos.de/)
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>DOWNLOAD_SCAFACOS</code></td>
+  <td>Download SCAFACOS and compile it as part of the build</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>SCAFACOS_LIBRARY</code></td>
+  <td>
+    SCAFACOS library file (only needed if at custom location)
+  </td>
+  <td>
+  </td>
+</tr>
+<tr>
+  <td><code>SCAFACOS_INCLUDE_DIR</code></td>
+  <td>
+    SCAFACOS include directory (only needed if at custom location)
+  </td>
   <td>
   </td>
 </tr>
@@ -1791,5 +2213,82 @@ cmake -D CMAKE_C_COMPILER=icc -D CMAKE_CXX_COMPILER=icpc -D CMAKE_Fortran_COMPIL
 cmake -D CMAKE_C_COMPILER=clang -D CMAKE_CXX_COMPILER=clang++ -D CMAKE_Fortran_COMPILER=flang ../cmake
 ```
 
+## LAMMPS Developer Options
 
-## Examples
+
+<table>
+<thead>
+<tr>
+  <th>Option</th>
+  <th>Description</th>
+  <th>Values</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td><code>ENABLE_TESTING</code></td>
+  <td>Control wheather to add tests via CTest</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>LAMMPS_TESTING_SOURCE_DIR</code></td>
+  <td>Custom location of lammps-testing repository (optional). If not specified it will download it via Git</td>
+  <td>
+  </td>
+</tr>
+<tr>
+  <td><code>LAMMPS_TESTING_GIT_TAG</code></td>
+  <td>If lammps-testing repository is cloned, this is the tag/commit that will be checked out</td>
+  <td>
+  <dl>
+    <dt><code>master</code> (default)</dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>ENABLE_COVERAGE</code></td>
+  <td>Enables code coverage support via gcov and adds a gcovr build target to generate a coverage report.</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>ENABLE_SANITIZE_ADDRESS</code></td>
+  <td>Enables Address Sanitizer support when compiling using GCC or Clang for detecting memory leaks in binaries while running them. See https://clang.llvm.org/docs/AddressSanitizer.html</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>ENABLE_SANITIZE_UNDEFINED</code></td>
+  <td>Enables Undefined Behavior Sanitizer support when compiling using GCC or Clang for detecting code that is running into undefined behavior of the language. See https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+<tr>
+  <td><code>ENABLE_SANITIZE_THREAD</code></td>
+  <td>Enables Thread Sanitizer support when compiling using GCC or Clang for detecting data races in binaries while running them. See https://clang.llvm.org/docs/ThreadSanitizer.html</td>
+  <td>
+  <dl>
+    <dt><code>off</code> (default)</dt>
+    <dt><code>on</code></dt>
+  </dl>
+  </td>
+</tr>
+</tbody>
+</table>

cmake/etc/profile.d/lammps.csh.in

@@ -1,4 +1,4 @@
 # set environment for LAMMPS and msi2lmp executables
 # to find potential and force field files
-if ( "$?LAMMPS_POTENTIALS" == 0 ) setenv LAMMPS_POTENTIALS @LAMMPS_POTENTIALS_DIR@
-if ( "$?MSI2LMP_LIBRARY" == 0 ) setenv MSI2LMP_LIBRARY @LAMMPS_FRC_FILES_DIR@
+if ( "$?LAMMPS_POTENTIALS" == 0 ) setenv LAMMPS_POTENTIALS @LAMMPS_INSTALL_DATADIR@/potentials
+if ( "$?MSI2LMP_LIBRARY" == 0 ) setenv MSI2LMP_LIBRARY @LAMMPS_INSTALL_DATADIR@/frc_files

cmake/etc/profile.d/lammps.sh.in

@@ -1,5 +1,5 @@
 # set environment for LAMMPS and msi2lmp executables
 # to find potential and force field files
-LAMMPS_POTENTIALS=${LAMMPS_POTENTIALS-@LAMMPS_POTENTIALS_DIR@}
-MSI2LMP_LIBRARY=${MSI2LMP_LIBRARY-@LAMMPS_FRC_FILES_DIR@}
+LAMMPS_POTENTIALS=${LAMMPS_POTENTIALS-@LAMMPS_INSTALL_DATADIR@/potentials}
+MSI2LMP_LIBRARY=${MSI2LMP_LIBRARY-@LAMMPS_INSTALL_DATADIR@/frc_files}
 export LAMMPS_POTENTIALS MSI2LMP_LIBRARY

cmake/presets/mingw-cross.cmake

@@ -3,9 +3,9 @@ set(WIN_PACKAGES ASPHERE BODY CLASS2 COLLOID COMPRESS CORESHELL DIPOLE GPU
                  REPLICA RIGID SHOCK SNAP SPIN SRD VORONOI USER-ATC USER-AWPMD
                  USER-BOCS USER-CGDNA USER-CGSDK USER-COLVARS USER-DIFFRACTION
                  USER-DPD USER-DRUDE USER-EFF USER-FEP USER-INTEL USER-MANIFOLD
-                 USER-MEAMC USER-MESO USER-MISC USER-MOFFF USER-MOLFILE USER-OMP
-                 USER-PHONON USER-PTM USER-QTB USER-REAXC USER-SDPD USER-SMD
-                 USER-SMTBQ USER-SPH USER-TALLY USER-UEF USER-YAFF)
+                 USER-MEAMC USER-MESO USER-MISC USER-MGPT USER-MOFFF USER-MOLFILE
+                 USER-OMP USER-PHONON USER-PTM USER-QTB USER-REAXC USER-SDPD
+                 USER-SMD USER-SMTBQ USER-SPH USER-TALLY USER-UEF USER-YAFF)
 
 foreach(PKG ${WIN_PACKAGES})
   set(PKG_${PKG} ON CACHE BOOL "" FORCE)
@@ -14,4 +14,4 @@ endforeach()
 set(DOWNLOAD_VORO ON CACHE BOOL "" FORCE)
 set(DOWNLOAD_EIGEN3 ON CACHE BOOL "" FORCE)
 set(LAMMPS_MEMALIGN "0" CACHE STRING "" FORCE)
-set(INTEL_LRT_MODE "none" CACHE STRING "" FORCE)
+set(CMAKE_INSTALL_PREFIX "${CMAKE_CURRENT_BINARY_DIR}/lammps-installer")

doc/include-file-conventions.md

@@ -0,0 +1,133 @@
+# Outline of include file conventions in LAMMPS
+
+This purpose of this document is to provide a point of reference
+for LAMMPS developers and contributors as to what include files
+and definitions to put where into LAMMPS source.
+Last change 2019-07-05
+
+## Table of Contents
+
+  * [Motivation](#motivation)
+  * [Rules](#rules)
+  * [Tools](#tools)
+  * [Legacy Code](#legacy-code)
+
+## Motivation
+
+The conventions outlined in this document are supposed to help make
+maintenance of the LAMMPS software easier.  By trying to achieve
+consistency across files contributed by different developers, it will
+become easier for the code maintainers to modify and adjust files and,
+overall, the chance for errors or portability issues will be reduced.
+The rules employed are supposed to minimize naming conflicts and
+simplify dependencies between files and thus speed up compilation. They
+may, as well, make otherwise hidden dependencies visible.
+
+## Rules
+
+Below are the various rules that are applied.  Not all are enforced
+strictly and automatically.  If there are no significant side effects,
+exceptions may be possible for cases where a full compliance to the
+rules may require a large effort compared to the benefit.
+
+### Core Files Versus Package Files
+
+All rules listed below are most strictly observed for core LAMMPS files,
+which are the files that are not part of a package, and the files of the
+packages MOLECULE, MANYBODY, KSPACE, and RIGID.  On the other end of
+the spectrum are USER packages and legacy packages that predate these
+rules and thus may not be fully compliant.  Also, new contributions
+will be checked more closely, while existing code will be incrementally
+adapted to the rules as time and required effort permits.
+
+### System Versus Local Header Files
+
+All system- or library-provided include files are included with angular
+brackets (examples: `#include <cstring>` or `#include <mpi.h>`) while
+include files provided with LAMMPS are included with double quotes
+(examples: `#include "pointers.h"` or `#include "compute_temp.h"`).
+
+For headers declaring functions of the C-library, the corresponding
+C++ versions should be included (examples: `#include <cstdlib>` or
+`#include <cctypes>`).  However, these includes are limited to those defined
+in the C++98 standard.  Some files thus must use the older style until
+the minimum C++ standard requirement of LAMMPS is lifted to C++11 or
+even beyond (examples: `#include <stdint.h>` versus `#include <cstdint>`
+or `#include <inttypes.h>` versus `#include <cinttypes>`).
+
+### C++ Standard Compliance
+
+LAMMPS core files currently correspond to the C++98 standard. Files
+requiring C++11 or later are only permitted in (optional) packages
+and particularly packages that are not part of the list of commonly
+used packages such as MOLECULE, KSPACE, MANYBODY, or RIGID.
+
+Also, LAMMPS uses the C-style stdio library for I/O instead of iostreams.
+Since using both at the same time can cause problems, iostreams should
+be avoided where possible.
+
+### Lean Header Files
+
+Header files will typically contain the definition of a (single) class.
+These header files should have as few include statements as possible.
+This is particularly important for classes that implement a "style" and
+thus use a macro of the kind `SomeStyle(some/name,SomeName)`. These will
+all be included in the auto-generated `"some_style.h"` files which 
+results in a high potential for direct or indirect symbol name clashes.
+
+In the ideal case, the header would only include one file defining the
+parent class. That would typically be either `#include "pointers.h"` for
+the `Pointers` class, or a header of a class derived from it like
+`#include "pair.h"` for the `Pair` class and so on.  References to other
+classes inside the class should be make through pointers, for which forward
+declarations (inside the `LAMMPS_NS` or the new class' namespace) can
+be employed.  The full definition will then be included into the corresponding
+implementation file.  In the given example from above, the header file
+would be called `some_name.h` and the implementation `some_name.cpp` (all
+lower case with underscores, while the class itself would be in camel case
+and no underscores `SomeName`, and the style name with lower case names separated by
+a forward slash).
+
+### Implementation Files
+
+In the implementation files (typically, those would have the same base name
+as the corresponding header with a .cpp extension instead of .h) include
+statements should follow the "include what you use" principle.
+
+### Order of Include Statements
+
+Include files should be included in this order:
+* the header matching the implementation (`some_class.h` for file `some_class.cpp`)
+* mpi.h
+* system and library headers (anything that is using angular brackets; C-library headers first, then C++)
+* LAMMPS local headers (preferably in alphabetical order)
+
+### Special Cases and Exceptions
+
+#### pointers.h
+
+The `pointer.h` header file also includes `cstdio` and `lmptype.h`
+(and through it `stdint.h`, `intttypes.h`, cstdlib, and `climits`).
+This means any header including `pointers.h` can assume that `FILE`,
+`NULL`, `INT_MAX` are defined.
+
+## Tools
+
+The [Include What You Use tool](https://include-what-you-use.org/)
+can be used to provide supporting information about compliance with
+the rules listed here.  There are some limitations and the IWYU tool
+may give incorrect advice.  The tools is activated by setting the
+CMake variable `CMAKE_CXX_INCLUDE_WHAT_YOU_USE` variable to the
+path of the `include-what-you-use` command.  When activated, the
+tool will be run after each compilation and provide suggestions for
+which include files should be added or removed.
+
+## Legacy Code
+
+A lot of code predates the application of the rules in this document
+and the rules themselves are a moving target.  So there are going to be
+significant chunks of code that do not fully comply.  This applies
+for example to the USER-REAXC, or the USER-ATC package.  The LAMMPS
+developers are dedicated to make an effort to improve the compliance
+and welcome volunteers wanting to help with the process.
+

doc/lammps.1

@@ -1,4 +1,4 @@
-.TH LAMMPS "18 June 2019" "2019-06-18"
+.TH LAMMPS "7 August 2019" "2019-08-07"
 .SH NAME
 .B LAMMPS
 \- Molecular Dynamics Simulator.

doc/src/Build.txt

@@ -29,6 +29,7 @@ as described on the "Install"_Install.html doc page.
    Build_package
    Build_extras
    Build_windows
+   Build_development
 
 END_RST -->
 
@@ -41,7 +42,8 @@ END_RST -->
 "Optional build settings"_Build_settings.html
 "Include packages in build"_Build_package.html
 "Packages with extra build options"_Build_extras.html
-"Notes for building LAMMPS on Windows"_Build_windows.html  :all(b)
+"Notes for building LAMMPS on Windows"_Build_windows.html
+"Development build options (CMake only)"_Build_development.html  :all(b)
 
 If you have problems building LAMMPS, it is often due to software
 issues on your local machine.  If you can, find a local expert to

doc/src/Build_basics.txt

@@ -235,12 +235,16 @@ running LAMMPS from Python via its library interface.
 
 -D BUILD_EXE=value           # yes (default) or no
 -D BUILD_LIB=value           # yes or no (default)
--D BUILD_SHARED_LIBS=value   # yes or no (default) :pre
+-D BUILD_SHARED_LIBS=value   # yes or no (default)
+-D LAMMPS_LIB_SUFFIX=name    # name = mpi, serial, mybox, titan, laptop, etc
+                             # no default value :pre
+
 
 Setting BUILD_EXE=no will not produce an executable.  Setting
 BUILD_LIB=yes will produce a static library named liblammps.a.
 Setting both BUILD_LIB=yes and BUILD_SHARED_LIBS=yes will produce a
-shared library named liblammps.so.
+shared library named liblammps.so. If LAMMPS_LIB_SUFFIX is set the generated
+libraries will be named liblammps_name.a or liblammps_name.so instead.
 
 [Traditional make]:
 
@@ -310,6 +314,30 @@ current LAMMPS version (HTML and PDF files), from the website
 
 :line
 
+Build LAMMPS tools :h4,link(tools)
+
+Some tools described in "Auxiliary tools"_Tools.html can be built directly
+using CMake or Make.
+
+[CMake variable]:
+
+-D BUILD_TOOLS=value       # yes or no (default) :pre
+
+The generated binaries will also become part of the LAMMPS installation (see below)
+
+[Traditional make]:
+
+cd lammps/tools
+make all              # build all binaries of tools
+make binary2txt       # build only binary2txt tool
+make chain            # build only chain tool
+make micelle2d        # build only micelle2d tool
+make thermo_extract   # build only thermo_extract tool
+:pre
+
+:line
+
+
 Install LAMMPS after a build :h4,link(install)
 
 After building LAMMPS, you may wish to copy the LAMMPS executable of

doc/src/Build_cmake.txt

@@ -52,11 +52,17 @@ LAMMPS or need to re-compile LAMMPS repeatedly, installation of the
 ccache (= Compiler Cache) software may speed up repeated compilation
 even more.
 
-After compilation, you can optionally copy the LAMMPS executable and
-library into your system folders (by default under $HOME/.local) with:
+After compilation, you may optionally install the LAMMPS executable into
+your system with:
 
 make install    # optional, copy LAMMPS executable & library elsewhere :pre
 
+This will install the lammps executable and library (if requested), some
+tools (if configured) and additional files like library API headers,
+manpages, potential and force field files. The location of the installation
+tree is set by the CMake variable "CMAKE_INSTALL_PREFIX" which defaults
+to $\{HOME\}/.local
+
 :line
 
 There are 3 variants of CMake: a command-line version (cmake), a text mode
@@ -114,7 +120,7 @@ The argument can be preceeded or followed by various CMake
 command-line options.  Several useful ones are:
 
 -D CMAKE_INSTALL_PREFIX=path  # where to install LAMMPS executable/lib if desired
--D CMAKE_BUILD_TYPE=type      # type = Release or Debug
+-D CMAKE_BUILD_TYPE=type      # type = RelWithDebInfo (default), Release, MinSizeRel, or Debug
 -G output                     # style of output CMake generates
 -DVARIABLE=value              # setting for a LAMMPS feature to enable
 -D VARIABLE=value             # ditto, but cannot come after CMakeLists.txt dir

doc/src/Build_development.txt

@@ -0,0 +1,86 @@
+"Higher level section"_Build.html - "LAMMPS WWW Site"_lws - "LAMMPS
+Documentation"_ld - "LAMMPS Commands"_lc :c
+
+:link(lws,http://lammps.sandia.gov)
+:link(ld,Manual.html)
+:link(lc,Commands_all.html)
+
+:line
+
+Development build options (CMake only) :h3
+
+The CMake build of LAMMPS has a few extra options which are useful during
+development,  testing or debugging.
+
+:line
+
+Verify compilation flags :h4,link(compilation)
+
+Sometimes it is necessary to verify the complete sequence of compilation flags
+generated by the CMake build. To enable a more verbose output during
+compilation you can use the following option.
+
+-D CMAKE_VERBOSE_MAKEFILE=value    # value = no (default) or yes :pre
+
+Another way of doing this without reconfiguration is calling make with variable VERBOSE set to 1:
+
+make VERBOSE=1 :pre
+
+:line
+
+Address, Undefined Behavior, and Thread Sanitizer Support :h4,link(sanitizer)
+
+Compilers such as GCC and Clang support generating binaries which use different
+sanitizers to detect problems in code during run-time. They can detect "memory leaks"_https://clang.llvm.org/docs/AddressSanitizer.html,
+code that runs into "undefined behavior"_https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html of the
+language and "data races"_https://clang.llvm.org/docs/ThreadSanitizer.html in threaded code.
+
+The following settings allow you enable these features if your compiler supports
+it. Please note that they come with a performance hit. However, they are
+usually faster than using tools like Valgrind.
+
+-D ENABLE_SANITIZE_ADDRESS=value    # enable Address Sanitizer, value = no (default) or yes
+-D ENABLE_SANITIZE_UNDEFINED=value  # enable Undefined Behaviour Sanitizer, value = no (default) or yes
+-D ENABLE_SANITIZE_THREAD=value     # enable Thread Sanitizer, value = no (default) or yes
+:pre
+
+:line
+
+Code Coverage and Testing :h4,link(testing)
+
+We do extensive regression testing of the LAMMPS code base on a continuous
+basis. Some of the logic to do this has been added to the CMake build so
+developers can run the tests directly on their workstation. 
+
+NOTE: this is incomplete and only represents a small subset of tests that we run
+
+-D ENABLE_TESTING=value               # enable simple run tests of LAMMPS, value = no (default) or yes
+-D LAMMPS_TESTING_SOURCE_DIR=path     # path to lammps-testing repository (option if in custom location)
+-D LAMMPS_TESTING_GIT_TAG=value       # version of lammps-testing repository that should be used, value = master (default) or custom git commit or tag
+:pre
+
+If you enable testing in the CMake build it will create an additional target called "test". You can run them with:
+
+make test
+:pre
+
+The test cases used come from the lammps-testing repository. They are
+derivatives of the examples folder with some modifications to make the run
+faster.
+
+You can also collect code coverage metrics while running the tests by enabling
+coverage support during building.
+
+-D ENABLE_COVERAGE=value  # enable coverage measurements, value = no (default) or yes :pre
+
+This will also add the following targets to generate coverage reports after running the LAMMPS executable:
+
+make test               # run tests first!
+make gen_coverage_html  # generate coverage report in HTML format
+make gen_coverage_xml   # generate coverage report in XML format
+:pre
+
+These reports require GCOVR to be installed. The easiest way to do this to install it via pip:
+
+pip install git+https://github.com/gcovr/gcovr.git :pre
+:pre

doc/src/Build_extras.txt

@@ -88,7 +88,7 @@ which GPU hardware to build for.
                           # generic (default) or intel (Intel CPU) or fermi, kepler, cypress (NVIDIA)
 -D GPU_ARCH=value         # primary GPU hardware choice for GPU_API=cuda
                           # value = sm_XX, see below
-                          # default is Cuda-compiler dependent, but typically sm_20
+                          # default is sm_30
 -D CUDPP_OPT=value        # optimization setting for GPU_API=cuda
                           # enables CUDA Performance Primitives Optimizations
                           # value = yes (default) or no
@@ -172,22 +172,17 @@ KIM package :h4,link(kim)
 
 To build with this package, the KIM library with API v2 must be downloaded
 and built on your system.  It must include the KIM models that you want to
-use with LAMMPS. If you want to use the "kim_query"_kim_query.html
+use with LAMMPS. If you want to use the "kim_query"_kim_commands.html
 command, you also need to have libcurl installed with the matching
 development headers and the curl-config tool.
 
-Note that in LAMMPS lingo, a KIM model driver is a pair style
-(e.g. EAM or Tersoff).  A KIM model is a pair style for a particular
-element or alloy and set of parameters, e.g. EAM for Cu with a
-specific EAM potential file.  Also note that downloading and installing
-the KIM API library with all its models, may take a long time (10s of
-minutes to hours) to build.  Of course you only need to do that once.
+See "Obtaining KIM Models"_http://openkim.org/doc/usage/obtaining-models to
+learn how to install a pre-build binary of the OpenKIM Repository of Models.
+See the list of all KIM models here: https://openkim.org/browse/models
 
-See the list of KIM model drivers here:
-https://openkim.org/browse/model-drivers/alphabetical
-
-See the list of all KIM models here:
-https://openkim.org/browse/models/by-model-drivers
+(Also note that when downloading and installing from source
+the KIM API library with all its models, may take a long time (tens of
+minutes to hours) to build.  Of course you only need to do that once.)
 
 [CMake build]:
 
@@ -359,6 +354,9 @@ be installed on your system.
 [CMake build]:
 
 -D MESSAGE_ZMQ=value    # build with ZeroMQ support, value = no (default) or yes
+-D ZMQ_LIBRARY=path     # ZMQ library file (only needed if a custom location)
+-D ZMQ_INCLUDE_DIR=path # ZMQ include directory (only needed if a custom location)
+:pre
 
 [Traditional make]:
 
@@ -371,6 +369,7 @@ simply invoke the lib/message/Install.py script with the specified args:
 make lib-message               # print help message
 make lib-message args="-m -z"  # build with MPI and socket (ZMQ) support
 make lib-message args="-s"     # build as serial lib with no ZMQ support
+:pre
 
 The build should produce two files: lib/message/cslib/src/libmessage.a
 and lib/message/Makefile.lammps.  The latter is copied from an

doc/src/Commands_all.txt

@@ -50,11 +50,11 @@ An alphabetic list of all general LAMMPS commands.
 "dump"_dump.html,
 "dump adios"_dump_adios.html,
 "dump image"_dump_image.html,
-"dump_modify"_dump_modify.html,
 "dump movie"_dump_image.html,
 "dump netcdf"_dump_netcdf.html,
 "dump netcdf/mpiio"_dump_netcdf.html,
 "dump vtk"_dump_vtk.html,
+"dump_modify"_dump_modify.html,
 "dynamical_matrix"_dynamical_matrix.html,
 "echo"_echo.html,
 "fix"_fix.html,
@@ -68,7 +68,9 @@ An alphabetic list of all general LAMMPS commands.
 "improper_style"_improper_style.html,
 "include"_include.html,
 "jump"_jump.html,
-"kim_query"_kim_query.html,
+"kim_init"_kim_commands.html,
+"kim_interactions"_kim_commands.html,
+"kim_query"_kim_commands.html,
 "kspace_modify"_kspace_modify.html,
 "kspace_style"_kspace_style.html,
 "label"_label.html,

doc/src/Commands_compute.txt

@@ -66,6 +66,7 @@ KOKKOS, o = USER-OMP, t = OPT.
 "group/group"_compute_group_group.html,
 "gyration"_compute_gyration.html,
 "gyration/chunk"_compute_gyration_chunk.html,
+"gyration/shape"_compute_gyration_shape.html,
 "heat/flux"_compute_heat_flux.html,
 "heat/flux/tally"_compute_tally.html,
 "hexorder/atom"_compute_hexorder_atom.html,
@@ -80,6 +81,7 @@ KOKKOS, o = USER-OMP, t = OPT.
 "meso/e/atom"_compute_meso_e_atom.html,
 "meso/rho/atom"_compute_meso_rho_atom.html,
 "meso/t/atom"_compute_meso_t_atom.html,
+"momentum"_compute_momentum.html,
 "msd"_compute_msd.html,
 "msd/chunk"_compute_msd_chunk.html,
 "msd/nongauss"_compute_msd_nongauss.html,

doc/src/Commands_pair.txt

@@ -222,6 +222,8 @@ OPT.
 "sph/rhosum"_pair_sph_rhosum.html,
 "sph/taitwater"_pair_sph_taitwater.html,
 "sph/taitwater/morris"_pair_sph_taitwater_morris.html,
+"spin/dipole/cut"_pair_spin_dipole.html,
+"spin/dipole/long"_pair_spin_dipole.html,
 "spin/dmi"_pair_spin_dmi.html,
 "spin/exchange"_pair_spin_exchange.html,
 "spin/magelec"_pair_spin_magelec.html,

doc/src/Eqs/angle_class2_p6.tex

@@ -0,0 +1,15 @@
+\documentclass[12pt]{article}
+
+\pagestyle{empty}
+\begin{document}
+
+$$
+  E_{a} = K_2\left(\theta - \theta_0\right)^2 + K_3\left(\theta - \theta_0\right)^3 + K_4\left(\theta - \theta_0\right)^4 + K_5\left(\theta - \theta_0\right)^5 + K_6\left(\theta - \theta_0\right)^6
+$$
+
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:

doc/src/Eqs/angle_cosine_buck6d.tex

@@ -0,0 +1,15 @@
+\documentclass[12pt]{article}
+
+\pagestyle{empty}
+\begin{document}
+
+$$
+  E = K \left[ 1 + \cos(n\theta - \theta_0)\right]
+$$
+
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:

doc/src/Eqs/compute_shape_parameters.tex

@@ -0,0 +1,13 @@
+\documentclass[12pt]{article}
+
+\pagestyle{empty}
+\begin{document}
+
+\begin{eqnarray*}
+ c = l_z - 0.5(l_y+l_x) \\
+ b = l_y - l_x \\
+ k = \frac{3}{2} \frac{l_x^2+l_y^2+l_z^2}{(l_x+l_y+l_z)^2} - \frac{1}{2} 
+\end{eqnarray*}
+
+\end{document}
+

doc/src/Eqs/improper_inversion_harmonic.tex

@@ -0,0 +1,15 @@
+\documentclass[12pt]{article}
+
+\pagestyle{empty}
+\begin{document}
+
+$$
+  E = K \left(\theta - \theta_0\right)^2
+$$
+
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:

doc/src/Eqs/pair_agni.tex

@@ -0,0 +1,18 @@
+\documentclass[12pt]{article}
+
+\pagestyle{empty}
+\begin{document}
+
+\begin{eqnarray*}
+  F_i^u & = & \sum_t^{N_t}\alpha_t \cdot \exp\left[-\frac{\left(d_{i,t}^u\right)^2}{2l^2}\right] \\
+  d_{i,t}^u & = & \left|\left| V_i^u(\eta) - V_t^u(\eta) \right|\right| \\
+  V_i^u(\eta) & = & \sum_{j \neq i}\frac{r^u_{ij}}{r_{ij}} \cdot e^{-\left(\frac{r_{ij}}{\eta} \right)^2} \cdot f_d\left(r_{ij}\right) \\
+  f_d\left(r_{ij}\right) & = & \frac{1}{2} \left[\cos\left(\frac{\pi r_{ij}}{R_c}\right) + 1 \right]
+\end{eqnarray*}
+
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:

doc/src/Eqs/pair_buck6d.tex

@@ -1,6 +1,7 @@
 \documentclass[12pt]{article}
 
 \begin{document}
+\pagestyle{empty}
 
 \begin{eqnarray*}
   E = A e^{-\kappa r} - \frac{C}{r^6} \cdot \frac{1}{1 + D r^{14}} \qquad r < r_c \\

doc/src/Eqs/pair_coul_gauss.tex

@@ -0,0 +1,15 @@
+\documentclass[12pt]{article}
+
+\pagestyle{empty}
+\begin{document}
+
+$$
+  E = \frac{C_{q_i q_j}}{\epsilon r_{ij}}\,\, \textrm{erf}\left(\alpha_{ij} r_{ij}\right)\quad\quad\quad r < r_c
+$$
+
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:

doc/src/Eqs/pair_kolmogorov_crespi_full.tex

@@ -27,7 +27,7 @@
   V_{ij} & = & e^{-\lambda (r_{ij} -z_0)} \left [ C + f(\rho_{ij}) + f(\rho_{ji}) - A \left ( \frac{r_{ij}}{z_0}\right )^{-6} \right ] \\
   \rho_{ij}^2 & = & r_{ij}^2 - ({\bf r}_{ij}\cdot {\bf n}_{i})^2 \\[15pt]
   \rho_{ji}^2 & = & r_{ij}^2 - ({\bf r}_{ij}\cdot  {\bf n}_{j})^2 \\[15pt]
-  f(\rho) & = &  e^{-(\rho/\delta)^2} \sum_{n=0}^2 C_{2n} { \rho/\delta }^{2n}
+  f(\rho) & = &  e^{-(\rho/\delta)^2} \sum_{n=0}^2 C_{2n} { (\rho/\delta) }^{2n}
 \end{eqnarray*}
 \endgroup
 \end{document}

doc/src/Errors_messages.txt

@@ -2438,6 +2438,14 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Compute gyration ID does not exist for compute gyration/shape} :dt
+
+Self-explanatory. Provide a valid compute ID. :dd
+
+{Compute gyration/shape compute ID does not point to a gyration compute} :dt
+
+Self-explanatory. Provide and ID of a compute gyration command. :dd
+
 {Compute ID for compute reduce does not exist} :dt
 
 Self-explanatory. :dd
@@ -5777,6 +5785,16 @@ definitions. :dd
 
 The data file header lists improper but no improper types. :dd
 
+{Incompatible KIM Simulator Model} :dt
+
+The requested KIM Simulator Model was defined for a different MD code
+and thus is not compatible with LAMMPS. :dd
+
+{Incompatible units for KIM Simulator Model} :dt
+
+The selected unit style is not compatible with the requested KIM
+Simulator Model. :dd
+
 {Incomplete use of variables in create_atoms command} :dt
 
 The var and set options must be used together. :dd
@@ -5890,6 +5908,11 @@ The element names in the ADP file do not match those requested. :dd
 
 The element names in the EAM file do not match those requested. :dd
 
+{Incorrect format of ... section in data file} :dt
+
+Number or type of values per line in the given section of the data file
+is not consistent with the requirements for this section. :dd
+
 {Incorrect format in COMB potential file} :dt
 
 Incorrect number of words per line in the potential file. :dd
@@ -7042,6 +7065,12 @@ The atom style defined does not have this attribute. :dd
 
 The atom style defined does not have these attributes. :dd
 
+{KIM Simulator Model has no Model definition} :dt
+
+There is no model definition (key: model-defn) in the KIM Simulator
+Model.  Please contact the OpenKIM database maintainers to verify
+and potentially correct this. :dd
+
 {KOKKOS package does not yet support comm_style tiled} :dt
 
 Self-explanatory. :dd
@@ -7546,6 +7575,18 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Must use 'kim_style init' command before simulation box is defined} :dt
+
+Self-explanatory. :dd
+
+{Must use 'kim_style define' command after simulation box is defined} :dt
+
+Self-explanatory. :dd
+
+{Must use 'kim_style init' command before 'kim_style define'} :dt
+
+Self-explanatory. :dd
+
 {Must use 'kspace_modify pressure/scalar no' for rRESPA with kspace_style MSM} :dt
 
 The kspace scalar pressure option cannot (yet) be used with rRESPA. :dd
@@ -9489,6 +9530,11 @@ See the "read_data 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
 
+{Species XXX is not supported by this KIM Simulator Model} :dt
+
+The kim_style define command was referencing a species that is not
+present in the requested KIM Simulator Model. :dd
+
 {Specified processors != physical processors} :dt
 
 The 3d grid of processors defined by the processors command does not

doc/src/Errors_warnings.txt

@@ -129,6 +129,16 @@ Self-explanatory. :dd
 
 Self-explanatory. :dd
 
+{Communication cutoff is 0.0. No ghost atoms will be generated. Atoms may get lost} :dt
+
+The communication cutoff defaults to the maximum of what is inferred from
+pair and bond styles (will be zero, if none are defined) and what is specified
+via "comm_modify cutoff"_comm_modify.html (defaults to 0.0).  If this results
+to 0.0, no ghost atoms will be generated and LAMMPS may lose atoms or use
+incorrect periodic images of atoms in interaction lists.  To avoid, either use
+"pair style zero"_pair_zero.html with a suitable cutoff or use "comm_modify
+cutoff"_comm_modify.html. :dd
+
 {Communication cutoff is too small for SNAP micro load balancing, increased to %lf} :dt
 
 Self-explanatory. :dd

doc/src/Examples.txt

@@ -73,7 +73,7 @@ granregion: use of fix wall/region/gran as boundary on granular particles
 hugoniostat: Hugoniostat shock dynamics
 hyper:    global and local hyperdynamics of diffusion on Pt surface
 indent:   spherical indenter into a 2d solid
-kim:      use of potentials in Knowledge Base for Interatomic Models (KIM)
+kim:      use of potentials from the "OpenKIM Repository"_openkim
 latte:    examples for using fix latte for DFTB via the LATTE library
 meam:     MEAM test for SiC and shear (same as shear examples)
 melt:     rapid melt of 3d LJ system
@@ -153,3 +153,5 @@ illustrate how to use the command(s) provided in that package.  Many
 of the sub-directories have their own README files which give further
 instructions.  See the "Packages_details"_Packages_details.html doc
 page for more info on specific USER packages.
+
+:link(openkim,https://openkim.org)

doc/src/Install_linux.txt

@@ -15,7 +15,8 @@ Binaries are available for different versions of Linux:
 "Pre-built Fedora Linux executables"_#fedora
 "Pre-built EPEL Linux executables (RHEL, CentOS)"_#epel
 "Pre-built OpenSuse Linux executables"_#opensuse
-"Gentoo Linux executable"_#gentoo :all(b)
+"Gentoo Linux executable"_#gentoo
+"Arch Linux build-script"_#arch :all(b)
 
 :line
 
@@ -168,3 +169,31 @@ for details.
 
 Thanks to Nicolas Bock and Christoph Junghans (LANL) for setting up
 this Gentoo capability.
+
+:line
+
+Archlinux build-script :h4,link(arch)
+
+LAMMPS is available via Arch's unofficial Arch User repository (AUR).
+
+There are three scripts available, named lammps, lammps-beta and lammps-git.
+They respectively package the stable, patch and git releases.
+
+To install, you will need to have the git package installed. You may use
+any of the above names in-place of lammps.
+
+$ git clone https://aur.archlinux.org/lammps.git :pre
+$ cd lammps :pre
+$ makepkg -s :pre
+# makepkg -i :pre
+
+To update, you may repeat the above, or change into the cloned directory,
+and execute the following, after which, if there are any changes, you may
+use makepkg as above.
+
+$ git pull :pre
+
+Alternatively, you may use an AUR helper to install these packages.
+
+Note that the AUR provides build-scripts that download the source and
+the build the package on your machine.

doc/src/Install_mac.txt

@@ -10,47 +10,34 @@ Documentation"_ld - "LAMMPS Commands"_lc :c
 Download an executable for Mac :h3
 
 LAMMPS can be downloaded, built, and configured for OS X on a Mac with
-"Homebrew"_homebrew.  Only four of the LAMMPS packages are unavailable
-at this time because of additional needs not yet met: KIM, GPU,
-USER-INTEL, USER-ATC.
+"Homebrew"_homebrew.  The following LAMMPS packages are unavailable at this
+time because of additional needs not yet met: GPU, KOKKOS, LATTE, MSCG,
+MESSAGE, MPIIO POEMS VORONOI.
 
 After installing Homebrew, you can install LAMMPS on your system with
 the following commands:
 
-% brew tap homebrew/science
-% brew install lammps              # serial version
-% brew install lammps --with-mpi   # mpi support :pre
+% brew install lammps :pre
 
-This will install the executable "lammps", a python module named
-"lammps", and additional resources with all the standard packages.  To
-get the location of the additional resources type this:
-
-% brew info lammps :pre
-
-This command also tells you additional installation options available.
-The user-packages are available as options, just install them like
-this example for the USER-OMP package:
-
-% brew install lammps --enable-user-omp :pre
-
-It is usually best to install LAMMPS with the most up to date source
-files, which can be done with the "--HEAD" option:
-
-% brew install lammps --HEAD :pre
-
-To re-install the LAMMPS HEAD, run this command occasionally (make sure
-to use the desired options).
-
-% brew install --force lammps --HEAD $\{options\} :pre
+This will install the executables "lammps_serial" and "lammps_mpi", as well as
+the LAMMPS "doc", "potentials", "tools", "bench", and "examples" directories.
 
 Once LAMMPS is installed, you can test the installation with the
 Lennard-Jones benchmark file:
 
 % brew test lammps -v :pre
 
+The LAMMPS binary is built with the "KIM package"_Build_extras#kim which
+results in Homebrew also installing the `kim-api` binaries when LAMMPS is
+installed.  In order to use potentials from "openkim.org"_openkim, you can
+install the `openkim-models` package
+
+% brew install openkim-models :pre
+
 If you have problems with the installation you can post issues to
 "this link"_homebrew.
 
 Thanks to Derek Thomas (derekt at cello.t.u-tokyo.ac.jp) for setting
 up the Homebrew capability.
-:link(homebrew,https://github.com/Homebrew/homebrew-science/issues)
+:link(homebrew,https://github.com/Homebrew/homebrew-core/issues)
+:link(openkim,https://openkim.org)

doc/src/Intro_features.txt

@@ -92,8 +92,8 @@ commands)
   implicit solvent potentials: hydrodynamic lubrication, Debye
   force-field compatibility with common CHARMM, AMBER, DREIDING, \
     OPLS, GROMACS, COMPASS options
-  access to "KIM archive"_http://openkim.org of potentials via \
-    "pair kim"_pair_kim.html
+  access to the "OpenKIM Repository"_http://openkim.org of potentials via \
+    "kim_init, kim_interactions, and kim_query"_kim_commands.html commands
   hybrid potentials: multiple pair, bond, angle, dihedral, improper \
     potentials can be used in one simulation
   overlaid potentials: superposition of multiple pair potentials :ul

doc/src/Manual.txt

@@ -1,7 +1,7 @@
 <!-- HTML_ONLY -->
 <HEAD>
 <TITLE>LAMMPS Users Manual</TITLE>
-<META NAME="docnumber" CONTENT="18 Jun 2019 version">
+<META NAME="docnumber" CONTENT="7 Aug 2019 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 @@
 :line
 
 LAMMPS Documentation :c,h1
-18 Jun 2019 version :c,h2
+7 Aug 2019 version :c,h2
 
 "What is a LAMMPS version?"_Manual_version.html
 

doc/src/Packages_details.txt

@@ -338,22 +338,37 @@ KIM package :link(PKG-KIM),h4
 
 [Contents:]
 
-A "pair_style kim"_pair_kim.html command which is a wrapper on the
-Knowledge Base for Interatomic Models (KIM) repository of interatomic
-potentials, enabling any of them to be used in LAMMPS simulations.
-Also a "kim_query"_kim_query.html command, which allows to query
-the OpenKIM database for stored properties.
+This package contains a set of commands that serve as a wrapper on the
+"Open Knowledgebase of Interatomic Models (OpenKIM)"_https://openkim.org
+repository of interatomic models (IMs)
+enabling compatible ones to be used in LAMMPS simulations.
+This includes "kim_init and kim_interactions"_kim_commands.html
+commands to select, initialize and instantiate the IM, and a
+"kim_query"_kim_commands.html command to perform web queries
+for material property predictions of OpenKIM IMs.
+Support for KIM IMs that conform to the
+"KIM Application Programming Interface (API)"_https://openkim.org/kim-api/
+is provided by the "pair_style kim"_pair_kim.html command.
 
-To use this package you must have the KIM library available on your
-system.
+NOTE: The command {pair_style kim} is called by {kim_interactions} and
+is not recommended to be directly used in input scripts.
+
+To use this package you must have the KIM API library available on your
+system. The KIM API is available for download on the
+"OpenKIM website"_https://openkim.org/kim-api/.
+When installing LAMMPS from binary, the kim-api package
+is a dependency that is automatically downloaded and installed.
 
 Information about the KIM project can be found at its website:
-https://openkim.org.  The KIM project is led by Ellad Tadmor and Ryan
-Elliott (U Minnesota).
+"https://openkim.org"_https://openkim.org.
+The KIM project is led by Ellad Tadmor and Ryan Elliott (U Minnesota)
+and is funded by the "National Science Foundation"_https://www.nsf.gov/.
 
 [Authors:] Ryan Elliott (U Minnesota) is the main developer for the KIM
-API which the "pair_style kim"_pair_kim.html command uses.  He
-developed the pair style.
+API and the {pair_style kim} command. Axel Kohlmeyer (Temple U) and
+Ellad Tadmor (U Minnesota) contributed to the "kim_commands"_kim_commands.html
+interface in close collaboration with Ryan Elliott.
+
 
 [Install:]
 
@@ -363,10 +378,11 @@ extras"_Build_extras.html doc page.
 
 [Supporting info:]
 
+"kim_commands"_kim_commands.html
+"pair_style kim"_pair_kim.html
 src/KIM: filenames -> commands
 src/KIM/README
 lib/kim/README
-"pair_style kim"_pair_kim.html
 examples/kim :ul
 
 :line
@@ -911,6 +927,8 @@ the usual manner via MD.  Various pair, fix, and compute styles.
 
 src/SPIN: filenames -> commands
 "Howto spins"_Howto_spins.html
+"pair_style spin/dipole/cut"_pair_spin_dipole.html
+"pair_style spin/dipole/long"_pair_spin_dipole.html
 "pair_style spin/dmi"_pair_spin_dmi.html
 "pair_style spin/exchange"_pair_spin_exchange.html
 "pair_style spin/magelec"_pair_spin_magelec.html
@@ -982,9 +1000,9 @@ USER-ADIOS package :link(PKG-USER-ADIOS),h4
 
 [Contents:]
 
-ADIOS is a high-performance I/O library. This package implements the 
+ADIOS is a high-performance I/O library. This package implements the
 dump "atom/adios" and dump "custom/adios" commands to write data using
-the ADIOS library. 
+the ADIOS library.
 
 [Authors:] Norbert Podhorszki (ORNL) from the ADIOS developer team.
 
@@ -1173,7 +1191,7 @@ USER-PLUMED package :link(PKG-USER-PLUMED),h4
 The fix plumed command allows you to use the PLUMED free energy plugin
 for molecular dynamics to analyze and bias your LAMMPS trajectory on
 the fly.  The PLUMED library is called from within the LAMMPS input
-script by using the "fix plumed _fix_plumed.html command.
+script by using the "fix plumed"_fix_plumed.html command.
 
 [Authors:] The "PLUMED library"_#PLUMED is written and maintained by
 Massimilliano Bonomi, Giovanni Bussi, Carlo Camiloni and Gareth

doc/src/Speed_kokkos.txt

@@ -46,16 +46,15 @@ software version 7.5 or later must be installed on your system. See
 the discussion for the "GPU package"_Speed_gpu.html for details of how
 to check and do this.
 
-NOTE: Kokkos with CUDA currently implicitly assumes that the MPI
-library is CUDA-aware and has support for GPU-direct. This is not
-always the case, especially when using pre-compiled MPI libraries
-provided by a Linux distribution. This is not a problem when using
-only a single GPU and a single MPI rank on a desktop. When running
-with multiple MPI ranks, you may see segmentation faults without
-GPU-direct support.  These can be avoided by adding the flags "-pk
-kokkos gpu/direct off"_Run_options.html to the LAMMPS command line or
-by using the command "package kokkos gpu/direct off"_package.html in
-the input file.
+NOTE: Kokkos with CUDA currently implicitly assumes that the MPI library 
+is CUDA-aware. This is not always the case, especially when using 
+pre-compiled MPI libraries provided by a Linux distribution. This is not 
+a problem when using only a single GPU with a single MPI rank. When 
+running with multiple MPI ranks, you may see segmentation faults without 
+CUDA-aware MPI support. These can be avoided by adding the flags "-pk 
+kokkos cuda/aware off"_Run_options.html to the LAMMPS command line or by 
+using the command "package kokkos cuda/aware off"_package.html in the 
+input file.
 
 [Building LAMMPS with the KOKKOS package:]
 
@@ -217,9 +216,8 @@ case, also packing/unpacking communication buffers on the host may give
 speedup (see the KOKKOS "package"_package.html command). Using CUDA MPS 
 is recommended in this scenario.
 
-Using a CUDA-aware MPI library with 
-support for GPU-direct is highly recommended. GPU-direct use can be 
-avoided by using "-pk kokkos gpu/direct no"_package.html. As above for 
+Using a CUDA-aware MPI library is highly recommended. CUDA-aware MPI use can be 
+avoided by using "-pk kokkos cuda/aware no"_package.html. 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 should not exceed N.
 

doc/src/angle_table.txt

@@ -143,6 +143,16 @@ instructions on how to use the accelerated styles effectively.
 
 :line
 
+[Restart info:]
+
+This angle style writes the settings for the "angle_style table"
+command to "binary restart files"_restart.html, so a angle_style
+command does not need to specified in an input script that reads a
+restart file.  However, the coefficient information is not stored in
+the restart file, since it is tabulated in the potential files.  Thus,
+angle_coeff commands do need to be specified in the restart input
+script.
+
 [Restrictions:]
 
 This angle style can only be used if LAMMPS was built with the

doc/src/bond_table.txt

@@ -140,6 +140,16 @@ instructions on how to use the accelerated styles effectively.
 
 :line
 
+[Restart info:]
+
+This bond style writes the settings for the "bond_style table"
+command to "binary restart files"_restart.html, so a bond_style
+command does not need to specified in an input script that reads a
+restart file.  However, the coefficient information is not stored in
+the restart file, since it is tabulated in the potential files.  Thus,
+bond_coeff commands do need to be specified in the restart input
+script.
+
 [Restrictions:]
 
 This bond style can only be used if LAMMPS was built with the MOLECULE

doc/src/comm_modify.txt

@@ -69,9 +69,15 @@ processors.  By default the ghost cutoff = neighbor cutoff = pairwise
 force cutoff + neighbor skin.  See the "neighbor"_neighbor.html command
 for more information about the skin distance.  If the specified Rcut is
 greater than the neighbor cutoff, then extra ghost atoms will be acquired.
-If the provided cutoff is smaller, the provided value will be ignored
-and the ghost cutoff is set to the neighbor cutoff. Specifying a
-cutoff value of 0.0 will reset any previous value to the default.
+If the provided cutoff is smaller, the provided value will be ignored,
+the ghost cutoff is set to the neighbor cutoff and a warning will be
+printed. Specifying a cutoff value of 0.0 will reset any previous value
+to the default. If bonded interactions exist and equilibrium bond length
+information is available, then also a heuristic based on that bond length
+is computed. It is used as communication cutoff, if there is no pair
+style present and no {comm_modify cutoff} command used. Otherwise a
+warning is printed, if this bond based estimate is larger than the
+communication cutoff used. A
 
 The {cutoff/multi} option is equivalent to {cutoff}, but applies to
 communication mode {multi} instead. Since in this case the communication

doc/src/commands_list.txt

@@ -53,7 +53,7 @@ Commands :h1
    include
    info
    jump
-   kim_query
+   kim_commands
    kspace_modify
    kspace_style
    label

doc/src/compute.txt

@@ -171,42 +171,40 @@ The individual style names on the "Commands
 compute"_Commands_compute.html doc page are followed by one or more of
 (g,i,k,o,t) to indicate which accelerated styles exist.
 
-"ackland/atom"_compute_ackland_atom.html -
+"ackland/atom"_compute_ackland_atom.html - determines the local lattice structure based on the Ackland formulation
 "adf"_compute_adf.html - angular distribution function of triples of atoms
 "aggregate/atom"_compute_cluster_atom.html - aggregate ID for each atom
-"angle"_compute_angle.html -
-"angle/local"_compute_angle_local.html -
-"angle/local"_compute_bond_local.html - theta and energy of each angle
+"angle"_compute_angle.html - energy of each angle sub-style
+"angle/local"_compute_angle_local.html - theta and energy of each angle
 "angmom/chunk"_compute_angmom_chunk.html - angular momentum for each chunk
-"basal/atom"_compute_basal_atom.html -
+"basal/atom"_compute_basal_atom.html - calculates the hexagonal close-packed "c" lattice vector of each atom
 "body/local"_compute_body_local.html - attributes of body sub-particles
-"bond"_compute_bond.html - values computed by a bond style
+"bond"_compute_bond.html - energy of each bond sub-style
 "bond/local"_compute_bond_local.html - distance and energy of each bond
 "centro/atom"_compute_centro_atom.html - centro-symmetry parameter for each atom
 "chunk/atom"_compute_chunk_atom.html - assign chunk IDs to each atom
 "chunk/spread/atom"_compute_chunk_spread_atom.html - spreads chunk values to each atom in chunk
 "cluster/atom"_compute_cluster_atom.html - cluster ID for each atom
 "cna/atom"_compute_cna_atom.html - common neighbor analysis (CNA) for each atom
-"cnp/atom"_compute_cnp_atom.html -
+"cnp/atom"_compute_cnp_atom.html - common neighborhood parameter (CNP) for each atom
 "com"_compute_com.html - center-of-mass of group of atoms
 "com/chunk"_compute_com_chunk.html - center-of-mass for each chunk
 "contact/atom"_compute_contact_atom.html - contact count for each spherical particle
 "coord/atom"_compute_coord_atom.html - coordination number for each atom
 "damage/atom"_compute_damage_atom.html - Peridynamic damage for each atom
-"dihedral"_compute_dihedral.html -
+"dihedral"_compute_dihedral.html - energy of each dihedral sub-style
 "dihedral/local"_compute_dihedral_local.html - angle of each dihedral
 "dilatation/atom"_compute_dilatation_atom.html - Peridynamic dilatation for each atom
-"dipole/chunk"_compute_dipole_chunk.html -
+"dipole/chunk"_compute_dipole_chunk.html - dipole vector and total dipole for each chunk
 "displace/atom"_compute_displace_atom.html - displacement of each atom
 "dpd"_compute_dpd.html -
 "dpd/atom"_compute_dpd_atom.html -
-"edpd/temp/atom"_compute_edpd_temp_atom.html -
-"entropy/atom"_compute_entropy_atom.html -
+"edpd/temp/atom"_compute_edpd_temp_atom.html - per-atom temperature for each eDPD particle in a group
+"entropy/atom"_compute_entropy_atom.html - pair entropy fingerprint of each atom
 "erotate/asphere"_compute_erotate_asphere.html - rotational energy of aspherical particles
 "erotate/rigid"_compute_erotate_rigid.html - rotational energy of rigid bodies
 "erotate/sphere"_compute_erotate_sphere.html - rotational energy of spherical particles
-"erotate/sphere/atom"_compute_erotate_sphere.html - rotational energy for each spherical particle
-"erotate/sphere/atom"_compute_erotate_sphere_atom.html -
+"erotate/sphere/atom"_compute_erotate_sphere_atom.html - rotational energy for each spherical particle
 "event/displace"_compute_event_displace.html - detect event on atom displacement
 "fep"_compute_fep.html -
 "force/tally"_compute_tally.html -
@@ -215,20 +213,22 @@ compute"_Commands_compute.html doc page are followed by one or more of
 "group/group"_compute_group_group.html - energy/force between two groups of atoms
 "gyration"_compute_gyration.html - radius of gyration of group of atoms
 "gyration/chunk"_compute_gyration_chunk.html - radius of gyration for each chunk
+"gyration/shape"_compute_gyration_shape.html - compute shape parameters from radius of gyration tensor
 "heat/flux"_compute_heat_flux.html - heat flux through a group of atoms
 "heat/flux/tally"_compute_tally.html -
 "hexorder/atom"_compute_hexorder_atom.html - bond orientational order parameter q6
-"improper"_compute_improper.html -
+"improper"_compute_improper.html - energy of each improper sub-style
 "improper/local"_compute_improper_local.html - angle of each improper
 "inertia/chunk"_compute_inertia_chunk.html - inertia tensor for each chunk
 "ke"_compute_ke.html - translational kinetic energy
 "ke/atom"_compute_ke_atom.html - kinetic energy for each atom
-"ke/atom/eff"_compute_ke_atom_eff.html -
-"ke/eff"_compute_ke_eff.html -
+"ke/atom/eff"_compute_ke_atom_eff.html - per-atom translational and radial kinetic energy in the electron force field model
+"ke/eff"_compute_ke_eff.html - kinetic energy of a group of nuclei and electrons in the electron force field model
 "ke/rigid"_compute_ke_rigid.html - translational kinetic energy of rigid bodies
-"meso/e/atom"_compute_meso_e_atom.html -
-"meso/rho/atom"_compute_meso_rho_atom.html -
-"meso/t/atom"_compute_meso_t_atom.html -
+"meso/e/atom"_compute_meso_e_atom.html - per-atom internal energy of Smooth-Particle Hydrodynamics atoms
+"meso/rho/atom"_compute_meso_rho_atom.html - per-atom mesoscopic density of Smooth-Particle Hydrodynamics atoms
+"meso/t/atom"_compute_meso_t_atom.html - per-atom internal temperature of Smooth-Particle Hydrodynamics atoms
+"momentum"_compute_momentum.html - translational momentum
 "msd"_compute_msd.html - mean-squared displacement of group of atoms
 "msd/chunk"_compute_msd_chunk.html - mean-squared displacement for each chunk
 "msd/nongauss"_compute_msd_nongauss.html - MSD and non-Gaussian parameter of group of atoms
@@ -242,73 +242,72 @@ compute"_Commands_compute.html doc page are followed by one or more of
 "pe/tally"_compute_tally.html -
 "plasticity/atom"_compute_plasticity_atom.html - Peridynamic plasticity for each atom
 "pressure"_compute_pressure.html - total pressure and pressure tensor
-"pressure/cylinder"_compute_pressure_cylinder.html -
-"pressure/uef"_compute_pressure_uef.html -
+"pressure/cylinder"_compute_pressure_cylinder.html - pressure tensor in cylindrical coordinates
+"pressure/uef"_compute_pressure_uef.html - pressure tensor in the reference frame of an applied flow field 
 "property/atom"_compute_property_atom.html - convert atom attributes to per-atom vectors/arrays
 "property/chunk"_compute_property_chunk.html - extract various per-chunk attributes
 "property/local"_compute_property_local.html - convert local attributes to localvectors/arrays
-"ptm/atom"_compute_ptm_atom.html -
+"ptm/atom"_compute_ptm_atom.html - determines the local lattice structure based on the Polyhedral Template Matching method
 "rdf"_compute_rdf.html - radial distribution function g(r) histogram of group of atoms
 "reduce"_compute_reduce.html - combine per-atom quantities into a single global value
 "reduce/chunk"_compute_reduce_chunk.html - reduce per-atom quantities within each chunk
 "reduce/region"_compute_reduce.html - same as compute reduce, within a region
 "rigid/local"_compute_rigid_local.html - extract rigid body attributes
-"saed"_compute_saed.html -
+"saed"_compute_saed.html - electron diffraction intensity on a mesh of reciprocal lattice nodes
 "slice"_compute_slice.html - extract values from global vector or array
 "smd/contact/radius"_compute_smd_contact_radius.html -
-"smd/damage"_compute_smd_damage.html -
+"smd/damage"_compute_smd_damage.html - damage status of SPH particles in Smooth Mach Dynamics
 "smd/hourglass/error"_compute_smd_hourglass_error.html -
-"smd/internal/energy"_compute_smd_internal_energy.html -
-"smd/plastic/strain"_compute_smd_plastic_strain.html -
-"smd/plastic/strain/rate"_compute_smd_plastic_strain_rate.html -
-"smd/rho"_compute_smd_rho.html -
-"smd/tlsph/defgrad"_compute_smd_tlsph_defgrad.html -
-"smd/tlsph/dt"_compute_smd_tlsph_dt.html -
+"smd/internal/energy"_compute_smd_internal_energy.html - per-particle enthalpy in Smooth Mach Dynamics
+"smd/plastic/strain"_compute_smd_plastic_strain.html - equivalent plastic strain per particle in Smooth Mach Dynamics
+"smd/plastic/strain/rate"_compute_smd_plastic_strain_rate.html - time rate of the equivalent plastic strain in Smooth Mach Dynamics
+"smd/rho"_compute_smd_rho.html - per-particle mass density in Smooth Mach Dynamics
+"smd/tlsph/defgrad"_compute_smd_tlsph_defgrad.html - deformation gradient in Smooth Mach Dynamics
+"smd/tlsph/dt"_compute_smd_tlsph_dt.html - CFL-stable time increment per particle in Smooth Mach Dynamics
 "smd/tlsph/num/neighs"_compute_smd_tlsph_num_neighs.html -
 "smd/tlsph/shape"_compute_smd_tlsph_shape.html -
 "smd/tlsph/strain"_compute_smd_tlsph_strain.html -
 "smd/tlsph/strain/rate"_compute_smd_tlsph_strain_rate.html -
-"smd/tlsph/stress"_compute_smd_tlsph_stress.html -
-"smd/triangle/vertices"_compute_smd_triangle_vertices.html -
+"smd/tlsph/stress"_compute_smd_tlsph_stress.html - per-particle Cauchy stress tensor for SPH particles
 "smd/triangle/vertices"_compute_smd_triangle_vertices.html -
 "smd/ulsph/num/neighs"_compute_smd_ulsph_num_neighs.html -
 "smd/ulsph/strain"_compute_smd_ulsph_strain.html -
 "smd/ulsph/strain/rate"_compute_smd_ulsph_strain_rate.html -
-"smd/ulsph/stress"_compute_smd_ulsph_stress.html -
-"smd/vol"_compute_smd_vol.html -
+"smd/ulsph/stress"_compute_smd_ulsph_stress.html - per-particle Cauchy stress tensor and von Mises equivalent stress in Smooth Mach Dynamics
+"smd/vol"_compute_smd_vol.html - per-particle volumes and their sum in Smooth Mach Dynamics
 "sna/atom"_compute_sna_atom.html - calculate bispectrum coefficients for each atom
 "snad/atom"_compute_sna_atom.html - derivative of bispectrum coefficients for each atom
 "snav/atom"_compute_sna_atom.html - virial contribution from bispectrum coefficients for each atom
-"spin"_compute_spin.html -
+"spin"_compute_spin.html - magnetic quantities for a system of atoms having spins
 "stress/atom"_compute_stress_atom.html - stress tensor for each atom
-"stress/mop"_compute_stress_mop.html -
-"stress/mop/profile"_compute_stress_mop.html -
+"stress/mop"_compute_stress_mop.html - normal components of the local stress tensor using the method of planes
+"stress/mop/profile"_compute_stress_mop.html - profile of the normal components of the local stress tensor using the method of planes
 "stress/tally"_compute_tally.html -
-"tdpd/cc/atom"_compute_tdpd_cc_atom.html -
+"tdpd/cc/atom"_compute_tdpd_cc_atom.html - per-atom chemical concentration of a specified species for each tDPD particle 
 "temp"_compute_temp.html - temperature of group of atoms
 "temp/asphere"_compute_temp_asphere.html - temperature of aspherical particles
 "temp/body"_compute_temp_body.html - temperature of body particles
 "temp/chunk"_compute_temp_chunk.html - temperature of each chunk
 "temp/com"_compute_temp_com.html - temperature after subtracting center-of-mass velocity
-"temp/cs"_compute_temp_cs.html -
+"temp/cs"_compute_temp_cs.html - temperature based on the center-of-mass velocity of atom pairs that are bonded to each other
 "temp/deform"_compute_temp_deform.html - temperature excluding box deformation velocity
-"temp/deform/eff"_compute_temp_deform_eff.html -
-"temp/drude"_compute_temp_drude.html -
-"temp/eff"_compute_temp_eff.html -
+"temp/deform/eff"_compute_temp_deform_eff.html - temperature excluding box deformation velocity in the electron force field model
+"temp/drude"_compute_temp_drude.html - temperature of Core-Drude pairs
+"temp/eff"_compute_temp_eff.html - temperature of a group of nuclei and electrons in the electron force field model
 "temp/partial"_compute_temp_partial.html - temperature excluding one or more dimensions of velocity
 "temp/profile"_compute_temp_profile.html - temperature excluding a binned velocity profile
 "temp/ramp"_compute_temp_ramp.html - temperature excluding ramped velocity component
 "temp/region"_compute_temp_region.html - temperature of a region of atoms
-"temp/region/eff"_compute_temp_region_eff.html -
-"temp/rotate"_compute_temp_rotate.html -
+"temp/region/eff"_compute_temp_region_eff.html - temperature of a region of nuclei and electrons in the electron force field model
+"temp/rotate"_compute_temp_rotate.html - temperature of a group of atoms after subtracting out their center-of-mass and angular velocities
 "temp/sphere"_compute_temp_sphere.html - temperature of spherical particles
-"temp/uef"_compute_temp_uef.html -
+"temp/uef"_compute_temp_uef.html - kinetic energy tensor in the reference frame of an applied flow field
 "ti"_compute_ti.html - thermodynamic integration free energy values
 "torque/chunk"_compute_torque_chunk.html - torque applied on each chunk
 "vacf"_compute_vacf.html - velocity auto-correlation function of group of atoms
 "vcm/chunk"_compute_vcm_chunk.html - velocity of center-of-mass for each chunk
 "voronoi/atom"_compute_voronoi_atom.html - Voronoi volume and neighbors for each atom
-"xrd"_compute_xrd.html - :ul
+"xrd"_compute_xrd.html - x-ray diffraction intensity on a mesh of reciprocal lattice nodes :ul
 
 [Restrictions:] none
 

doc/src/compute_gyration.txt

@@ -67,6 +67,7 @@ distance^2 "units"_units.html respectively.
 
 [Related commands:]
 
-"compute gyration/chunk"_compute_gyration_chunk.html
+"compute gyration/chunk"_compute_gyration_chunk.html,
+"compute gyration/shape"_compute_gyration_shape.html
 
 [Default:] none

doc/src/compute_gyration_shape.txt

@@ -0,0 +1,86 @@
+"LAMMPS WWW Site"_lws - "LAMMPS Documentation"_ld - "LAMMPS Commands"_lc :c
+
+:link(lws,http://lammps.sandia.gov)
+:link(ld,Manual.html)
+:link(lc,Commands_all.html)
+
+:line
+
+compute gyration/shape command :h3
+
+[Syntax:]
+
+compute ID group-ID gyration compute-ID :pre
+
+ID, group-ID are documented in "compute"_compute.html command
+gyration/shape = style name of this compute command
+compute-ID = ID of "compute gyration"_compute_gyration.html command :ul
+
+[Examples:]
+
+compute 1 molecule gyration/shape pe :pre
+
+[Description:]
+
+Define a computation that calculates the eigenvalues of the gyration tensor of a
+group of atoms and three shape parameters. The computation includes all effects
+due to atoms passing thru periodic boundaries.
+
+The three computed shape parameters are the asphericity, b, the acylindricity, c,
+and the relative shape anisotropy, k:
+
+:c,image(Eqs/compute_shape_parameters.jpg)
+
+where lx <= ly <= lz are the three eigenvalues of the gyration tensor.
+The asphericity  is always non-negative and zero only when the three principal
+moments are equal. This zero condition is met when the distribution of particles
+is spherically symmetric (hence the name asphericity) but also whenever the particle
+distribution is symmetric with respect to the three coordinate axes, e.g.,
+when the particles are distributed uniformly on a cube, tetrahedron or other Platonic
+solid. The acylindricity is always non-negative and zero only when the two principal
+moments are equal. This zero condition is met when the distribution of particles is
+cylindrically symmetric (hence the name, acylindricity), but also whenever the particle
+distribution is symmetric with respect to the two coordinate axes, e.g., when the
+particles are distributed uniformly on a regular prism. the relative shape anisotropy
+is bounded between zero (if all points are spherically symmetric) and one
+(if all points lie on a line).
+
+NOTE: The coordinates of an atom contribute to the gyration tensor in
+"unwrapped" form, by using the image flags associated with each atom.
+See the "dump custom"_dump.html command for a discussion of "unwrapped"
+coordinates. See the Atoms section of the "read_data"_read_data.html
+command for a discussion of image flags and how they are set for each
+atom.  You can reset the image flags (e.g. to 0) before invoking this
+compute by using the "set image"_set.html command.
+
+[Output info:]
+
+This compute calculates a global vector of
+length 6, which can be accessed by indices 1-6. The first three values are the
+eigenvalues of the gyration tensor followed by the asphericity, the acylindricity
+and the relative shape anisotropy.  The computed values can be used by any command
+that uses global  vector values from a compute as input.  See the "Howto
+output"_Howto_output.html doc page for an overview of LAMMPS output
+options.
+
+The vector values calculated by this compute are
+"intensive".  The first five vector values will be in
+distance^2 "units"_units.html while the sixth one is dimensionless.
+
+[Restrictions:]
+
+This compute is part of the USER-MISC package.  It is only enabled if
+LAMMPS was built with that package.  See the "Build
+package"_Build_package.html doc page for more info.
+
+[Related commands:]
+
+"compute gyration"_compute_gyration.html
+
+[Default:] none
+
+:line
+
+:link(Theodorou)
+[(Theodorou)] Theodorou, Suter, Macromolecules, 18, 1206 (1985).
+

doc/src/compute_hexorder_atom.txt

@@ -65,7 +65,7 @@ In an isotropic liquid, local neighborhoods may still exhibit
 weak hexagonal symmetry, but because the orientational correlation
 decays quickly with distance, the value of phi will be different for
 different atoms, and so when {q}6 is averaged over all the atoms
-in the system, \|<{q}6>\| << 1.
+in the system, |<{q}6>| << 1.
 
 The value of {qn} is set to zero for atoms not in the
 specified compute group, as well as for atoms that have less than

doc/src/compute_momentum.txt

@@ -0,0 +1,49 @@
+"LAMMPS WWW Site"_lws - "LAMMPS Documentation"_ld - "LAMMPS Commands"_lc :c
+
+:link(lws,http://lammps.sandia.gov)
+:link(ld,Manual.html)
+:link(lc,Commands_all.html)
+
+:line
+
+compute momentum command :h3
+
+[Syntax:]
+
+compute ID group-ID momentum :pre
+
+ID, group-ID are documented in "compute"_compute.html command
+momentum = style name of this compute command :ul
+
+[Examples:]
+
+compute 1 all momentum :pre
+
+[Description:]
+
+Define a computation that calculates the translational momentum
+of a group of particles.
+
+The momentum of each particles is computed as m v, where m and v are
+the mass and velocity of the particle.
+
+[Output info:]
+
+This compute calculates a global vector (the summed momentum) of
+length 3. This value can be used by any command that uses a global
+vector value from a compute as input. See the "Howto
+output"_Howto_output.html doc page for an overview of LAMMPS output
+options.
+
+The vector value calculated by this compute is "extensive". The vector
+value will be in mass*velocity "units"_units.html.
+
+[Restrictions:]
+
+This compute is part of the USER-MISC package.  It is only enabled if
+LAMMPS was built with that package.  See the "Build
+package"_Build_package.html doc page for more info.
+
+[Related commands:]
+
+[Default:] none

doc/src/compute_pressure.txt

@@ -16,12 +16,13 @@ ID, group-ID are documented in "compute"_compute.html command
 pressure = style name of this compute command
 temp-ID = ID of compute that calculates temperature, can be NULL if not needed
 zero or more keywords may be appended
-keyword = {ke} or {pair} or {bond} or {angle} or {dihedral} or {improper} or {kspace} or {fix} or {virial} :ul
+keyword = {ke} or {pair} or {bond} or {angle} or {dihedral} or {improper} or {kspace} or {fix} or {virial} or {pair/hybrid} :ul
 
 [Examples:]
 
 compute 1 all pressure thermo_temp
-compute 1 all pressure NULL pair bond :pre
+compute 1 all pressure NULL pair bond
+compute 1 all pressure NULL pair/hybrid lj/cut :pre
 
 [Description:]
 
@@ -67,6 +68,9 @@ extra keywords are listed, then only those components are summed to
 compute temperature or ke and/or the virial.  The {virial} keyword
 means include all terms except the kinetic energy {ke}.
 
+The {pair/hybrid} keyword means to only include contribution
+from a sub-style in a {hybrid} or {hybrid/overlay} pair style.
+
 Details of how LAMMPS computes the virial efficiently for the entire
 system, including for many-body potentials and accounting for the
 effects of periodic boundary conditions are discussed in

doc/src/computes.txt

@@ -44,6 +44,7 @@ Computes :h1
    compute_group_group
    compute_gyration
    compute_gyration_chunk
+   compute_gyration_shape
    compute_heat_flux
    compute_hexorder_atom
    compute_improper
@@ -57,6 +58,7 @@ Computes :h1
    compute_meso_e_atom
    compute_meso_rho_atom
    compute_meso_t_atom
+   compute_momentum
    compute_msd
    compute_msd_chunk
    compute_msd_nongauss

doc/src/create_atoms.txt

@@ -242,9 +242,8 @@ write_dump      all atom sinusoid.lammpstrj :pre
 
 :c,image(JPG/sinusoid_small.jpg,JPG/sinusoid.jpg)
 
-The {rotate} keyword can only be used with the {single} style and
-when adding a single molecule. It allows to specify the orientation
-at which the molecule is inserted.  The axis of rotation is
+The {rotate} keyword allows specification of the orientation
+at which molecules are inserted.  The axis of rotation is
 determined by the rotation vector (Rx,Ry,Rz) that goes through the
 insertion point.  The specified {theta} determines the angle of
 rotation around that axis.  Note that the direction of rotation for

doc/src/dihedral_table.txt

@@ -191,6 +191,16 @@ switch"_Run_options.html when you invoke LAMMPS, or you can use the
 See the "Speed packages"_Speed_packages.html doc page for more
 instructions on how to use the accelerated styles effectively.
 
+[Restart info:]
+
+This dihedral style writes the settings for the "dihedral_style table"
+command to "binary restart files"_restart.html, so a dihedral_style
+command does not need to specified in an input script that reads a
+restart file.  However, the coefficient information is not stored in
+the restart file, since it is tabulated in the potential files.  Thus,
+dihedral_coeff commands do need to be specified in the restart input
+script.
+
 [Restrictions:]
 
 This dihedral style can only be used if LAMMPS was built with the

doc/src/dihedral_table_cut.txt

@@ -189,6 +189,16 @@ Note that one file can contain many sections, each with a tabulated
 potential. LAMMPS reads the file section by section until it finds one
 that matches the specified keyword.
 
+[Restart info:]
+
+This dihedral style writes the settings for the "dihedral_style table/cut"
+command to "binary restart files"_restart.html, so a dihedral_style
+command does not need to specified in an input script that reads a
+restart file.  However, the coefficient information is not stored in
+the restart file, since it is tabulated in the potential files.  Thus,
+dihedral_coeff commands do need to be specified in the restart input
+script.
+
 [Restrictions:]
 
 This dihedral style can only be used if LAMMPS was built with the

doc/src/fix.txt

@@ -165,40 +165,40 @@ page are followed by one or more of (g,i,k,o,t) to indicate which
 accelerated styles exist.
 
 "adapt"_fix_adapt.html - change a simulation parameter over time
-"adapt/fep"_fix_adapt_fep.html -
+"adapt/fep"_fix_adapt_fep.html - enhanced version of fix adapt
 "addforce"_fix_addforce.html - add a force to each atom
-"addtorque"_fix_addtorque.html -
+"addtorque"_fix_addtorque.html - add a torque to a group of atoms
 "append/atoms"_fix_append_atoms.html - append atoms to a running simulation
-"atc"_fix_atc.html -
+"atc"_fix_atc.html - initiates a coupled MD/FE simulation
 "atom/swap"_fix_atom_swap.html - Monte Carlo atom type swapping
 "ave/atom"_fix_ave_atom.html - compute per-atom time-averaged quantities
 "ave/chunk"_fix_ave_chunk.html - compute per-chunk time-averaged quantities
 "ave/correlate"_fix_ave_correlate.html - compute/output time correlations
 "ave/correlate/long"_fix_ave_correlate_long.html -
 "ave/histo"_fix_ave_histo.html - compute/output time-averaged histograms
-"ave/histo/weight"_fix_ave_histo.html -
+"ave/histo/weight"_fix_ave_histo.html - weighted version of fix ave/histo
 "ave/time"_fix_ave_time.html - compute/output global time-averaged quantities
 "aveforce"_fix_aveforce.html - add an averaged force to each atom
 "balance"_fix_balance.html - perform dynamic load-balancing
-"bocs"_fix_bocs.html -
+"bocs"_fix_bocs.html - NPT style time integration with pressure correction
 "bond/break"_fix_bond_break.html - break bonds on the fly
 "bond/create"_fix_bond_create.html - create bonds on the fly
-"bond/react"_fix_bond_react.html -
+"bond/react"_fix_bond_react.html - apply topology changes to model reactions
 "bond/swap"_fix_bond_swap.html - Monte Carlo bond swapping
 "box/relax"_fix_box_relax.html - relax box size during energy minimization
-"client/md"_fix_client_md.html -
-"cmap"_fix_cmap.html -
-"colvars"_fix_colvars.html -
-"controller"_fix_controller.html -
+"client/md"_fix_client_md.html - MD client for client/server simulations
+"cmap"_fix_cmap.html - enables CMAP cross-terms of the CHARMM force field
+"colvars"_fix_colvars.html - interface to the collective variables “Colvars” library
+"controller"_fix_controller.html - apply control loop feedback mechanism
 "deform"_fix_deform.html - change the simulation box size/shape
 "deposit"_fix_deposit.html - add new atoms above a surface
-"dpd/energy"_fix_dpd_energy.html -
+"dpd/energy"_fix_dpd_energy.html - constant energy dissipative particle dynamics
 "drag"_fix_drag.html - drag atoms towards a defined coordinate
-"drude"_fix_drude.html -
-"drude/transform/direct"_fix_drude_transform.html -
-"drude/transform/inverse"_fix_drude_transform.html -
+"drude"_fix_drude.html - part of Drude oscillator polarization model
+"drude/transform/direct"_fix_drude_transform.html -  part of Drude oscillator polarization model
+"drude/transform/inverse"_fix_drude_transform.html -  part of Drude oscillator polarization model
 "dt/reset"_fix_dt_reset.html - reset the timestep based on velocity, forces
-"edpd/source"_fix_dpd_source.html -
+"edpd/source"_fix_dpd_source.html - add heat source to eDPD simulations
 "efield"_fix_efield.html - impose electric field on system
 "ehex"_fix_ehex.html - enhanced heat exchange algorithm
 "electron/stopping"_fix_electron_stopping.html - electronic stopping power as a friction force
@@ -208,27 +208,26 @@ accelerated styles exist.
 "eos/table/rx"_fix_eos_table_rx.html -
 "evaporate"_fix_evaporate.html - remove atoms from simulation periodically
 "external"_fix_external.html - callback to an external driver program
-"ffl"_fix_ffl.html -
-"filter/corotate"_fix_filter_corotate.html -
-"flow/gauss"_fix_flow_gauss.html -
+"ffl"_fix_ffl.html - apply a Fast-Forward Langevin equation thermostat
+"filter/corotate"_fix_filter_corotate.html - implement corotation filter to allow larger timesteps with r-RESPA
+"flow/gauss"_fix_flow_gauss.html - Gaussian dynamics for constant mass flux
 "freeze"_fix_freeze.html - freeze atoms in a granular simulation
 "gcmc"_fix_gcmc.html - grand canonical insertions/deletions
-"gld"_fix_gcmc.html - generalized Langevin dynamics integrator
-"gld"_fix_gld.html -
-"gle"_fix_gle.html -
+"gld"_fix_gld.html - generalized Langevin dynamics integrator
+"gle"_fix_gle.html - generalized Langevin equation thermostat
 "gravity"_fix_gravity.html - add gravity to atoms in a granular simulation
-"grem"_fix_grem.html -
+"grem"_fix_grem.html - implements the generalized replica exchange method
 "halt"_fix_halt.html - terminate a dynamics run or minimization
 "heat"_fix_heat.html - add/subtract momentum-conserving heat
 "hyper/global"_fix_hyper_global.html - global hyperdynamics
 "hyper/local"_fix_hyper_local.html - local hyperdynamics
-"imd"_fix_imd.html -
+"imd"_fix_imd.html - implements the “Interactive MD” (IMD) protocol 
 "indent"_fix_indent.html - impose force due to an indenter
-"ipi"_fix_ipi.html -
+"ipi"_fix_ipi.html - enable LAMMPS to run as a client for i-PI path-integral simulations
 "langevin"_fix_langevin.html - Langevin temperature control
-"langevin/drude"_fix_langevin_drude.html -
-"langevin/eff"_fix_langevin_eff.html -
-"langevin/spin"_fix_langevin_spin.html -
+"langevin/drude"_fix_langevin_drude.html - Langevin temperature control of Drude oscillators
+"langevin/eff"_fix_langevin_eff.html - Langevin temperature control for the electron force field model
+"langevin/spin"_fix_langevin_spin.html - Langevin temperature control for a spin or spin-lattice system
 "latte"_fix_latte.html - wrapper on LATTE density-functional tight-binding code
 "lb/fluid"_fix_lb_fluid.html -
 "lb/momentum"_fix_lb_momentum.html -
@@ -236,64 +235,60 @@ accelerated styles exist.
 "lb/rigid/pc/sphere"_fix_lb_rigid_pc_sphere.html -
 "lb/viscous"_fix_lb_viscous.html -
 "lineforce"_fix_lineforce.html - constrain atoms to move in a line
-"manifoldforce"_fix_manifoldforce.html -
-"meso"_fix_meso.html -
-"meso"_fix_meso_move.html - move mesoscopic SPH/SDPD particles in a prescribed fashion
-"meso/move"_fix_meso_move.html -
+"manifoldforce"_fix_manifoldforce.html - restrain atoms to a manifold during minimization
+"meso"_fix_meso.html - time integration for SPH/DPDE particles
+"meso/move"_fix_meso_move.html - move mesoscopic SPH/SDPD particles in a prescribed fashion
 "meso/stationary"_fix_meso_stationary.html -
 "momentum"_fix_momentum.html - zero the linear and/or angular momentum of a group of atoms
 "move"_fix_move.html - move atoms in a prescribed fashion
-"mscg"_fix_mscg.html -
+"mscg"_fix_mscg.html - apply MSCG method for force-matching to generate coarse grain models
 "msst"_fix_msst.html - multi-scale shock technique (MSST) integration
-"mvv/dpd"_fix_mvv_dpd.html -
-"mvv/edpd"_fix_mvv_dpd.html -
-"mvv/tdpd"_fix_mvv_dpd.html -
+"mvv/dpd"_fix_mvv_dpd.html - DPD using the modified velocity-Verlet integration algorithm
+"mvv/edpd"_fix_mvv_dpd.html - constant energy DPD using the modified velocity-Verlet algrithm
+"mvv/tdpd"_fix_mvv_dpd.html - constant temperature DPD using the modified velocity-Verlet algorithm
 "neb"_fix_neb.html - nudged elastic band (NEB) spring forces
 "nph"_fix_nh.html - constant NPH time integration via Nose/Hoover
 "nph/asphere"_fix_nph_asphere.html - NPH for aspherical particles
-"nph/body"_fix_nph_body.html -
-"nph/body"_fix_nve_body.html - NPH for body particles
-"nph/eff"_fix_nh_eff.html -
+"nph/body"_fix_nph_body.html - NPH for body particles
+"nph/eff"_fix_nh_eff.html - NPH for  nuclei and electrons in the electron force field model
 "nph/sphere"_fix_nph_sphere.html - NPH for spherical particles
 "nphug"_fix_nphug.html - constant-stress Hugoniostat integration
 "npt"_fix_nh.html - constant NPT time integration via Nose/Hoover
 "npt/asphere"_fix_npt_asphere.html - NPT for aspherical particles
-"npt/body"_fix_npt_body.html -
-"npt/body"_fix_nve_body.html - NPT for body particles
-"npt/eff"_fix_nh_eff.html -
+"npt/body"_fix_npt_body.html - NPT for body particles
+"npt/eff"_fix_nh_eff.html - NPT for  nuclei and electrons in the electron force field model
 "npt/sphere"_fix_npt_sphere.html - NPT for spherical particles
-"npt/uef"_fix_nh_uef.html -
+"npt/uef"_fix_nh_uef.html - NPT style time integration with diagonal flow
 "nve"_fix_nve.html - constant NVE time integration
 "nve/asphere"_fix_nve_asphere.html - NVE for aspherical particles
-"nve/asphere/noforce"_fix_nve_asphere_noforce.html - NVE for aspherical particles without forces"
-"nve/awpmd"_fix_nve_awpmd.html -
+"nve/asphere/noforce"_fix_nve_asphere_noforce.html - NVE for aspherical particles without forces
+"nve/awpmd"_fix_nve_awpmd.html - NVE for the Antisymmetrized Wave Packet Molecular Dynamics model
 "nve/body"_fix_nve_body.html - NVE for body particles
-"nve/dot"_fix_nve_dot.html -
-"nve/dotc/langevin"_fix_nve_dotc_langevin.html -
-"nve/eff"_fix_nve_eff.html -
+"nve/dot"_fix_nve_dot.html - rigid body constant energy time integrator for coarse grain models
+"nve/dotc/langevin"_fix_nve_dotc_langevin.html - Langevin style rigid body time integrator for coarse grain models
+"nve/eff"_fix_nve_eff.html - NVE for  nuclei and electrons in the electron force field model
 "nve/limit"_fix_nve_limit.html - NVE with limited step length
 "nve/line"_fix_nve_line.html - NVE for line segments
 "nve/manifold/rattle"_fix_nve_manifold_rattle.html -
 "nve/noforce"_fix_nve_noforce.html - NVE without forces (v only)
 "nve/sphere"_fix_nve_sphere.html - NVE for spherical particles
-"nve/spin"_fix_nve_spin.html -
+"nve/spin"_fix_nve_spin.html - NVE for a spin or spin-lattice system
 "nve/tri"_fix_nve_tri.html - NVE for triangles
-"nvk"_fix_nvk.html -
-"nvt"_fix_nh.html - constant NVT time integration via Nose/Hoover
+"nvk"_fix_nvk.html - constant kinetic energy time integration
+"nvt"_fix_nh.html - NVT time integration via Nose/Hoover
 "nvt/asphere"_fix_nvt_asphere.html - NVT for aspherical particles
-"nvt/body"_fix_nve_body.html - NVT for body particles
-"nvt/body"_fix_nvt_body.html -
-"nvt/eff"_fix_nh_eff.html -
+"nvt/body"_fix_nvt_body.html - NVT for body particles
+"nvt/eff"_fix_nh_eff.html - NVE for  nuclei and electrons in the electron force field model
 "nvt/manifold/rattle"_fix_nvt_manifold_rattle.html -
 "nvt/sllod"_fix_nvt_sllod.html - NVT for NEMD with SLLOD equations
-"nvt/sllod/eff"_fix_nvt_sllod_eff.html -
+"nvt/sllod/eff"_fix_nvt_sllod_eff.html - NVT for NEMD with SLLOD equations for the electron force field model
 "nvt/sphere"_fix_nvt_sphere.html - NVT for spherical particles
-"nvt/uef"_fix_nh_uef.html -
+"nvt/uef"_fix_nh_uef.html - NVT style time integration with diagonal flow
 "oneway"_fix_oneway.html - constrain particles on move in one direction
 "orient/bcc"_fix_orient.html - add grain boundary migration force for BCC
 "orient/fcc"_fix_orient.html - add grain boundary migration force for FCC
-"phonon"_fix_phonon.html -
-"pimd"_fix_pimd.html -
+"phonon"_fix_phonon.html - calculate dynamical matrix from MD simulations
+"pimd"_fix_pimd.html - Feynman path integral molecular dynamics
 "planeforce"_fix_planeforce.html - constrain atoms to move in a plane
 "plumed"_fix_plumed.html - wrapper on PLUMED free energy library
 "poems"_fix_poems.html - constrain clusters of atoms to move as coupled rigid bodies
@@ -302,24 +297,24 @@ accelerated styles exist.
 "press/berendsen"_fix_press_berendsen.html - pressure control by Berendsen barostat
 "print"_fix_print.html - print text and variables during a simulation
 "property/atom"_fix_property_atom.html - add customized per-atom values
-"python/invoke"_fix_python_invoke.html -
-"python/move"_fix_python_move.html -
-"qbmsst"_fix_qbmsst.html -
+"python/invoke"_fix_python_invoke.html - call a Python function during a simulation
+"python/move"_fix_python_move.html -  call a Python function during a simulation run
+"qbmsst"_fix_qbmsst.html - quantum bath multi-scale shock technique time integrator
 "qeq/comb"_fix_qeq_comb.html - charge equilibration for COMB potential
 "qeq/dynamic"_fix_qeq.html - charge equilibration via dynamic method
 "qeq/fire"_fix_qeq.html - charge equilibration via FIRE minimizer
 "qeq/point"_fix_qeq.html - charge equilibration via point method
-"qeq/reax"_fix_qeq_reax.html -
+"qeq/reax"_fix_qeq_reax.html - charge equilibration for ReaxFF potential
 "qeq/shielded"_fix_qeq.html - charge equilibration via shielded method
 "qeq/slater"_fix_qeq.html - charge equilibration via Slater method
-"qmmm"_fix_qmmm.html -
-"qtb"_fix_qtb.html -
+"qmmm"_fix_qmmm.html - functionality to enable a quantum mechanics/molecular mechanics coupling
+"qtb"_fix_qtb.html - implement quantum thermal bath scheme
 "rattle"_fix_shake.html - RATTLE constraints on bonds and/or angles
 "reax/c/bonds"_fix_reaxc_bonds.html - write out ReaxFF bond information
 "reax/c/species"_fix_reaxc_species.html - write out ReaxFF molecule information
 "recenter"_fix_recenter.html - constrain the center-of-mass position of a group of atoms
 "restrain"_fix_restrain.html - constrain a bond, angle, dihedral
-"rhok"_fix_rhok.html -
+"rhok"_fix_rhok.html - add bias potential for long-range ordered systems
 "rigid"_fix_rigid.html - constrain one or more clusters of atoms to move as a rigid body with NVE integration
 "rigid/meso"_fix_rigid_meso.html - constrain clusters of mesoscopic SPH/SDPD particles to move as a rigid body
 "rigid/nph"_fix_rigid.html - constrain one or more clusters of atoms to move as a rigid body with NPH integration
@@ -332,11 +327,11 @@ accelerated styles exist.
 "rigid/nvt/small"_fix_rigid.html - constrain many small clusters of atoms to move as a rigid body with NVT integration
 "rigid/small"_fix_rigid.html - constrain many small clusters of atoms to move as a rigid body with NVE integration
 "rx"_fix_rx.html -
-"saed/vtk"_fix_saed_vtk.html -
+"saed/vtk"_fix_saed_vtk.html - 
 "setforce"_fix_setforce.html - set the force on each atom
 "shake"_fix_shake.html - SHAKE constraints on bonds and/or angles
-"shardlow"_fix_shardlow.html -
-"smd"_fix_smd.html -
+"shardlow"_fix_shardlow.html - integration of DPD equations of motion using the Shardlow splitting
+"smd"_fix_smd.html - applied a steered MD force to a group
 "smd/adjust_dt"_fix_smd_adjust_dt.html -
 "smd/integrate_tlsph"_fix_smd_integrate_tlsph.html -
 "smd/integrate_ulsph"_fix_smd_integrate_ulsph.html -
@@ -355,13 +350,13 @@ accelerated styles exist.
 "temp/csld"_fix_temp_csvr.html - canonical sampling thermostat with Langevin dynamics
 "temp/csvr"_fix_temp_csvr.html - canonical sampling thermostat with Hamiltonian dynamics
 "temp/rescale"_fix_temp_rescale.html - temperature control by velocity rescaling
-"temp/rescale/eff"_fix_temp_rescale_eff.html -
+"temp/rescale/eff"_fix_temp_rescale_eff.html - temperature control by velocity rescaling in the electron force field model
 "tfmc"_fix_tfmc.html - perform force-bias Monte Carlo with time-stamped method
 "thermal/conductivity"_fix_thermal_conductivity.html - Muller-Plathe kinetic energy exchange for thermal conductivity calculation
 "ti/spring"_fix_ti_spring.html -
 "tmd"_fix_tmd.html - guide a group of atoms to a new configuration
 "ttm"_fix_ttm.html - two-temperature model for electronic/atomic coupling
-"ttm/mod"_fix_ttm.html -
+"ttm/mod"_fix_ttm.html - enhanced two-temperature model with additional options
 "tune/kspace"_fix_tune_kspace.html - auto-tune KSpace parameters
 "vector"_fix_vector.html - accumulate a global vector every N timesteps
 "viscosity"_fix_viscosity.html - Muller-Plathe momentum exchange for viscosity calculation
@@ -369,7 +364,7 @@ accelerated styles exist.
 "wall/body/polygon"_fix_wall_body_polygon.html -
 "wall/body/polyhedron"_fix_wall_body_polyhedron.html -
 "wall/colloid"_fix_wall.html - Lennard-Jones wall interacting with finite-size particles
-"wall/ees"_fix_wall_ees.html -
+"wall/ees"_fix_wall_ees.html - wall for ellipsoidal particles
 "wall/gran"_fix_wall_gran.html - frictional wall(s) for granular simulations
 "wall/gran/region"_fix_wall_gran_region.html -
 "wall/harmonic"_fix_wall.html - harmonic spring wall
@@ -379,7 +374,7 @@ accelerated styles exist.
 "wall/piston"_fix_wall_piston.html - moving reflective piston wall
 "wall/reflect"_fix_wall_reflect.html - reflecting wall(s)
 "wall/region"_fix_wall_region.html - use region surface as wall
-"wall/region/ees"_fix_wall_ees.html -
+"wall/region/ees"_fix_wall_ees.html - use region surface as wall for ellipsoidal particles
 "wall/srd"_fix_wall_srd.html - slip/no-slip wall for SRD particles :ul
 
 [Restrictions:]

doc/src/fix_adapt.txt

@@ -149,8 +149,7 @@ meaning of these parameters:
 "spin/neel"_pair_spin_neel.html: coulombic_cutoff: type global:
 "table"_pair_table.html: table_cutoff: type pairs:
 "ufm"_pair_ufm.html: epsilon,sigma: type pairs:
-"soft"_pair_soft.html: a: type pairs:
-"kim"_pair_kim.html: PARAM_FREE_*&#58i,j,...: global :tb(c=3,s=:)
+"soft"_pair_soft.html: a: type pairs: :tb(c=3,s=:)
 
 NOTE: It is easy to add new pairwise potentials and their parameters
 to this list.  All it typically takes is adding an extract() method to

doc/src/fix_bocs.txt

@@ -47,13 +47,13 @@ or {cubic_spline}.
 
 With either spline method, the only argument that needs to follow it
 is the name of a file that contains the desired pressure correction
-as a function of volume. The file should be formatted so each line has:
+as a function of volume. The file must be formatted so each line has:
 
 Volume_i, PressureCorrection_i :pre
 
 Note both the COMMA and the SPACE separating the volume's
 value and its corresponding pressure correction. The volumes in the file
-should be uniformly spaced. Both the volumes and the pressure corrections
+must be uniformly spaced. Both the volumes and the pressure corrections
 should be provided in the proper units, e.g. if you are using {units real},
 the volumes should all be in cubic angstroms, and the pressure corrections
 should all be in atmospheres. Furthermore, the table should start/end at a

doc/src/fix_bond_react.txt

@@ -24,7 +24,7 @@ common_keyword = {stabilization} :l
   {stabilization} values = {no} or {yes} {group-ID} {xmax}
     {no} = no reaction site stabilization
     {yes} = perform reaction site stabilization
-      {group-ID} = user-assigned prefix for the dynamic group of non-reacting atoms
+      {group-ID} = user-assigned prefix for the dynamic group of atoms not currently involved in a reaction
       {xmax} = xmax value that is used by an internally-created "nve/limit"_fix_nve_limit.html integrator :pre
 react = mandatory argument indicating new reaction specification :l
   react-ID = user-assigned name for the reaction :l
@@ -52,6 +52,8 @@ react = mandatory argument indicating new reaction specification :l
 
 [Examples:]
 
+For unabridged example scripts and files, see examples/USER/misc/bond_react.
+
 molecule mol1 pre_reacted_topology.txt
 molecule mol2 post_reacted_topology.txt
 fix 5 all bond/react react myrxn1 all 1 0 3.25 mol1 mol2 map_file.txt :pre
@@ -106,6 +108,20 @@ involved in any new reactions. The {xmax} value keyword should
 typically be set to the maximum distance that non-reacting atoms move
 during the simulation.
 
+Fix bond/react creates and maintains two important dynamic groups of
+atoms when using the {stabilization} keyword. The first group contains
+all atoms currently involved in a reaction; this group is
+automatically thermostatted by an internally-created
+"nve/limit"_fix_nve_limit.html integrator. The second group contains
+all atoms currently not involved in a reaction. This group should be
+used by a thermostat in order to time integrate the system. The name
+of this group of non-reacting atoms is created by appending '_REACT'
+to the group-ID argument of the {stabilization} keyword, as shown in
+the second example above.
+
+NOTE: When using reaction stabilization, you should generally not have
+a separate thermostat which acts on the 'all' group.
+
 The group-ID set using the {stabilization} keyword can be an existing
 static group or a previously-unused group-ID. It cannot be specified
 as 'all'. If the group-ID is previously unused, the fix bond/react
@@ -116,20 +132,17 @@ internally-created dynamic group. In both cases, this new dynamic
 group is named by appending '_REACT' to the group-ID, e.g.
 nvt_grp_REACT. By specifying an existing group, you may thermostat
 constant-topology parts of your system separately. The dynamic group
-contains only non-reacting atoms at a given timestep, and therefore
-should be used by a subsequent system-wide time integrator such as
-nvt, npt, or nve, as shown in the second example above. The time
-integration command should be placed after the fix bond/react command
-due to the internal dynamic grouping performed by fix bond/react.
+contains only atoms not involved in a reaction at a given timestep,
+and therefore should be used by a subsequent system-wide time
+integrator such as nvt, npt, or nve, as shown in the second example
+above (full examples can be found at examples/USER/misc/bond_react).
+The time integration command should be placed after the fix bond/react
+command due to the internal dynamic grouping performed by fix
+bond/react.
 
 NOTE: If the group-ID is an existing static group, react-group-IDs
 should also be specified as this static group, or a subset.
 
-NOTE: If the group-ID is previously unused, the internally-created
-group applies to all atoms in the system, i.e. you should generally
-not have a separate thermostat which acts on the 'all' group, or any
-other group.
-
 The following comments pertain to each {react} argument (in other
 words, can be customized for each reaction, or reaction step):
 
@@ -352,12 +365,13 @@ an atom that is not deleted. In addition to deleting unwanted reaction
 by-products, this feature can be used to remove specific topologies,
 such as small rings, that may be otherwise indistinguishable.
 
-Also, it may be beneficial to ensure reacting atoms are at a certain
-temperature before being released to the overall thermostat. For this,
-you can use the internally-created dynamic group named
-"bond_react_MASTER_group." For example, adding the following command
-would thermostat the group of all atoms currently involved in a
-reaction:
+Optionally, you can enforce additional behaviors on reacting atoms.
+For example, it may be beneficial to force reacting atoms to remain at
+a certain temperature. For this, you can use the internally-created
+dynamic group named "bond_react_MASTER_group", which consists of all
+atoms currently involved in a reaction. For example, adding the
+following command would add an additional thermostat to the group of
+all currently-reacting atoms:
 
 fix 1 bond_react_MASTER_group temp/rescale 1 300 300 10 1 :pre
 

doc/src/fix_plumed.txt

@@ -114,5 +114,5 @@ The default options are plumedfile = NULL and outfile = NULL
 :link(PLUMED)
 [(PLUMED)] G.A. Tribello, M. Bonomi, D. Branduardi, C. Camilloni and G. Bussi, Comp. Phys. Comm 185, 604 (2014)
 
-:link(plumeddocs,http://www.plumed.org/documentation)
+:link(plumeddocs,http://www.plumed.org/doc.html)
 :link(plumedhome,http://www.plumed.org/)

doc/src/fix_rhok.txt

@@ -39,8 +39,8 @@ An example of using the interface pinning method is located in the
 
 [Restrictions:]
 
-This fix is part of the MISC package.  It is only enabled if LAMMPS
-was built with that package.  See the "Build
+This fix is part of the USER-MISC package.  It is only enabled if
+LAMMPS was built with that package.  See the "Build
 package"_Build_package.html doc page for more info.
 
 [Related commands:]

doc/src/if.txt

@@ -57,8 +57,7 @@ Boolean expression is FALSE, then no commands are executed.
 The syntax for Boolean expressions is described below.
 
 Each command (t1, f1, e1, etc) can be any valid LAMMPS input script
-command, except an "include"_include.html command, which is not
-allowed.  If the command is more than one word, it must enclosed in
+command.  If the command is more than one word, it must enclosed in
 quotes, so it will be treated as a single argument, as in the examples
 above.
 

doc/src/improper_fourier.txt

@@ -27,7 +27,7 @@ The {fourier} improper style uses the following potential:
 where K is the force constant and omega is the angle between the IL
 axis and the IJK plane:
 
-:c,image(Eqs/umbrella.jpg)
+:c,image(JPG/umbrella.jpg)
 
 If all parameter (see bellow) is not zero, the all the three possible angles will taken in account.
 

doc/src/improper_inversion_harmonic.txt

@@ -28,7 +28,7 @@ where K is the force constant and omega is the angle evaluated for
 all three axis-plane combinations centered around the atom I.  For
 the IL axis and the IJK plane omega looks as follows:
 
-:c,image(Eqs/umbrella.jpg)
+:c,image(JPG/umbrella.jpg)
 
 Note that the {inversion/harmonic} angle term evaluation differs to
 the "improper_umbrella"_improper_umbrella.html due to the cyclic

doc/src/improper_umbrella.txt

@@ -29,7 +29,7 @@ commonly referred to as a classic inversion and used in the
 where K is the force constant and omega is the angle between the IL
 axis and the IJK plane:
 
-:c,image(Eqs/umbrella.jpg)
+:c,image(JPG/umbrella.jpg)
 
 If omega0 = 0 the potential term has a minimum for the planar
 structure.  Otherwise it has two minima at +/- omega0, with a barrier

doc/src/kim_commands.txt

@@ -0,0 +1,522 @@
+"LAMMPS WWW Site"_lws - "LAMMPS Documentation"_ld - "LAMMPS Commands"_lc :c
+
+:link(lws,http://lammps.sandia.gov)
+:link(ld,Manual.html)
+:link(lc,Commands_all.html)
+
+:line
+
+kim_init command :h3
+kim_interactions command :h3
+kim_query command :h3
+
+[Syntax:]
+
+kim_init model user_units unitarg
+kim_interactions typeargs
+kim_query variable formatarg query_function queryargs :pre
+
+model = name of the KIM interatomic model (the KIM ID for models archived in OpenKIM)
+user_units = the LAMMPS "units"_units.html style assumed in the LAMMPS input script
+unitarg = {unit_conversion_mode} (optional)
+typeargs = atom type to species mapping (one entry per atom type) or {fixed_types} for models with a preset fixed mapping
+variable = name of a (string style) variable where the result of the query is stored
+formatarg = {split} (optional)
+query_function = name of the OpenKIM web API query function to be used
+queryargs = a series of {keyword=value} pairs that represent the web query; supported keywords depend on the query function :ul
+
+
+[Examples:]
+
+kim_init SW_StillingerWeber_1985_Si__MO_405512056662_005 metal
+kim_interactions Si
+kim_init Sim_LAMMPS_ReaxFF_StrachanVanDuinChakraborty_2003_CHNO__SM_107643900657_000 real
+kim_init Sim_LAMMPS_ReaxFF_StrachanVanDuinChakraborty_2003_CHNO__SM_107643900657_000 metal unit_conversion_mode
+kim_interactions C H O
+Sim_LAMMPS_IFF_PCFF_HeinzMishraLinEmami_2015Ver1v5_FccmetalsMineralsSolvents Polymers__SM_039297821658_000 real
+kim_interactions fixed_types
+kim_query a0 get_lattice_constant_cubic crystal=\["fcc"\] species=\["Al"\] units=\["angstrom"\] :pre
+
+[Description:]
+
+The set of {kim_commands} provide a high-level wrapper around the
+"Open Knowledgebase of Interatomic Models (OpenKIM)"_https://openkim.org
+repository of interatomic models (IMs) (potentials and force fields),
+so that they can be used by LAMMPS scripts.  These commands do not implement
+any computations directly, but rather generate LAMMPS input commands based
+on the information retrieved from the OpenKIM repository to initialize and
+activate OpenKIM IMs and query their predictions for use in the LAMMPS script.
+All LAMMPS input commands generated and executed by {kim_commands} are
+echoed to the LAMMPS log file.
+
+Benefits of Using OpenKIM IMs :h4
+
+Employing OpenKIM IMs provides LAMMPS users with multiple benefits:
+
+Reliability :h5
+
+All content archived in OpenKIM is reviewed by the "KIM Editor"_https://openkim.org/governance/ for quality.
+IMs in OpenKIM are archived with full provenance control. Each is associated with a maintainer responsible for the integrity of the content. All changes are tracked and recorded.
+IMs in OpenKIM are exhaustively tested using "KIM Tests"_https://openkim.org/doc/evaluation/kim-tests/ that compute a host of material properties, and "KIM Verification Checks"_https://openkim.org/doc/evaluation/kim-verification-checks/ that provide the user with information on various aspects of the IM behavior and coding correctness. This information is displayed on the IM's page accessible through the  "OpenKIM browse interface"_https://openkim.org/browse. :ul
+
+Reproducibility :h5
+
+Each IM in OpenKIM is issued a unique identifier ("KIM ID"_https://openkim.org/doc/schema/kim-ids/), which includes a version number (last three digits).  Any changes that can result in different numerical values lead to a version increment in the KIM ID. This makes it possible to reproduce simulations since the specific version of a specific IM used can be retrieved using its KIM ID.
+OpenKIM is a member organization of "DataCite"_https://datacite.org/ and issues digital object identifiers (DOIs) to all IMs archived in OpenKIM. This makes it possible to cite the IM code used in a simulation in a publications to give credit to the developers and further facilitate reproducibility. :ul
+
+Convenience :h5
+
+IMs in OpenKIM are distributed in binary form along with LAMMPS and can be used in a LAMMPS input script simply by providing their KIM ID in the {kim_init} command documented on this page.
+The {kim_query} web query tool provides the ability to use the predictions of IMs for supported material properties (computed via "KIM Tests"_https://openkim.org/doc/evaluation/kim-tests/) as part of a LAMMPS input script setup and analysis.
+Support is provided for unit conversion between the "unit style"_units.html used in the LAMMPS input script and the units required by the OpenKIM IM. This makes it possible to use a single input script with IMs using different units without change and minimizes the likelihood of errors due to incompatible units.  :ul
+
+:link(IM_types)
+Types of IMs in OpenKIM :h4
+
+There are two types of IMs archived in OpenKIM:
+
+The first type is called a {KIM Portable Model} (PM). A KIM PM is an independent computer implementation of an IM written in one of the languages supported by KIM (C, C++, Fortran) that conforms to the KIM Application Programming Interface ("KIM API"_https://openkim.org/kim-api/) Portable Model Interface (PMI) standard. A KIM PM will work seamlessly with any simulation code that supports the KIM API/PMI standard (including LAMMPS; see "complete list of supported codes"_https://openkim.org/projects-using-kim/).
+The second type is called a {KIM Simulator Model} (SM). A KIM SM is an IM that is implemented natively within a simulation code ({simulator}) that supports the KIM API Simulator Model Interface (SMI); in this case LAMMPS. A separate SM package is archived in OpenKIM for each parameterization of the IM, which includes all of the necessary parameter files, LAMMPS commands, and metadata (supported species, units, etc.) needed to run the IM in LAMMPS. :ol
+
+With these two IM types, OpenKIM can archive and test almost all IMs that
+can be used by LAMMPS. (It is easy to contribute new IMs to OpenKIM, see
+the "upload instructions"_https://openkim.org/doc/repository/adding-content/.)
+
+OpenKIM IMs are uniquely identified by a
+"KIM ID"_https://openkim.org/doc/schema/kim-ids/.
+The extended KIM ID consists of
+a human-readable prefix identifying the type of IM, authors, publication year,
+and supported species, separated by two underscores from the KIM ID itself,
+which begins with an IM code
+({MO} for a KIM Portable Model, and {SM} for a KIM Simulator Model)
+followed by a unique 12-digit code and a 3-digit version identifier.
+By convention SM prefixes begin with {Sim_} to readily identify them.
+
+SW_StillingerWeber_1985_Si__MO_405512056662_005
+Sim_LAMMPS_ReaxFF_StrachanVanDuinChakraborty_2003_CHNO__SM_107643900657_000 :pre
+
+Each OpenKIM IM has a dedicated "Model Page" on "OpenKIM"_https://openkim.org
+providing all the information on the IM including a title, description,
+authorship and citation information, test and verification check results,
+visualizations of results, a wiki with documentation and user comments, and
+access to raw files, and other information.
+The URL for the Model Page is constructed from the
+"extended KIM ID"_https://openkim.org/doc/schema/kim-ids/ of the IM:
+
+https://openkim.org/id/extended_KIM_ID
+:pre
+
+For example for the Stillinger-Weber potential
+listed above the Model Page is located at:
+
+"https://openkim.org/id/SW_StillingerWeber_1985_Si__MO_405512056662_005"_https://openkim.org/id/SW_StillingerWeber_1985_Si__MO_405512056662_005
+:pre
+
+See the "current list of KIM PMs and SMs archived in OpenKIM"_https://openkim.org/browse/models/by-species.
+This list is sorted by species and can be filtered to display only
+IMs for certain species combinations.
+
+See "Obtaining KIM Models"_http://openkim.org/doc/usage/obtaining-models to
+learn how to install a pre-build binary of the OpenKIM Repository of Models.
+
+NOTE: It is also possible to locally install IMs not archived in OpenKIM,
+in which case their names do not have to conform to the KIM ID format.
+
+Using OpenKIM IMs with LAMMPS :h4
+
+Two commands are employed when using OpenKIM IMs, one to select the
+IM and perform necessary initialization ({kim_init}), and the second
+to set up the IM for use by executing any necessary LAMMPS commands
+({kim_interactions}). Both are required.
+
+See the {examples/kim} directory for example input scripts that use KIM PMs
+and KIM SMs.
+
+OpenKIM IM Initialization ({kim_init}) :h5
+
+The {kim_init} mode command must be issued [before]
+the simulation box is created (normally at the top of the file).
+This command sets the OpenKIM IM that will be used and may issue
+additional commands changing LAMMPS default settings that are required
+for using the selected IM (such as "units"_units.html or
+"atom_style"_atom_style.html). If needed, those settings can be overridden,
+however, typically a script containing a {kim_init} command
+would not include {units} and {atom_style} commands.
+
+The required arguments of {kim_init} are the {model} name of the
+IM to be used in the simulation (for an IM archived in OpenKIM this is
+its "extended KIM ID"_https://openkim.org/doc/schema/kim-ids/, and
+the {user_units}, which are the LAMMPS "units style"_units.html used
+in the input script.  (Any dimensioned numerical values in the input
+script and values read in from files are expected to be in the
+{user_units} system.)
+
+The selected IM can be either a "KIM PM or a KIM SM"_#IM_types.
+For a KIM SM, the {kim_init} command verifies that the SM is designed
+to work with LAMMPS (and not another simulation code).
+In addition, the LAMMPS version used for defining
+the SM and the LAMMPS version being currently run are
+printed to help diagnose any incompatible changes to input script or
+command syntax between the two LAMMPS versions.
+
+Based on the selected model {kim_init} may modify the
+"atom_style"_atom_style.html.
+Some SMs have requirements for this setting. If this is the case, then
+{atom_style} will be set to the required style. Otherwise, the value is left
+unchanged (which in the absence of an {atom_style} command in the input script
+is the "default atom_style value"_atom_style.html).
+
+Regarding units, the {kim_init} command behaves in different ways depending
+on whether or not {unit conversion mode} is activated as indicated by the
+optional {unitarg} argument.
+If unit conversion mode is [not] active, then {user_units} must
+either match the required units of the IM or the IM must be able
+to adjust its units to match. (The latter is only possible with some KIM PMs;
+SMs can never adjust their units.) If a match is possible, the LAMMPS
+"units"_units.html command is called to set the units to
+{user_units}. If the match fails, the simulation is terminated with
+an error.
+
+Here is an example of a LAMMPS script to compute the cohesive energy
+of a face-centered cubic (fcc) lattice for the Ercolessi and Adams (1994)
+potential for Al:
+
+kim_init         EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005 metal
+boundary         p p p
+lattice          fcc 4.032
+region           simbox block 0 1 0 1 0 1 units lattice
+create_box       1 simbox
+create_atoms     1 box
+mass             1 26.981539
+kim_interactions Al
+run              0
+variable         Ec equal (pe/count(all))/$\{_u_energy\}
+print            "Cohesive Energy = $\{EcJ\} eV"
+:pre
+
+The above script will end with an error in the {kim_init} line if the
+IM is changed to another potential for Al that does not work with {metal}
+units. To address this {kim_init} offers the {unit_conversion_mode}.
+If unit conversion mode {is} active, then {kim_init} calls the LAMMPS
+"units"_units.html command to set the units to the IM's required or
+preferred units. Conversion factors between the IM's units and the {user_units}
+are defined for all "physical quantities"_units.html (mass, distance, etc.).
+(Note that converting to or from the "lj" unit style is not supported.)
+These factors are stored as "internal style variables"_variable.html with
+the following standard names:
+
+_u_mass
+_u_distance
+_u_time
+_u_energy
+_u_velocity
+_u_force
+_u_torque
+_u_temperature
+_u_pressure
+_u_viscosity
+_u_charge
+_u_dipole
+_u_efield
+_u_density :pre
+
+If desired, the input script can be designed to work with these conversion
+factors so that the script will work without change with any OpenKIM IM.
+(This approach is used in the
+"OpenKIM Testing Framework"_https://openkim.org/doc/evaluation/kim-tests/.)
+For example, the script given above for the cohesive energy of fcc Al
+can be rewritten to work with any IM regardless of units. The following
+script constructs an fcc lattice with a lattice parameter defined in
+meters, computes the total energy, and prints the cohesive energy in
+Joules regardless of the units of the IM.
+
+kim_init         EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005 si unit_conversion_mode
+boundary         p p p
+lattice          fcc 4.032e-10*$\{_u_distance\}
+region           simbox block 0 1 0 1 0 1 units lattice
+create_box       1 simbox
+create_atoms     1 box
+mass             1 4.480134e-26*$\{_u_mass\}
+kim_interactions Al
+run              0
+variable         Ec_in_J equal (pe/count(all))/$\{_u_energy\}
+print            "Cohesive Energy = $\{Ec_in_J\} J" :pre
+
+Note the multiplication by $\{_u_distance\} and $\{_u_mass\} to convert
+from SI units (specified in the {kim_init} command) to whatever units the
+IM uses (metal in this case), and the division by $\{_u_energy\}
+to convert from the IM's energy units to SI units (Joule). This script
+will work correctly for any IM for Al (KIM PM or SM) selected by the
+{kim_init} command.
+
+Care must be taken to apply unit conversion to dimensional variables read in
+from a file. For example if a configuration of atoms is read in from a
+dump file using the "read_dump"_read_dump.html command, the following can
+be done to convert the box and all atomic positions to the correct units:
+
+variable xyfinal equal xy*$\{_u_distance\}
+variable xzfinal equal xz*$\{_u_distance\}
+variable yzfinal equal yz*$\{_u_distance\}
+change_box all x scale $\{_u_distance\} &
+                       y scale $\{_u_distance\} &
+                       z scale $\{_u_distance\} &
+                       xy final $\{xyfinal\} &
+                       xz final $\{xzfinal\} &
+                       yz final $\{yzfinal\} &
+                       remap  :pre
+
+NOTE: Unit conversion will only work if the conversion factors are placed in
+all appropriate places in the input script. It is up to the user to do this
+correctly.
+
+OpenKIM IM Execution ({kim_interactions}) :h5
+
+The second and final step in using an OpenKIM IM is to execute the
+{kim_interactions} command. This command must be preceded by a {kim_init}
+command and a command that defines the number of atom types {N} (such as
+"create_box"_create_box.html).
+The {kim_interactions} command has one argument {typeargs}. This argument
+contains either a list of {N} chemical species, which defines a mapping between
+atom types in LAMMPS to the available species in the OpenKIM IM, or the
+keyword {fixed_types} for models that have a preset fixed mapping (i.e.
+the mapping between LAMMPS atom types and chemical species is defined by
+the model and cannot be changed). In the latter case, the user must consult
+the model documentation to see how many atom types there are and how they
+map to the chemical species.
+
+For example, consider an OpenKIM IM that supports Si and C species.
+If the LAMMPS simulation has four atom types, where the first three are Si,
+and the fourth is C, the following {kim_interactions} command would be used:
+
+kim_interactions Si Si Si C
+:pre
+
+Alternatively, for a model with a fixed mapping the command would be:
+
+kim_interactions fixed_types
+:pre
+
+The {kim_interactions} command performs all the necessary steps to set up
+the OpenKIM IM selected in the {kim_init} command. The specific actions depend
+on whether the IM is a KIM PM or a KIM SM.  For a KIM PM,
+a "pair_style kim"_pair_kim.html command is executed followed by
+the appropriate {pair_coeff} command. For example, for the
+Ercolessi and Adams (1994) KIM PM for Al set by the following commands:
+
+kim_init EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005 metal
+...
+...  box specification lines skipped
+...
+kim_interactions Al :pre
+
+the {kim_interactions} command executes the following LAMMPS input commands:
+
+pair_style kim EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005
+pair_coeff * * Al  :pre
+
+For a KIM SM, the generated input commands may be more complex
+and require that LAMMPS is built with the required packages included
+for the type of potential being used. The set of commands to be executed
+is defined in the SM specification file, which is part of the SM package.
+For example, for the Strachan et al. (2003) ReaxFF SM
+set by the following commands:
+
+kim_init Sim_LAMMPS_ReaxFF_StrachanVanDuinChakraborty_2003_CHNO__SM_107643900657_000 real
+...
+...  box specification lines skipped
+...
+kim_interactions C H N O  :pre
+
+the {kim_interactions} command executes the following LAMMPS input commands:
+
+pair_style reax/c lmp_control safezone 2.0 mincap 100
+pair_coeff * * ffield.reax.rdx C H N O
+fix reaxqeq all qeq/reax 1 0.0 10.0 1.0e-6 param.qeq  :pre
+
+Note that the files {lmp_control}, {ffield.reax.rdx} and {param.qeq}
+are specific to the Strachan et al. (2003) ReaxFF parameterization
+and are archived as part of the SM package in OpenKIM.
+Note also that parameters like cutoff radii and charge tolerances,
+which have an effect on IM predictions, are also included in the
+SM definition ensuring reproducibility.
+
+NOTE: When using {kim_init} and {kim_interactions} to select
+and set up an OpenKIM IM, other LAMMPS commands
+for the same functions (such as pair_style, pair_coeff, bond_style,
+bond_coeff, fixes related to charge equilibration, etc.) should normally
+not appear in the input script.
+
+Using OpenKIM Web Queries in LAMMPS ({kim_query}) :h5
+
+The {kim_query} command performs a web query to retrieve the predictions
+of the IM set by {kim_init} for material properties archived in
+"OpenKIM"_https://openkim.org.  The {kim_query} command must be preceded
+by a {kim_init} command. The result of the query is stored in a
+"string style variable"_variable.html, the name of which is given as the first
+argument of the {kim_query command}.  (For the case of multiple
+return values, the optional {split} keyword can be used after the
+variable name to separate the results into multiple variables; see
+the "example"_#split_example below.)
+The second required argument {query_function} is the name of the
+query function to be called (e.g. {get_lattice_constant_cubic}).
+All following "arguments"_Commands_parse.html are parameters handed over to
+the web query in the format {keyword=value}, where {value} is always
+an array of one or more comma-separated items in brackets.
+The list of supported keywords and the type and format of their values
+depend on the query function used. The current list of query functions
+is available on the OpenKIM webpage at
+"https://openkim.org/doc/usage/kim-query"_https://openkim.org/doc/usage/kim-query.
+
+NOTE: All query functions require the {model} keyword, which identifies
+the IM whose predictions are being queried. This keyword is automatically
+generated by {kim_query} based on the IM set in {kim_init} and must not
+be specified as an argument to {kim_query}.
+
+NOTE: Each {query_function} is associated with a default method (implemented
+as a "KIM Test"_https://openkim.org/doc/evaluation/kim-tests/)
+used to compute this property. In cases where there are multiple
+methods in OpenKIM for computing a property, a {method} keyword can
+be provided to select the method of choice.  See the
+"query documentation"_https://openkim.org/doc/repository/kim-query
+to see which methods are available for a given {query function}.
+
+{kim_query} Usage Examples and Further Clarifications: :h6
+
+The data obtained by {kim_query} commands can be used as part of the setup
+or analysis phases of LAMMPS simulations. Some examples are given below.
+
+[Define an equilibrium fcc crystal]
+
+kim_init         EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005 metal
+boundary         p p p
+kim_query        a0 get_lattice_constant_cubic crystal=\["fcc"\] species=\["Al"\] units=\["angstrom"\]
+lattice          fcc $\{a0\}
+... :pre
+
+The {kim_query} command retrieves from "OpenKIM"_https://openkim.org
+the equilibrium lattice constant predicted by the Ercolessi and Adams (1994)
+potential for the fcc structure and places it in
+variable {a0}. This variable is then used on the next line to set up the
+crystal. By using {kim_query}, the user is saved the trouble and possible
+error of tracking this value down, or of having to perform an energy
+minimization to find the equilibrium lattice constant.
+
+Note that in {unit_conversion_mode} the results obtained from a
+{kim_query} would need to be converted to the appropriate units system.
+For example, in the above script, the lattice command would need to be
+changed to: "lattice fcc $\{a0\}*$\{_u_distance\}".
+
+:link(split_example)
+[Define an equilibrium hcp crystal]
+
+kim_init         EAM_Dynamo_Mendelev_2007_Zr__MO_848899341753_000 metal
+boundary         p p p
+kim_query        latconst split get_lattice_constant_hexagonal crystal=\["hcp"\] species=\["Zr"\] units=\["angstrom"\]
+variable         a0 equal latconst_1
+variable         c0 equal latconst_2
+variable         c_to_a equal $\{c0\}/$\{a0\}
+lattice          custom $\{a0\} a1 0.5 -0.866025 0 a2 0.5 0.866025 0 a3 0 0 $\{c_to_a\} &
+                 basis 0.333333 0.666666 0.25 basis 0.666666 0.333333 0.75
+... :pre
+
+In this case the {kim_query} returns two arguments (since the hexagonal
+close packed (hcp) structure has two independent lattice constants).
+The default behavior of {kim_query} returns the result as a string
+with the values separated by commas. The optional keyword {split}
+separates the result values into individual variables of the form
+{prefix_I}, where {prefix} is set to the the {kim_query} {variable} argument
+and {I} ranges from 1 to the number of returned values. The number and order of
+the returned values is determined by the type of query performed.
+
+[Define a crystal at finite temperature accounting for thermal expansion]
+
+kim_init         EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005 metal
+boundary         p p p
+kim_query        a0 get_lattice_constant_cubic crystal=\["fcc"\] species=\["Al"\] units=\["angstrom"\]
+kim_query        alpha get_linear_thermal_expansion_coefficient_cubic  crystal=\["fcc"\] species=\["Al"\] units=\["1/K"\] temperature=\[293.15\] temperature_units=\["K"\]
+variable         DeltaT equal 300
+lattice          fcc $\{a0\}*$\{alpha\}*$\{DeltaT\}
+... :pre
+
+As in the previous example, the equilibrium lattice constant is obtained
+for the Ercolessi and Adams (1994) potential. However, in this case the
+crystal is scaled to the appropriate lattice constant at room temperature
+(293.15 K) by using the linear thermal expansion constant predicted by the
+potential.
+
+NOTE: When passing numerical values as arguments (as in the case
+of the temperature in the above example) it is also possible to pass a
+tolerance indicating how close to the value is considered a match.
+If no tolerance is passed a default value is used. If multiple results
+are returned (indicating that the tolerance is too large), {kim_query}
+will return an error. See the
+"query documentation"_https://openkim.org/doc/repository/kim-query
+to see which numerical arguments and tolerances are available for a
+given {query function}.
+
+[Compute defect formation energy]
+
+kim_init         EAM_Dynamo_ErcolessiAdams_1994_Al__MO_123629422045_005 metal
+...
+... Build fcc crystal containing some defect and compute the total energy
+... which is stored in the variable {Etot}
+...
+kim_query        Ec get_cohesive_energy_cubic crystal=\["fcc"\] species=\["Al"\] units=\["eV"\]
+variable         Eform equal $\{Etot\} - count(all)*$\{Ec\}
+... :pre
+
+The defect formation energy {Eform} is computed by subtracting from {Etot} the
+ideal fcc cohesive energy of the atoms in the system obtained from
+"OpenKIM"_https://openkim.org for the Ercolessi and Adams (1994) potential.
+
+NOTE: {kim_query} commands return results archived in
+"OpenKIM"_https://openkim.org. These results are obtained
+using programs for computing material properties
+(KIM Tests and KIM Test Drivers) that were contributed to OpenKIM.
+In order to give credit to Test developers, the number of times results
+from these programs are queried is tracked. No other information about
+the nature of the query or its source is recorded.
+
+
+Citation of OpenKIM IMs :h4
+
+When publishing results obtained using OpenKIM IMs researchers are requested
+to cite the OpenKIM project "(Tadmor)"_#kim-mainpaper, KIM API
+"(Elliott)"_#kim-api, and the specific IM codes used in the simulations,
+in addition to the relevant scientific references for the IM.
+The citation format for an IM is displayed on its page on
+"OpenKIM"_https://openkim.org along with the corresponding BibTex file,
+and is automatically added to the LAMMPS {log.cite} file.
+
+Citing the IM software (KIM infrastructure and specific PM or SM codes)
+used in the simulation gives credit to the researchers who developed them
+and enables open source efforts like OpenKIM to function.
+
+
+[Restrictions:]
+
+The set of {kim_commands} is part of the KIM package.  It is only enabled if
+LAMMPS is built with that package. A requirement for the KIM package,
+is the KIM API library that must be downloaded from the
+"OpenKIM website"_https://openkim.org/kim-api/ and installed before
+LAMMPS is compiled. When installing LAMMPS from binary, the kim-api package
+is a dependency that is automatically downloaded and installed. See the KIM
+section of the "Packages details"_Packages_details.html for details.
+
+Furthermore, when using {kim_commands} to run KIM SMs, any packages required
+by the native potential being used or other commands or fixes that it invokes
+must be installed.
+
+[Related commands:]
+
+"pair_style kim"_pair_kim.html
+
+:line
+
+:link(kim-mainpaper)
+[(Tadmor)] Tadmor, Elliott, Sethna, Miller and Becker, JOM, 63, 17 (2011).
+doi: "https://doi.org/10.1007/s11837-011-0102-6"_https://doi.org/10.1007/s11837-011-0102-6
+
+:link(kim-api)
+[(Elliott)] Elliott, Tadmor and Bernstein, "https://openkim.org/kim-api"_https://openkim.org/kim-api (2011)
+doi: "https://doi.org/10.25950/FF8F563A"_https://doi.org/10.25950/FF8F563A

doc/src/kim_query.txt

@@ -1,46 +0,0 @@
-"LAMMPS WWW Site"_lws - "LAMMPS Documentation"_ld - "LAMMPS Commands"_lc :c
-
-:link(lws,http://lammps.sandia.gov)
-:link(ld,Manual.html)
-:link(lc,Commands_all.html)
-
-:line
-
-kim_query command :h3
-
-[Syntax:]
-
-kim_query variable query_function web_query_flags :pre
-
-variable = name of a (string style) variable where the result of the query is stored
-query_function = name of the OpenKIM web API query function to be used
-web_query_flags = a series of keyword=value pairs that represent the web query; supported keywords depend on query function :ul
-
-[Examples:]
-
-kim_query latconst get_test_result test=TE_156715955670 model=MO_800509458712 &
-  prop=structure-cubic-crystal-npt species=\["Al"\] keys=\["a"\] units=\["angstrom"\] :pre
-
-[Description:]
-
-The kim_query command allows to retrieve properties from the OpenKIM
-through a web query. The result is stored in a string style
-"variable"_variable.html, the name of which must be given as the first
-argument of the kim_query command.  The second required argument is the
-name of the actual query function (e.g. {get_test_result}).  All following
-arguments are parameters handed over to the web query in the format
-{keyword=value}.  The list of supported keywords and the type of how
-the value has to be encoded depends on the query function used.  This
-mirrors the functionality available on the OpenKIM webpage at
-"https://query.openkim.org"_https://query.openkim.org/
-
-[Restrictions:]
-
-This command is part of the KIM package.  It is only enabled if
-LAMMPS was built with that package.  Furthermore, its correct
-functioning depends on compiling LAMMPS with libcurl support.
-See the "Build package"_Build_package.html doc page for more info.
-
-[Related commands:]
-
-"pair_style kim"_pair_kim.html, "variable"_variable.html

doc/src/lammps.book

@@ -42,6 +42,7 @@ Commands_compute.html
 Commands_pair.html
 Commands_bond.html
 Commands_kspace.html
+Commands_removed.html
 Packages.html
 Packages_standard.html
 Packages_user.html
@@ -167,7 +168,7 @@ if.html
 include.html
 info.html
 jump.html
-kim_query.html
+kim_commands.html
 label.html
 lattice.html
 log.html
@@ -455,6 +456,7 @@ compute_global_atom.html
 compute_group_group.html
 compute_gyration.html
 compute_gyration_chunk.html
+compute_gyration_shape.html
 compute_heat_flux.html
 compute_hexorder_atom.html
 compute_improper.html
@@ -468,6 +470,7 @@ compute_ke_rigid.html
 compute_meso_e_atom.html
 compute_meso_rho_atom.html
 compute_meso_t_atom.html
+compute_momentum.html
 compute_msd.html
 compute_msd_chunk.html
 compute_msd_nongauss.html
@@ -647,6 +650,7 @@ pair_sph_lj.html
 pair_sph_rhosum.html
 pair_sph_taitwater.html
 pair_sph_taitwater_morris.html
+pair_spin_dipole.html
 pair_spin_dmi.html
 pair_spin_exchange.html
 pair_spin_magelec.html

doc/src/package.txt

@@ -64,7 +64,7 @@ args = arguments specific to the style :l
       {no_affinity} values = none
   {kokkos} args = keyword value ...
     zero or more keyword/value pairs may be appended
-    keywords = {neigh} or {neigh/qeq} or {neigh/thread} or {newton} or {binsize} or {comm} or {comm/exchange} or {comm/forward} or {comm/reverse} or {gpu/direct}
+    keywords = {neigh} or {neigh/qeq} or {neigh/thread} or {newton} or {binsize} or {comm} or {comm/exchange} or {comm/forward} or {comm/reverse} or {cuda/aware}
       {neigh} value = {full} or {half}
         full = full neighbor list
         half = half neighbor list built in thread-safe manner
@@ -87,9 +87,9 @@ args = arguments specific to the style :l
         no = perform communication pack/unpack in non-KOKKOS mode
         host = perform pack/unpack on host (e.g. with OpenMP threading)
         device = perform pack/unpack on device (e.g. on GPU)
-      {gpu/direct} = {off} or {on}
-        off = do not use GPU-direct
-        on = use GPU-direct (default)
+      {cuda/aware} = {off} or {on}
+        off = do not use CUDA-aware MPI
+        on = use CUDA-aware MPI (default)
   {omp} args = Nthreads keyword value ...
     Nthread = # of OpenMP threads to associate with each MPI process
     zero or more keyword/value pairs may be appended
@@ -520,19 +520,21 @@ pack/unpack communicated data. When running small systems on a GPU,
 performing the exchange pack/unpack on the host CPU can give speedup 
 since it reduces the number of CUDA kernel launches.
 
-The {gpu/direct} keyword chooses whether GPU-direct will be used. When 
+The {cuda/aware} keyword chooses whether CUDA-aware MPI will be used. When 
 this keyword is set to {on}, buffers in GPU memory are passed directly 
 through MPI send/receive calls. This reduces overhead of first copying 
-the data to the host CPU. However GPU-direct is not supported on all 
+the data to the host CPU. However CUDA-aware MPI is not supported on all 
 systems, which can lead to segmentation faults and would require using a 
-value of {off}. If LAMMPS can safely detect that GPU-direct is not 
+value of {off}. If LAMMPS can safely detect that CUDA-aware MPI is not 
 available (currently only possible with OpenMPI v2.0.0 or later), then 
-the {gpu/direct} keyword is automatically set to {off} by default. When 
-the {gpu/direct} keyword is set to {off} while any of the {comm} 
+the {cuda/aware} keyword is automatically set to {off} by default. When 
+the {cuda/aware} keyword is set to {off} while any of the {comm} 
 keywords are set to {device}, the value for these {comm} keywords will 
 be automatically changed to {host}. This setting has no effect if not 
-running on GPUs. GPU-direct is available for OpenMPI 1.8 (or later 
-versions), Mvapich2 1.9 (or later), and CrayMPI.
+running on GPUs. CUDA-aware MPI is available for OpenMPI 1.8 (or later 
+versions), Mvapich2 1.9 (or later) when the "MV2_USE_CUDA" environment
+variable is set to "1", CrayMPI, and IBM Spectrum MPI when the "-gpu"
+flag is used.
 
 :line
 
@@ -641,8 +643,8 @@ switch"_Run_options.html.
 
 For the KOKKOS package, the option defaults for GPUs are neigh = full, 
 neigh/qeq = full, newton = off, binsize for GPUs = 2x LAMMPS default 
-value, comm = device, gpu/direct = on. When LAMMPS can safely detect 
-that GPU-direct is not available, the default value of gpu/direct 
+value, comm = device, cuda/aware = on. When LAMMPS can safely detect 
+that CUDA-aware MPI is not available, the default value of cuda/aware 
 becomes "off". For CPUs or Xeon Phis, the option defaults are neigh = 
 half, neigh/qeq = half, newton = on, binsize = 0.0, and comm = no. The 
 option neigh/thread = on when there are 16K atoms or less on an MPI 

doc/src/pair_adp.txt

@@ -42,16 +42,17 @@ the ADP potential files themselves.  Likewise, the ADP potential files
 list atomic masses; thus you do not need to use the "mass"_mass.html
 command to specify them.
 
-The NIST WWW site distributes and documents ADP potentials:
+[ADP potentials are available from:]
 
-http://www.ctcms.nist.gov/potentials :pre
+The NIST WWW site at http://www.ctcms.nist.gov/potentials.
+Note that ADP potentials obtained from NIST must be converted
+into the extended DYNAMO {setfl} format discussed below.
+:l
 
-Note that these must be converted into the extended DYNAMO {setfl}
-format discussed below.
-
-The NIST site is maintained by Chandler Becker (cbecker at nist.gov)
-who is good resource for info on interatomic potentials and file
-formats.
+The OpenKIM Project at https://openkim.org/browse/models/by-type provides
+ADP potentials that can be used directly in LAMMPS with the "kim_commands
+interface"_kim_commands.html.
+:l
 
 :line
 

doc/src/pair_class2.txt

@@ -155,7 +155,7 @@ All of the lj/class2 pair styles write their information to "binary
 restart files"_restart.html, so pair_style and pair_coeff commands do
 not need to be specified in an input script that reads a restart file.
 
-Only the {lj/class2} pair style support the use of the
+Only the {lj/class2} and {lj/class2/coul/long} pair styles support the use of the
 {inner}, {middle}, and {outer} keywords of the "run_style
 respa"_run_style.html command, meaning the pairwise forces can be
 partitioned by distance at different levels of the rRESPA hierarchy.

doc/src/pair_coul_shield.txt

@@ -13,7 +13,7 @@ pair_style coul/shield command :h3
 pair_style coul/shield cutoff tap_flag :pre
 
 cutoff = global cutoff (distance units)
-tap_flag = 0/1 to turn off/on the taper function
+tap_flag = 0/1 to turn off/on the taper function :ul
 
 [Examples:]
 

doc/src/pair_hbond_dreiding.txt

@@ -46,7 +46,7 @@ Here, {r} is the radial distance between the donor (D) and acceptor
 (A) atoms and {theta} is the bond angle between the acceptor, the
 hydrogen (H) and the donor atoms:
 
-:c,image(Eqs/dreiding_hbond.jpg)
+:c,image(JPG/dreiding_hbond.jpg)
 
 These 3-body interactions can be defined for pairs of acceptor and
 donor atoms, based on atom types.  For each donor/acceptor atom pair,

doc/src/pair_ilp_graphene_hbn.txt

@@ -13,17 +13,17 @@ pair_style ilp/graphene/hbn command :h3
 pair_style \[hybrid/overlay ...\] ilp/graphene/hbn cutoff tap_flag :pre
 
 cutoff = global cutoff (distance units)
-tap_flag = 0/1 to turn off/on the taper function
+tap_flag = 0/1 to turn off/on the taper function :ul
 
 [Examples:]
 
-pair_style hybrid/overlay ilp/graphene/hbn 16.0 1
-pair_coeff * * ilp/graphene/hbn  BNCH.ILP B N C :pre
+pair_style  hybrid/overlay ilp/graphene/hbn 16.0 1
+pair_coeff  * * ilp/graphene/hbn  BNCH.ILP B N C :pre
 
 pair_style  hybrid/overlay rebo tersoff ilp/graphene/hbn 16.0 coul/shield 16.0
-pair_coeff  * * rebo                 CH.rebo     NULL NULL C
-pair_coeff  * * tersoff              BNC.tersoff B    N    NULL
-pair_coeff  * * ilp/graphene/hbn     BNCH.ILP    B    N    C
+pair_coeff  * * rebo              CH.rebo     NULL NULL C
+pair_coeff  * * tersoff           BNC.tersoff B    N    NULL
+pair_coeff  * * ilp/graphene/hbn  BNCH.ILP    B    N    C
 pair_coeff  1 1 coul/shield 0.70
 pair_coeff  1 2 coul/shield 0.695
 pair_coeff  2 2 coul/shield 0.69 :pre
@@ -85,6 +85,22 @@ be found in "(Ouyang)"_#Ouyang.
 This potential must be used in combination with hybrid/overlay.
 Other interactions can be set to zero using pair_style {none}.
 
+This pair style tallies a breakdown of the total interlayer potential
+energy into sub-categories, which can be accessed via the "compute
+pair"_compute_pair.html command as a vector of values of length 2.
+The 2 values correspond to the following sub-categories:
+
+{E_vdW} = vdW (attractive) energy
+{E_Rep} = Repulsive energy :ol
+
+To print these quantities to the log file (with descriptive column
+headings) the following commands could be included in an input script:
+
+compute 0 all pair ilp/graphene/hbn
+variable Evdw  equal c_0\[1\]
+variable Erep  equal c_0\[2\]
+thermo_style custom step temp epair v_Erep v_Evdw :pre
+
 :line
 
 [Mixing, shift, table, tail correction, restart, rRESPA info]:

doc/src/pair_kim.txt

@@ -12,76 +12,72 @@ pair_style kim command :h3
 
 pair_style kim model :pre
 
-model = name of KIM model (potential)
+model = name of a KIM model (the KIM ID for models archived in OpenKIM)
 
 [Examples:]
 
-pair_style kim ex_model_Ar_P_LJ
-pair_coeff * * Ar Ar :pre
+pair_style kim SW_StillingerWeber_1985_Si__MO_405512056662_005
+pair_coeff * * Si :pre
 
 [Description:]
 
-This pair style is a wrapper on the "Knowledge Base for Interatomic
+This pair style is a wrapper on the "Open Knowledgebase of Interatomic
 Models (OpenKIM)"_https://openkim.org repository of interatomic
-potentials, so that they can be used by LAMMPS scripts.
+potentials to enable their use in LAMMPS scripts.
 
-Note that in LAMMPS lingo, a KIM model driver is a pair style
-(e.g. EAM or Tersoff).  A KIM model is a pair style for a particular
-element or alloy and set of parameters, e.g. EAM for Cu with a
-specific EAM potential file.
+The preferred interface for using interatomic models archived in
+OpenKIM is the "kim_commands interface"_kim_commands.html. That
+interface supports both "KIM Portable Models" (PMs) that conform to the
+KIM API Portable Model Interface (PMI) and can be used by any
+simulation code that conforms to the KIM API/PMI, and
+"KIM Simulator Models" that are natively implemented within a single
+simulation code (like LAMMPS) and can only be used with it.
+The {pair_style kim} command is limited to KIM PMs. It is
+used by the "kim_commands interface"_kim_commands.html as needed.
 
-See the current list of "KIM model
-drivers"_https://openkim.org/browse/model-drivers/alphabetical.
+NOTE: Since {pair_style kim} is called by {kim_interactions} as needed,
+is not recommended to be directly used in input scripts.
 
-See the current list of all "KIM
-models"_https://openkim.org/browse/models/by-model-drivers
-
-To use this pair style, you must first download and install the KIM
-API library from the "OpenKIM website"_https://openkim.org.  The KIM
-section of the "Packages details"_Packages_details.html doc page has
-instructions on how to do this with a simple make command, when
-building LAMMPS.
-
-See the examples/kim dir for an input script that uses a KIM model
-(potential) for Lennard-Jones.
- 
 :line
 
-The argument {model} is the name of the KIM model for a specific
-potential as KIM defines it.  In principle, LAMMPS can invoke any KIM
-model.  You should get an error or warning message from either LAMMPS
-or KIM if there is an incompatibility.
+The argument {model} is the name of the KIM PM.
+For potentials archived in OpenKIM
+this is the extended KIM ID (see "kim_commands"_kim_commands.html
+for details). LAMMPS can invoke any KIM PM, however there can
+be incompatibilities (for example due to unit matching issues).
+In the event of an incompatibility, the code will terminate with
+an error message. Check both the LAMMPS and KIM log files for details.
 
-Only a single pair_coeff command is used with the {kim} style which
-specifies the mapping of LAMMPS atom types to KIM elements.  This is
-done by specifying N additional arguments after the * * in the
-pair_coeff command, where N is the number of LAMMPS atom types:
+Only a single {pair_coeff} command is used with the {kim} style, which
+specifies the mapping of LAMMPS atom types to the species supported by
+the KIM PM.  This is done by specifying {N} additional arguments
+after the * * in the {pair_coeff} command, where {N} is the number of
+LAMMPS atom types:
 
 N element names = mapping of KIM elements to atom types :ul
 
-As an example, imagine the KIM model supports Si and C atoms.  If your
-LAMMPS simulation has 4 atom types and you want the 1st 3 to be Si,
-and the 4th to be C, you would use the following pair_coeff command:
+For example, consider a KIM PM that supports Si and C species.
+If the LAMMPS simulation has four atom types, where the first three are Si,
+and the fourth is C, the following {pair_coeff} command would be used:
 
 pair_coeff * * Si Si Si C :pre
 
-The 1st 2 arguments must be * * so as to span all LAMMPS atom types.
-The first three Si arguments map LAMMPS atom types 1,2,3 to Si as
-defined within KIM.  The final C argument maps LAMMPS atom type 4 to C
-as defined within KIM.
+The first two arguments must be * * so as to span all LAMMPS atom types.
+The first three Si arguments map LAMMPS atom types 1, 2, and 3 to Si as
+defined within KIM PM.  The final C argument maps LAMMPS atom type 4 to C.
 
 :line
 
 In addition to the usual LAMMPS error messages, the KIM library itself
 may generate errors, which should be printed to the screen.  In this
-case it is also useful to check the kim.log file for additional error
-information.  The file kim.log should be generated in the same
+case it is also useful to check the {kim.log} file for additional error
+information.  The file {kim.log} should be generated in the same
 directory where LAMMPS is running.
 
 To download, build, and install the KIM library on your system, see
-the lib/kim/README file.  Once you have done this and built LAMMPS
+the {lib/kim/README} file.  Once you have done this and built LAMMPS
 with the KIM package installed you can run the example input scripts
-in examples/kim.
+in {examples/kim}.
 
 :line
 
@@ -103,15 +99,14 @@ This pair style can only be used via the {pair} keyword of the
 
 [Restrictions:]
 
-This pair style is part of the KIM package.  It is only enabled if
-LAMMPS was built with that package.  See the "Build
-package"_Build_package.html doc page for more info.
+This pair style is part of the KIM package. See details on
+restrictions in "kim_commands"_kim_commands.html.
 
 This current version of pair_style kim is compatible with the
 kim-api package version 2.0.0 and higher.
 
 [Related commands:]
 
-"pair_coeff"_pair_coeff.html
+"pair_coeff"_pair_coeff.html, "kim_commands"_kim_commands.html
 
 [Default:] none

doc/src/pair_kolmogorov_crespi_full.txt

@@ -13,7 +13,7 @@ pair_style kolmogorov/crespi/full command :h3
 pair_style hybrid/overlay kolmogorov/crespi/full cutoff tap_flag :pre
 
 cutoff = global cutoff (distance units)
-tap_flag = 0/1 to turn off/on the taper function
+tap_flag = 0/1 to turn off/on the taper function :ul
 
 [Examples:]
 
@@ -74,6 +74,22 @@ comparison of these parameters can be found in "(Ouyang)"_#Ouyang1.
 This potential must be used in combination with hybrid/overlay.
 Other interactions can be set to zero using pair_style {none}.
 
+This pair style tallies a breakdown of the total interlayer potential
+energy into sub-categories, which can be accessed via the "compute
+pair"_compute_pair.html command as a vector of values of length 2.
+The 2 values correspond to the following sub-categories:
+
+{E_vdW} = vdW (attractive) energy
+{E_Rep} = Repulsive energy :ol
+
+To print these quantities to the log file (with descriptive column
+headings) the following commands could be included in an input script:
+
+compute 0 all pair kolmogorov/crespi/full
+variable Evdw  equal c_0\[1\]
+variable Erep  equal c_0\[2\]
+thermo_style custom step temp epair v_Erep v_Evdw :pre
+
 :line
 
 [Mixing, shift, table, tail correction, restart, rRESPA info]:

doc/src/pair_meamc.txt

@@ -147,7 +147,8 @@ asub     = "A" parameter for MEAM (see e.g. "(Baskes)"_#Baskes) :pre
 
 The alpha, b0, b1, b2, b3, t0, t1, t2, t3 parameters correspond to the
 standard MEAM parameters in the literature "(Baskes)"_#Baskes (the b
-parameters are the standard beta parameters).  The rozero parameter is
+parameters are the standard beta parameters). Note that only parameters
+normalized to t0 = 1.0 are supported.  The rozero parameter is
 an element-dependent density scaling that weights the reference
 background density (see e.g. equation 4.5 in "(Gullet)"_#Gullet) and
 is typically 1.0 for single-element systems.  The ibar parameter

doc/src/pair_modify.txt

@@ -13,7 +13,8 @@ pair_modify command :h3
 pair_modify keyword values ... :pre
 
 one or more keyword/value pairs may be listed :ulb,l
-keyword = {pair} or {shift} or {mix} or {table} or {table/disp} or {tabinner} or {tabinner/disp} or {tail} or {compute} :l
+keyword = {pair} or {shift} or {mix} or {table} or {table/disp} or {tabinner}
+or {tabinner/disp} or {tail} or {compute} or {nofdotr} :l
   {pair} values = sub-style N {special} which wt1 wt2 wt3
                or sub-style N {compute/tally} flag
     sub-style = sub-style of "pair hybrid"_pair_hybrid.html
@@ -33,7 +34,8 @@ keyword = {pair} or {shift} or {mix} or {table} or {table/disp} or {tabinner} or
   {tabinner/disp} value = cutoff
     cutoff = inner cutoff at which to begin table (distance units)
   {tail} value = {yes} or {no}
-  {compute} value = {yes} or {no} :pre
+  {compute} value = {yes} or {no}
+  {nofdotr} :pre
 :ule
 
 [Examples:]
@@ -212,6 +214,10 @@ a pair style will not work, because the
 "kspace_style"_kspace_style.html command requires a Kspace-compatible
 pair style be defined.
 
+The {nofdotr} keyword allows to disable an optimization that computes
+the global stress tensor from the total forces and atom positions rather
+than from summing forces between individual pairs of atoms.
+
 :line
 
 The {special} keyword allows to override the 1-2, 1-3, and 1-4

doc/src/pair_oxdna.txt

@@ -23,9 +23,11 @@ style1 = {hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxs
 style2 = {oxdna/excv} or {oxdna/stk} or {oxdna/hbond} or {oxdna/xstk} or {oxdna/coaxstk}
 args = list of arguments for these particular styles :ul
 
-  {oxdna/stk} args = seq T 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
+  {oxdna/stk} args = seq T xi kappa 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
     seq = seqav (for average sequence stacking strength) or seqdep (for sequence-dependent stacking strength)
     T = temperature (oxDNA units, 0.1 = 300 K)
+    xi = temperature-independent coefficient in stacking strength
+    kappa = coefficient of linear temperature dependence in stacking strength
   {oxdna/hbond} args = seq eps 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
     seq = seqav (for average sequence base-pairing strength) or seqdep (for sequence-dependent base-pairing strength)
     eps = 1.077 (between base pairs A-T and C-G) or 0 (all other pairs) :pre
@@ -34,7 +36,7 @@ args = list of arguments for these particular styles :ul
 
 pair_style hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxstk
 pair_coeff * * oxdna/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna/stk     seqdep 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
+pair_coeff * * oxdna/stk     seqdep 0.1 1.3448 2.6568 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
 pair_coeff * * oxdna/hbond   seqdep 0.0 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 1 4 oxdna/hbond   seqdep 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 2 3 oxdna/hbond   seqdep 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
@@ -62,7 +64,7 @@ NOTE: These pair styles have to be used together with the related oxDNA bond sty
 {oxdna/fene} for the connectivity of the phosphate backbone (see also documentation of
 "bond_style oxdna/fene"_bond_oxdna.html). Most of the coefficients
 in the above example have to be kept fixed and cannot be changed without reparameterizing the entire model.
-Exceptions are the first and second coefficient after {oxdna/stk} (seq=seqdep and T=0.1 in the above example)
+Exceptions are the first four coefficients after {oxdna/stk} (seq=seqdep, T=0.1, xi=1.3448 and kappa=2.6568 in the above example)
 and the first coefficient after {oxdna/hbond} (seq=seqdep in the above example).
 When using a Langevin thermostat, e.g. through "fix langevin"_fix_langevin.html
 or "fix nve/dotc/langevin"_fix_nve_dotc_langevin.html

doc/src/pair_oxdna2.txt

@@ -24,10 +24,12 @@ style1 = {hybrid/overlay oxdna2/excv oxdna2/stk oxdna2/hbond oxdna2/xstk oxdna2/
 style2 = {oxdna2/excv} or {oxdna2/stk} or {oxdna2/hbond} or {oxdna2/xstk} or {oxdna2/coaxstk} or {oxdna2/dh}
 args = list of arguments for these particular styles :ul
 
-  {oxdna2/stk} args = seq T 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
+  {oxdna2/stk} args = seq T xi kappa 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
     seq = seqav (for average sequence stacking strength) or seqdep (for sequence-dependent stacking strength)
     T = temperature (oxDNA units, 0.1 = 300 K)
-  {oxdna/hbond} args = seq eps 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
+    xi = temperature-independent coefficient in stacking strength 
+    kappa = coefficient of linear temperature dependence in stacking strength 
+  {oxdna2/hbond} args = seq eps 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
     seq = seqav (for average sequence base-pairing strength) or seqdep (for sequence-dependent base-pairing strength)
     eps = 1.0678 (between base pairs A-T and C-G) or 0 (all other pairs)
   {oxdna2/dh} args = T rhos qeff
@@ -39,7 +41,7 @@ args = list of arguments for these particular styles :ul
 
 pair_style hybrid/overlay oxdna2/excv oxdna2/stk oxdna2/hbond oxdna2/xstk oxdna2/coaxstk oxdna2/dh
 pair_coeff * * oxdna2/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna2/stk     seqdep 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
+pair_coeff * * oxdna2/stk     seqdep 0.1 1.3523 2.6717 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
 pair_coeff * * oxdna2/hbond   seqdep 0.0 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 1 4 oxdna2/hbond   seqdep 1.0678 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 2 3 oxdna2/hbond   seqdep 1.0678 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
@@ -68,8 +70,8 @@ NOTE: These pair styles have to be used together with the related oxDNA2 bond st
 {oxdna2/fene} for the connectivity of the phosphate backbone (see also documentation of
 "bond_style oxdna2/fene"_bond_oxdna.html). Most of the coefficients
 in the above example have to be kept fixed and cannot be changed without reparameterizing the entire model.
-Exceptions are the first and the second coefficient after {oxdna2/stk} (seq=seqdep and T=0.1 in the above example),
-the first coefficient after {oxdna/hbond} (seq=seqdep in the above example) and the three coefficients
+Exceptions are the first four coefficients after {oxdna2/stk} (seq=seqdep, T=0.1, xi=1.3523 and kappa=2.6717 in the above example),
+the first coefficient after {oxdna2/hbond} (seq=seqdep in the above example) and the three coefficients
 after {oxdna2/dh} (T=0.1, rhos=1.0, qeff=0.815 in the above example). When using a Langevin thermostat
 e.g. through "fix langevin"_fix_langevin.html or "fix nve/dotc/langevin"_fix_nve_dotc_langevin.html
 the temperature coefficients have to be matched to the one used in the fix.

doc/src/pair_spin_dipole.txt

@@ -81,9 +81,3 @@ currently supported.
 "fix nve/spin"_fix_nve_spin.html
 
 [Default:] none
-
-:line
-
-:link(Allen2)
-[(Allen)] Allen and Tildesley, Computer Simulation of Liquids,
-Clarendon Press, Oxford, 1987.

doc/src/pair_style.txt

@@ -284,6 +284,8 @@ accelerated styles exist.
 "sph/rhosum"_pair_sph_rhosum.html -
 "sph/taitwater"_pair_sph_taitwater.html -
 "sph/taitwater/morris"_pair_sph_taitwater_morris.html -
+"spin/dipole/cut"_pair_spin_dipole.html -
+"spin/dipole/long"_pair_spin_dipole.html -
 "spin/dmi"_pair_spin_dmi.html -
 "spin/exchange"_pair_spin_exchange.html -
 "spin/magelec"_pair_spin_magelec.html -

doc/src/pairs.txt

@@ -105,6 +105,7 @@ Pair Styles :h1
    pair_sph_rhosum
    pair_sph_taitwater
    pair_sph_taitwater_morris
+   pair_spin_dipole
    pair_spin_dmi
    pair_spin_exchange
    pair_spin_magelec

doc/src/read_data.txt

@@ -565,6 +565,7 @@ molecular: atom-ID molecule-ID atom-type x y z
 peri: atom-ID atom-type volume density x y z
 smd: atom-ID atom-type molecule volume mass kernel-radius contact-radius x y z
 sphere: atom-ID atom-type diameter density x y z
+spin: atom-ID atom-type sp x y z spx spy spz
 template: atom-ID molecule-ID template-index template-atom atom-type x y z
 tri: atom-ID molecule-ID atom-type triangleflag density x y z
 wavepacket: atom-ID atom-type charge spin eradius etag cs_re cs_im x y z
@@ -595,6 +596,8 @@ mux,muy,muz = components of dipole moment of atom (dipole units)
 q = charge on atom (charge units)
 rho = density (need units) for SPH particles
 spin = electron spin (+1/-1), 0 = nuclei, 2 = fixed-core, 3 = pseudo-cores (i.e. ECP)
+sp = norm of magnetic spin of atom (in number of Bohr magnetons)
+spx,spy,spz = components of magnetic spin of atom (adim normalized vector)
 template-atom = which atom within a template molecule the atom is
 template-index = which molecule within the molecule template the atom is part of
 theta = internal temperature of a DPD particle

doc/src/replicate.txt

@@ -14,7 +14,8 @@ replicate nx ny nz {keyword} :pre
 
 nx,ny,nz = replication factors in each dimension :ulb
 optional {keyword} = {bbox} :l
-  {bbox} = only check atoms in replicas that overlap with a processor's sub-domain :ule
+  {bbox} = only check atoms in replicas that overlap with a processor's sub-domain :pre
+:ule
 
 [Examples:]
 
@@ -45,11 +46,13 @@ file that crosses a periodic boundary should be between two atoms with
 image flags that differ by 1.  This will allow the bond to be
 unwrapped appropriately.
 
-The optional keyword {bbox} uses a bounding box to only check atoms
-in replicas that overlap with a processor's sub-domain when assigning
-atoms to processors, and thus can result in substantial speedups for
-calculations using a large number of processors. It does require
-temporarily using more memory.
+The optional keyword {bbox} uses a bounding box to only check atoms in
+replicas that overlap with a processor's sub-domain when assigning
+atoms to processors.  It typically results in a substantial speedup
+when using the replicate command on a large number of processors.  It
+does require temporary use of more memory, specifically that each
+processor can store all atoms in the entire system before it is
+replicated.
 
 [Restrictions:]
 

doc/utils/sphinx-config/_themes/lammps_theme/static/css/theme.css

@@ -5092,4 +5092,17 @@ span[id*='MathJax-Span'] {
   src: local("Roboto Slab Bold"), local("RobotoSlab-Bold"), url(../fonts/RobotoSlab-Bold.ttf) format("truetype");
 }
 
+.codeblock, pre.literal-block, .rst-content .literal-block, .rst-content pre.literal-block, div[class^='highlight'] {
+  font-size: 12px;
+  line-height: 1.5;
+  display: block;
+  overflow: auto;
+  color: #404040;
+  padding: 12px 12px;
+}
+
+.codeblock,div[class^='highlight'] {
+  padding: 0;
+}
+
 /*# sourceMappingURL=theme.css.map */

doc/utils/sphinx-config/false_positives.txt

@@ -20,6 +20,7 @@ acolor
 acos
 Acta
 actinide
+acylindricity
 addforce
 Addington
 addtorque
@@ -101,6 +102,7 @@ api
 Appl
 Apu
 arccos
+Archlinux
 arcsin
 arg
 args
@@ -112,6 +114,7 @@ askoose
 asphere
 ASPHERE
 aspherical
+asphericity
 Asq
 assignee
 Asta
@@ -480,6 +483,7 @@ cvff
 cwiggle
 cygwin
 Cygwin
+cylindrically
 Cyrot
 cyrstals
 Daivis
@@ -525,6 +529,7 @@ decrementing
 deeppink
 deepskyblue
 defgrad
+defn
 deformable
 del
 deleteIDs
@@ -573,6 +578,7 @@ Dihedrals
 dihydride
 Dij
 dimdim
+dimensioned
 dimensionality
 dimgray
 dipolar
@@ -602,6 +608,7 @@ Dobson
 Dodds
 dodgerblue
 dof
+doi
 Donadio
 dotc
 Doty
@@ -753,6 +760,7 @@ equilibrating
 equilibration
 Equilibria
 equilization
+Ercolessi
 eradius
 erate
 erc
@@ -879,6 +887,7 @@ Fogarty
 Foiles
 fopenmp
 forestgreen
+formatarg
 formulae
 Forschungszentrum
 Fortran
@@ -1513,6 +1522,7 @@ lz
 Maaravi
 Mackay
 Mackrodt
+Macromolecules
 macroparticle
 Madura
 Magda
@@ -1520,6 +1530,7 @@ Magdeburg
 magelec
 Maginn
 magneton
+magnetons
 mainboard
 mainboards
 makefile
@@ -1527,6 +1538,7 @@ Makefile
 makefiles
 Makefiles
 makelist
+makepkg
 Makse
 malloc
 Malolepsza
@@ -1536,6 +1548,7 @@ Mandelli
 Manh
 manifoldforce
 Manolopoulos
+manpages
 manybody
 MANYBODY
 Maras
@@ -1616,6 +1629,7 @@ meso
 mesoparticle
 mesoscale
 mesoscopic
+metadata
 metadynamics
 Metadynamics
 Methfessel
@@ -2254,6 +2268,7 @@ quati
 quatj
 quatk
 quatw
+queryargs
 Queteschiner
 qw
 qx
@@ -2283,6 +2298,7 @@ rcutfac
 rdc
 rdf
 RDideal
+rdx
 README
 realtime
 reamin
@@ -2309,6 +2325,8 @@ Rensselaer
 reparameterizing
 repo
 representable
+Reproducibility
+reproducibility
 repuls
 rescale
 rescaled
@@ -2425,6 +2443,8 @@ Salles
 sandia
 Sandia
 sandybrown
+Sanitizer
+sanitizers
 sc
 scafacos
 SCAFACOS
@@ -2599,6 +2619,7 @@ Stoll
 stopstep
 Stouch
 Straatsma
+Strachan
 Stratford
 Strathclyde
 Straub
@@ -2626,6 +2647,7 @@ superset
 supersphere
 Supinski
 surfactants
+Suter
 Sutmann
 svn
 sw
@@ -2687,6 +2709,7 @@ th
 Thakkar
 thb
 thei
+Theodorou
 Theor
 thermalization
 thermalize
@@ -2809,6 +2832,7 @@ txt
 typeI
 typeJ
 typeN
+typeargs
 Tz
 Tzou
 ub
@@ -2837,6 +2861,7 @@ undump
 uniaxial
 uniaxially
 unimodal
+unitarg
 unitless
 Universite
 unix

examples/USER/cgdna/README

@@ -22,6 +22,17 @@ A - C - G - T - A - C - G - T
 |   |   |   |   |   |   |   |
 T - G - C - A   T - G - C - A
 
+/examples/duplex3:
+This is basically the duplex1 run with sequence-dependent stacking
+and hydrogen-bonding strengths enabled and both nucleotide mass and 
+moment of inertia set to the value of the standalone implementation 
+of oxDNA (M = I = 1). To achieve this, the masses can be set directly 
+in the input and data file, whereas the moment of inertia is set via 
+the diameter of the ellipsoid in the data file and has a value of 3.16227766.
+The change of mass and moment of inertia allows direct comparision of 
+e.g. trajectory data, energies or time-dependent observables on a per-timestep 
+basis until numerical noise causes deviations at later simulation times. 
+
 /util:
 This directory contains a simple python setup tool which creates 
 single straight or helical DNA strands, DNA duplexes or arrays of DNA 

examples/USER/cgdna/examples/oxDNA/duplex1/data.duplex1

@@ -32,7 +32,7 @@ Atoms
 9 3  4.860249842674775e-01  3.518234140414733e-01  3.897628551303121e-01 2 1 1
 10 4  5.999999999999996e-01 -1.332267629550188e-16 -1.110223024625157e-16 2 1 1
 
-# Atom-ID, translational, rotational velocity
+# Atom-ID, translational velocity, angular momentum
 Velocities
 
 1  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00

examples/USER/cgdna/examples/oxDNA/duplex1/in.duplex1

@@ -1,6 +1,7 @@
 variable number	equal 1
 variable ofreq	equal 1000
 variable efreq	equal 1000
+variable T      equal 0.1
 
 units lj
 
@@ -30,7 +31,7 @@ bond_coeff * 2.0 0.25 0.7525
 # oxDNA pair interactions
 pair_style hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxstk
 pair_coeff * * oxdna/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna/stk     seqav 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
+pair_coeff * * oxdna/stk     seqav ${T} 1.3448 2.6568 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
 pair_coeff * * oxdna/hbond   seqav 0.0   8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 1 4 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 2 3 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
@@ -39,9 +40,9 @@ pair_coeff * * oxdna/coaxstk 46.0 0.4 0.6 0.22 0.58 2.0 2.541592653589793 0.65 1
 
 # NVE ensemble
 fix 1 all nve/dot
-#fix 1 all nve/dotc/langevin 0.1 0.1 0.03 457145 angmom 10
+#fix 1 all nve/dotc/langevin ${T} ${T} 0.03 457145 angmom 10
 #fix 1 all nve/asphere
-#fix 2 all langevin 0.1 0.1 0.03 457145 angmom 10
+#fix 2 all langevin ${T} ${T} 0.03 457145 angmom 10
 
 timestep 1e-5
 
@@ -72,6 +73,6 @@ fix 5 all print ${efreq} "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${e
 #dump_modify out sort id
 #dump_modify out format line "%d   %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le"
 
-run 10000
+run 1000000
 
 #write_restart config.${number}.*

examples/USER/cgdna/examples/oxDNA/duplex1/log.27Nov18.duplex1.g++.1

@@ -1,172 +0,0 @@
-LAMMPS (27 Nov 2018)
-  using 1 OpenMP thread(s) per MPI task
-variable number	equal 1
-variable ofreq	equal 1000
-variable efreq	equal 1000
-
-units lj
-
-dimension 3
-
-newton off
-
-boundary  p p p
-
-atom_style hybrid bond ellipsoid
-atom_modify sort 0 1.0
-
-# Pair interactions require lists of neighbours to be calculated
-neighbor 1.0 bin
-neigh_modify every 1 delay 0 check yes
-
-read_data data.duplex1
-  orthogonal box = (-20 -20 -20) to (20 20 20)
-  1 by 1 by 1 MPI processor grid
-  reading atoms ...
-  10 atoms
-  reading velocities ...
-  10 velocities
-  10 ellipsoids
-  scanning bonds ...
-  2 = max bonds/atom
-  reading bonds ...
-  8 bonds
-  2 = max # of 1-2 neighbors
-  2 = max # of 1-3 neighbors
-  2 = max # of 1-4 neighbors
-  4 = max # of special neighbors
-
-set atom * mass 3.1575
-  10 settings made for mass
-
-group all type 1 4
-10 atoms in group all
-
-# oxDNA bond interactions - FENE backbone
-bond_style oxdna/fene
-bond_coeff * 2.0 0.25 0.7525
-
-# oxDNA pair interactions
-pair_style hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxstk
-pair_coeff * * oxdna/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna/stk     seqav 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
-pair_coeff * * oxdna/hbond   seqav 0.0   8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff 1 4 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff 2 3 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff * * oxdna/xstk    47.5 0.575 0.675 0.495 0.655 2.25 0.791592653589793 0.58 1.7 1.0 0.68 1.7 1.0 0.68 1.5 0 0.65 1.7 0.875 0.68 1.7 0.875 0.68
-pair_coeff * * oxdna/coaxstk 46.0 0.4 0.6 0.22 0.58 2.0 2.541592653589793 0.65 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 -0.65 2.0 -0.65
-
-# NVE ensemble
-fix 1 all nve/dot
-#fix 1 all nve/dotc/langevin 0.1 0.1 0.03 457145 angmom 10
-#fix 1 all nve/asphere
-#fix 2 all langevin 0.1 0.1 0.03 457145 angmom 10
-
-timestep 1e-5
-
-#comm_style tiled
-#fix 3 all balance 10000 1.1 rcb
-
-#compute mol all chunk/atom molecule
-#compute mychunk all vcm/chunk mol
-#fix 4 all ave/time 10000 1 10000 c_mychunk[1] c_mychunk[2] c_mychunk[3] file vcm.txt mode vector
-
-#dump pos all xyz ${ofreq} traj.${number}.xyz
-
-#compute quat all property/atom quatw quati quatj quatk
-#dump quat all custom ${ofreq} quat.${number}.txt id c_quat[1] c_quat[2] c_quat[3] c_quat[4]
-#dump_modify quat sort id
-#dump_modify quat format line "%d  %13.6le  %13.6le  %13.6le  %13.6le"
-
-compute erot all erotate/asphere
-compute ekin all ke
-compute epot all pe
-variable erot equal c_erot
-variable ekin equal c_ekin
-variable epot equal c_epot
-variable etot equal c_erot+c_ekin+c_epot
-fix 5 all print ${efreq} "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${epot} | etot = ${etot}" screen yes
-fix 5 all print 1000 "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${epot} | etot = ${etot}" screen yes
-
-#dump out all custom ${ofreq} out.${number}.txt id x y z vx vy vz fx fy fz tqx tqy tqz
-#dump_modify out sort id
-#dump_modify out format line "%d   %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le"
-
-run 10000
-Neighbor list info ...
-  update every 1 steps, delay 0 steps, check yes
-  max neighbors/atom: 2000, page size: 100000
-  master list distance cutoff = 1.92828
-  ghost atom cutoff = 1.92828
-  binsize = 0.964142, bins = 42 42 42
-  5 neighbor lists, perpetual/occasional/extra = 5 0 0
-  (1) pair oxdna/excv, perpetual
-      attributes: half, newton off
-      pair build: half/bin/newtoff
-      stencil: half/bin/3d/newtoff
-      bin: standard
-  (2) pair oxdna/stk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (3) pair oxdna/hbond, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (4) pair oxdna/xstk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (5) pair oxdna/coaxstk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-Per MPI rank memory allocation (min/avg/max) = 2.859 | 2.859 | 2.859 Mbytes
-Step Temp E_pair E_mol TotEng Press 
-       0            0   -1.4711818 0.0069384985   -1.4642433 -6.2745089e-05 
-1000  ekin = 0.00113448721737003 |  erot = 0.00413455947734281 | epot = -14.6477022915193 | etot = -14.6424332448246
-2000  ekin = 0.00449927223902336 |  erot = 0.0164446434455805 | epot = -14.6633771605337 | etot = -14.6424332448491
-3000  ekin = 0.00997964450841065 |  erot = 0.0366523356056461 | epot = -14.6890652250033 | etot = -14.6424332448892
-4000  ekin = 0.0173888111295073 |  erot = 0.0643039804300221 | epot = -14.7241260365031 | etot = -14.6424332449436
-5000  ekin = 0.0264744514136619 |  erot = 0.0987844033142066 | epot = -14.7676920997383 | etot = -14.6424332450104
-6000  ekin = 0.0369277948556079 |  erot = 0.139336571052565 | epot = -14.8186976109956 | etot = -14.6424332450875
-7000  ekin = 0.04839505571915 |  erot = 0.18508629569208 | epot = -14.8759145965832 | etot = -14.642433245172
-8000  ekin = 0.0604909336920643 |  erot = 0.23507130752353 | epot = -14.9379954864767 | etot = -14.6424332452611
-9000  ekin = 0.0728137406440561 |  erot = 0.288273694501537 | epot = -15.003520680497 | etot = -14.6424332453514
-10000  ekin = 0.0849615563085879 |  erot = 0.343654369293472 | epot = -15.0710491710418 | etot = -14.6424332454398
-   10000 0.0062934486   -1.5138305 0.0067255788   -1.4986088 -9.9021593e-05 
-Loop time of 0.141929 on 1 procs for 10000 steps with 10 atoms
-
-Performance: 60875.649 tau/day, 70457.927 timesteps/s
-99.9% CPU use with 1 MPI tasks x 1 OpenMP threads
-
-MPI task timing breakdown:
-Section |  min time  |  avg time  |  max time  |%varavg| %total
----------------------------------------------------------------
-Pair    | 0.11467    | 0.11467    | 0.11467    |   0.0 | 80.79
-Bond    | 0.0050094  | 0.0050094  | 0.0050094  |   0.0 |  3.53
-Neigh   | 0          | 0          | 0          |   0.0 |  0.00
-Comm    | 0.0013616  | 0.0013616  | 0.0013616  |   0.0 |  0.96
-Output  | 4.0531e-06 | 4.0531e-06 | 4.0531e-06 |   0.0 |  0.00
-Modify  | 0.017901   | 0.017901   | 0.017901   |   0.0 | 12.61
-Other   |            | 0.002982   |            |       |  2.10
-
-Nlocal:    10 ave 10 max 10 min
-Histogram: 1 0 0 0 0 0 0 0 0 0
-Nghost:    0 ave 0 max 0 min
-Histogram: 1 0 0 0 0 0 0 0 0 0
-Neighs:    43 ave 43 max 43 min
-Histogram: 1 0 0 0 0 0 0 0 0 0
-
-Total # of neighbors = 43
-Ave neighs/atom = 4.3
-Ave special neighs/atom = 3.6
-Neighbor list builds = 0
-Dangerous builds = 0
-
-#write_restart config.${number}.*
-Total wall time: 0:00:00

examples/USER/cgdna/examples/oxDNA/duplex1/log.27Nov18.duplex1.g++.4

@@ -1,172 +0,0 @@
-LAMMPS (27 Nov 2018)
-  using 1 OpenMP thread(s) per MPI task
-variable number	equal 1
-variable ofreq	equal 1000
-variable efreq	equal 1000
-
-units lj
-
-dimension 3
-
-newton off
-
-boundary  p p p
-
-atom_style hybrid bond ellipsoid
-atom_modify sort 0 1.0
-
-# Pair interactions require lists of neighbours to be calculated
-neighbor 1.0 bin
-neigh_modify every 1 delay 0 check yes
-
-read_data data.duplex1
-  orthogonal box = (-20 -20 -20) to (20 20 20)
-  1 by 2 by 2 MPI processor grid
-  reading atoms ...
-  10 atoms
-  reading velocities ...
-  10 velocities
-  10 ellipsoids
-  scanning bonds ...
-  2 = max bonds/atom
-  reading bonds ...
-  8 bonds
-  2 = max # of 1-2 neighbors
-  2 = max # of 1-3 neighbors
-  2 = max # of 1-4 neighbors
-  4 = max # of special neighbors
-
-set atom * mass 3.1575
-  10 settings made for mass
-
-group all type 1 4
-10 atoms in group all
-
-# oxDNA bond interactions - FENE backbone
-bond_style oxdna/fene
-bond_coeff * 2.0 0.25 0.7525
-
-# oxDNA pair interactions
-pair_style hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxstk
-pair_coeff * * oxdna/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna/stk     seqav 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
-pair_coeff * * oxdna/hbond   seqav 0.0   8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff 1 4 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff 2 3 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff * * oxdna/xstk    47.5 0.575 0.675 0.495 0.655 2.25 0.791592653589793 0.58 1.7 1.0 0.68 1.7 1.0 0.68 1.5 0 0.65 1.7 0.875 0.68 1.7 0.875 0.68
-pair_coeff * * oxdna/coaxstk 46.0 0.4 0.6 0.22 0.58 2.0 2.541592653589793 0.65 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 -0.65 2.0 -0.65
-
-# NVE ensemble
-fix 1 all nve/dot
-#fix 1 all nve/dotc/langevin 0.1 0.1 0.03 457145 angmom 10
-#fix 1 all nve/asphere
-#fix 2 all langevin 0.1 0.1 0.03 457145 angmom 10
-
-timestep 1e-5
-
-#comm_style tiled
-#fix 3 all balance 10000 1.1 rcb
-
-#compute mol all chunk/atom molecule
-#compute mychunk all vcm/chunk mol
-#fix 4 all ave/time 10000 1 10000 c_mychunk[1] c_mychunk[2] c_mychunk[3] file vcm.txt mode vector
-
-#dump pos all xyz ${ofreq} traj.${number}.xyz
-
-#compute quat all property/atom quatw quati quatj quatk
-#dump quat all custom ${ofreq} quat.${number}.txt id c_quat[1] c_quat[2] c_quat[3] c_quat[4]
-#dump_modify quat sort id
-#dump_modify quat format line "%d  %13.6le  %13.6le  %13.6le  %13.6le"
-
-compute erot all erotate/asphere
-compute ekin all ke
-compute epot all pe
-variable erot equal c_erot
-variable ekin equal c_ekin
-variable epot equal c_epot
-variable etot equal c_erot+c_ekin+c_epot
-fix 5 all print ${efreq} "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${epot} | etot = ${etot}" screen yes
-fix 5 all print 1000 "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${epot} | etot = ${etot}" screen yes
-
-#dump out all custom ${ofreq} out.${number}.txt id x y z vx vy vz fx fy fz tqx tqy tqz
-#dump_modify out sort id
-#dump_modify out format line "%d   %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le"
-
-run 10000
-Neighbor list info ...
-  update every 1 steps, delay 0 steps, check yes
-  max neighbors/atom: 2000, page size: 100000
-  master list distance cutoff = 1.92828
-  ghost atom cutoff = 1.92828
-  binsize = 0.964142, bins = 42 42 42
-  5 neighbor lists, perpetual/occasional/extra = 5 0 0
-  (1) pair oxdna/excv, perpetual
-      attributes: half, newton off
-      pair build: half/bin/newtoff
-      stencil: half/bin/3d/newtoff
-      bin: standard
-  (2) pair oxdna/stk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (3) pair oxdna/hbond, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (4) pair oxdna/xstk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (5) pair oxdna/coaxstk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-Per MPI rank memory allocation (min/avg/max) = 7.341 | 7.523 | 7.705 Mbytes
-Step Temp E_pair E_mol TotEng Press 
-       0            0   -1.4711818 0.0069384985   -1.4642433 -6.2745089e-05 
-1000  ekin = 0.00113448721737009 |  erot = 0.0041345594773427 | epot = -14.6477022915193 | etot = -14.6424332448246
-2000  ekin = 0.00449927223902292 |  erot = 0.0164446434455803 | epot = -14.6633771605337 | etot = -14.6424332448491
-3000  ekin = 0.00997964450840756 |  erot = 0.0366523356056465 | epot = -14.6890652250033 | etot = -14.6424332448892
-4000  ekin = 0.017388811129498 |  erot = 0.0643039804300254 | epot = -14.7241260365031 | etot = -14.6424332449436
-5000  ekin = 0.0264744514136422 |  erot = 0.098784403314214 | epot = -14.7676920997383 | etot = -14.6424332450104
-6000  ekin = 0.0369277948555727 |  erot = 0.139336571052581 | epot = -14.8186976109956 | etot = -14.6424332450875
-7000  ekin = 0.0483950557190949 |  erot = 0.185086295692111 | epot = -14.8759145965832 | etot = -14.642433245172
-8000  ekin = 0.0604909336919856 |  erot = 0.235071307523583 | epot = -14.9379954864767 | etot = -14.6424332452611
-9000  ekin = 0.0728137406439517 |  erot = 0.288273694501617 | epot = -15.003520680497 | etot = -14.6424332453514
-10000  ekin = 0.0849615563084573 |  erot = 0.34365436929359 | epot = -15.0710491710418 | etot = -14.6424332454398
-   10000 0.0062934486   -1.5138305 0.0067255788   -1.4986088 -0.00010196899 
-Loop time of 0.134536 on 4 procs for 10000 steps with 10 atoms
-
-Performance: 64220.659 tau/day, 74329.466 timesteps/s
-97.3% CPU use with 4 MPI tasks x 1 OpenMP threads
-
-MPI task timing breakdown:
-Section |  min time  |  avg time  |  max time  |%varavg| %total
----------------------------------------------------------------
-Pair    | 0.0030077  | 0.052212   | 0.093066   |  17.4 | 38.81
-Bond    | 0.00061846 | 0.00234    | 0.0039451  |   2.8 |  1.74
-Neigh   | 0          | 0          | 0          |   0.0 |  0.00
-Comm    | 0.013431   | 0.014091   | 0.014596   |   0.4 | 10.47
-Output  | 5.0783e-05 | 5.1141e-05 | 5.1498e-05 |   0.0 |  0.04
-Modify  | 0.0011578  | 0.0059478  | 0.010331   |   4.8 |  4.42
-Other   |            | 0.05989    |            |       | 44.52
-
-Nlocal:    2.5 ave 5 max 0 min
-Histogram: 1 0 1 0 0 0 0 0 1 1
-Nghost:    7.5 ave 10 max 5 min
-Histogram: 1 0 1 0 0 0 0 0 1 1
-Neighs:    17.5 ave 33 max 0 min
-Histogram: 1 0 1 0 0 0 0 0 1 1
-
-Total # of neighbors = 70
-Ave neighs/atom = 7
-Ave special neighs/atom = 3.6
-Neighbor list builds = 0
-Dangerous builds = 0
-
-#write_restart config.${number}.*
-Total wall time: 0:00:00

examples/USER/cgdna/examples/oxDNA/duplex2/data.duplex2

@@ -38,7 +38,7 @@ Atoms
 15 3  4.860249842674773e-01  3.518234140414733e-01  3.897628551303119e-01 2 1 1
 16 4  5.999999999999995e-01 -3.330669073875470e-17 -3.330669073875470e-16 2 1 1
 
-# Atom-ID, translational, rotational velocity
+# Atom-ID, translational velocity, angular momentum
 Velocities
 
 1  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00  0.000000000000000e+00

examples/USER/cgdna/examples/oxDNA/duplex2/in.duplex2

@@ -1,6 +1,7 @@
 variable number	equal 2
 variable ofreq	equal 1000
 variable efreq	equal 1000
+variable T      equal 0.1
 
 units lj
 
@@ -30,7 +31,7 @@ bond_coeff * 2.0 0.25 0.7525
 # oxDNA pair interactions
 pair_style hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxstk
 pair_coeff * * oxdna/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna/stk     seqav 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
+pair_coeff * * oxdna/stk     seqav ${T} 1.3448 2.6568 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
 pair_coeff * * oxdna/hbond   seqav 0.0   8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 1 4 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
 pair_coeff 2 3 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
@@ -39,9 +40,9 @@ pair_coeff * * oxdna/coaxstk 46.0 0.4 0.6 0.22 0.58 2.0 2.541592653589793 0.65 1
 
 # NVE ensemble
 #fix 1 all nve/dot
-fix 1 all nve/dotc/langevin 0.1 0.1 0.03 457145 angmom 10
+fix 1 all nve/dotc/langevin ${T} ${T} 0.03 457145 angmom 10
 #fix 1 all nve/asphere
-#fix 2 all langevin 0.1 0.1 0.03 457145 angmom 10
+#fix 2 all langevin ${T} ${T} 0.03 457145 angmom 10
 
 timestep 1e-5
 
@@ -72,6 +73,6 @@ fix 5 all print ${efreq} "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${e
 #dump_modify out sort id
 #dump_modify out format line "%d   %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le"
 
-run 10000
+run 1000000
 
 #write_restart config.${number}.*

examples/USER/cgdna/examples/oxDNA/duplex2/log.27Nov18.duplex2.g++.1

@@ -1,172 +0,0 @@
-LAMMPS (27 Nov 2018)
-  using 1 OpenMP thread(s) per MPI task
-variable number	equal 2
-variable ofreq	equal 1000
-variable efreq	equal 1000
-
-units lj
-
-dimension 3
-
-newton off
-
-boundary  p p p
-
-atom_style hybrid bond ellipsoid
-atom_modify sort 0 1.0
-
-# Pair interactions require lists of neighbours to be calculated
-neighbor 1.0 bin
-neigh_modify every 1 delay 0 check yes
-
-read_data data.duplex2
-  orthogonal box = (-20 -20 -20) to (20 20 20)
-  1 by 1 by 1 MPI processor grid
-  reading atoms ...
-  16 atoms
-  reading velocities ...
-  16 velocities
-  16 ellipsoids
-  scanning bonds ...
-  2 = max bonds/atom
-  reading bonds ...
-  13 bonds
-  2 = max # of 1-2 neighbors
-  2 = max # of 1-3 neighbors
-  4 = max # of 1-4 neighbors
-  6 = max # of special neighbors
-
-set atom * mass 3.1575
-  16 settings made for mass
-
-group all type 1 4
-16 atoms in group all
-
-# oxDNA bond interactions - FENE backbone
-bond_style oxdna/fene
-bond_coeff * 2.0 0.25 0.7525
-
-# oxDNA pair interactions
-pair_style hybrid/overlay oxdna/excv oxdna/stk oxdna/hbond oxdna/xstk oxdna/coaxstk
-pair_coeff * * oxdna/excv    2.0 0.7 0.675 2.0 0.515 0.5 2.0 0.33 0.32
-pair_coeff * * oxdna/stk     seqav 0.1 6.0 0.4 0.9 0.32 0.6 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 0.65 2.0 0.65
-pair_coeff * * oxdna/hbond   seqav 0.0   8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff 1 4 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff 2 3 oxdna/hbond   seqav 1.077 8.0 0.4 0.75 0.34 0.7 1.5 0 0.7 1.5 0 0.7 1.5 0 0.7 0.46 3.141592653589793 0.7 4.0 1.5707963267948966 0.45 4.0 1.5707963267948966 0.45
-pair_coeff * * oxdna/xstk    47.5 0.575 0.675 0.495 0.655 2.25 0.791592653589793 0.58 1.7 1.0 0.68 1.7 1.0 0.68 1.5 0 0.65 1.7 0.875 0.68 1.7 0.875 0.68
-pair_coeff * * oxdna/coaxstk 46.0 0.4 0.6 0.22 0.58 2.0 2.541592653589793 0.65 1.3 0 0.8 0.9 0 0.95 0.9 0 0.95 2.0 -0.65 2.0 -0.65
-
-# NVE ensemble
-#fix 1 all nve/dot
-fix 1 all nve/dotc/langevin 0.1 0.1 0.03 457145 angmom 10
-#fix 1 all nve/asphere
-#fix 2 all langevin 0.1 0.1 0.03 457145 angmom 10
-
-timestep 1e-5
-
-#comm_style tiled
-#fix 3 all balance 10000 1.1 rcb
-
-#compute mol all chunk/atom molecule
-#compute mychunk all vcm/chunk mol
-#fix 4 all ave/time 10000 1 10000 c_mychunk[1] c_mychunk[2] c_mychunk[3] file vcm.txt mode vector
-
-#dump pos all xyz ${ofreq} traj.${number}.xyz
-
-#compute quat all property/atom quatw quati quatj quatk
-#dump quat all custom ${ofreq} quat.${number}.txt id c_quat[1] c_quat[2] c_quat[3] c_quat[4]
-#dump_modify quat sort id
-#dump_modify quat format line "%d  %13.6le  %13.6le  %13.6le  %13.6le"
-
-compute erot all erotate/asphere
-compute ekin all ke
-compute epot all pe
-variable erot equal c_erot
-variable ekin equal c_ekin
-variable epot equal c_epot
-variable etot equal c_erot+c_ekin+c_epot
-fix 5 all print ${efreq} "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${epot} | etot = ${etot}" screen yes
-fix 5 all print 1000 "$(step)  ekin = ${ekin} |  erot = ${erot} | epot = ${epot} | etot = ${etot}" screen yes
-
-#dump out all custom ${ofreq} out.${number}.txt id x y z vx vy vz fx fy fz tqx tqy tqz
-#dump_modify out sort id
-#dump_modify out format line "%d   %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le  %13.6le %13.6le %13.6le"
-
-run 10000
-Neighbor list info ...
-  update every 1 steps, delay 0 steps, check yes
-  max neighbors/atom: 2000, page size: 100000
-  master list distance cutoff = 1.92828
-  ghost atom cutoff = 1.92828
-  binsize = 0.964142, bins = 42 42 42
-  5 neighbor lists, perpetual/occasional/extra = 5 0 0
-  (1) pair oxdna/excv, perpetual
-      attributes: half, newton off
-      pair build: half/bin/newtoff
-      stencil: half/bin/3d/newtoff
-      bin: standard
-  (2) pair oxdna/stk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (3) pair oxdna/hbond, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (4) pair oxdna/xstk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-  (5) pair oxdna/coaxstk, perpetual, copy from (1)
-      attributes: half, newton off
-      pair build: copy
-      stencil: none
-      bin: none
-Per MPI rank memory allocation (min/avg/max) = 2.861 | 2.861 | 2.861 Mbytes
-Step Temp E_pair E_mol TotEng Press 
-       0            0   -1.5402493 0.0070469125   -1.5332024 -8.5641987e-05 
-1000  ekin = 1.54234964773389 |  erot = 1.71563526070267 | epot = -24.5477045187653 | etot = -21.2897196103287
-2000  ekin = 1.85988866919215 |  erot = 1.9424302796508 | epot = -24.4843044999595 | etot = -20.6819855511165
-3000  ekin = 2.68354339452998 |  erot = 2.14216528317607 | epot = -24.4019350693561 | etot = -19.57622639165
-4000  ekin = 2.04461800191989 |  erot = 1.49015219763162 | epot = -24.2959428773347 | etot = -20.7611726777832
-5000  ekin = 1.76794859210155 |  erot = 2.54289684465818 | epot = -24.2337587736863 | etot = -19.9229133369266
-6000  ekin = 3.1106424806079 |  erot = 2.04409805200892 | epot = -24.1585729744133 | etot = -19.0038324417964
-7000  ekin = 3.21360097519306 |  erot = 2.71941303605722 | epot = -24.0566262531609 | etot = -18.1236122419107
-8000  ekin = 2.82489935901743 |  erot = 2.66790555575696 | epot = -24.0194805097633 | etot = -18.526675594989
-9000  ekin = 2.69381302856378 |  erot = 2.59107820129446 | epot = -23.9216126050554 | etot = -18.6367213751972
-10000  ekin = 2.65765007662471 |  erot = 1.95562671446597 | epot = -23.7978334881241 | etot = -19.1845566970334
-   10000   0.11811778   -1.4992295  0.011864944   -1.3212615 -0.00013416809 
-Loop time of 0.295538 on 1 procs for 10000 steps with 16 atoms
-
-Performance: 29234.801 tau/day, 33836.575 timesteps/s
-99.7% CPU use with 1 MPI tasks x 1 OpenMP threads
-
-MPI task timing breakdown:
-Section |  min time  |  avg time  |  max time  |%varavg| %total
----------------------------------------------------------------
-Pair    | 0.20959    | 0.20959    | 0.20959    |   0.0 | 70.92
-Bond    | 0.0073669  | 0.0073669  | 0.0073669  |   0.0 |  2.49
-Neigh   | 0          | 0          | 0          |   0.0 |  0.00
-Comm    | 0.0016472  | 0.0016472  | 0.0016472  |   0.0 |  0.56
-Output  | 5.0068e-06 | 5.0068e-06 | 5.0068e-06 |   0.0 |  0.00
-Modify  | 0.073117   | 0.073117   | 0.073117   |   0.0 | 24.74
-Other   |            | 0.003813   |            |       |  1.29
-
-Nlocal:    16 ave 16 max 16 min
-Histogram: 1 0 0 0 0 0 0 0 0 0
-Nghost:    0 ave 0 max 0 min
-Histogram: 1 0 0 0 0 0 0 0 0 0
-Neighs:    88 ave 88 max 88 min
-Histogram: 1 0 0 0 0 0 0 0 0 0
-
-Total # of neighbors = 88
-Ave neighs/atom = 5.5
-Ave special neighs/atom = 3.75
-Neighbor list builds = 0
-Dangerous builds = 0
-
-#write_restart config.${number}.*
-Total wall time: 0:00:00