Merge pull request #1593 from akohlmey/next_version

Step version string for next patch release

cmake/Modules/CodeCoverage.cmake

@@ -0,0 +1,28 @@
+###############################################################################
+# Coverage
+#
+# Requires latest gcovr (for GCC 8.1 support):#
+# pip install git+https://github.com/gcovr/gcovr.git
+###############################################################################
+if(ENABLE_COVERAGE)
+    find_program(GCOVR_BINARY gcovr)
+    find_package_handle_standard_args(GCOVR DEFAULT_MSG GCOVR_BINARY)
+
+    if(GCOVR_FOUND)
+        get_filename_component(ABSOLUTE_LAMMPS_SOURCE_DIR ${LAMMPS_SOURCE_DIR} ABSOLUTE)
+
+        add_custom_target(
+            gen_coverage_xml
+            COMMAND ${GCOVR_BINARY} -s -x -r ${ABSOLUTE_LAMMPS_SOURCE_DIR} --object-directory=${CMAKE_BINARY_DIR} -o coverage.xml
+            WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
+            COMMENT "Generating XML Coverage Report..."
+        )
+
+        add_custom_target(
+            gen_coverage_html
+            COMMAND ${GCOVR_BINARY} -s  --html --html-details -r ${ABSOLUTE_LAMMPS_SOURCE_DIR} --object-directory=${CMAKE_BINARY_DIR} -o coverage.html
+            WORKING_DIRECTORY ${CMAKE_BINARY_DIR}
+            COMMENT "Generating HTML Coverage Report..."
+        )
+    endif()
+endif()

cmake/Modules/Documentation.cmake

@@ -0,0 +1,59 @@
+###############################################################################
+# Build documentation
+###############################################################################
+option(BUILD_DOC "Build LAMMPS documentation" OFF)
+if(BUILD_DOC)
+  include(ProcessorCount)
+  ProcessorCount(NPROCS)
+  find_package(PythonInterp 3 REQUIRED)
+
+  set(VIRTUALENV ${PYTHON_EXECUTABLE} -m virtualenv)
+
+  file(GLOB DOC_SOURCES ${LAMMPS_DOC_DIR}/src/[^.]*.txt)
+  file(GLOB PDF_EXTRA_SOURCES ${LAMMPS_DOC_DIR}/src/lammps_commands*.txt ${LAMMPS_DOC_DIR}/src/lammps_support.txt ${LAMMPS_DOC_DIR}/src/lammps_tutorials.txt)
+  list(REMOVE_ITEM DOC_SOURCES ${PDF_EXTRA_SOURCES})
+
+  add_custom_command(
+    OUTPUT docenv
+    COMMAND ${VIRTUALENV} docenv
+  )
+
+  set(DOCENV_BINARY_DIR ${CMAKE_BINARY_DIR}/docenv/bin)
+
+  add_custom_command(
+    OUTPUT requirements.txt
+    DEPENDS docenv
+    COMMAND ${CMAKE_COMMAND} -E copy ${LAMMPS_DOC_DIR}/utils/requirements.txt requirements.txt
+    COMMAND ${DOCENV_BINARY_DIR}/pip install -r requirements.txt --upgrade
+    COMMAND ${DOCENV_BINARY_DIR}/pip install --upgrade ${LAMMPS_DOC_DIR}/utils/converters
+  )
+
+  set(RST_FILES "")
+  set(RST_DIR ${CMAKE_BINARY_DIR}/rst)
+  file(MAKE_DIRECTORY ${RST_DIR})
+  foreach(TXT_FILE ${DOC_SOURCES})
+    get_filename_component(FILENAME ${TXT_FILE} NAME_WE)
+    set(RST_FILE ${RST_DIR}/${FILENAME}.rst)
+    list(APPEND RST_FILES ${RST_FILE})
+    add_custom_command(
+      OUTPUT ${RST_FILE}
+      DEPENDS requirements.txt docenv ${TXT_FILE}
+      COMMAND ${DOCENV_BINARY_DIR}/txt2rst -o ${RST_DIR} ${TXT_FILE}
+    )
+  endforeach()
+
+  add_custom_command(
+    OUTPUT html
+    DEPENDS ${RST_FILES}
+    COMMAND ${CMAKE_COMMAND} -E copy_directory ${LAMMPS_DOC_DIR}/src ${RST_DIR}
+    COMMAND ${DOCENV_BINARY_DIR}/sphinx-build -j ${NPROCS} -b html -c ${LAMMPS_DOC_DIR}/utils/sphinx-config -d ${CMAKE_BINARY_DIR}/doctrees ${RST_DIR} html
+  )
+
+  add_custom_target(
+    doc ALL
+    DEPENDS html
+    SOURCES ${LAMMPS_DOC_DIR}/utils/requirements.txt ${DOC_SOURCES}
+  )
+
+  install(DIRECTORY ${CMAKE_BINARY_DIR}/html DESTINATION ${CMAKE_INSTALL_DOCDIR})
+endif()

cmake/Modules/LAMMPSUtils.cmake

@@ -0,0 +1,71 @@
+# Utility functions
+function(list_to_bulletpoints result)
+    list(REMOVE_AT ARGV 0)
+    set(temp "")
+    foreach(item ${ARGV})
+        set(temp "${temp}* ${item}\n")
+    endforeach()
+    set(${result} "${temp}" PARENT_SCOPE)
+endfunction(list_to_bulletpoints)
+
+function(validate_option name values)
+    string(TOLOWER ${${name}} needle_lower)
+    string(TOUPPER ${${name}} needle_upper)
+    list(FIND ${values} ${needle_lower} IDX_LOWER)
+    list(FIND ${values} ${needle_upper} IDX_UPPER)
+    if(${IDX_LOWER} LESS 0 AND ${IDX_UPPER} LESS 0)
+        list_to_bulletpoints(POSSIBLE_VALUE_LIST ${${values}})
+        message(FATAL_ERROR "\n########################################################################\n"
+                            "Invalid value '${${name}}' for option ${name}\n"
+                            "\n"
+                            "Possible values are:\n"
+                            "${POSSIBLE_VALUE_LIST}"
+                            "########################################################################")
+    endif()
+endfunction(validate_option)
+
+function(get_lammps_version version_header variable)
+    file(READ ${version_header} line)
+    set(MONTHS x Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec)
+    string(REGEX REPLACE "#define LAMMPS_VERSION \"([0-9]+) ([A-Za-z]+) ([0-9]+)\"" "\\1" day "${line}")
+    string(REGEX REPLACE "#define LAMMPS_VERSION \"([0-9]+) ([A-Za-z]+) ([0-9]+)\"" "\\2" month "${line}")
+    string(REGEX REPLACE "#define LAMMPS_VERSION \"([0-9]+) ([A-Za-z]+) ([0-9]+)\"" "\\3" year "${line}")
+    string(STRIP ${day} day)
+    string(STRIP ${month} month)
+    string(STRIP ${year} year)
+    list(FIND MONTHS "${month}" month)
+    string(LENGTH ${day} day_length)
+    string(LENGTH ${month} month_length)
+    if(day_length EQUAL 1)
+        set(day "0${day}")
+    endif()
+    if(month_length EQUAL 1)
+        set(month "0${month}")
+    endif()
+    set(${variable} "${year}${month}${day}" PARENT_SCOPE)
+endfunction()
+
+function(check_for_autogen_files source_dir)
+    message(STATUS "Running check for auto-generated files from make-based build system")
+    file(GLOB SRC_AUTOGEN_FILES ${source_dir}/style_*.h)
+    file(GLOB SRC_AUTOGEN_PACKAGES ${source_dir}/packages_*.h)
+    list(APPEND SRC_AUTOGEN_FILES ${SRC_AUTOGEN_PACKAGES} ${source_dir}/lmpinstalledpkgs.h ${source_dir}/lmpgitversion.h)
+    foreach(_SRC ${SRC_AUTOGEN_FILES})
+      get_filename_component(FILENAME "${_SRC}" NAME)
+      if(EXISTS ${source_dir}/${FILENAME})
+        message(FATAL_ERROR "\n########################################################################\n"
+                              "Found header file(s) generated by the make-based build system\n"
+                              "\n"
+                              "Please run\n"
+                              "make -C ${source_dir} purge\n"
+                              "to remove\n"
+                              "########################################################################")
+      endif()
+    endforeach()
+endfunction()
+
+macro(pkg_depends PKG1 PKG2)
+  if(PKG_${PKG1} AND NOT (PKG_${PKG2} OR BUILD_${PKG2}))
+    message(FATAL_ERROR "${PKG1} package needs LAMMPS to be build with ${PKG2}")
+  endif()
+endmacro()

cmake/Modules/Packages/COMPRESS.cmake

@@ -0,0 +1,5 @@
+if(PKG_COMPRESS)
+  find_package(ZLIB REQUIRED)
+  include_directories(${ZLIB_INCLUDE_DIRS})
+  list(APPEND LAMMPS_LINK_LIBS ${ZLIB_LIBRARIES})
+endif()

cmake/Modules/Packages/CORESHELL.cmake

@@ -0,0 +1,13 @@
+if(PKG_CORESHELL)
+    set(CORESHELL_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/CORESHELL)
+    set(CORESHELL_SOURCES)
+    set_property(GLOBAL PROPERTY "CORESHELL_SOURCES" "${CORESHELL_SOURCES}")
+
+    # detects styles which have a CORESHELL version
+    RegisterStylesExt(${CORESHELL_SOURCES_DIR} cs CORESHELL_SOURCES)
+
+    get_property(CORESHELL_SOURCES GLOBAL PROPERTY CORESHELL_SOURCES)
+
+    list(APPEND LIB_SOURCES ${CORESHELL_SOURCES})
+    include_directories(${CORESHELL_SOURCES_DIR})
+endif()

cmake/Modules/Packages/GPU.cmake

