Home
EDEMpy
EDEMpy is a Python library for accessing EDEM data from .h5 files (the underlying EDEM file format). EDEMpy does not require prior knowledge of advanced programming.
EDEMpy Syntax
The following sections provide an overview of the syntax used in EDEMpy.
Read Contact, Bond, and Collision data
You use the same syntax for reading contact and collision data. The only differences are in the available properties in each case.

Welcome
What's New
New features and enhancements available in EDEM.
Release Notes
This document contains information about the EDEM release, such as key features and enhancements, bug fixes, and known issues.
About EDEM
EDEM is a high-performance simulation software for bulk and granular materials.
Get Started with EDEM
The EDEM user interface comprises three icons for each simulation component - Creator, Simulator, and Analyst.
EDEM Creator
EDEM Creator is the pre-processor for creating an EDEM simulation model, including setting up equipment and defining the generation of bulk materials.
EDEM Simulator
EDEM Simulator is a powerful solver used for fast and efficient simulations.
EDEM Analyst
EDEM Analyst is the post-processor used to analyze and visualize the results of your simulation.
EDEM Contact Models
A Contact Model describes how elements behave when they come into contact with each other.
EDEM Cal Utility
EDEM Cal is a utility which works with EDEM and is designed to assist in performing calibration.
GPU CUDA Guide
The EDEM CUDA GPU module uses the latest General Purpose Computing on Graphical Processing Units (GPU) technology.
Programming Guide
The EDEM Programming Guide describes the EDEM API.
Coupling Interface Programming Guide
The Coupling Interface Programming Guide provides an overview of how to use the EDEM Coupling Interface to couple with a generic CFD code and/or Multi Body dynamics codes.
EDEMpy
EDEMpy is a Python library for accessing EDEM data from .h5 files (the underlying EDEM file format). EDEMpy does not require prior knowledge of advanced programming.
- Set up a Python Virtual Environment
  A Python Virtual Environment is a folder containing a standalone Python installation. It is recommended to create a new Virtual Environment for each Python project, as this helps track project dependencies and enables sharing of Python projects.
- Install EDEMpy
  The EDEM installation folder includes EDEMpy as a PIP package file ready to be installed.
- EDEMpy Syntax
  The following sections provide an overview of the syntax used in EDEMpy.
  - Load a Deck
    To start using EDEMpy, load an existing deck by creating a Deck object and providing the full path to a .dem file. By default, decks are loaded in 'read-only' mode to prevent any accidental changes.
  - Read Particle Data
    You can read particle information (positions, velocities, and so on) for a given particle type in a given Time Step which is contained in a ParticleType object.
  - Read Geometry Data
    You can query Geometry information in a similar way to querying particles.
  - Read Contact, Bond, and Collision data
    You use the same syntax for reading contact and collision data. The only differences are in the available properties in each case.
  - Create Bins
    EDEMpy offers methods for binning objects using the BoxBin and CylinderBin classes.
  - Write Data
    EDEMpy provides functionality to modify decks for the purposes of automated pre-processing.
  - Custom Properties
    EDEMpy has four types of custom properties that you can read from and write into.
EDEM Solver Capabilities
EDEM contains four solver engines.
Appendix
This section provides additional information about how to estimate simulation time, supported EDEM File types, attribute definitions, and so on.
EDEM Terminology
Definitions of terms used in EDEM.
References and Bibliography
This section cites the contributions made by various authors and sources that have been used as reference material for EDEM, and the specifics of how they have been applied can be found in the individual contact model sections.

Read Contact, Bond, and Collision data

You use the same syntax for reading contact and collision data. The only differences are in the available properties in each case.

To read contact, bond, and collision data:

Use the following command:

# Looking at the last timestep
timestep = deck.timestep[deck.numTimesteps - 1]
# Get contact data for particle-particle contacts
surf_contacts = timestep.contact.surfSurf
surf_contacts.getIds()
surf_contacts.getPositions()
surf_contacts.getNormalForce()
surf_contacts.getNormalOverlap()
surf_contacts.getTangentialForce()
surf_contacts.getTangentialOverlap()
# ...
# The same information is available for particle-geometry contacts
geom_contacts = timestep.contact.surfGeom
geom_contacts.getIds()
geom_contacts.getPositions()
# ...
# Bonds are very similar
bonds = timestep.bond
bonds.getIds()
bonds.getPositions()
# Bonds have some additional properties, however
bonds.getState()
bonds.getNormalTorque()
bonds.getTangentialTorque()
# ...
# The syntax for collisions is the same as contacts, with some additional information
surf_collisions = timestep.collision.surfSurf
surf_collisions.getIds()
surf_collisions.getPositions()
surf_collisions.getNormalEnergy()
surf_collisions.getFirstRadius()
surf_collisions.getSecondRadius()
# ...
# And again for particle-geometry collisions
geom_collisions = timestep.collision.surfGeom
geom_collisions.getIds()
geom_collisions.getPositions()
# ...

For more information about the list of available properties, see the EDEMpy API Reference Help included in the EDEM installation folder.