Gamdpy implements molecular dynamics on GPU's in Python, relying heavily on the numba package (numba.org) which does JIT (Just-In-Time) compilation both to CPU and GPU (cuda). The gamdpy package being pure Python (letting numba do the heavy lifting of generating fast code) results in an extremely extendable package: simply by interjecting Python functions in the right places, the (experienced) user can extend most aspect of the code, including new integrators, new pair-potentials, new properties to be calculated during simulation, new particle properties, ...
The Users Guide (gamdpy.readthedocs.io)
Tutorials Includes instructions on how to try out gamdpy on google.colab, by getting access to a NVIDIA GPU for free.
A class containing all relevant information about a configuration, including the simulation box (class sim_box).
- Vectors (r, v, f, etc): (N,D) float array storing D-dimensional vector for each particle
- Scalars (mass, kinetic energy, etc.): (N,) float array storing scalar for each particle
- sim_box (data describing box + functions implementing how to calculate distances and how to implement BC). For now:orthorombic (default) and lees_edwards
Classes implementing a simulation algorithm. Currently implemented:
- class NVE
- class NVT : Nose-Hoover thermostat
- class NVT_Langevin
- class NPT_Atomic
- class NPT_Langevin
- class GradientDescent
- class NVU_RT (Experimental)
Temperature/Pressure can be controlled by a user-supplied function, see examples/kablj.py
Classes implementing interactions that can be applied to particles in the system:
- class PairPotential (stores potential parameters and the neighbour list to use (class NbList)
- fixed interactions (interactions known beforehand):
- bonds, angles, and dihedrals
- planar interactions: smooth walls, gravity, electric fields, ...
- point interactions, e.g., tethering
An interaction is responsible for keeping any internal datastructures up to date (in particular: class PairPotential is responsible for keeping its neighbor-list (class NbList up to date).
Classes implementing actions on the configuration which are not related to the interactions or the integration of the equation of motion. These classes include momentum reset and savers.
- class TrajectorySaver
- class ScalarSaver
- class MomentumReset
This class takes a Configuration, an Integrator, a (list of) Interaction(s) and a list of Runtime actions and sets up a simulation. Performing simulation is done by a method of this class.
Takes a Configuration and a (list of) Interaction(s), and evaluates properties and assign them to the appropiate fields in the configuration.