@@ -0,0 +1,194 @@
+if(PKG_GPU)
+    if (CMAKE_VERSION VERSION_LESS "3.1")
+      message(FATAL_ERROR "For the GPU package you need at least cmake-3.1")
+    endif()
+    set(GPU_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/GPU)
+    set(GPU_SOURCES ${GPU_SOURCES_DIR}/gpu_extra.h
+                    ${GPU_SOURCES_DIR}/fix_gpu.h
+                    ${GPU_SOURCES_DIR}/fix_gpu.cpp)
+
+    set(GPU_API "opencl" CACHE STRING "API used by GPU package")
+    set(GPU_API_VALUES opencl cuda)
+    set_property(CACHE GPU_API PROPERTY STRINGS ${GPU_API_VALUES})
+    validate_option(GPU_API GPU_API_VALUES)
+    string(TOUPPER ${GPU_API} GPU_API)
+
+    set(GPU_PREC "mixed" CACHE STRING "LAMMPS GPU precision")
+    set(GPU_PREC_VALUES double mixed single)
+    set_property(CACHE GPU_PREC PROPERTY STRINGS ${GPU_PREC_VALUES})
+    validate_option(GPU_PREC GPU_PREC_VALUES)
+    string(TOUPPER ${GPU_PREC} GPU_PREC)
+
+    if(GPU_PREC STREQUAL "DOUBLE")
+      set(GPU_PREC_SETTING "DOUBLE_DOUBLE")
+    elseif(GPU_PREC STREQUAL "MIXED")
+      set(GPU_PREC_SETTING "SINGLE_DOUBLE")
+    elseif(GPU_PREC STREQUAL "SINGLE")
+      set(GPU_PREC_SETTING "SINGLE_SINGLE")
+    endif()
+
+    file(GLOB GPU_LIB_SOURCES ${LAMMPS_LIB_SOURCE_DIR}/gpu/[^.]*.cpp)
+    file(MAKE_DIRECTORY ${LAMMPS_LIB_BINARY_DIR}/gpu)
+
+    if(GPU_API STREQUAL "CUDA")
+      find_package(CUDA REQUIRED)
+      find_program(BIN2C bin2c)
+      if(NOT BIN2C)
+        message(FATAL_ERROR "Could not find bin2c, use -DBIN2C=/path/to/bin2c to help cmake finding it.")
+      endif()
+      option(CUDPP_OPT "Enable CUDPP_OPT" ON)
+      option(CUDA_MPS_SUPPORT "Enable tweaks to support CUDA Multi-process service (MPS)" OFF)
+      if(CUDA_MPS_SUPPORT)
+        set(GPU_CUDA_MPS_FLAGS "-DCUDA_PROXY")
+      endif()
+
+      set(GPU_ARCH "sm_30" CACHE STRING "LAMMPS GPU CUDA SM primary architecture (e.g. sm_60)")
+
+      file(GLOB GPU_LIB_CU ${LAMMPS_LIB_SOURCE_DIR}/gpu/[^.]*.cu ${CMAKE_CURRENT_SOURCE_DIR}/gpu/[^.]*.cu)
+      list(REMOVE_ITEM GPU_LIB_CU ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_pppm.cu)
+
+      cuda_include_directories(${LAMMPS_LIB_SOURCE_DIR}/gpu ${LAMMPS_LIB_BINARY_DIR}/gpu)
+
+      if(CUDPP_OPT)
+        cuda_include_directories(${LAMMPS_LIB_SOURCE_DIR}/gpu/cudpp_mini)
+        file(GLOB GPU_LIB_CUDPP_SOURCES ${LAMMPS_LIB_SOURCE_DIR}/gpu/cudpp_mini/[^.]*.cpp)
+        file(GLOB GPU_LIB_CUDPP_CU ${LAMMPS_LIB_SOURCE_DIR}/gpu/cudpp_mini/[^.]*.cu)
+      endif()
+
+      # build arch/gencode commands for nvcc based on CUDA toolkit version and use choice
+      # --arch translates directly instead of JIT, so this should be for the preferred or most common architecture
+      set(GPU_CUDA_GENCODE "-arch=${GPU_ARCH} ")
+      # Fermi (GPU Arch 2.x) is supported by CUDA 3.2 to CUDA 8.0
+      if((CUDA_VERSION VERSION_GREATER "3.1") AND (CUDA_VERSION VERSION_LESS "9.0"))
+        string(APPEND GPU_CUDA_GENCODE "-gencode arch=compute_20,code=[sm_20,compute_20] ")
+      endif()
+      # Kepler (GPU Arch 3.x) is supported by CUDA 5 and later
+      if(CUDA_VERSION VERSION_GREATER "4.9")
+        string(APPEND GPU_CUDA_GENCODE "-gencode arch=compute_30,code=[sm_30,compute_30] -gencode arch=compute_35,code=[sm_35,compute_35] ")
+      endif()
+      # Maxwell (GPU Arch 5.x) is supported by CUDA 6 and later
+      if(CUDA_VERSION VERSION_GREATER "5.9")
+        string(APPEND GPU_CUDA_GENCODE "-gencode arch=compute_50,code=[sm_50,compute_50] -gencode arch=compute_52,code=[sm_52,compute_52] ")
+      endif()
+      # Pascal (GPU Arch 6.x) is supported by CUDA 8 and later
+      if(CUDA_VERSION VERSION_GREATER "7.9")
+        string(APPEND GPU_CUDA_GENCODE "-gencode arch=compute_60,code=[sm_60,compute_60] -gencode arch=compute_61,code=[sm_61,compute_61] ")
+      endif()
+      # Volta (GPU Arch 7.0) is supported by CUDA 9 and later
+      if(CUDA_VERSION VERSION_GREATER "8.9")
+        string(APPEND GPU_CUDA_GENCODE "-gencode arch=compute_70,code=[sm_70,compute_70] ")
+      endif()
+      # Turing (GPU Arch 7.5) is supported by CUDA 10 and later
+      if(CUDA_VERSION VERSION_GREATER "9.9")
+        string(APPEND GPU_CUDA_GENCODE "-gencode arch=compute_75,code=[sm_75,compute_75] ")
+      endif()
+
+      cuda_compile_fatbin(GPU_GEN_OBJS ${GPU_LIB_CU} OPTIONS
+              -DUNIX -O3 --use_fast_math -Wno-deprecated-gpu-targets -DNV_KERNEL -DUCL_CUDADR ${GPU_CUDA_GENCODE} -D_${GPU_PREC_SETTING})
+
+      cuda_compile(GPU_OBJS ${GPU_LIB_CUDPP_CU} OPTIONS ${CUDA_REQUEST_PIC}
+              -DUNIX -O3 --use_fast_math -Wno-deprecated-gpu-targets -DUCL_CUDADR ${GPU_CUDA_GENCODE} -D_${GPU_PREC_SETTING})
+
+      foreach(CU_OBJ ${GPU_GEN_OBJS})
+        get_filename_component(CU_NAME ${CU_OBJ} NAME_WE)
+        string(REGEX REPLACE "^.*_lal_" "" CU_NAME "${CU_NAME}")
+        add_custom_command(OUTPUT ${LAMMPS_LIB_BINARY_DIR}/gpu/${CU_NAME}_cubin.h
+          COMMAND ${BIN2C} -c -n ${CU_NAME} ${CU_OBJ} > ${LAMMPS_LIB_BINARY_DIR}/gpu/${CU_NAME}_cubin.h
+          DEPENDS ${CU_OBJ}
+          COMMENT "Generating ${CU_NAME}_cubin.h")
+        list(APPEND GPU_LIB_SOURCES ${LAMMPS_LIB_BINARY_DIR}/gpu/${CU_NAME}_cubin.h)
+      endforeach()
+      set_directory_properties(PROPERTIES ADDITIONAL_MAKE_CLEAN_FILES "${LAMMPS_LIB_BINARY_DIR}/gpu/*_cubin.h")
+
+
+      add_library(gpu STATIC ${GPU_LIB_SOURCES} ${GPU_LIB_CUDPP_SOURCES} ${GPU_OBJS})
+      target_link_libraries(gpu ${CUDA_LIBRARIES} ${CUDA_CUDA_LIBRARY})
+      target_include_directories(gpu PRIVATE ${LAMMPS_LIB_BINARY_DIR}/gpu ${CUDA_INCLUDE_DIRS})
+      target_compile_definitions(gpu PRIVATE -D_${GPU_PREC_SETTING} -DMPI_GERYON -DUCL_NO_EXIT ${GPU_CUDA_MPS_FLAGS})
+      if(CUDPP_OPT)
+        target_include_directories(gpu PRIVATE ${LAMMPS_LIB_SOURCE_DIR}/gpu/cudpp_mini)
+        target_compile_definitions(gpu PRIVATE -DUSE_CUDPP)
+      endif()
+
+      list(APPEND LAMMPS_LINK_LIBS gpu)
+
+      add_executable(nvc_get_devices ${LAMMPS_LIB_SOURCE_DIR}/gpu/geryon/ucl_get_devices.cpp)
+      target_compile_definitions(nvc_get_devices PRIVATE -DUCL_CUDADR)
+      target_link_libraries(nvc_get_devices PRIVATE ${CUDA_LIBRARIES} ${CUDA_CUDA_LIBRARY})
+      target_include_directories(nvc_get_devices PRIVATE ${CUDA_INCLUDE_DIRS})
+
+
+    elseif(GPU_API STREQUAL "OPENCL")
+      find_package(OpenCL REQUIRED)
+      set(OCL_TUNE "generic" CACHE STRING "OpenCL Device Tuning")
+      set(OCL_TUNE_VALUES intel fermi kepler cypress generic)
+      set_property(CACHE OCL_TUNE PROPERTY STRINGS ${OCL_TUNE_VALUES})
+      validate_option(OCL_TUNE OCL_TUNE_VALUES)
+      string(TOUPPER ${OCL_TUNE} OCL_TUNE)
+
+      include(OpenCLUtils)
+      set(OCL_COMMON_HEADERS ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_preprocessor.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_aux_fun1.h)
+
+      file(GLOB GPU_LIB_CU ${LAMMPS_LIB_SOURCE_DIR}/gpu/[^.]*.cu)
+      list(REMOVE_ITEM GPU_LIB_CU
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_gayberne.cu
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_gayberne_lj.cu
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_re_squared.cu
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_re_squared_lj.cu
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff.cu
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_zbl.cu
+        ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_mod.cu
+      )
+
+      foreach(GPU_KERNEL ${GPU_LIB_CU})
+          get_filename_component(basename ${GPU_KERNEL} NAME_WE)
+          string(SUBSTRING ${basename} 4 -1 KERNEL_NAME)
+          GenerateOpenCLHeader(${KERNEL_NAME} ${CMAKE_CURRENT_BINARY_DIR}/gpu/${KERNEL_NAME}_cl.h ${OCL_COMMON_HEADERS} ${GPU_KERNEL})
+          list(APPEND GPU_LIB_SOURCES ${CMAKE_CURRENT_BINARY_DIR}/gpu/${KERNEL_NAME}_cl.h)
+      endforeach()
+
+      GenerateOpenCLHeader(gayberne ${CMAKE_CURRENT_BINARY_DIR}/gpu/gayberne_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_ellipsoid_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_gayberne.cu)
+      GenerateOpenCLHeader(gayberne_lj ${CMAKE_CURRENT_BINARY_DIR}/gpu/gayberne_lj_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_ellipsoid_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_gayberne_lj.cu)
+      GenerateOpenCLHeader(re_squared ${CMAKE_CURRENT_BINARY_DIR}/gpu/re_squared_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_ellipsoid_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_re_squared.cu)
+      GenerateOpenCLHeader(re_squared_lj ${CMAKE_CURRENT_BINARY_DIR}/gpu/re_squared_lj_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_ellipsoid_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_re_squared_lj.cu)
+      GenerateOpenCLHeader(tersoff ${CMAKE_CURRENT_BINARY_DIR}/gpu/tersoff_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff.cu)
+      GenerateOpenCLHeader(tersoff_zbl ${CMAKE_CURRENT_BINARY_DIR}/gpu/tersoff_zbl_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_zbl_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_zbl.cu)
+      GenerateOpenCLHeader(tersoff_mod ${CMAKE_CURRENT_BINARY_DIR}/gpu/tersoff_mod_cl.h ${OCL_COMMON_HEADERS} ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_mod_extra.h ${LAMMPS_LIB_SOURCE_DIR}/gpu/lal_tersoff_mod.cu)
+
+      list(APPEND GPU_LIB_SOURCES
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/gayberne_cl.h
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/gayberne_lj_cl.h
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/re_squared_cl.h
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/re_squared_lj_cl.h
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/tersoff_cl.h
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/tersoff_zbl_cl.h
+        ${CMAKE_CURRENT_BINARY_DIR}/gpu/tersoff_mod_cl.h
+      )
+
+      add_library(gpu STATIC ${GPU_LIB_SOURCES})
+      target_link_libraries(gpu ${OpenCL_LIBRARIES})
+      target_include_directories(gpu PRIVATE ${CMAKE_CURRENT_BINARY_DIR}/gpu ${OpenCL_INCLUDE_DIRS})
+      target_compile_definitions(gpu PRIVATE -D_${GPU_PREC_SETTING} -D${OCL_TUNE}_OCL -DMPI_GERYON -DUCL_NO_EXIT)
+      target_compile_definitions(gpu PRIVATE -DUSE_OPENCL)
+
+      list(APPEND LAMMPS_LINK_LIBS gpu)
+
+      add_executable(ocl_get_devices ${LAMMPS_LIB_SOURCE_DIR}/gpu/geryon/ucl_get_devices.cpp)
+      target_compile_definitions(ocl_get_devices PRIVATE -DUCL_OPENCL)
+      target_link_libraries(ocl_get_devices PRIVATE ${OpenCL_LIBRARIES})
+      target_include_directories(ocl_get_devices PRIVATE ${OpenCL_INCLUDE_DIRS})
+    endif()
+
+    # GPU package
+    FindStyleHeaders(${GPU_SOURCES_DIR} FIX_CLASS fix_ FIX)
+
+    set_property(GLOBAL PROPERTY "GPU_SOURCES" "${GPU_SOURCES}")
+
+    # detects styles which have GPU version
+    RegisterStylesExt(${GPU_SOURCES_DIR} gpu GPU_SOURCES)
+
+    get_property(GPU_SOURCES GLOBAL PROPERTY GPU_SOURCES)
+
+    list(APPEND LIB_SOURCES ${GPU_SOURCES})
+    include_directories(${GPU_SOURCES_DIR})
+endif()

cmake/Modules/Packages/KIM.cmake

@@ -0,0 +1,45 @@
+if(PKG_KIM)
+  find_package(CURL)
+  if(CURL_FOUND)
+    include_directories(${CURL_INCLUDE_DIRS})
+    list(APPEND LAMMPS_LINK_LIBS ${CURL_LIBRARIES})
+    add_definitions(-DLMP_KIM_CURL)
+  endif()
+  find_package(KIM-API QUIET)
+  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})
+  if(DOWNLOAD_KIM)
+    if(CMAKE_GENERATOR STREQUAL "Ninja")
+      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(ExternalProject)
+    ExternalProject_Add(kim_build
+      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}
+                 -DCMAKE_Fortran_COMPILER=${CMAKE_Fortran_COMPILER}
+                 -DCMAKE_INSTALL_PREFIX=<INSTALL_DIR>
+                 -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}
+      )
+    ExternalProject_get_property(kim_build INSTALL_DIR)
+    set(KIM-API_INCLUDE_DIRS ${INSTALL_DIR}/include/kim-api)
+    set(KIM-API_LDFLAGS ${INSTALL_DIR}/${CMAKE_INSTALL_LIBDIR}/libkim-api${CMAKE_SHARED_LIBRARY_SUFFIX})
+    list(APPEND LAMMPS_DEPS kim_build)
+  else()
+    find_package(KIM-API REQUIRED)
+  endif()
+  list(APPEND LAMMPS_LINK_LIBS "${KIM-API_LDFLAGS}")
+  include_directories(${KIM-API_INCLUDE_DIRS})
+endif()

cmake/Modules/Packages/KOKKOS.cmake

