potential
This keyword is used to specify the interatomic potential model for the system.
The interatomic potentials chapter describes model forms and parameter files. External integrations are described under Deep Potential and NNAP.
Syntax
potential <potential_filename> [<model_options>]
Parameters
The first parameter, potential_filename, is the filename (including
relative or absolute path) of the potential file to be used. Some potential
types require additional parameters, as described in their corresponding
sections.
NEP models must use the nep.txt format with
format_version 1 and one hidden layer.
For standard NEP, temperature-dependent NEP, and nep_spin models, a multi-GPU run can
optionally specify the spatial partition direction:
potential <potential_filename> [partition_direction]
Here, partition_direction can be x, y, or z. These
correspond to the a, b, and c directions, respectively, for a
triclinic box. If the direction is omitted, GPUMD selects it automatically,
normally along the thickest direction of the box.
The optional partition direction applies only to the multi-GPU implementation
of standard NEP, temperature-dependent NEP, and nep_spin models. For ordinary MD, charge and vdW NEP models
currently use the single-GPU implementation in gpumd; see Long-range models for their boundary conditions and usage.
With multi_replica, complete replicas are assigned to GPUs and the partition-direction parameter is not supported.
Output
None.
Examples
potential Si_NEP.txt
For a multi-GPU NEP run, one can force the decomposition along a specific direction, for example:
potential Si_NEP.txt x
Notes
For NEP-spin input requirements, integrator choices, output, and continuation, see NEP-spin runtime use.