4.4. Force Field
The force field encompasses a broader set of operators and mechanisms responsible for computing forces acting on particles within the particle environment. It includes various types of forces such as gravitational forces, contact forces, and other external influences that affect particle dynamics.
4.4.1. Contact Force Laws
A contact law, in the context of the Discrete Element Method (DEM), is the principle used to calculate the force between two particles from their relative displacement. In DEM simulations, a contact law models the interaction between particles, capturing elastic deformation and linear force behaviors.
There are two kinds of interaction:
pure contact interaction
cohesive interaction
The main laws available in exaDEM are:
Name |
type |
Description |
|---|---|---|
|
pure contact |
Default configuration : elastic linear normal force, normal viscosity force, Coulomb friction tangent force and rolling resistance |
|
Cohesive |
Addition of a normal cohesive force depending on the distance between particles |
|
Cohesive |
Addition of an adhesive law at contact to model Van der Waals force for hard particles |
The variables required to describe interactions are:
Variable |
Description |
|---|---|
\(cp\) |
The contact position |
\(r_i\) |
The position of particle \(i\) |
\(r_j\) |
The position of particle \(j\) |
\(v_i\) |
The velocity of particle \(i\) |
\(v_j\) |
The velocity of particle \(j\) |
\(vrot_i\) |
The angular velocity of particle \(i\) |
\(vrot_j\) |
The angular velocity of particle \(j\) |
\(m_i\) |
The mass of particle \(i\) |
\(m_j\) |
The mass of particle \(j\) |
\(\delta_n\) |
The interpenetration / particle overlap |
Each kind of interaction also requires additional constants, reflecting for most of them mechanical properties:
Constant |
Description |
|---|---|
\(\Delta_t\) |
The timestep increment |
\(\alpha_n\) |
The damping rate |
\(k_n\) |
The normal stiffness coefficient |
\(k_t\) |
The tangential stiffness coefficient |
\(v_t\) |
The relative tangential velocity |
\(k_r\) |
The rotational stiffness coefficient |
\(\mu\) |
The coefficient of friction |
4.4.1.1. hooke law: elastic normal force with tangential friction
In the Discrete Element Method (DEM), the equations of motion (translations and rotations) are discretized in time. Only the rigid-body displacements are considered. Small overlaps between the particles are allowed and used as strain variables. The total contact force between particle \(i\) and particle \(j\) is given by
where \(f_n\) the normal component of the contact force and \(\textbf{f}_t\) is the tangential force vector. These forces are expressed in the local contact frame \((\textbf{n},\textbf{t},\textbf{s})\) as a function of the overlaps and tangential displacements. They are calculated from force laws that generally describe frictional contact interactions. An important feature of DEM is to allow the particles to overlap. This overlap \(\delta_n\) represents a normal strain localized in the vicinity of the contact point. A simple linear relation is assumed between normal contact force and \(\delta_n\) . This is consistent with the fact that the overlaps allow for a penalty-based explicit formulation of particle motions, i.e., the elastic repulsion force is mobilized to prevent penalizing the overlap. The condition of particle undeformability implies that the overlaps must stay small compared to particle size. In this linear approximation, the normal component of the contact force is given by
where \(k_n\) is the normal stiffness coefficient, \(v_n\) the normal component of the relative velocity (between particle \(i\) and particle \(j\)), and \(\nu_n\) is the viscous damping coefficient. \(\nu_n\) is related to the restitution coefficient \(e_n\) by
where:
\(\nu_n\) is the viscous damping rate during the collision
\(\alpha_n\) is the damping parameter, calculated from the restitution coefficient \(e_n\)
\(m_{\text{eff}}\) is the effective mass of the two colliding particles, defined by \(m_{\text{eff}} = \frac{m_i m_j}{m_i + m_j}\)
Note
The formulas are identical to those used in Rockable (see Rockable Force Laws) but are implemented differently to align with the exaDEM data structure.
The tangential force represents the frictional resistance between particles when they slide against each other. This force is calculated based on the relative tangential velocity (\(v_t\)) and a tangential stiffness parameter (\(k_t\), called ktContact in Rockable).
The Coulomb friction model is used to limit the tangential force, ensuring that it does not exceed the product of the friction coefficient \(\mu\) and the normal force (\(f_n\)):
The tangential force \(f_t\) is incrementally updated at each time step according to the following relation, starting from the onset of contact:
where:
\(f_t\) is the tangential force,
\(k_t\) is the tangential stiffness,
\(v_t\) is the relative tangential velocity, and
\(\delta t\) is the time step.
The friction force is reset to zero as soon as contact is lost.
4.4.1.2. cohesive law: cohesive normal force
This interaction requires two additional parameters:
Constant |
Description |
|---|---|
\(fc\) |
Cohesive force threshold |
\(dncut\) |
Distance cutoff for cohesive interaction |
There are three cases, depending on the interpenetration \(\delta_n\) between the two particles:
\(\delta_n < -dncut\)
\(-dncut < \delta_n < 0\)
\(0 < \delta_n < dncut\)
Warning
Cohesive forces (dncut) are only applied if you use the operators contact_[*]_[*]_[*]_cohesive. Otherwise we only consider the case \(\delta_n < 0.0\).
Formula between particle i and particle j if \(\delta_n < -dncut\) :
with the effective mass:
and the relative velocity norm:
Formula between particle i and particle j if \(-dncut < \delta_n < 0\) :
with:
Formula between particle i and particle j if \(0 < \delta_n < dncut\) :
with n the normalized vector from particle i to particle j
4.4.1.3. dmt law: adhesive normal force (Van der Waals)
DMT (Derjaguin–Muller–Toporov) is usually used to compute pull-off forces (the force needed to split two rigid objects in contact), computed from a global energy balance. To define it, it needs an additional parameter representing an energy:
Constant |
Description |
|---|---|
\(\gamma\) |
Adhesion energy per unit of surface |
In case of contact, an additional force \(f_{DMT}\) is added to the normal force such that :
with:
where the effective radius \(R_{eff}\) is obtained from the respective radii \(R_{i}\) and \(R_{j}\) of the particles i and j:
and \(\gamma\) is the surface energy (linked to Van der Waals forces).
Note
Since DMT force law is added to the normal force, it requires the definition of a pure contact law, such as hooke one.
4.4.2. Contact Law Operators
Contact Law Operators select a contact law and define its parameters.
The operator naming convention follows the rule below:
contact_[material_mode]_[particle_type]_[pure_contact_law]_[cohesion_law]
Where each field is defined as follows:
Field |
Possible values |
Description |
|---|---|---|
[material_mode] |
|
Material interaction mode |
[particle_type] |
|
Type of particles |
[pure_contact_law] |
|
Pure contact law |
[cohesion_law] |
|
Cohesion / adhesion law |
Note
For convenience, simplified operator names are available. They are strict equivalents of the full naming convention.
Sphere operators
contact_sphereis equivalent tocontact_singlemat_sphere_hookeorcontact_singlemat_sphere_hooke_nonecontact_multimat_sphereis equivalent tocontact_multimat_sphere_hooke_none
Polyhedron operators
contact_polyhedronis equivalent tocontact_singlemat_polyhedron_hookeorcontact_singlemat_polyhedron_hooke_nonecontact_multimat_polyhedronis equivalent tocontact_multimat_polyhedron_hooke_none
In a contact operator, the following parameters can be defined:
symetric |
Activate or disable symmetric updates (do not disable it with polyhedron). |
config |
Data structure that contains contact force parameters (dncut, kn, kt, kr, fc, mu, damp_rate). Type = exaDEM::ContactParams. No default parameter. |
config_driver |
Data structure that contains contact force parameters (dncut, kn, kt, kr, fc, mu, damp_rate). Type = exaDEM::ContactParams. This parameter is optional. |
save_interactions |
Store interactions into the classifier data structure. Default is false. |
Here are four YAML examples:
- contact_sphere:
symetric: true
config: { kn: 100000, kt: 100000, kr: 0.1, mu: 0.9, damp_rate: 0.9}
- contact_polyhedron:
config: { kn: 10000, kt: 10000, kr: 0.1, mu: 0.1, damp_rate: 0.9}
config_driver: { kn: 10000, kt: 10000, kr: 0.1, mu: 0.3, damp_rate: 0.9}
- contact_singlemat_sphere_hooke_cohesive:
symetric: true
config: { dncut: 0.1 m, kn: 100000, kt: 100000, kr: 0.1, fc: 0.05, mu: 0.9, damp_rate: 0.9}
- contact_singlemat_polyhedron_hooke_cohesive:
config: { dncut: 0.1 m, kn: 10000, kt: 10000, kr: 0.1, fc: 0.05, mu: 0.1, damp_rate: 0.9}
config_driver: { dncut: 0.1 m, kn: 10000, kt: 10000, kr: 0.1, fc: 0.05, mu: 0.3, damp_rate: 0.9}
- contact_singlemat_sphere_hooke_dmt:
config: { kn: 1000, kt: 1000, kr: 0.1,mu: 0.2, damp_rate: 0.9, gamma: 10.}
config_driver: { kn: 1000, kt: 800, kr: 0.1,mu: 0.5, damp_rate: 0.9, gamma: 10.}
Note
If you set symetric: false, make sure the interaction lists were also built without the symmetry option – by default, exaDEM always builds them with symmetry enabled, to limit the number of calculations.
Note
The cohesion law ([cohesion_law] = cohesive) adds a cohesion force between rcut and rcut+dncut, scaled by the cohesion force parameter fc.
Note
The
contact_[*]_sphere_[*]_[*]operators are designed to process interactions built innbh_sphere(please, include the config_spheres.msp file).The
contact_[*]_polyhedron_[*]_[*]operators are designed to process interactions built innbh_polyhedron(please, include the config_polyhedra.msp file). For the list of polyhedron interaction types these operators process, see Polyhedra - Interaction / Contact on the R-Shape / Polyhedron page.
4.4.3. Multi-Material
In the previous section, the contact law used the same parameters for every interaction (singlemat mode). It is also possible to make the contact law depend on the group of the interacting particles (multimat mode). This section explains how to define contact-law values between particles, as well as between particles and drivers.
Note
Unlike in some other DEM codes, the coefficients are not derived from the material properties (such as Poisson’s ratio and Young’s modulus).
Note
Since exaDEM-1.2.3, multi-material contact parameters are indexed by group (an integer, see the group particle field in the Particle Fields page) instead of directly by particle type. Before 1.2.3, the particle type was used directly. This decouples the shape/material identity (type) from the contact-law identity (group): several particle types can share the same group and therefore reuse the same contact parameters. Groups must be assigned beforehand, either with the group parameter of set_fields or with the dedicated set_group operator (see the Particle Fields page).
To handle multiple particle groups, use one of the contact_multimat_[*]_[*]_[*] operators, as illustrated below.
YAML example for polyhedra:
compute_force:
- gravity_force
- contact_multimat_polyhedron
YAML example for spheres:
compute_force:
- gravity_force
- contact_multimat_sphere:
symetric: true
The following examples illustrate the definition of contact parameters for two particle groups (group 0, group 1) and a driver identified by 0.
4.4.3.1. Particle-Particle Contact Parameters
Operator Name:
multimat_contact_paramsDescription: This operator defines the contact law parameters between different particle groups.
Parameter |
Description |
|---|---|
|
List of the first particle group indice(s). |
|
List of the second particle group indice(s). |
|
Normal force coefficient for the specified interaction type. |
|
Tangential force coefficient for the specified interaction type. |
|
Rolling resistance coefficient for the specified interaction type. |
|
Friction coefficient for the specified interaction type. |
|
Damping rate coefficient for the specified interaction type. |
|
Applies the same parameter set to all undefined interaction configurations. |
|
Number of distinct groups ( |
Note
group1/group2 replace the former mat1/mat2 parameters (pre-1.2.3, which took particle type names directly). Particle groups must be assigned beforehand via the group parameter of set_fields or the set_group operator.
YAML example:
- multimat_contact_params:
group1: [ 0, 0, 1 ]
group2: [ 0, 1, 1 ]
kn: [ 5000, 10000, 15000 ]
kt: [ 4000, 8000, 12000 ]
kr: [ 0.0, 0.0, 0.0 ]
mu: [ 0.1, 0.2, 0.3 ]
damprate: [ 0.999, 0.999, 0.999 ]
With default_config:
- multimat_contact_params:
group1: [ 0 ]
group2: [ 0 ]
kn: [ 5000 ]
kt: [ 4000 ]
kr: [ 0.0 ]
mu: [ 0.1 ]
damprate: [ 0.999 ]
default_config: { kn: 15000, kt: 12000, kr: 0.0, mu: 0.3, damp_rate: 0.999 }
A complete example is available (please report if the link does not work): rotating-multimat.msp
4.4.3.2. Particle-Driver Contact Parameters
Operator Name:
drivers_contact_paramsDescription: This operator defines the contact law parameters between particles and drivers.
Parameters:
Parameter |
Description |
|---|---|
|
List of particle group indice(s) concerned by the interaction. |
|
Identifier(s) of the driver(s) interacting with the particles. |
|
Normal force coefficient for the specified interaction type. |
|
Tangential force coefficient for the specified interaction type. |
|
Rolling resistance coefficient for the specified interaction type. |
|
Friction coefficient for the specified interaction type. |
|
Damping rate coefficient for the specified interaction type. |
|
Applies the same parameter set to all undefined interaction configurations. |
Note
group replaces the former mat parameter (pre-1.2.3, which took particle type names directly). Particle groups must be assigned beforehand via the group parameter of set_fields or the set_group operator.
- drivers_contact_params:
group: [ 0, 1 ]
driver_id: [ 0, 0 ]
kn: [ 10000, 15000 ]
kt: [ 8000, 12000 ]
kr: [ 0.0, 0.1 ]
mu: [ 0.5, 0.5 ]
damprate: [ 0.999, 0.999 ]
A complete example is available (please report if the link does not work): rotating-multimat.msp
4.4.3.3. Checking Group Completeness
Operator Name:
check_group_completeness(sinceexaDEM-1.2.3)Description: Verifies that the number of groups configured in
multimat_cp(viamultimat_contact_paramsand/ordrivers_contact_params) is large enough to cover the maximumgroupindex actually present on particles. The simulation stops if a particle references a group for which no contact parameters were set up.Parameters: none.
- check_group_completeness
Note
This operator has no effect (it silently returns) if multimat_cp has not been produced yet, so it can safely be placed anywhere after multimat_contact_params and/or drivers_contact_params in the operator chain, typically right before compute_force.
4.4.4. External Forces
External forces are additional influences acting on particles within the simulation environment, originating from sources outside the particle system itself. These forces can include environmental factors like wind, fluid flow, or magnetic fields, as well as user-defined forces applied to specific particles or regions.
4.4.4.1. Gravity Operator
Formula:
With f the forces, m the particle mass, and g the gravity constant.
Operator Name:
gravity_forceDescription: This operator computes forces related to the gravity.
Parameter:
gravity |
Gravity vector, one value per axis. Default values are x = 0, y = 0, z = -9.807 |
YAML example:
- gravity_force:
gravity: [0,0,-0.009807]
4.4.4.2. Quadratic Drag Force
Formula:
With f the particle force, cx the aerodynamic coefficient, \(\mu\) the drag coefficient, \(\|v\|\) the norm of the particle velocity, and v the particle velocity.
Operator Name:
quadratic_forceDescription: External force modeling air or fluid drag: \(\textbf{f} = -\mu \cdot cx \cdot \|v\| \cdot \textbf{v}\).
Parameter:
cx |
aerodynamic coefficient, default value is for air = 0.38. |
mu |
drag coefficient. default value is for air = 0.000015. |
YAML example: see example quadratic-force-test/QuadraticForceInput.msp
- quadratic_force:
cx: 0.38
mu: 0.0000015
4.4.4.3. Fluid Grid Force
Operator Name:
sphere_fluid_frictionDescription: External force modeling drag from a fluid velocity field defined on a grid.
With fv the fluid velocity, pv the particle velocity, r the particle radius, and cx a coefficient set to 1 by default.
Note
The fluid velocity fv for each point of the grid has been defined by the operator set_cell_values (pure exaNBody operator).
4.4.5. Inner Bond Forces
Note
This section describes the force law applied between already-bonded faces. The geometric/sticking side of fragmentation – pre-cutting grains, the sticking threshold that decides which vertices get bonded in the first place, and interface breakage – is described in the Fragmentation Feature section of the R-Shape / Polyhedron page (see Fragmentation Feature).
The inner_bond_force law models a cohesive bond between two contacting
polyhedron faces, combining a linear elastic + viscous normal force, a
linear elastic tangential force accumulated over the contact history, and
a fracture criterion that breaks the bond once the stored elastic energy
exceeds a material-dependent threshold.
With overlap \(\delta = d_n - d_{n0}\) and relative normal velocity \(v_n\):
where \(w\) is the per-interaction weight and \(\gamma\) is the
viscous damping coefficient derived from damp_rate. The stored elastic
energies (tension only) are:
4.4.5.1. Inner Bond Parameters
Name |
Unit |
Description |
|---|---|---|
|
force/length |
Normal stiffness coefficient. |
|
force/length |
Tangential stiffness coefficient. |
|
dimensionless |
Normal damping ratio. |
|
energy/area |
MixedMode fracture energy release rate. Mutually exclusive with
|
|
energy/area |
SeparateModes normal fracture energy release rate (requires |
|
energy/area |
SeparateModes tangential fracture energy release rate (requires |
Note
Exactly one fracture mode must be configured: g alone (MixedMode), or
gn together with gt (SeparateModes). Mixing the two, or omitting
both, is rejected at parsing time.
4.4.5.2. Usage Examples
Single configuration (no groups), mixed-mode fracture:
inner_bond_params:
kn: 10000 N/m
kt: 8000 N/m
damp_rate: 0.1
g: 5.0 J/m^2
Single configuration (no groups), separate-mode fracture:
inner_bond_params:
kn: 10000 N/m
kt: 8000 N/m
damp_rate: 0.1
gn: 5.0 J/m^2
gt: 2.0 J/m^2
With multiple groups, use the inner_bond_params operator with one entry
per (group1[p], group2[p]) pair in parallel arrays:
Note
Since exaDEM-1.2.3, pairs are defined with group1/group2 (particle group indices) instead of the former mat1/mat2 (particle type names). Particle groups must be assigned beforehand via the group parameter of set_fields or the set_group operator.
- inner_bond_params:
group1: [ 0, 0, 1 ]
group2: [ 0, 1, 1 ]
kn: [ 5000, 10000, 15000 ]
kt: [ 4000, 8000, 12000 ]
damp_rate: [ 0.999, 0.999, 0.999 ]
gn: [ 1e-5, 1e-5, 1e-5 ]
gt: [ 1e-5, 1e-5, 1e-5 ]
# or, mixed mode for every pair:
- inner_bond_params:
group1: [ 0, 1 ]
group2: [ 0, 1 ]
kn: [ 5000, 15000 ]
kt: [ 4000, 12000 ]
damp_rate: [ 0.999, 0.999 ]
g: [ 1e-5, 1e-5 ]
4.4.5.3. See also
stick_polyhedra— builds the inner-bond interactions and computes the fracture criterion’s area term per bonded face.apply_interface_fracture_criterion— applies the configured rupture mode (mixed or separate) to decide whether a bonded interface breaks.