@@ -0,0 +1,53 @@
+if(PKG_KOKKOS)
+  set(LAMMPS_LIB_KOKKOS_SRC_DIR ${LAMMPS_LIB_SOURCE_DIR}/kokkos)
+  set(LAMMPS_LIB_KOKKOS_BIN_DIR ${LAMMPS_LIB_BINARY_DIR}/kokkos)
+  add_definitions(-DLMP_KOKKOS)
+  add_subdirectory(${LAMMPS_LIB_KOKKOS_SRC_DIR} ${LAMMPS_LIB_KOKKOS_BIN_DIR})
+
+  set(Kokkos_INCLUDE_DIRS ${LAMMPS_LIB_KOKKOS_SRC_DIR}/core/src
+                          ${LAMMPS_LIB_KOKKOS_SRC_DIR}/containers/src
+                          ${LAMMPS_LIB_KOKKOS_SRC_DIR}/algorithms/src
+                          ${LAMMPS_LIB_KOKKOS_BIN_DIR})
+  include_directories(${Kokkos_INCLUDE_DIRS})
+  list(APPEND LAMMPS_LINK_LIBS kokkos)
+
+  set(KOKKOS_PKG_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/KOKKOS)
+  set(KOKKOS_PKG_SOURCES ${KOKKOS_PKG_SOURCES_DIR}/kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/atom_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/atom_vec_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/comm_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/comm_tiled_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/neighbor_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/neigh_list_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/neigh_bond_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/fix_nh_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/nbin_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/npair_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/domain_kokkos.cpp
+                         ${KOKKOS_PKG_SOURCES_DIR}/modify_kokkos.cpp)
+
+  if(PKG_KSPACE)
+    list(APPEND KOKKOS_PKG_SOURCES ${KOKKOS_PKG_SOURCES_DIR}/gridcomm_kokkos.cpp)
+  endif()
+
+  set_property(GLOBAL PROPERTY "KOKKOS_PKG_SOURCES" "${KOKKOS_PKG_SOURCES}")
+
+  # detects styles which have KOKKOS version
+  RegisterStylesExt(${KOKKOS_PKG_SOURCES_DIR} kokkos KOKKOS_PKG_SOURCES)
+
+  # register kokkos-only styles
+  RegisterNBinStyle(${KOKKOS_PKG_SOURCES_DIR}/nbin_kokkos.h)
+  RegisterNPairStyle(${KOKKOS_PKG_SOURCES_DIR}/npair_kokkos.h)
+
+  if(PKG_USER-DPD)
+    get_property(KOKKOS_PKG_SOURCES GLOBAL PROPERTY KOKKOS_PKG_SOURCES)
+    list(APPEND KOKKOS_PKG_SOURCES ${KOKKOS_PKG_SOURCES_DIR}/npair_ssa_kokkos.cpp)
+    RegisterNPairStyle(${KOKKOS_PKG_SOURCES_DIR}/npair_ssa_kokkos.h)
+    set_property(GLOBAL PROPERTY "KOKKOS_PKG_SOURCES" "${KOKKOS_PKG_SOURCES}")
+  endif()
+
+  get_property(KOKKOS_PKG_SOURCES GLOBAL PROPERTY KOKKOS_PKG_SOURCES)
+
+  list(APPEND LIB_SOURCES ${KOKKOS_PKG_SOURCES})
+  include_directories(${KOKKOS_PKG_SOURCES_DIR})
+endif()

cmake/Modules/Packages/KSPACE.cmake

@@ -0,0 +1,42 @@
+if(PKG_KSPACE)
+  option(FFT_SINGLE "Use single precision FFTs instead of double precision FFTs" OFF)
+  set(FFTW "FFTW3")
+  if(FFT_SINGLE)
+    set(FFTW "FFTW3F")
+    add_definitions(-DFFT_SINGLE)
+  endif()
+  find_package(${FFTW} QUIET)
+  if(${FFTW}_FOUND)
+    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 FFTW3 MKL)
+  set_property(CACHE FFT PROPERTY STRINGS ${FFT_VALUES})
+  validate_option(FFT FFT_VALUES)
+  string(TOUPPER ${FFT} FFT)
+
+  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})
+  validate_option(FFT_PACK FFT_PACK_VALUES)
+  if(NOT FFT_PACK STREQUAL "array")
+    string(TOUPPER ${FFT_PACK} FFT_PACK)
+    add_definitions(-DFFT_PACK_${FFT_PACK})
+  endif()
+endif()

cmake/Modules/Packages/LATTE.cmake

@@ -0,0 +1,38 @@
+if(PKG_LATTE)
+  enable_language(Fortran)
+  find_package(LATTE)
+  if(LATTE_FOUND)
+    set(DOWNLOAD_LATTE_DEFAULT OFF)
+  else()
+    set(DOWNLOAD_LATTE_DEFAULT ON)
+  endif()
+  option(DOWNLOAD_LATTE "Download the LATTE library instead of using an already installed one" ${DOWNLOAD_LATTE_DEFAULT})
+  if(DOWNLOAD_LATTE)
+    if (CMAKE_VERSION VERSION_LESS "3.7") # due to SOURCE_SUBDIR
+      message(FATAL_ERROR "For downlading LATTE you need at least cmake-3.7")
+    endif()
+    if(CMAKE_GENERATOR STREQUAL "Ninja")
+      message(FATAL_ERROR "Cannot build downloaded LATTE library with Ninja build tool")
+    endif()
+    message(STATUS "LATTE download requested - we will build our own")
+    include(ExternalProject)
+    ExternalProject_Add(latte_build
+      URL https://github.com/lanl/LATTE/archive/v1.2.1.tar.gz
+      URL_MD5 85ac414fdada2d04619c8f936344df14
+      SOURCE_SUBDIR cmake
+      CMAKE_ARGS -DCMAKE_INSTALL_PREFIX=<INSTALL_DIR> ${CMAKE_REQUEST_PIC}
+      -DBLAS_LIBRARIES=${BLAS_LIBRARIES} -DLAPACK_LIBRARIES=${LAPACK_LIBRARIES}
+      -DCMAKE_Fortran_COMPILER=${CMAKE_Fortran_COMPILER} -DCMAKE_Fortran_FLAGS=${CMAKE_Fortran_FLAGS}
+      -DCMAKE_Fortran_FLAGS_${BTYPE}=${CMAKE_Fortran_FLAGS_${BTYPE}} -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE}
+    )
+    ExternalProject_get_property(latte_build INSTALL_DIR)
+    set(LATTE_LIBRARIES ${INSTALL_DIR}/${CMAKE_INSTALL_LIBDIR}/liblatte.a)
+    list(APPEND LAMMPS_DEPS latte_build)
+  else()
+    find_package(LATTE)
+    if(NOT LATTE_FOUND)
+      message(FATAL_ERROR "LATTE library not found, help CMake to find it by setting LATTE_LIBRARY, or set DOWNLOAD_LATTE=ON to download it")
+    endif()
+  endif()
+  list(APPEND LAMMPS_LINK_LIBS ${LATTE_LIBRARIES} ${LAPACK_LIBRARIES})
+endif()

cmake/Modules/Packages/MESSAGE.cmake

@@ -0,0 +1,29 @@
+if(PKG_MESSAGE)
+  option(MESSAGE_ZMQ "Use ZeroMQ in MESSAGE package" OFF)
+  file(GLOB_RECURSE cslib_SOURCES ${LAMMPS_LIB_SOURCE_DIR}/message/cslib/[^.]*.F
+      ${LAMMPS_LIB_SOURCE_DIR}/message/cslib/[^.]*.c
+      ${LAMMPS_LIB_SOURCE_DIR}/message/cslib/[^.]*.cpp)
+
+  add_library(cslib STATIC ${cslib_SOURCES})
+  if(BUILD_MPI)
+    target_compile_definitions(cslib PRIVATE -DMPI_YES)
+    set_target_properties(cslib PROPERTIES OUTPUT_NAME "csmpi")
+  else()
+    target_compile_definitions(cslib PRIVATE -DMPI_NO)
+    target_include_directories(cslib PRIVATE ${LAMMPS_LIB_SOURCE_DIR}/message/cslib/src/STUBS_MPI)
+    set_target_properties(cslib PROPERTIES OUTPUT_NAME "csnompi")
+  endif()
+
+  if(MESSAGE_ZMQ)
+    target_compile_definitions(cslib PRIVATE -DZMQ_YES)
+    find_package(ZMQ REQUIRED)
+    target_include_directories(cslib PRIVATE ${ZMQ_INCLUDE_DIRS})
+    target_link_libraries(cslib PUBLIC ${ZMQ_LIBRARIES})
+  else()
+    target_compile_definitions(cslib PRIVATE -DZMQ_NO)
+    target_include_directories(cslib PRIVATE ${LAMMPS_LIB_SOURCE_DIR}/message/cslib/src/STUBS_ZMQ)
+  endif()
+
+  list(APPEND LAMMPS_LINK_LIBS cslib)
+  include_directories(${LAMMPS_LIB_SOURCE_DIR}/message/cslib/src)
+endif()

cmake/Modules/Packages/MSCG.cmake

@@ -0,0 +1,45 @@
+if(PKG_MSCG)
+  find_package(GSL REQUIRED)
+  find_package(MSCG QUIET)
+  if(MSGC_FOUND)
+    set(DOWNLOAD_MSCG_DEFAULT OFF)
+  else()
+    set(DOWNLOAD_MSCG_DEFAULT ON)
+  endif()
+  option(DOWNLOAD_MSCG "Download MSCG library instead of using an already installed one)" ${DOWNLOAD_MSCG_DEFAULT})
+  if(DOWNLOAD_MSCG)
+    if (CMAKE_VERSION VERSION_LESS "3.7") # due to SOURCE_SUBDIR
+      message(FATAL_ERROR "For downlading MSCG you need at least cmake-3.7")
+    endif()
+    if(CMAKE_GENERATOR STREQUAL "Ninja")
+      message(FATAL_ERROR "Cannot build downloaded MSCG library with Ninja build tool")
+    endif()
+    include(ExternalProject)
+    if(NOT LAPACK_FOUND)
+      set(EXTRA_MSCG_OPTS "-DLAPACK_LIBRARIES=${CMAKE_CURRENT_BINARY_DIR}/liblinalg.a")
+    endif()
+    ExternalProject_Add(mscg_build
+      URL https://github.com/uchicago-voth/MSCG-release/archive/1.7.3.1.tar.gz
+      URL_MD5 8c45e269ee13f60b303edd7823866a91
+      SOURCE_SUBDIR src/CMake
+      CMAKE_ARGS -DCMAKE_INSTALL_PREFIX=<INSTALL_DIR> ${CMAKE_REQUEST_PIC} ${EXTRA_MSCG_OPTS}
+      BUILD_COMMAND make mscg INSTALL_COMMAND ""
+      )
+    ExternalProject_get_property(mscg_build BINARY_DIR)
+    set(MSCG_LIBRARIES ${BINARY_DIR}/libmscg.a)
+    ExternalProject_get_property(mscg_build SOURCE_DIR)
+    set(MSCG_INCLUDE_DIRS ${SOURCE_DIR}/src)
+    list(APPEND LAMMPS_DEPS mscg_build)
+    if(NOT LAPACK_FOUND)
+      file(MAKE_DIRECTORY ${MSCG_INCLUDE_DIRS})
+      add_dependencies(mscg_build linalg)
+    endif()
+  else()
+    find_package(MSCG)
+    if(NOT MSCG_FOUND)
+      message(FATAL_ERROR "MSCG not found, help CMake to find it by setting MSCG_LIBRARY and MSCG_INCLUDE_DIRS, or set DOWNLOAD_MSCG=ON to download it")
+    endif()
+  endif()
+  list(APPEND LAMMPS_LINK_LIBS ${MSCG_LIBRARIES} ${GSL_LIBRARIES} ${LAPACK_LIBRARIES})
+  include_directories(${MSCG_INCLUDE_DIRS})
+endif()

cmake/Modules/Packages/OPT.cmake

@@ -0,0 +1,13 @@
+if(PKG_OPT)
+    set(OPT_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/OPT)
+    set(OPT_SOURCES)
+    set_property(GLOBAL PROPERTY "OPT_SOURCES" "${OPT_SOURCES}")
+
+    # detects styles which have OPT version
+    RegisterStylesExt(${OPT_SOURCES_DIR} opt OPT_SOURCES)
+
+    get_property(OPT_SOURCES GLOBAL PROPERTY OPT_SOURCES)
+
+    list(APPEND LIB_SOURCES ${OPT_SOURCES})
+    include_directories(${OPT_SOURCES_DIR})
+endif()

cmake/Modules/Packages/PYTHON.cmake

@@ -0,0 +1,6 @@
+if(PKG_PYTHON)
+  find_package(PythonLibs REQUIRED)
+  add_definitions(-DLMP_PYTHON)
+  include_directories(${PYTHON_INCLUDE_DIR})
+  list(APPEND LAMMPS_LINK_LIBS ${PYTHON_LIBRARY})
+endif()

cmake/Modules/Packages/QEQ.cmake

@@ -0,0 +1,20 @@
+# Fix qeq/fire requires MANYBODY (i.e. COMB and COMB3) to be installed
+if(PKG_QEQ)
+  set(QEQ_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/QEQ)
+  file(GLOB QEQ_HEADERS ${QEQ_SOURCES_DIR}/fix*.h)
+  file(GLOB QEQ_SOURCES ${QEQ_SOURCES_DIR}/fix*.cpp)
+
+  if(NOT PKG_MANYBODY)
+    list(REMOVE_ITEM QEQ_HEADERS ${QEQ_SOURCES_DIR}/fix_qeq_fire.h)
+    list(REMOVE_ITEM QEQ_SOURCES ${QEQ_SOURCES_DIR}/fix_qeq_fire.cpp)
+  endif()
+  set_property(GLOBAL PROPERTY "QEQ_SOURCES" "${QEQ_SOURCES}")
+
+  foreach(MY_HEADER ${QEQ_HEADERS})
+    AddStyleHeader(${MY_HEADER} FIX)
+  endforeach()
+
+  get_property(QEQ_SOURCES GLOBAL PROPERTY QEQ_SOURCES)
+  list(APPEND LIB_SOURCES ${QEQ_SOURCES})
+  include_directories(${QEQ_SOURCES_DIR})
+endif()

