diff --git a/doc/Section_commands.html b/doc/Section_commands.html index 5fb8988b45..2f222a14cb 100644 --- a/doc/Section_commands.html +++ b/doc/Section_commands.html @@ -323,9 +323,9 @@ in the command's documentation. pair_coeffpair_modifypair_stylepair_writeprdprint processorsread_dataread_restartregionreplicatereset_timestep restartrunrun_stylesetshapeshell -special_bondstemperthermothermo_modifythermo_styletimestep -uncomputeundumpunfixunitsvariablevelocity -write_restart +special_bondstadtemperthermothermo_modifythermo_style +timestepuncomputeundumpunfixunitsvariable +velocitywrite_restart
diff --git a/doc/Section_howto.html b/doc/Section_howto.html index 0b92fc19aa..4bc3da2a86 100644 --- a/doc/Section_howto.html +++ b/doc/Section_howto.html @@ -1154,7 +1154,7 @@ discussed below, it can be referenced via the following bracket notation, where ID in this case is the ID of a compute. The leading "c_" would be replaced by "f_" for a fix, or "v_" for a variable:

-
+
c_ID entire scalar, vector, or array
c_ID[I] one element of vector, one column of array
c_ID[I][J] one element of array @@ -1348,7 +1348,7 @@ data and scalar/vector/array data. input, that could be an element of a vector or array. Likewise a vector input could be a column of an array.

-
+
diff --git a/doc/Section_intro.html b/doc/Section_intro.html index 5e7cd6e066..f9b00bb689 100644 --- a/doc/Section_intro.html +++ b/doc/Section_intro.html @@ -219,6 +219,7 @@ commands)

nudged elastic band parallel replica dynamics +temperature accelerated dynamics parallel tempering

Pre- and post-processing diff --git a/doc/Section_start.html b/doc/Section_start.html index 4be3c89537..419414938f 100644 --- a/doc/Section_start.html +++ b/doc/Section_start.html @@ -327,6 +327,45 @@ build it. In the src/MAKE/Windows directory are some notes from users on how they built LAMMPS under Windows, so you can look at their instructions for tips. Good luck - we can't help you on this one.

+

(5) Changing the size limits in src/lmptype.h +

+

If you are running a very large problem (billions of atoms or more) +and get a run-time error about the system being too big, either on a +per-processor basis or in total size, then you may need to change one +or more settings in src/lmptype.h and re-compile LAMMPS. +

+

As the documentation in that file explains, you have basically +two choices to make: +

+
  • set the data type size of integer atom IDs to 4 or 8 bytes +
  • set the data type size of integers that store the total system size to 4 or 8 bytes +
+

The default for atom IDs is 4-byte integers since there is a memory +and communication cost for 8-byte integers. Non-molecular problems do +not need atom IDs so this does not restrict their size. Molecular +problems (which use IDs to define molecular topology), are limited to +about 2 billion atoms (2^31) with 4-byte IDs. With 8-byte IDs they +are effectively unlimited in size (2^63). +

+

The default for total system size quantities (like the number of atoms +or timesteps) is 8-byte integers by default which is effectively +unlimited in size (2^63). If your system does not support 8-byte +integers, an error will be generated, and you will need to set +"bigint" to 4-byte integers. This restricts your total system size to +about 2 billion atoms or timesteps (2^31). +

+

Note that in src/lmptype.h there are also settings for the MPI data +types associated with the integers that store atom IDs and total +system sizes, which need to be set consistent with the associated C +data types. +

+

In all cases, the size of problem that can be run on a per-processor +basis is limited by 4-byte integer storage to about 2 billion atoms +per processor (2^31), which should not normally be a restriction since +such a problem would have a huge per-processor memory footprint due to +neighbor lists and would run very slowly in terms of CPU +secs/timestep. +


2.3 Making LAMMPS with optional packages diff --git a/doc/Section_start.txt b/doc/Section_start.txt index ae747ded66..4faa069315 100644 --- a/doc/Section_start.txt +++ b/doc/Section_start.txt @@ -322,6 +322,45 @@ build it. In the src/MAKE/Windows directory are some notes from users on how they built LAMMPS under Windows, so you can look at their instructions for tips. Good luck - we can't help you on this one. +(5) Changing the size limits in src/lmptype.h + +If you are running a very large problem (billions of atoms or more) +and get a run-time error about the system being too big, either on a +per-processor basis or in total size, then you may need to change one +or more settings in src/lmptype.h and re-compile LAMMPS. + +As the documentation in that file explains, you have basically +two choices to make: + +set the data type size of integer atom IDs to 4 or 8 bytes +set the data type size of integers that store the total system size to 4 or 8 bytes :ul + +The default for atom IDs is 4-byte integers since there is a memory +and communication cost for 8-byte integers. Non-molecular problems do +not need atom IDs so this does not restrict their size. Molecular +problems (which use IDs to define molecular topology), are limited to +about 2 billion atoms (2^31) with 4-byte IDs. With 8-byte IDs they +are effectively unlimited in size (2^63). + +The default for total system size quantities (like the number of atoms +or timesteps) is 8-byte integers by default which is effectively +unlimited in size (2^63). If your system does not support 8-byte +integers, an error will be generated, and you will need to set +"bigint" to 4-byte integers. This restricts your total system size to +about 2 billion atoms or timesteps (2^31). + +Note that in src/lmptype.h there are also settings for the MPI data +types associated with the integers that store atom IDs and total +system sizes, which need to be set consistent with the associated C +data types. + +In all cases, the size of problem that can be run on a per-processor +basis is limited by 4-byte integer storage to about 2 billion atoms +per processor (2^31), which should not normally be a restriction since +such a problem would have a huge per-processor memory footprint due to +neighbor lists and would run very slowly in terms of CPU +secs/timestep. + :line 2.3 Making LAMMPS with optional packages :h4,link(2_3)

Command Input Output
thermo_style custom global scalars screen, log file
dump custom per-atom vectors dump file