Skip to main content

SBEL Chrono DEM-Engine

Now version 3: GPU-accelerated discrete element simulation built for performance, with C++ and Python APIs.

DEM-Engine (DEME) simulates granular materials using one or two NVIDIA GPUs. This branch supports sphere clumps, mesh particles, analytical boundaries, rigid combined owners, and customizable contact force models. It also provides an interactive visualizer and host/device data access for co-simulation.

DEM-Engine granular simulation DEM-Engine demo animation

DEM-Engine simulation animation DEM-Engine demo animation

What's new in DEME 3?

Get started with DEME 3: installation guide — Python packages, C++ source builds, and system requirements.

  • Mesh contact: mesh–mesh collisions and a new clump–mesh scheme that combines triangle contributions into patch/island contacts before evaluating forces.
  • Rigid combined bodies: group members into one rigid assembly, replacing geometry-wildcard-based constructions with member-level controls.
  • On-device coupling: exchange state and forces directly with other GPU packages.
  • Persistent kernel caching: reuse compiled kernels across compatible repeated runs to reduce initialization time.
  • Interactive visualization and expanded Python workflows.

When to stay with DEME 2: DEME 3 currently supports only NVIDIA GPUs and may use more memory. If you need non-NVIDIA GPU support, or your application does not need mesh–mesh contact or the new aggregated clump–mesh contact scheme, consider staying with DEME 2.4.2, the final DEME 2 release.

For C++, use the upstream v2.4.2 tag:

git clone --branch v2.4.2 --recurse-submodules https://github.com/projectchrono/DEM-Engine.git DEM-Engine-2.4.2

For pyDEME, explicitly pin the Python distribution: python -m pip install "deme==2.4.2". Use version 2.4.2's installation requirements and examples for either route. See DEME 3 features and migration considerations for details, including the contact-model changes and memory tradeoffs.

Why use DEME?

DEME is designed for large granular simulations where particle shape, contact physics, and computational cost matter. Typical applications include mixing, hopper flow, soil penetration, wheel–terrain interaction, and granular impact.

  • Complex particle shapes. Represent grains with clumped spheres or mesh particles, and build rigid assemblies with combined owners. DEME supports mesh–mesh contact, allowing mesh particles to collide with one another.
  • Custom contact physics. Define your own contact force models, including cohesion, electrostatic interactions, and bonds that can break. Material properties and per-contact variables let you tailor the model to your problem.
  • GPU performance. Use one or two NVIDIA GPUs, including consumer and data center hardware. As an illustrative benchmark from the main-branch README, one million three-sphere clumps simulated for one million timesteps takes around one hour on RTX 3080s. Runtime depends on the geometry, contact model, and simulation settings.
  • Control over the simulation. Prescribe motion, extract forces, and update geometry to model processes such as mesh deformation or grain breakage. The examples show how to supply these behaviors through the API.
  • On-device co-simulation. Exchange simulation state and forces directly with other GPU-based packages through device buffers, avoiding CPU round trips for the exchanged data. Host data access also supports coupling to solvers such as Chrono for multibody dynamics or other physics.
  • C++ and Python workflows. Start with Python or integrate the C++ library into an application. The C++ API follows a Chrono-like design, and the interactive visualizer helps inspect simulations as they run.

Start here

Online documentation · Python API and methods · C++ API reference

Task Documentation
Install Python, build C++, or install the C++ library Installation
Run a first simulation Quickstart · Python example
Understand owners, families, frames, and runtime setup Core concepts
Use mesh particles, templates, and combined bodies Mesh particles
Find a demo to adapt Examples · C++ sources
Use Python Python guide · Demos · API reference
Look up the C++ API C++ reference
Select GPUs or exchange simulation data Device selection · Data access
Visualize results Interactive visualization and ParaView
Diagnose installation or runtime errors Troubleshooting
Build or host the documentation website Build and preview · Hosting
Contribute or cite DEME Project information · Architecture

The documentation index collects the guide sources. The linked site is currently hosted by the Ruochun fork. GitHub Actions rebuilds and publishes it on pushes to the branch selected by that repository's DOCS_PUBLISH_BRANCH variable. See Hosting for setup and switching publication to main. The C++ reference is generated from headers; the Python reference must be regenerated and committed when bindings change.

Python in brief

On a supported Linux or WSL2 host with a CUDA 12.8-compatible NVIDIA driver:

python -m pip install "deme[cuda12]"

The cuda12 extra installs CUDA runtime libraries, NVRTC, and headers through pip; no system CUDA Toolkit installation is needed for Python wheels. This setup applies only to the Python extension; standalone C++ applications keep their normal CUDA configuration. Use plain pip install deme to use an existing toolkit.

import deme

solver = deme.DEMSolver()

