This is an event-driven molecular dynamics (EDMD) code for hard spheres. It uses neighbor lists [1] and an efficient event calendar [2] for efficiency.
See http://arxiv.org/abs/2201.01100 for a complete description and benchmarking.
Four simulation codes are included, in their respective subfolders. Three of these are variations of a microcanonical simulation code, simulating a constant number particles in a cubic volume
with periodic boundary conditions at constant energy.
- Cell contains a simulation code where collision checks are based on a cell list.
- Multi contains a simualtion code where collision checks are based on a neighbor list, and is more typically more efficient than the Cell code at sufficiently high densities.
- Single contains a simualtion code where collision checks are based on a neighbor list, and only a single event is scheduled per particle. This is typically more efficient than the Multi code. Additionally, a separate simulation code Grow is included in which the particles grow over time until a desired packing fraction is reached. This can be helpful for creating initial configurations.
Each code consists of a single code file plus a header file. A makefile is included for each code, as well as sample initial configurations. All simulation parameters are defined as global variables near the top of the main code file.
We simulate systems of hard spheres in a constant volume
in three dimensions. Each particle
has a position
, a diameter
, a mass
, and a radius
.
The simulation code operates in the following units:
- Lengths are measured in units of the maximum particle size
.
- Mass is measured in units of a reference mass
, which is typically chosen to be the mass of a particle with diameter
- Time is measured in units of
. Here,
with
Boltzmann's constant. Note that the simulation assumes that no particles with a diameter greater than
exist in the simulation, and uses assumption in the creation of the cell list. Hence, all particles necessarily have a diameter
. By default, the simulation code sets the mass of all particles to be equal to
The simulation code measures the pressure during the simulation, and outputs it in the form of a reduced pressure
. The average pressure in a given time interval
is measured via the virial expression
where
is the number density with
the system volume and
the number of particles, and the sum in the last term is taken over all collisions in the time interval
. For each collision,
is the center-to-center vector connecting the two colliding particles
and
, and
is the momentum change of particle
due to the collision.
Additionally, as a check on conservation of energy, the simulation measures the temperature of the system, using the equipartition theorem
The temperature is reported in units of
, and should be constant during the simulation (up to numerical accuracy). A thermostat function is included in the simulation codes, but is disabled by default. Since the total kinetic energy is a conserved quantity, the temperature remains constant even without a thermostat. Hence, all simulations reported in the main text are performed in the microcanonical ensemble (i.e. at constant total energy).
The configuration files from the simulation are written in a simple text-based format, which can contain multiple snapshots per file. For each frame, the format consists of lines (with
the number of particles), as follows:
- One line containing just the number of particles
- One line containing the box size, specifying the box length
,
, and
along the three axes, separated by whitespace.
- One line per particle containing: a letter indicating particle type, three numbers indicating the real-space particle coordinates, and one number indicating the particle radius. The movie files that are created by the simulation code include multiple of these frames consecutively in a single text file. Note that although the code assumes periodic boundary conditions, coordinates of particles that leave the box during the simulation will be printed as being outside of the simulation box, to allow for analysis of long-time dynamics. Hence, any structural analysis or visualization should apply periodic boundary conditions explicitly.
The simulation codes can read in snapshots in this format as initial configurations. Periodic boundaries will be applied to the snapshot at the start of the simulation. Note that the simulation code assumes that all box lengths, positions, and radii are given in units of , which is the largest possible particle diameter. Hence, the radius of a particle in the initial configuration should never be given as a number larger than 0.5.
Adaptation to different configuration file formats can be done via modification of the loadparticles, write, and outputsnapshot functions.