cmake/Modules/Packages/USER-H5MD.cmake

@@ -0,0 +1,8 @@
+if(PKG_USER-H5MD)
+  enable_language(C)
+
+  find_package(HDF5 REQUIRED)
+  target_link_libraries(h5md ${HDF5_LIBRARIES})
+  target_include_directories(h5md PRIVATE ${HDF5_INCLUDE_DIRS})
+  include_directories(${HDF5_INCLUDE_DIRS})
+endif()

cmake/Modules/Packages/USER-INTEL.cmake

@@ -0,0 +1,118 @@
+if(PKG_USER-INTEL)
+  check_include_file_cxx(immintrin.h FOUND_IMMINTRIN)
+  if(NOT FOUND_IMMINTRIN)
+    message(FATAL_ERROR "immintrin.h header not found, Intel package won't work without it")
+  endif()
+
+  add_definitions(-DLMP_USER_INTEL)
+
+  set(INTEL_ARCH "cpu" CACHE STRING "Architectures used by USER-INTEL (cpu or knl)")
+  set(INTEL_ARCH_VALUES cpu knl)
+  set_property(CACHE INTEL_ARCH PROPERTY STRINGS ${INTEL_ARCH_VALUES})
+  validate_option(INTEL_ARCH INTEL_ARCH_VALUES)
+  string(TOUPPER ${INTEL_ARCH} INTEL_ARCH)
+
+  find_package(Threads QUIET)
+  if(Threads_FOUND)
+    set(INTEL_LRT_MODE "threads" CACHE STRING "Long-range threads mode (none, threads, or c++11)")
+  else()
+    set(INTEL_LRT_MODE "none" CACHE STRING "Long-range threads mode (none, threads, or c++11)")
+  endif()
+  set(INTEL_LRT_VALUES none threads c++11)
+  set_property(CACHE INTEL_LRT_MODE PROPERTY STRINGS ${INTEL_LRT_VALUES})
+  validate_option(INTEL_LRT_MODE INTEL_LRT_VALUES)
+  string(TOUPPER ${INTEL_LRT_MODE} INTEL_LRT_MODE)
+  if(INTEL_LRT_MODE STREQUAL "THREADS")
+    if(Threads_FOUND)
+      add_definitions(-DLMP_INTEL_USELRT)
+      list(APPEND LAMMPS_LINK_LIBS ${CMAKE_THREAD_LIBS_INIT})
+    else()
+      message(FATAL_ERROR "Must have working threads library for Long-range thread support")
+    endif()
+  endif()
+  if(INTEL_LRT_MODE STREQUAL "C++11")
+    add_definitions(-DLMP_INTEL_USERLRT -DLMP_INTEL_LRT11)
+  endif()
+
+  if(CMAKE_CXX_COMPILER_ID STREQUAL "Intel")
+    if(CMAKE_CXX_COMPILER_VERSION VERSION_LESS 16)
+      message(FATAL_ERROR "USER-INTEL needs at least a 2016 Intel compiler, found ${CMAKE_CXX_COMPILER_VERSION}")
+    endif()
+  else()
+    message(WARNING "USER-INTEL gives best performance with Intel compilers")
+  endif()
+
+  find_package(TBB QUIET)
+  if(TBB_FOUND)
+    list(APPEND LAMMPS_LINK_LIBS ${TBB_MALLOC_LIBRARIES})
+  else()
+    add_definitions(-DLMP_INTEL_NO_TBB)
+    if(CMAKE_CXX_COMPILER_ID STREQUAL "Intel")
+      message(WARNING "USER-INTEL with Intel compilers should use TBB malloc libraries")
+    endif()
+  endif()
+
+  find_package(MKL QUIET)
+  if(MKL_FOUND)
+    add_definitions(-DLMP_USE_MKL_RNG)
+    list(APPEND LAMMPS_LINK_LIBS ${MKL_LIBRARIES})
+  else()
+    message(STATUS "Pair style dpd/intel will be faster with MKL libraries")
+  endif()
+
+  if((NOT ${CMAKE_SYSTEM_NAME} STREQUAL "Windows") AND (NOT ${LAMMPS_MEMALIGN} STREQUAL "64") AND (NOT ${LAMMPS_MEMALIGN} STREQUAL "128") AND (NOT ${LAMMPS_MEMALIGN} STREQUAL "256"))
+    message(FATAL_ERROR "USER-INTEL only supports memory alignment of 64, 128 or 256 on this platform")
+  endif()
+
+  if(INTEL_ARCH STREQUAL "KNL")
+    if(NOT CMAKE_CXX_COMPILER_ID STREQUAL "Intel")
+      message(FATAL_ERROR "Must use Intel compiler with USER-INTEL for KNL architecture")
+    endif()
+    set(CMAKE_EXE_LINKER_FLAGS  "${CMAKE_EXE_LINKER_FLAGS} -xHost -qopenmp -qoffload")
+    set(MIC_OPTIONS "-qoffload-option,mic,compiler,\"-fp-model fast=2 -mGLOB_default_function_attrs=\\\"gather_scatter_loop_unroll=4\\\"\"")
+    add_compile_options(-xMIC-AVX512 -qoffload -fno-alias -ansi-alias -restrict -qoverride-limits ${MIC_OPTIONS})
+    add_definitions(-DLMP_INTEL_OFFLOAD)
+  else()
+    if(CMAKE_CXX_COMPILER_ID STREQUAL "Intel")
+      if(CMAKE_CXX_COMPILER_VERSION VERSION_EQUAL 17.3 OR CMAKE_CXX_COMPILER_VERSION VERSION_EQUAL 17.4)
+        set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -xCOMMON-AVX512")
+      else()
+        set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -xHost")
+      endif()
+      include(CheckCXXCompilerFlag)
+      foreach(_FLAG -O2 -fp-model fast=2 -no-prec-div -qoverride-limits -qopt-zmm-usage=high -qno-offload -fno-alias -ansi-alias -restrict)
+        check_cxx_compiler_flag("${__FLAG}" COMPILER_SUPPORTS${_FLAG})
+        if(COMPILER_SUPPORTS${_FLAG})
+          add_compile_options(${_FLAG})
+        endif()
+      endforeach()
+    else()
+      add_compile_options(-O3 -ffast-math)
+    endif()
+  endif()
+
+  # collect sources
+  set(USER-INTEL_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/USER-INTEL)
+  set(USER-INTEL_SOURCES ${USER-INTEL_SOURCES_DIR}/fix_intel.cpp
+                         ${USER-INTEL_SOURCES_DIR}/fix_nh_intel.cpp
+                         ${USER-INTEL_SOURCES_DIR}/intel_buffers.cpp
+                         ${USER-INTEL_SOURCES_DIR}/nbin_intel.cpp
+                         ${USER-INTEL_SOURCES_DIR}/npair_intel.cpp)
+
+  set_property(GLOBAL PROPERTY "USER-INTEL_SOURCES" "${USER-INTEL_SOURCES}")
+
+  # detect styles which have a USER-INTEL version
+  RegisterStylesExt(${USER-INTEL_SOURCES_DIR} intel USER-INTEL_SOURCES)
+  RegisterNBinStyle(${USER-INTEL_SOURCES_DIR}/nbin_intel.h)
+  RegisterNPairStyle(${USER-INTEL_SOURCES_DIR}/npair_intel.h)
+  RegisterFixStyle(${USER-INTEL_SOURCES_DIR}/fix_intel.h)
+
+  get_property(USER-INTEL_SOURCES GLOBAL PROPERTY USER-INTEL_SOURCES)
+  if(PKG_KSPACE)
+    list(APPEND USER-INTEL_SOURCES ${USER-INTEL_SOURCES_DIR}/verlet_lrt_intel.cpp)
+    RegisterIntegrateStyle(${USER-INTEL_SOURCES_DIR}/verlet_lrt_intel.h)
+  endif()
+
+  list(APPEND LIB_SOURCES ${USER-INTEL_SOURCES})
+  include_directories(${USER-INTEL_SOURCES_DIR})
+endif()

cmake/Modules/Packages/USER-MOLFILE.cmake

@@ -0,0 +1,10 @@
+if(PKG_USER-MOLFILE)
+  set(MOLFILE_INCLUDE_DIRS "${LAMMPS_LIB_SOURCE_DIR}/molfile" CACHE STRING "Path to VMD molfile plugin headers")
+  add_library(molfile INTERFACE)
+  target_include_directories(molfile INTERFACE ${MOLFILE_INCLUDE_DIRS})
+  # no need to link with -ldl on windows
+  if(NOT ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
+    target_link_libraries(molfile INTERFACE ${CMAKE_DL_LIBS})
+  endif()
+  list(APPEND LAMMPS_LINK_LIBS molfile)
+endif()

cmake/Modules/Packages/USER-NETCDF.cmake

@@ -0,0 +1,6 @@
+if(PKG_USER-NETCDF)
+  find_package(NetCDF REQUIRED)
+  include_directories(${NETCDF_INCLUDE_DIRS})
+  list(APPEND LAMMPS_LINK_LIBS ${NETCDF_LIBRARIES})
+  add_definitions(-DLMP_HAS_NETCDF -DNC_64BIT_DATA=0x0020)
+endif()

cmake/Modules/Packages/USER-OMP.cmake

@@ -0,0 +1,42 @@
+if(PKG_USER-OMP)
+    set(USER-OMP_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/USER-OMP)
+    set(USER-OMP_SOURCES ${USER-OMP_SOURCES_DIR}/thr_data.cpp
+                         ${USER-OMP_SOURCES_DIR}/thr_omp.cpp
+                         ${USER-OMP_SOURCES_DIR}/fix_omp.cpp
+                         ${USER-OMP_SOURCES_DIR}/fix_nh_omp.cpp
+                         ${USER-OMP_SOURCES_DIR}/fix_nh_sphere_omp.cpp
+                         ${USER-OMP_SOURCES_DIR}/domain_omp.cpp)
+    add_definitions(-DLMP_USER_OMP)
+    set_property(GLOBAL PROPERTY "OMP_SOURCES" "${USER-OMP_SOURCES}")
+
+    # detects styles which have USER-OMP version
+    RegisterStylesExt(${USER-OMP_SOURCES_DIR} omp OMP_SOURCES)
+    RegisterFixStyle(${USER-OMP_SOURCES_DIR}/fix_omp.h)
+
+    get_property(USER-OMP_SOURCES GLOBAL PROPERTY OMP_SOURCES)
+
+    # manually add package dependent source files from USER-OMP that do not provide styles
+
+    if(PKG_ASPHERE)
+      list(APPEND USER-OMP_SOURCES ${USER-OMP_SOURCES_DIR}/fix_nh_asphere_omp.cpp)
+    endif()
+
+    if(PKG_RIGID)
+      list(APPEND USER-OMP_SOURCES ${USER-OMP_SOURCES_DIR}/fix_rigid_nh_omp.cpp)
+    endif()
+
+    if(PKG_USER-REAXC)
+      list(APPEND USER-OMP_SOURCES ${USER-OMP_SOURCES_DIR}/reaxc_bond_orders_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_hydrogen_bonds_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_nonbonded_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_bonds_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_init_md_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_torsion_angles_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_forces_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_multi_body_omp.cpp
+                                   ${USER-OMP_SOURCES_DIR}/reaxc_valence_angles_omp.cpp)
+    endif()
+
+    list(APPEND LIB_SOURCES ${USER-OMP_SOURCES})
+    include_directories(${USER-OMP_SOURCES_DIR})
+endif()

cmake/Modules/Packages/USER-PLUMED.cmake

@@ -0,0 +1,91 @@
+if(PKG_USER-PLUMED)
+  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)
+    pkg_check_modules(PLUMED QUIET plumed)
+    if(PLUMED_FOUND)
+      set(DOWNLOAD_PLUMED_DEFAULT OFF)
+    endif()
+  endif()
+
+  option(DOWNLOAD_PLUMED "Download Plumed package instead of using an already installed one" ${DOWNLOAD_PLUMED_DEFAULT})
+  if(DOWNLOAD_PLUMED)
+    if(CMAKE_GENERATOR STREQUAL "Ninja")
+      message(FATAL_ERROR "Cannot build downloaded Plumed library with Ninja build tool")
+    endif()
+    if(BUILD_MPI)
+      set(PLUMED_CONFIG_MPI "--enable-mpi")
+      set(PLUMED_CONFIG_CC  ${CMAKE_MPI_C_COMPILER})
+      set(PLUMED_CONFIG_CXX  ${CMAKE_MPI_CXX_COMPILER})
+    else()
+      set(PLUMED_CONFIG_MPI "--disable-mpi")
+      set(PLUMED_CONFIG_CC  ${CMAKE_C_COMPILER})
+      set(PLUMED_CONFIG_CXX  ${CMAKE_CXX_COMPILER})
+    endif()
+    if(BUILD_OMP)
+      set(PLUMED_CONFIG_OMP "--enable-openmp")
+    else()
+      set(PLUMED_CONFIG_OMP "--disable-openmp")
+    endif()
+    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.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}
+                                               --enable-modules=all
+                                               ${PLUMED_CONFIG_MPI}
+                                               ${PLUMED_CONFIG_OMP}
+                                               CXX=${PLUMED_CONFIG_CXX}
+                                               CC=${PLUMED_CONFIG_CC}
+    )
+    ExternalProject_get_property(plumed_build INSTALL_DIR)
+    set(PLUMED_INSTALL_DIR ${INSTALL_DIR})
+    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 ${PLUMED_LINK_LIBS} ${CMAKE_DL_LIBS})
+    elseif(PLUMED_MODE STREQUAL "SHARED")
+      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${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")
+  else()
+    find_package(PkgConfig REQUIRED)
+    pkg_check_modules(PLUMED REQUIRED plumed)
+    if(PLUMED_MODE STREQUAL "STATIC")
+      add_definitions(-D__PLUMED_WRAPPER_CXX=1)
+      include(${PLUMED_LIBDIR}/plumed/src/lib/Plumed.cmake.static)
+    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${CMAKE_SHARED_LIBRARY_SUFFIX})
+      include(${PLUMED_LIBDIR}/plumed/src/lib/Plumed.cmake.runtime)
+    endif()
+    list(APPEND LAMMPS_LINK_LIBS ${PLUMED_LOAD})
+  endif()
+  include_directories(${PLUMED_INCLUDE_DIRS})
+endif()

