Known Issues

This section describes the known issues in EDEM version 2025.1.

Non-manifold Geometry sections from legacy decks

In versions prior to EDEM 2024, Geometries could incorrectly be assigned as volume (closed) Geometries instead of surface (open) Geometries. From EDEM 2024 onwards, if non-manifold Geometries (when more than two triangles share the same edge) are loaded from an older deck, they will be converted to surface (open) Geometries. This will not affect simulation behavior unless the Geometry has volume packing, a factory attached, or if the mass, center of mass, or Moment of Inertia was being used (in which case, it is recommended to recompute them in the Geometry Mass tab or re-import the CAD file). A warning will be displayed when this conversion happens.

EDEM Solver Compatibility

The EDEM Solver Engine has some restrictions on the types of simulations it can run in the current version. For more information about solver capabilities, see EDEM Solver Capabilities.

MotionView Geometry Import

To use the parent-child functionality in EDEM with a rotating Geometry imported from MotionView, the Geometries local origin must be moved using the local origin offset to the center of the geometry. If the local origin is not at the center of the rotating Geometry, the child will move around an axis relative to the automatic local origin (0,0,0). This will cause the child to move in unwanted directions.

EDEM CPU utilization higher than expected

On some computers, the Windows Task Manager can show that EDEM is using significantly more CPU threads than expected. This will typically happen when there are many idle CPU threads available. As a workaround, you can create the following environment variable: OMP_WAIT_POLICY=passive. This will restrict the number of CPU threads EDEM is using to the number that you have specified. Testing has not shown this issue to have any noticeable effect on simulation performance.