After installation, run a Python demo from the repository root:

python python/demos/single_sphere_collide.py --smoke-test

This headless example simulates two colliding spheres over meshes and writes visualization files. The first run may take time to compile CUDA kernels. See the Python demos for more examples, command-line options, and instructions for viewing their output.

See installation requirements for wheel compatibility and source builds. New scripts should use import deme; import DEME remains a compatibility alias. Features in this checkout may be newer than a released wheel.

Community and license

Demo videos · Project Chrono forum · Contributors · BSD-3-Clause license · Citation

Citation

If you use DEME in your research, please cite the DEM-Engine design and usage paper:

@article{zhang_2024_deme,
title = {Chrono {DEM-Engine}: A Discrete Element Method dual-{GPU} simulator with customizable contact forces and element shape},
journal = {Computer Physics Communications},
volume = {300},
pages = {109196},
year = {2024},
issn = {0010-4655},
doi = {https://doi.org/10.1016/j.cpc.2024.109196},
author = {Ruochun Zhang and Bonaventura Tagliafierro and Colin {Vanden Heuvel} and Shlok Sabarwal and Luning Bakke and Yulong Yue and Xin Wei and Radu Serban and Dan Negruţ},
keywords = {Discrete Element Method, GPU computing, Physics-based simulation, Scientific package, BSD3 open-source},
}

For the clump-based granular solver and its application to rover dynamics, see the granular simulation paper:

@article{ruochunGRC-DEM2023,
      title={A {GPU}-accelerated simulator for the {DEM} analysis of granular systems composed of clump-shaped elements}, 
      author={Ruochun Zhang and Colin {Vanden Heuvel} and Alexander Schepelmann and Arno Rogg and Dimitrios Apostolopoulos and Samuel Chandler and Radu Serban and Dan Negrut},
      year={2024},
      journal={Engineering with Computers},
      doi={https://doi.org/10.1007/s00366-023-01921-9}
}

Metadata

Release files for deme3 3.0.17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for deme3 3.0.17
File
deme3-3.0.17-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details
deme3-3.0.17-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details
deme3-3.0.17-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details
deme3-3.0.17-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details
deme3-3.0.17-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details
deme3-3.0.17-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details

Total release size: 264.4 MB

Release files / deme3-3.0.17-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL deme3-3.0.17-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 44.1 MB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
15749437a5e54c6db010d26aa3c36aaad70fff56ac48a3522b0b14a3b3f67fcb
BLAKE2b-256 checksum
How to use checksums
bc7d1e881cad6ca5684933d586cbd661dedd328328d2f3cc521345a65367c666
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / deme3-3.0.17-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL deme3-3.0.17-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 44.1 MB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
44825ffb76fa689c6c99605e6fb95fc101faf3daf7467cb631b1c58a22f8f839
BLAKE2b-256 checksum
How to use checksums
01d28cd145efe87eed481179355e88f95bb1d4daa434ced7c90a64de0dbf74ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / deme3-3.0.17-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL deme3-3.0.17-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 44.1 MB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
3014b9a9513657d7bacdc94c1f89666c3cdcdd1453f65a3e011dcf31a4d3206e
BLAKE2b-256 checksum
How to use checksums
5357439651a4a8755916663ab653f6a32791b57f57582adaea4bdeae9e13038f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / deme3-3.0.17-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL deme3-3.0.17-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 44.1 MB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
5bcf168c0ca026601d95e26eed642dfef160e76e4ebb2956008a898f18423bd5
BLAKE2b-256 checksum
How to use checksums
9c59de086a61fc7795601893e15fb72b107b9a09e03a87c50485cab3da0ca77f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / deme3-3.0.17-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL deme3-3.0.17-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 44.1 MB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
f630c2b13c50b91093a02209808c1bc9fe3722481c07c1823efbd9d702c2fc46
BLAKE2b-256 checksum
How to use checksums
30034945cfceaec2e49731965d0a2e3a12e4f72f971857cbc877d80c8c05ea58
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release files / deme3-3.0.17-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL deme3-3.0.17-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 44.1 MB
Tags CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
cd7bc0eff355ea10bc0fd62a9e8df942e6535925662f86424724486357c20ca5
BLAKE2b-256 checksum
How to use checksums
57d399199b6ce20f6e866a01c436f2a711808842a75999447ec9de1e797ed284
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.

Transparency log

Release history Release notifications | RSS feed

3.0.19

6 release files

This release

3.0.17 This release

6 release files

3.0.13

6 release files

3.0.12

6 release files

3.0.9

6 release files

3.0.8

6 release files

3.0.7

6 release files

3.0.6

6 release files

3.0.5

6 release files

3.0.4

6 release files

3.0.3

6 release files

3.0.1

6 release files

3.0.0

6 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page