cmake/Modules/Packages/USER-QMMM.cmake

@@ -0,0 +1,9 @@
+if(PKG_USER-QMMM)
+  enable_language(Fortran)
+  enable_language(C)
+
+  message(WARNING "Building QMMM with CMake is still experimental")
+  find_package(QE REQUIRED)
+  include_directories(${QE_INCLUDE_DIRS})
+  list(APPEND LAMMPS_LINK_LIBS ${QE_LIBRARIES})
+endif()

cmake/Modules/Packages/USER-QUIP.cmake

@@ -0,0 +1,5 @@
+if(PKG_USER-QUIP)
+  enable_language(Fortran)
+  find_package(QUIP REQUIRED)
+  list(APPEND LAMMPS_LINK_LIBS ${QUIP_LIBRARIES} ${LAPACK_LIBRARIES})
+endif()

cmake/Modules/Packages/USER-SCAFACOS.cmake

@@ -0,0 +1,62 @@
+if(PKG_USER-SCAFACOS)
+  enable_language(Fortran)
+  enable_language(C)
+
+  find_package(GSL REQUIRED)
+  find_package(PkgConfig QUIET)
+  set(DOWNLOAD_SCAFACOS_DEFAULT ON)
+  if(PKG_CONFIG_FOUND)
+    pkg_check_modules(SCAFACOS QUIET scafacos)
+    if(SCAFACOS_FOUND)
+      set(DOWNLOAD_SCAFACOS_DEFAULT OFF)
+    endif()
+  endif()
+  option(DOWNLOAD_SCAFACOS "Download ScaFaCoS library instead of using an already installed one" ${DOWNLOAD_SCAFACOS_DEFAULT})
+  if(DOWNLOAD_SCAFACOS)
+    if(CMAKE_GENERATOR STREQUAL "Ninja")
+      message(FATAL_ERROR "Cannot build downloaded ScaFaCoS library with Ninja build tool")
+    endif()
+    message(STATUS "ScaFaCoS download requested - we will build our own")
+    include(ExternalProject)
+    ExternalProject_Add(scafacos_build
+      URL https://github.com/scafacos/scafacos/releases/download/v1.0.1/scafacos-1.0.1.tar.gz
+      URL_MD5 bd46d74e3296bd8a444d731bb10c1738
+      CONFIGURE_COMMAND <SOURCE_DIR>/configure --prefix=<INSTALL_DIR> --disable-doc
+                                               --enable-fcs-solvers=fmm,p2nfft,direct,ewald,p3m
+                                               --with-internal-fftw --with-internal-pfft
+                                               --with-internal-pnfft ${CONFIGURE_REQUEST_PIC}
+                                               FC=${CMAKE_MPI_Fortran_COMPILER}
+                                               CXX=${CMAKE_MPI_CXX_COMPILER}
+                                               CC=${CMAKE_MPI_C_COMPILER}
+                                               F77=
+    )
+    ExternalProject_get_property(scafacos_build INSTALL_DIR)
+    set(SCAFACOS_BUILD_DIR ${INSTALL_DIR})
+    set(SCAFACOS_INCLUDE_DIRS ${SCAFACOS_BUILD_DIR}/include)
+    list(APPEND LAMMPS_DEPS scafacos_build)
+    # list and order from pkg_config file of ScaFaCoS build
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_direct.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_ewald.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_fmm.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_p2nfft.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_p3m.a)
+    list(APPEND LAMMPS_LINK_LIBS ${GSL_LIBRARIES})
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_near.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_gridsort.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_resort.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_redist.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_common.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_pnfft.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_pfft.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_fftw3_mpi.a)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_BUILD_DIR}/lib/libfcs_fftw3.a)
+    list(APPEND LAMMPS_LINK_LIBS ${MPI_Fortran_LIBRARIES})
+    list(APPEND LAMMPS_LINK_LIBS ${MPI_C_LIBRARIES})
+  else()
+    find_package(PkgConfig REQUIRED)
+    pkg_check_modules(SCAFACOS REQUIRED scafacos)
+    list(APPEND LAMMPS_LINK_LIBS ${SCAFACOS_LDFLAGS})
+  endif()
+  include_directories(${SCAFACOS_INCLUDE_DIRS})
+endif()

cmake/Modules/Packages/USER-SDPD.cmake

@@ -0,0 +1,13 @@
+# Fix rigid/meso requires RIGID to be installed
+if(PKG_USER-SDPD)
+  set(USER-SDPD_SOURCES_DIR ${LAMMPS_SOURCE_DIR}/USER-SDPD)
+
+  get_property(hlist GLOBAL PROPERTY FIX)
+  if(NOT PKG_RIGID)
+    list(REMOVE_ITEM hlist ${USER-SDPD_SOURCES_DIR}/fix_rigid_meso.h)
+    list(REMOVE_ITEM LIB_SOURCES ${USER-SDPD_SOURCES_DIR}/fix_rigid_meso.cpp)
+  endif()
+  set_property(GLOBAL PROPERTY FIX "${hlist}")
+
+  include_directories(${USER-SDPD_SOURCES_DIR})
+endif()

cmake/Modules/Packages/USER-SMD.cmake

@@ -0,0 +1,28 @@
+if(PKG_USER-SMD)
+  find_package(Eigen3 NO_MODULE)
+  if(EIGEN3_FOUND)
+    set(DOWNLOAD_EIGEN3_DEFAULT OFF)
+  else()
+    set(DOWNLOAD_EIGEN3_DEFAULT ON)
+  endif()
+  option(DOWNLOAD_EIGEN3 "Download Eigen3 instead of using an already installed one)" ${DOWNLOAD_EIGEN3_DEFAULT})
+  if(DOWNLOAD_EIGEN3)
+    message(STATUS "Eigen3 download requested - we will build our own")
+    include(ExternalProject)
+    ExternalProject_Add(Eigen3_build
+      URL http://bitbucket.org/eigen/eigen/get/3.3.7.tar.gz
+      URL_MD5 f2a417d083fe8ca4b8ed2bc613d20f07
+      CONFIGURE_COMMAND "" BUILD_COMMAND "" INSTALL_COMMAND ""
+    )
+    ExternalProject_get_property(Eigen3_build SOURCE_DIR)
+    set(EIGEN3_INCLUDE_DIR ${SOURCE_DIR})
+    list(APPEND LAMMPS_DEPS Eigen3_build)
+  else()
+    find_package(Eigen3 NO_MODULE)
+    mark_as_advanced(Eigen3_DIR)
+    if(NOT EIGEN3_FOUND)
+      message(FATAL_ERROR "Eigen3 not found, help CMake to find it by setting EIGEN3_INCLUDE_DIR, or set DOWNLOAD_EIGEN3=ON to download it")
+    endif()
+  endif()
+  include_directories(${EIGEN3_INCLUDE_DIR})
+endif()

cmake/Modules/Packages/USER-VTK.cmake

@@ -0,0 +1,6 @@
+if(PKG_USER-VTK)
+  find_package(VTK REQUIRED NO_MODULE)
+  include(${VTK_USE_FILE})
+  add_definitions(-DLAMMPS_VTK)
+  list(APPEND LAMMPS_LINK_LIBS ${VTK_LIBRARIES})
+endif()

cmake/Modules/Packages/VORONOI.cmake

@@ -0,0 +1,41 @@
+if(PKG_VORONOI)
+  find_package(VORO)
+  if(VORO_FOUND)
+    set(DOWNLOAD_VORO_DEFAULT OFF)
+  else()
+    set(DOWNLOAD_VORO_DEFAULT ON)
+  endif()
+  option(DOWNLOAD_VORO "Download and compile the Voro++ library instead of using an already installed one" ${DOWNLOAD_VORO_DEFAULT})
+  if(DOWNLOAD_VORO)
+    if(CMAKE_GENERATOR STREQUAL "Ninja")
+      message(FATAL_ERROR "Cannot build downloaded Voro++ library with Ninja build tool")
+    endif()
+    message(STATUS "Voro++ download requested - we will build our own")
+    include(ExternalProject)
+
+    if(BUILD_SHARED_LIBS)
+      set(VORO_BUILD_CFLAGS "${CMAKE_SHARED_LIBRARY_CXX_FLAGS} ${CMAKE_CXX_FLAGS} ${CMAKE_CXX_FLAGS_${BTYPE}}")
+    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})
+
+    ExternalProject_Add(voro_build
+      URL https://download.lammps.org/thirdparty/voro++-0.4.6.tar.gz
+      URL_MD5 2338b824c3b7b25590e18e8df5d68af9
+      CONFIGURE_COMMAND "" BUILD_COMMAND make ${VORO_BUILD_OPTIONS} BUILD_IN_SOURCE 1 INSTALL_COMMAND ""
+      )
+    ExternalProject_get_property(voro_build SOURCE_DIR)
+    set(VORO_LIBRARIES ${SOURCE_DIR}/src/libvoro++.a)
+    set(VORO_INCLUDE_DIRS ${SOURCE_DIR}/src)
+    list(APPEND LAMMPS_DEPS voro_build)
+  else()
+    find_package(VORO)
+    if(NOT VORO_FOUND)
+      message(FATAL_ERROR "Voro++ library not found. Help CMake to find it by setting VORO_LIBRARY and VORO_INCLUDE_DIR, or set DOWNLOAD_VORO=ON to download it")
+    endif()
+  endif()
+  include_directories(${VORO_INCLUDE_DIRS})
+  list(APPEND LAMMPS_LINK_LIBS ${VORO_LIBRARIES})
+endif()

cmake/Modules/Testing.cmake

