Releases: brucefan1983/GPUMD
Releases Β· brucefan1983/GPUMD
GPUMD-v3.4.1
- Fixed a small bug for the multi-GPU version of NEP about partition direction. #270
- Fixed a small bug for variable time step. #271
- Fixed the heat current for small-box MD with NEP #274
- Moved
NEP_CPU
to a separate repo (https://github.com/brucefan1983/NEP_CPU), where a NEP-LAMMPS interface is also created.
GPUMD-v3.4
- Removed
- Removed a few empirical potentials (Vashishta, SW, REBO-LJ, and Buckingham-Coulomb) and removed the hybrid-potential scheme. For those who want to use these features,
GPUMD-v3.3.1
will be the best choice. - There will not be a list of atom types (integers) after the potential filename for the
potential
keyword. - There will be no support for "hybrid" potentials. One should write the
potential
keyword once and only once inrun.in
. - Removed the
neighbor
keyword inrun.in
. The code will build the neighbor list at each step with the potential cutoff. The user does not need to estimate a neighbor list size now. For NEP models, the information of neighbor list size will be recorded intonep.txt
. For empirical potentials, the code has chosen reasonable neighbor list sizes. - Removed the so-called "driver input file" for both the
gpumd
andnep
executables.
- Removed a few empirical potentials (Vashishta, SW, REBO-LJ, and Buckingham-Coulomb) and removed the hybrid-potential scheme. For those who want to use these features,
- Changed
- Changed
xyz.in
tomodel.xyz
, and changedtrain.in/test.in
totrain.xyz/test.xyz
. All the.xyz
files are in the extended XYZ format. See the manual pages https://gpumd.zheyongfan.org/index.php/The_model.xyz_input_file and https://gpumd.zheyongfan.org/index.php/The_train.xyz_input_file for details on the extended XYZ format.
- Changed
- Added
- Added multi-GPU (single-node) support for both training and MD simulation with the NEP model. The code will use all the GPUs available. The available GPUs can be set by running e.g.
export CUDA_VISIBLE_DEVICES=0,1
(0 and 1 are the IDs of the GPUs to be used) in the command line or by specifying something in a job-submission script in a cluster.
- Added multi-GPU (single-node) support for both training and MD simulation with the NEP model. The code will use all the GPUs available. The available GPUs can be set by running e.g.
GPUMD-v3.3.1
GPUMD-v3.3
-
- Fixed a bug related to the ZBL part of NEP for small box simulations.
-
- Fixed a bug related to momentum correction for systems with non-uniform particle masses. See PR #172
-
- Added a new Langevin thermostat. See PR #173
-
- Changed the grammars of the
neighbor
keyword.
- Changed the grammars of the
-
- Added a
change_box
keyword. See PR #174
- Added a
-
- Finished NEP3 (4-body and 5-body descriptors, linear combination of radial basis functions).
-
- Added many examples as used in the NEP3 paper (https://arxiv.org/abs/2205.10046).
-
- Added a standalone C++ code for NEP (used in PyNEP: https://github.com/bigd4/PyNEP).
-
- Fixed a bug related to neighbor list updating (might occur when a box thickness is slightly smaller than an integer multiple of the neighbor list cutoff). See PR #190
GPUMD-v3.2
- Added NEP2 back (equivalent to the NEP as last released in GPUMD-v3.0). One can use the
version
keyword innep.in
to choose between NEP2 and NEP3. - Fixed a bug related to virial calculation using NEP potentials with small boxes (angular part of the virial has not been accumulated).
- Extended the
time_step
keyword inrun.in
such that it can also accept two parameters, where the second one is the largest distance any atom can travel within one step (useful for cascade simulation).
GPUMD-v3.1.1
- Fixed a bug related to MD simulations with the NEP potential:
- This bug exists in both
GPUMD-v3.0
andGPUMD-v3.1
. The bug is only for thegpumd
executable, not for thenep
executable. - It occurs when one runs MD simulations with one or more directions being non-periodic and the box thickness in a non-periodic direction is less than twice of the force cutoff distance of the NEP potential. In this case, the code will wrongly treat the non-periodic directions as periodic and replicate the box in those directions.
- There is a similar bug to be fixed in the next release
GPUMD-v3.2
, so we strongly suggest usingGPUMD-v3.2
.
- This bug exists in both
GPUMD-v3.1
- Changed the NEP potential from NEP2 to NEP3.
- Improved the radial functions, again.
- Added 4-body descriptors.
GPUMD-v3.0
- Enabled O(N) neighbor list algorithm for triclinic box.
- Enabled triclinic box NPT.
- Added the stochastic cell rescaling (SCR) barostat.
- Changed the syntax for NPT.
- Extended the EAM potential to support alloys.
- Changed
nep.in
from fixed format to free-style format. - Added a
type_weight
keyword innep.in
to enable type-wise force weight. - Added a
force_delta
keyword innep.in
to possibly emphasize the accuracy of smaller forces. - Enabled configuration-wise weight in
trian.in
. - Allowed for adding the universal ZBL potential for NEP training.
- Allowed to run MD with the NEP potential using a small box (box thickness smaller than twice of the force cutoff).
- Removed center-of-mass random drift during Langevin thermostatting.
- Corrected pressure calculation during NVE run.
- Added a
dump_exyz
command inrun.in
to dump an extended XYZ file with some data. - Corrected particle wrapping after neighbor list updating with triclinic box.
GPUMD-v2.9.1
- The convergence speed of NEP training has been significantly improved in most cases.
- Changed
movie.xyz
from the simplest XYZ format to an extended XYZ format. - Used atom symbols in
restart.out
for NEP potentials. - Reported an error message if NPT is used with triclinic box.
- Fixed a hidden bug related to variable initialization.
GPUMD-v2.9
- Removed the
phonon
executable, and added thecompute_phonon
keyword inrun.in
to do phonon dispersion calculation. - Enabled isotropic pressure controlling in NPT.
- Added the
compute_cohesive
keyword inrun.in
to compute the cohesive energy curve. - Added the
compute_elastic
keyword inrun.in
to compute the elastic constants (only for cubic systems now). - Reduced the weighting factor of the virial loss in NEP training from 1 to 0.1 (virial is usually not as important as force and energy and should have a smaller weighting factor).
- Fixed a hidden memory bug for the nep executable.