@@ -0,0 +1,52 @@
+###############################################################################
+# Testing
+###############################################################################
+option(ENABLE_TESTING "Enable testing" OFF)
+if(ENABLE_TESTING AND BUILD_EXE)
+  enable_testing()
+  option(LAMMPS_TESTING_SOURCE_DIR "Location of lammps-testing source directory" "")
+  option(LAMMPS_TESTING_GIT_TAG    "Git tag of lammps-testing" "master")
+  mark_as_advanced(LAMMPS_TESTING_SOURCE_DIR LAMMPS_TESTING_GIT_TAG)
+
+  if (CMAKE_VERSION VERSION_GREATER "3.10.3" AND NOT LAMMPS_TESTING_SOURCE_DIR)
+    include(FetchContent)
+
+    FetchContent_Declare(lammps-testing
+      GIT_REPOSITORY https://github.com/lammps/lammps-testing.git
+      GIT_TAG ${LAMMPS_TESTING_GIT_TAG}
+    )
+
+    FetchContent_GetProperties(lammps-testing)
+    if(NOT lammps-testing_POPULATED)
+      message(STATUS "Downloading tests...")
+      FetchContent_Populate(lammps-testing)
+    endif()
+
+    set(LAMMPS_TESTING_SOURCE_DIR ${lammps-testing_SOURCE_DIR})
+  elseif(NOT LAMMPS_TESTING_SOURCE_DIR)
+    message(WARNING "Full test-suite requires CMake >= 3.11 or copy of\n"
+                    "https://github.com/lammps/lammps-testing in LAMMPS_TESTING_SOURCE_DIR")
+  endif()
+
+  add_test(ShowHelp ${CMAKE_BINARY_DIR}/${LAMMPS_BINARY} -help)
+
+  if(EXISTS ${LAMMPS_TESTING_SOURCE_DIR})
+    message(STATUS "Running test discovery...")
+
+    file(GLOB_RECURSE TEST_SCRIPTS ${LAMMPS_TESTING_SOURCE_DIR}/tests/core/*/in.*)
+    foreach(script_path ${TEST_SCRIPTS})
+      get_filename_component(TEST_NAME ${script_path} EXT)
+      get_filename_component(SCRIPT_NAME ${script_path} NAME)
+      get_filename_component(PARENT_DIR ${script_path} DIRECTORY)
+      string(SUBSTRING ${TEST_NAME} 1 -1 TEST_NAME)
+      string(REPLACE "-" "_" TEST_NAME ${TEST_NAME})
+      string(REPLACE "+" "_" TEST_NAME ${TEST_NAME})
+      set(TEST_NAME "test_core_${TEST_NAME}_serial")
+      add_test(${TEST_NAME} ${CMAKE_BINARY_DIR}/${LAMMPS_BINARY} -in ${SCRIPT_NAME})
+      set_tests_properties(${TEST_NAME} PROPERTIES WORKING_DIRECTORY ${PARENT_DIR})
+    endforeach()
+    list(LENGTH TEST_SCRIPTS NUM_TESTS)
+
+    message(STATUS "Found ${NUM_TESTS} tests.")
+  endif()
+endif()

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

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 "31 May 2019" "2019-05-31"
+.TH LAMMPS "31 July 2019" "2019-07-31"
 .SH NAME
 .B LAMMPS
 \- Molecular Dynamics Simulator.

doc/src/Build_cmake.txt

@@ -32,10 +32,18 @@ cmake \[options ...\] ../cmake     # configuration with (command-line) cmake
 make                             # compilation :pre
 
 The cmake command will detect available features, enable selected
-packages and options, and will generate the build environment.  The make
-command will then compile and link LAMMPS, producing (by default) an
-executable called "lmp" and a library called "liblammps.a" in the
-"build" folder.
+packages and options, and will generate the build environment.  By default
+this build environment will be created for "Unix Makefiles" on most
+platforms and particularly on Linux.  However, alternate build tools
+(e.g. Ninja) and support files for Integrated Development Environments
+(IDE) like Eclipse, CodeBlocks, or Kate can be generated, too. This is
+selected via the "-G" command line flag. For the rest of the documentation
+we will assume that the build environment is generated for makefiles
+and thus the make command will be used to compile and link LAMMPS as
+indicated above, producing (by default) an executable called "lmp" and
+a library called "liblammps.a" in the "build" folder.  When generating
+a build environment for the "Ninja" build tool, the build command would
+be "ninja" instead of "make".
 
 If your machine has multiple CPU cores (most do these days), using a
 command like "make -jN" (with N being the number of available local
@@ -44,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

doc/src/Build_extras.txt

@@ -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]:
 

doc/src/Commands.txt

@@ -33,6 +33,11 @@ commands in it are used to define a LAMMPS simulation.
    Commands_bond
    Commands_kspace
 
+.. toctree::
+   :maxdepth: 1
+
+   Commands_removed
+
 END_RST -->
 
 <!-- HTML_ONLY -->
@@ -49,5 +54,7 @@ END_RST -->
 "Bond, angle, dihedral, improper commands"_Commands_bond.html
 "KSpace solvers"_Commands_kspace.html  :all(b)
 
+"Removed commands and packages"_Commands_removed.html  :all(b)
+
 <!-- END_HTML_ONLY -->
 

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_bond.txt

@@ -28,8 +28,12 @@ OPT.
 
 "none"_bond_none.html,
 "zero"_bond_zero.html,
-"hybrid"_bond_hybrid.html :tb(c=3,ea=c)
-
+"hybrid"_bond_hybrid.html,
+,
+,
+,
+,
+,
 "class2 (ko)"_bond_class2.html,
 "fene (iko)"_bond_fene.html,
 "fene/expand (o)"_bond_fene_expand.html,
@@ -56,8 +60,12 @@ OPT.
 
 "none"_angle_none.html,
 "zero"_angle_zero.html,
-"hybrid"_angle_hybrid.html :tb(c=3,ea=c)
-
+"hybrid"_angle_hybrid.html,
+,
+,
+,
+,
+,
 "charmm (iko)"_angle_charmm.html,
 "class2 (ko)"_angle_class2.html,
 "class2/p6"_angle_class2.html,
@@ -89,8 +97,12 @@ OPT.
 
 "none"_dihedral_none.html,
 "zero"_dihedral_zero.html,
-"hybrid"_dihedral_hybrid.html :tb(c=3,ea=c)
-
+"hybrid"_dihedral_hybrid.html,
+,
+,
+,
+,
+,
 "charmm (iko)"_dihedral_charmm.html,
 "charmmfsw"_dihedral_charmm.html,
 "class2 (ko)"_dihedral_class2.html,
@@ -117,8 +129,12 @@ OPT.
 
 "none"_improper_none.html,
 "zero"_improper_zero.html,
-"hybrid"_improper_hybrid.html :tb(c=3,ea=c)
-
+"hybrid"_improper_hybrid.html,
+,
+,
+,
+,
+,
 "class2 (ko)"_improper_class2.html,
 "cossq (o)"_improper_cossq.html,
 "cvff (io)"_improper_cvff.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

@@ -27,8 +27,11 @@ OPT.
 "none"_pair_none.html,
 "zero"_pair_zero.html,
 "hybrid (k)"_pair_hybrid.html,
-"hybrid/overlay (k)"_pair_hybrid.html :tb(c=4,ea=c)
-
+"hybrid/overlay (k)"_pair_hybrid.html,
+,
+,
+,
+,
 "adp (o)"_pair_adp.html,
 "agni (o)"_pair_agni.html,
 "airebo (io)"_pair_airebo.html,
@@ -219,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/Commands_removed.txt

@@ -0,0 +1,66 @@
+"Higher level section"_Commands.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.html)
+
+:line
+
+Removed commands and packages :h3
+
+This page lists LAMMPS commands and packages that have been removed from
+the distribution and provides suggestions for alternatives or replacements.
+LAMMPS has special dummy styles implemented, that will stop LAMMPS and
+print a suitable error message in most cases, when a style/command is used
+that has been removed.
+
+Fix ave/spatial and fix ave/spatial/sphere :h4
+
+The fixes ave/spatial and ave/spatial/sphere have been removed from LAMMPS
+since they were superseded by the more general and extensible "chunk
+infrastructure".  Here the system is partitioned in one of many possible
+ways through the "compute chunk/atom"_compute_chunk_atom.html command
+and then averaging is done using "fix ave/chunk"_fix_ave_chunk.html.
+Please refer to the "chunk HOWTO"_Howto_chunk.html section for an overview.
+
+MEAM package :h4
+
+The MEAM package has been removed since it was superseded by the
+"USER-MEAMC package"_Package_details.html#PKG-USER-MEAMC. The code in
+the USER-MEAMC package is a translation of the Fortran code of MEAM into C++,
+which removes several restrictions (e.g. there can be multiple instances
+in hybrid pair styles) and allows for some optimizations leading
+to better performance.  The new pair style "meam/c"_pair_meamc.html has
+the exact same syntax as the old "meam" pair style and thus pair style
+"meam"_pair_meamc.html is an alias to the new style and backward
+compatibility of old inputs is preserved.
+
+REAX package :h4
+
+The REAX package has been removed since it was superseded by the
+"USER-REAXC package"_Package_details.html#PKG-USER-REAXC.  The USER-REAXC
+package has been tested to yield equivalent results to the REAX package,
+offers better performance, supports OpenMP multi-threading via USER-OMP,
+and GPU and threading parallelization through KOKKOS.  The new pair styles
+are not syntax compatible with the removed reax pair style, so input
+files will have to be adapted.
+
+USER-CUDA package :h4
+
+The USER-CUDA package had been removed, since it had been unmaintained
+for a long time and had known bugs and problems.  Significant parts of
+the design were transferred to the
+"KOKKOS package"_Package_details.html#PKG-KOKKOS, which has similar
+performance characteristics on Nvidia GPUs. Both, the KOKKOS
+and the "GPU package"_Package_details.html#PKG-GPU are maintained
+and allow running LAMMPS with GPU acceleration.
+
+restart2data tool :h4
+
+The functionality of the restart2data tool has been folded into the
+LAMMPS executable directly instead of having a separate tool.  A
+combination of the commands "read_restart"_read_restart.html and
+"write_data"_write_data.html can be used to the same effect.  For added
+convenience this conversion can also be triggered by "command line
+flags"_Run_options.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_spin_dipole.tex

@@ -0,0 +1,42 @@
+\documentclass[preview]{standalone}
+\usepackage{varwidth}
+\usepackage[utf8x]{inputenc}
+\usepackage{amsmath,amssymb,graphics,bm,setspace}
+
+\begin{document}
+\begin{varwidth}{50in}
+  \begin{equation}
+    \mathcal{H}_{\rm long}= 
+    -\frac{\mu_{0} \left( \mu_B\right)^2}{4\pi} 
+    \sum_{i,j,i\neq j}^{N}
+    \frac{g_i g_j}{r_{ij}^3}
+    \Big(3 
+    \left(\bm{e}_{ij}\cdot \bm{s}_{i}\right) 
+    \left(\bm{e}_{ij}\cdot \bm{s}_{j}\right) 
+    -\bm{s}_i\cdot\bm{s}_j \Big)
+    \nonumber
+  \end{equation}
+  \begin{equation}
+    \bm{\omega}_i = 
+    \frac{\mu_0 (\mu_B)^2}{4\pi\hbar}\sum_{j}
+    \frac{g_i g_j}{r_{ij}^3}
+    \, \Big(
+    3\,(\bm{e}_{ij}\cdot\bm{s}_{j})\bm{e}_{ij}
+    -\bm{s}_{j} \Big) \nonumber
+  \end{equation}
+  \begin{equation}
+    \bm{F}_i =
+    \frac{3\, \mu_0 (\mu_B)^2}{4\pi} \sum_j
+    \frac{g_i g_j}{r_{ij}^4}
+    \Big[\big( (\bm{s}_i\cdot\bm{s}_j) 
+    -5(\bm{e}_{ij}\cdot\bm{s}_i)
+    (\bm{e}_{ij}\cdot\bm{s}_j)\big) \bm{e}_{ij}+
+    \big(
+    (\bm{e}_{ij}\cdot\bm{s}_i)\bm{s}_j+
+    (\bm{e}_{ij}\cdot\bm{s}_j)\bm{s}_i
+    \big)
+    \Big]
+    \nonumber
+  \end{equation}
+\end{varwidth}
+\end{document}

doc/src/Eqs/pair_spin_long_range.tex

@@ -0,0 +1,20 @@
+\documentclass[preview]{standalone}
+\usepackage{varwidth}
+\usepackage[utf8x]{inputenc}
+\usepackage{amsmath,amssymb,graphics,bm,setspace}
+
+\begin{document}
+\begin{varwidth}{50in}
+  \begin{equation}
+    \mathcal{H}_{\rm long}= 
+    -\frac{\mu_{0} \left( \mu_B\right)^2}{4\pi} 
+    \sum_{i,j,i\neq j}^{N}
+    \frac{g_i g_j}{r_{ij}^3}
+    \Big(3 
+    \left(\bm{e}_{ij}\cdot \bm{s}_{i}\right) 
+    \left(\bm{e}_{ij}\cdot \bm{s}_{j}\right) 
+    -\bm{s}_i\cdot\bm{s}_j \Big)
+    \nonumber
+  \end{equation}
+\end{varwidth}
+\end{document}

doc/src/Eqs/pair_spin_long_range_force.tex

@@ -0,0 +1,23 @@
+\documentclass[preview]{standalone}
+\usepackage{varwidth}
+\usepackage[utf8x]{inputenc}
+\usepackage{amsmath,amssymb,graphics,bm,setspace}
+
+\begin{document}
+\begin{varwidth}{50in}
+  \begin{equation}
+    \bm{F}_i =
+    \frac{\mu_0 (\mu_B)^2}{4\pi} \sum_j
+    \frac{g_i g_j}{r_{ij}^4}
+    \Big[\big( (\bm{s}_i\cdot\bm{s}_j) 
+    -5(\bm{e}_{ij}\cdot\bm{s}_i)
+    (\bm{e}_{ij}\cdot\bm{s}_j)\big) \bm{e}_{ij}+
+    \big(
+    (\bm{e}_{ij}\cdot\bm{s}_i)\bm{s}_j+
+    (\bm{e}_{ij}\cdot\bm{s}_j)\bm{s}_i
+    \big)
+    \Big]
+    \nonumber
+  \end{equation}
+\end{varwidth}
+\end{document}

doc/src/Eqs/pair_spin_long_range_magforce.tex

@@ -0,0 +1,17 @@
+\documentclass[preview]{standalone}
+\usepackage{varwidth}
+\usepackage[utf8x]{inputenc}
+\usepackage{amsmath,amssymb,graphics,bm,setspace}
+
+\begin{document}
+\begin{varwidth}{50in}
+  \begin{equation}
+    \bm{\omega}_i = 
+    \frac{\mu_0 (\mu_B)^2}{4\pi\hbar}\sum_{j}
+    \frac{g_i g_j}{r_{ij}^3}
+    \, \Big(
+    3\,(\bm{e}_{ij}\cdot\bm{s}_{j})\bm{e}_{ij}
+    -\bm{s}_{j} \Big) \nonumber
+  \end{equation}
+\end{varwidth}
+\end{document}

doc/src/Errors_messages.txt

@@ -610,6 +610,62 @@ This means there is something invalid about the topology definitions. :dd
 
 The data file header lists bonds but no bond types. :dd
 
+{Bond/react: Cannot use fix bond/react with non-molecular systems} :dt
+
+Only systems with bonds that can be changed can be used. Atom_style
+template does not qualify. :dd
+
+{Bond/react: Rmax cutoff is longer than pairwise cutoff} :dt
+
+This is not allowed because bond creation is done using the pairwise
+neighbor list. :dd
+
+{Bond/react: Molecule template ID for fix bond/react does not exist} :dt
+
+A valid molecule template must have been created with the molecule
+command. :dd
+
+{Bond/react: Reaction templates must contain the same number of atoms} :dt
+
+There should be a one-to-one correspondence between atoms in the
+pre-reacted and post-reacted templates, as specified by the map file. :dd
+
+{Bond/react: Unknown section in map file} :dt
+
+Please ensure reaction map files are properly formatted. :dd
+
+{Bond/react: Atom affected by reaction too close to template edge} :dt
+
+This means an atom which changes type or connectivity during the
+reaction is too close to an 'edge' atom defined in the superimpose
+file. This could cause incorrect assignment of bonds, angle, etc.
+Generally, this means you must include more atoms in your templates,
+such that there are at least two atoms between each atom involved in
+the reaction and an edge atom. :dd
+
+{Bond/react: Fix bond/react needs ghost atoms from farther away} :dt
+
+This is because a processor needs to superimpose the entire unreacted
+molecule template onto simulation atoms it knows about. The
+comm_modify cutoff command can be used to extend the communication
+range. :dd
+
+{Bond/react: A deleted atom cannot remain bonded to an atom that is not deleted} :dt
+
+Self-explanatory. :dd
+
+{Bond/react special bond generation overflow} :dt
+
+The number of special bonds per-atom created by a reaction exceeds the
+system setting. See the read_data or create_box command for how to
+specify this value. :dd
+
+{Bond/react topology/atom exceed system topology/atom} :dt
+
+The number of bonds, angles etc per-atom created by a reaction exceeds
+the system setting. See the read_data or create_box command for how to
+specify this value. :dd
+
 {Both restart files must use % or neither} :dt
 
 Self-explanatory. :dd
@@ -2146,10 +2202,6 @@ Self-explanatory. :dd
 
 This is a current restriction in LAMMPS. :dd
 
-{Cannot use pair hybrid with GPU neighbor list builds} :dt
-
-Neighbor list builds must be done on the CPU for this pair style. :dd
-
 {Cannot use pair tail corrections with 2d simulations} :dt
 
 The correction factors are only currently defined for 3d systems. :dd
@@ -2386,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
@@ -5467,10 +5527,6 @@ Self-explanatory. :dd
 For this pair style, you cannot run part of the force calculation on
 the host.  See the package command. :dd
 
-{GPU split param must be positive for hybrid pair styles} :dt
-
-See the package gpu command. :dd
-
 {GPUs are requested but Kokkos has not been compiled for CUDA} :dt
 
 Re-compile Kokkos with CUDA support to use GPUs. :dd
@@ -5729,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
@@ -5842,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
@@ -6994,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
@@ -7041,6 +7118,18 @@ Self-explanatory. :dd
 
 One or more GPUs must be used when Kokkos is compiled for CUDA. :dd
 
+{Kspace_modify mesh parameter must be all zero or all positive} :dt
+
+Valid kspace mesh parameters are >0. The code will try to auto-detect
+suitable values when all three mesh sizes are set to zero (the default). :dd
+
+{Kspace_modify mesh/disp parameter must be all zero or all positive} :dt
+
+Valid kspace mesh/disp parameters are >0. The code will try to auto-detect
+suitable values when all three mesh sizes are set to zero [and]
+the required accuracy via {force/disp/real} as well as
+{force/disp/kspace} is set. :dd
+
 {Kspace style does not support compute group/group} :dt
 
 Self-explanatory. :dd
@@ -7486,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
@@ -9429,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

@@ -82,6 +82,15 @@ bond/angle/dihedral.  LAMMPS computes this by taking the maximum bond
 length, multiplying by the number of bonds in the interaction (e.g. 3
 for a dihedral) and adding a small amount of stretch. :dd
 
+{Bond/react: Atom affected by reaction too close to template edge} :dt
+
+This means an atom which changes type or connectivity during the
+reaction is too close to an 'edge' atom defined in the superimpose
+file. This could cause incorrect assignment of bonds, angle, etc.
+Generally, this means you must include more atoms in your templates,
+such that there are at least two atoms between each atom involved in
+the reaction and an edge atom. :dd
+
 {Both groups in compute group/group have a net charge; the Kspace boundary correction to energy will be non-zero} :dt
 
 Self-explanatory. :dd
@@ -120,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="31 May 2019 version">
+<META NAME="docnumber" CONTENT="31 Jul 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
-31 May 2019 version :c,h2
+31 Jul 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.
 

doc/src/Speed_compare.txt

@@ -104,7 +104,7 @@ code (with a performance penalty due to having data transfers between
 host and GPU). :ulb,l
 
 The GPU package requires neighbor lists to be built on the CPU when using
-exclusion lists, hybrid pair styles, or a triclinic simulation box. :l
+exclusion lists, or a triclinic simulation box. :l
 
 The GPU package can be compiled for CUDA or OpenCL and thus supports
 both, Nvidia and AMD GPUs well. On Nvidia hardware, using CUDA is typically

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:]
 
@@ -207,19 +206,20 @@ supports.
 
 [Running on GPUs:]
 
-Use the "-k" "command-line switch"_Run_options.html to
-specify the number of GPUs per node. Typically the -np setting of the
-mpirun command should set the number of MPI tasks/node to be equal to
-the number of physical GPUs on the node.  You can assign multiple MPI
-tasks to the same GPU with the KOKKOS package, but this is usually
-only faster if significant portions of the input script have not
-been ported to use Kokkos. 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 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.
+Use the "-k" "command-line switch"_Run_options.html to specify the 
+number of GPUs per node. Typically the -np setting of the mpirun command 
+should set the number of MPI tasks/node to be equal to the number of 
+physical GPUs on the node. You can assign multiple MPI tasks to the same 
+GPU with the KOKKOS package, but this is usually only faster if some 
+portions of the input script have not been ported to use Kokkos. In this 
+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 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.
 
 -k on g Ng :pre
 

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/compute_sna_atom.txt

@@ -24,12 +24,7 @@ twojmax = band limit for bispectrum components (non-negative integer) :l
 R_1, R_2,... = list of cutoff radii, one for each type (distance units) :l
 w_1, w_2,... = list of neighbor weights, one for each type  :l
 zero or more keyword/value pairs may be appended :l
-keyword = {diagonal} or {rmin0} or {switchflag} or {bzeroflag} or {quadraticflag} :l
-  {diagonal} value = {0} or {1} or {2} or {3}
-     {0} = all j1, j2, j <= twojmax, j2 <= j1
-     {1} = subset satisfying j1 == j2
-     {2} = subset satisfying j1 == j2 == j3
-     {3} = subset satisfying j2 <= j1 <= j
+keyword = {rmin0} or {switchflag} or {bzeroflag} or {quadraticflag} :l
   {rmin0} value = parameter in distance to angle conversion (distance units)
   {switchflag} value = {0} or {1}
      {0} = do not use switching function
@@ -44,7 +39,7 @@ keyword = {diagonal} or {rmin0} or {switchflag} or {bzeroflag} or {quadraticflag
 
 [Examples:]
 
-compute b all sna/atom 1.4 0.99363 6 2.0 2.4 0.75 1.0 diagonal 3 rmin0 0.0
+compute b all sna/atom 1.4 0.99363 6 2.0 2.4 0.75 1.0 rmin0 0.0
 compute db all sna/atom 1.4 0.95 6 2.0 1.0
 compute vb all sna/atom 1.4 0.95 6 2.0 1.0 :pre
 
@@ -151,7 +146,7 @@ The argument {rfac0} and the optional keyword {rmin0} define the
 linear mapping from radial distance to polar angle {theta0} on the
 3-sphere.
 
-The argument {twojmax} and the keyword {diagonal} define which
+The argument {twojmax} defines which
 bispectrum components are generated. See section below on output for a
 detailed explanation of the number of bispectrum components and the
 ordered in which they are listed.
@@ -192,23 +187,18 @@ command that includes all pairs in the neighbor list.
 Compute {sna/atom} calculates a per-atom array, each column
 corresponding to a particular bispectrum component.  The total number
 of columns and the identity of the bispectrum component contained in
-each column depend on the values of {twojmax} and {diagonal}, as
+each column depend of the value of {twojmax}, as
 described by the following piece of python code:
 
 for j1 in range(0,twojmax+1):
-    if(diagonal==2):
-        print j1/2.,j1/2.,j1/2.
-    elif(diagonal==1):
-        for j in range(0,min(twojmax,2*j1)+1,2):
-            print j1/2.,j1/2.,j/2.
-    elif(diagonal==0):
-        for j2 in range(0,j1+1):
-            for j in range(j1-j2,min(twojmax,j1+j2)+1,2):
-                print j1/2.,j2/2.,j/2.
-    elif(diagonal==3):
-        for j2 in range(0,j1+1):
-            for j in range(j1-j2,min(twojmax,j1+j2)+1,2):
-                if (j>=j1): print j1/2.,j2/2.,j/2. :pre
+    for j2 in range(0,j1+1):
+        for j in range(j1-j2,min(twojmax,j1+j2)+1,2):
+            if (j>=j1): print j1/2.,j2/2.,j/2. :pre
+
+NOTE: the {diagonal} keyword allowing other possible choices
+for the number of bispectrum components was removed in 2019, 
+since all potentials use the value of 3, corresponding to the
+above set of bispectrum components.
 
 Compute {snad/atom} evaluates a per-atom array. The columns are
 arranged into {ntypes} blocks, listed in order of atom type {I}.  Each
@@ -259,7 +249,7 @@ package"_Build_package.html doc page for more info.
 
 [Default:]
 
-The optional keyword defaults are {diagonal} = 0, {rmin0} = 0,
+The optional keyword defaults are {rmin0} = 0,
 {switchflag} = 1, {bzeroflag} = 1, {quadraticflag} = 0,
 
 :line

doc/src/compute_tally.txt

@@ -88,6 +88,8 @@ potentials only include the pair potential portion of the EAM
 interaction when used by this compute, not the embedding term.  Also
 bonded or Kspace interactions do not contribute to this compute.
 
+The computes in this package are not compatible with dynamic groups.
+
 [Related commands:]
 
 {compute group/group}_compute_group_group.html, {compute

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_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_bond_react.txt

@@ -18,13 +18,13 @@ fix ID group-ID bond/react common_keyword values ...
 
 ID, group-ID are documented in "fix"_fix.html command. Group-ID is ignored. :ulb,l
 bond/react = style name of this fix command :l
-zero or more common keyword/value pairs may be appended directly after 'bond/react' :l
-these apply to all reaction specifications (below) :l
+the common keyword/values may be appended directly after 'bond/react' :l
+this applies to all reaction specifications (below) :l
 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,30 +132,29 @@ 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):
 
 A check for possible new reaction sites is performed every {Nevery}
 timesteps.
 
-Two conditions must be met for a reaction to occur. First a bonding
-atom pair must be identified. Second, the topology surrounding the
-bonding atom pair must match the topology of the pre-reaction
-template. If both these conditions are met, the reaction site is
+Three physical conditions must be met for a reaction to occur. First,
+a bonding atom pair must be identified within the reaction distance
+cutoffs. Second, the topology surrounding the bonding atom pair must
+match the topology of the pre-reaction template. Finally, any reaction
+constraints listed in the map file (see below) must be satisfied. If
+all of these conditions are met, the reaction site is eligible to be
 modified to match the post-reaction template.
 
 A bonding atom pair will be identified if several conditions are met.
@@ -203,14 +218,24 @@ new types must also be defined during the setup of a given simulation.
 A discussion of correctly handling this is also provided on the
 "molecule"_molecule.html command page.
 
+NOTE: When a reaction occurs, it is possible that the resulting
+topology/atom (e.g. special bonds, dihedrals, etc.) exceeds that of
+the existing system and reaction templates. As when inserting
+molecules, enough space for this increased topology/atom must be
+reserved by using the relevant "extra" keywords to the
+"read_data"_read_data.html or "create_box"_create_box.html commands.
+
 The map file is a text document with the following format:
 
 A map file has a header and a body. The header of map file the
-contains one mandatory keyword and three optional keywords. The
-mandatory keyword is 'equivalences' and the optional keywords are
-'edgeIDs' and 'deleteIDs' and 'customIDs':
+contains one mandatory keyword and four optional keywords. The
+mandatory keyword is 'equivalences':
+
+N {equivalences} = # of atoms N in the reaction molecule templates :pre
+
+The optional keywords are 'edgeIDs', 'deleteIDs', 'customIDs' and
+'constraints':
 
-N {equivalences} = # of atoms N in the reaction molecule templates
 N {edgeIDs} = # of edge atoms N in the pre-reacted molecule template
 N {deleteIDs} = # of atoms N that are specified for deletion
 N {customIDs} = # of atoms N that are specified for a custom update
@@ -244,8 +269,8 @@ A sample map file is given below:
 
 # this is a map file :pre
 
-2 edgeIDs
-7 equivalences :pre
+7 equivalences
+2 edgeIDs :pre
 
 BondingIDs :pre
 
@@ -297,26 +322,25 @@ can allow for the possibility of one or more reverse reactions.
 
 The optional keywords deal with the probability of a given reaction
 occurring as well as the stable equilibration of each reaction site as
-it occurs.
+it occurs:
 
-The {prob} keyword can affect whether an eligible reaction actually
-occurs. The fraction setting must be a value between 0.0 and 1.0. A
-uniform random number between 0.0 and 1.0 is generated and the
+The {prob} keyword can affect whether or not an eligible reaction
+actually occurs. The fraction setting must be a value between 0.0 and
+1.0. A uniform random number between 0.0 and 1.0 is generated and the
 eligible reaction only occurs if the random number is less than the
 fraction. Up to N reactions are permitted to occur, as optionally
 specified by the {max_rxn} keyword.
 
 The {stabilize_steps} keyword allows for the specification of how many
 timesteps a reaction site is stabilized before being returned to the
-overall system thermostat.
-
-In order to produce the most physical behavior, this 'reaction site
-equilibration time' should be tuned to be as small as possible while
-retaining stability for a given system or reaction step. After a
-limited number of case studies, this number has been set to a default
-of 60 timesteps. Ideally, it should be individually tuned for each fix
-reaction step. Note that in some situations, decreasing rather than
-increasing this parameter will result in an increase in stability.
+overall system thermostat. In order to produce the most physical
+behavior, this 'reaction site equilibration time' should be tuned to
+be as small as possible while retaining stability for a given system
+or reaction step. After a limited number of case studies, this number
+has been set to a default of 60 timesteps. Ideally, it should be
+individually tuned for each fix reaction step. Note that in some
+situations, decreasing rather than increasing this parameter will
+result in an increase in stability.
 
 The {update_edges} keyword can increase the number of atoms whose
 atomic charges are updated, when the pre-reaction template contains
@@ -324,11 +348,11 @@ edge atoms. When the value is set to 'charges,' all atoms' atomic
 charges are updated to those specified by the post-reaction template,
 including atoms near the edge of reaction templates. When the value is
 set to 'custom,' an additional section must be included in the map
-file that specifies whether to update charges, on a per-atom basis.
-The format of this section is detailed above. Listing a pre-reaction
-atom ID with a value of 'charges' will force the update of the atom's
-charge, even if it is near a template edge. Atoms not near a template
-edge are unaffected by this setting.
+file that specifies whether or not to update charges, on a per-atom
+basis. The format of this section is detailed above. Listing a
+pre-reaction atom ID with a value of 'charges' will force the update
+of the atom's charge, even if it is near a template edge. Atoms not
+near a template edge are unaffected by this setting.
 
 A few other considerations:
 
@@ -341,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/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/repository/kim-query"_https://openkim.org/doc/repository/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/kspace_modify.txt

@@ -392,7 +392,8 @@ boundaries can be set using "boundary"_boundary.html (the slab
 approximation in not needed).  The {slab} keyword is not currently
 supported by Ewald or PPPM when using a triclinic simulation cell. The
 slab correction has also been extended to point dipole interactions
-"(Klapp)"_#Klapp in "kspace_style"_kspace_style.html {ewald/disp}.
+"(Klapp)"_#Klapp in "kspace_style"_kspace_style.html {ewald/disp},
+{ewald/dipole}, and {pppm/dipole}.
 
 NOTE: If you wish to apply an electric field in the Z-direction, in
 conjunction with the {slab} keyword, you should do it by adding

doc/src/kspace_style.txt

@@ -20,6 +20,10 @@ style = {none} or {ewald} or {ewald/disp} or {ewald/omp} or {pppm} or {pppm/cg}
     accuracy = desired relative error in forces
   {ewald/omp} value = accuracy
     accuracy = desired relative error in forces
+  {ewald/dipole} value = accuracy
+    accuracy = desired relative error in forces
+  {ewald/dipole/spin} value = accuracy
+    accuracy = desired relative error in forces
   {pppm} value = accuracy
     accuracy = desired relative error in forces
   {pppm/cg} values = accuracy (smallq)
@@ -47,6 +51,10 @@ style = {none} or {ewald} or {ewald/disp} or {ewald/omp} or {pppm} or {pppm/cg}
     accuracy = desired relative error in forces
   {pppm/stagger} value = accuracy
     accuracy = desired relative error in forces
+  {pppm/dipole} value = accuracy
+    accuracy = desired relative error in forces
+  {pppm/dipole/spin} value = accuracy
+    accuracy = desired relative error in forces
   {msm} value = accuracy
     accuracy = desired relative error in forces
   {msm/cg} value = accuracy (smallq)
@@ -105,9 +113,15 @@ The {ewald/disp} style adds a long-range dispersion sum option for
 but in a more efficient manner than the {ewald} style.  The 1/r^6
 capability means that Lennard-Jones or Buckingham potentials can be
 used without a cutoff, i.e. they become full long-range potentials.
-The {ewald/disp} style can also be used with point-dipoles
-"(Toukmaji)"_#Toukmaji and is currently the only kspace solver in
-LAMMPS with this capability.
+The {ewald/disp} style can also be used with point-dipoles, see
+"(Toukmaji)"_#Toukmaji.
+
+The {ewald/dipole} style adds long-range standard Ewald summations 
+for dipole-dipole interactions, see "(Toukmaji)"_#Toukmaji.
+
+The {ewald/dipole/spin} style adds long-range standard Ewald 
+summations for magnetic dipole-dipole interactions between
+magnetic spins.
 
 :line
 
@@ -128,6 +142,12 @@ The optional {smallq} argument defines the cutoff for the absolute
 charge value which determines whether a particle is considered charged
 or not.  Its default value is 1.0e-5.
 
+The {pppm/dipole} style invokes a particle-particle particle-mesh solver 
+for dipole-dipole interactions, following the method of "(Cerda)"_#Cerda2008.
+
+The {pppm/dipole/spin} style invokes a particle-particle particle-mesh solver 
+for magnetic dipole-dipole interactions between magnetic spins. 
+
 The {pppm/tip4p} style is identical to the {pppm} style except that it
 adds a charge at the massless 4th site in each TIP4P water molecule.
 It should be used with "pair styles"_pair_style.html with a
@@ -317,7 +337,10 @@ using ideas from chapter 3 of "(Hardy)"_#Hardy2006, with equation 3.197
 of particular note. When using {msm} with non-periodic boundary
 conditions, it is expected that the error estimation will be too
 pessimistic. RMS force errors for dipoles when using {ewald/disp}
-are estimated using equations 33 and 46 of "(Wang)"_#Wang.
+or {ewald/dipole} are estimated using equations 33 and 46 of
+"(Wang)"_#Wang. The RMS force errors for {pppm/dipole} are estimated
+using the equations in "(Cerda)"_#Cerda2008.
+
 
 See the "kspace_modify"_kspace_modify.html command for additional
 options of the K-space solvers that can be set, including a {force}
@@ -464,6 +487,9 @@ Illinois at Urbana-Champaign, (2006).
 :link(Sutmann2013)
 [(Sutmann)] Sutmann, Arnold, Fahrenberger, et. al., Physical review / E 88(6), 063308 (2013)
 
+:link(Cerda2008)
+[(Cerda)] Cerda, Ballenegger, Lenz, Holm, J Chem Phys 129, 234104 (2008)
+
 :link(Who2012)
 [(Who)] Who, Author2, Author3, J of Long Range Solvers, 35, 164-177
 (2012).

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,13 +64,16 @@ 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 {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
       {neigh/qeq} value = {full} or {half}
         full = full neighbor list
         half = half neighbor list built in thread-safe manner
+      {neigh/thread} value = {off} or {on}
+        off = thread only over atoms
+        on = thread over both atoms and neighbors
       {newton} = {off} or {on}
         off = set Newton pairwise and bonded flags off
         on = set Newton pairwise and bonded flags on
@@ -84,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
@@ -173,12 +176,10 @@ computation will be built.  If {neigh} is {yes}, which is the default,
 neighbor list building is performed on the GPU.  If {neigh} is {no},
 neighbor list building is performed on the CPU.  GPU neighbor list
 building currently cannot be used with a triclinic box.  GPU neighbor
-list calculation currently cannot be used with
-"hybrid"_pair_hybrid.html pair styles.  GPU neighbor lists are not
-compatible with commands that are not GPU-enabled.  When a non-GPU
-enabled command requires a neighbor list, it will also be built on the
-CPU.  In these cases, it will typically be more efficient to only use
-CPU neighbor list builds.
+lists are not compatible with commands that are not GPU-enabled.  When
+a non-GPU enabled command requires a neighbor list, it will also be
+built on the CPU.  In these cases, it will typically be more efficient
+to only use CPU neighbor list builds.
 
 The {newton} keyword sets the Newton flags for pairwise (not bonded)
 interactions to {off} or {on}, the same as the "newton"_newton.html
@@ -442,7 +443,19 @@ running on CPUs, a {half} neighbor list is the default because it are
 often faster, just as it is for non-accelerated pair styles. Similarly, 
 the {neigh/qeq} keyword determines how neighbor lists are built for "fix 
 qeq/reax/kk"_fix_qeq_reax.html. If not explicitly set, the value of 
-{neigh/qeq} will match {neigh}. 
+{neigh/qeq} will match {neigh}.
+
+If the {neigh/thread} keyword is set to {off}, then the KOKKOS package 
+threads only over atoms. However, for small systems, this may not expose 
+enough parallelism to keep a GPU busy. When this keyword is set to {on}, 
+the KOKKOS package threads over both atoms and neighbors of atoms. When 
+using {neigh/thread} {on}, a full neighbor list must also be used. Using 
+{neigh/thread} {on} may be slower for large systems, so this this option 
+is turned on by default only when there are 16K atoms or less owned by 
+an MPI rank and when using a full neighbor list. Not all KOKKOS-enabled 
+potentials support this keyword yet, and only thread over atoms. Many 
+simple pair-wise potentials such as Lennard-Jones do support threading 
+over both atoms and neighbors.
 
 The {newton} keyword sets the Newton flags for pairwise and bonded 
 interactions to {off} or {on}, the same as the "newton"_newton.html 
@@ -475,10 +488,10 @@ are rebuilt. The data is only for atoms that migrate to new processors.
 "Forward" communication happens every timestep. "Reverse" communication 
 happens every timestep if the {newton} option is on. The data is for 
 atom coordinates and any other atom properties that needs to be updated 
-for ghost atoms owned by each processor. 
+for ghost atoms owned by each processor.
 
 The {comm} keyword is simply a short-cut to set the same value for both 
-the {comm/exchange} and {comm/forward} and {comm/reverse} keywords. 
+the {comm/exchange} and {comm/forward} and {comm/reverse} keywords.
 
 The value options for all 3 keywords are {no} or {host} or {device}. A 
 value of {no} means to use the standard non-KOKKOS method of 
@@ -486,39 +499,42 @@ packing/unpacking data for the communication. A value of {host} means to
 use the host, typically a multi-core CPU, and perform the 
 packing/unpacking in parallel with threads. A value of {device} means to 
 use the device, typically a GPU, to perform the packing/unpacking 
-operation. 
+operation.
 
 The optimal choice for these keywords depends on the input script and 
 the hardware used. The {no} value is useful for verifying that the 
 Kokkos-based {host} and {device} values are working correctly. It is the 
-default when running on CPUs since it is usually the fastest. 
+default when running on CPUs since it is usually the fastest.
 
 When running on CPUs or Xeon Phi, the {host} and {device} values work 
 identically. When using GPUs, the {device} value is the default since it 
 will typically be optimal if all of your styles used in your input 
 script are supported by the KOKKOS package. In this case data can stay 
 on the GPU for many timesteps without being moved between the host and 
-GPU, if you use the {device} value. This requires that your MPI is able 
-to access GPU memory directly. Currently that is true for OpenMPI 1.8 
-(or later versions), Mvapich2 1.9 (or later), and CrayMPI. If your 
-script uses styles (e.g. fixes) which are not yet supported by the 
-KOKKOS package, then data has to be move between the host and device 
-anyway, so it is typically faster to let the host handle communication, 
-by using the {host} value. Using {host} instead of {no} will enable use 
-of multiple threads to pack/unpack communicated data. 
+GPU, if you use the {device} value. If your script uses styles (e.g. 
+fixes) which are not yet supported by the KOKKOS package, then data has 
+to be move between the host and device anyway, so it is typically faster 
+to let the host handle communication, by using the {host} value. Using 
+{host} instead of {no} will enable use of multiple threads to 
+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.
+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
 
@@ -627,14 +643,15 @@ 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. These 
-settings are made automatically by the required "-k on" "command-line 
-switch"_Run_options.html. You can change them by using the package 
-kokkos command in your input script or via the "-pk kokkos command-line 
-switch"_Run_options.html.
+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 
+rank, otherwise it is "off". These settings are made automatically by 
+the required "-k on" "command-line switch"_Run_options.html. You can 
+change them by using the package kokkos command in your input script or 
+via the "-pk kokkos command-line switch"_Run_options.html.
 
 For the OMP package, the default is Nthreads = 0 and the option
 defaults are neigh = yes.  These settings are made automatically if