Error when running a fracture sealing MFiX-DEM case

Please include project files - Main menu/Submit bug report - attach zip file here.
fractureplugging.zip (38.4 MB)
When I use MFiX to simulate particle transport in a wellbore–fracture system, I keep receiving the following error. I have tried various fixes—adjusting the boundary conditions, initial conditions, time-step settings, and even modifying the STL file—but nothing seems to work. Could someone please help me, or at least point me in the right direction for troubleshooting? I’m a new user and would really appreciate any guidance. Thank you very much.

Ready

Starting env OMP_NUM_THREADS=16 C:\ProgramData\miniforge3\envs\mfix-25.2.1\Scripts\mfixsolver_smp.bat -s -f D:\MFiX\fractureplugging\fractureplugging.mfx

(mfix-25.2.1) D:/MFiX/fractureplugging>call python -m mfixgui.pymfix -m “Scripts/mfixsolver_smp.so” -s -f D:/MFiX/fractureplugging/fractureplugging.mfx

Using C:/ProgramData/miniforge3/envs/mfix-25.2.1/Scripts/d3.dll

Using C:/ProgramData/miniforge3/envs/mfix-25.2.1/Scripts/mfixsolver_smp.so

MFiX running, simulation time: 0.000ms elapsed time: 0:00:00

Number of SMP threads: 16

MFiX (25.2.1) simulation on host: DESKTOP-E0V5OEG

Run name: FRACTUREPLUGGING Time: 22: 5 Date: 9- 1-2025

Project version: 131

Message from open_files.f:394

Mesh file was not found: FRACTUREPLUGGING.msh

Mesh generation will be performed and a mesh file will be saved.

Mesh file was successfully opened: FRACTUREPLUGGING.msh

Message from check_data/check_solids_dem.f:1101

At time = 0.000000E+00 sec., DEM solids time step is computed based on particle properties,

DTSOLID (sec) = 0.116804E-05

Message from check_data/check_geometry.f:191

DES grid size:

DESGRIDSEARCH_IMAX = 200

DESGRIDSEARCH_JMAX = 100

DESGRIDSEARCH_KMAX = 30

From GET_STL_FACET_COUNT: Counting STL facets…

Message from cartesian_grid/get_stl_data.f:693

Counting facets from geometry_0005.stl …

Message from cartesian_grid/get_stl_data.f:693

Counting facets from geometry_0006.stl …

Message from cartesian_grid/get_stl_data.f:719

Total number of STL facets found = 15856

Maximum additional facets needed for BC/IS = 18

From GET_STL_DATA: Analyzing BCs…

BC_ID BC_TYPE

  5    CG_MI

  6    CG_NSW

Number of CG BCs = 2

Message from cartesian_grid/get_stl_data.f:879

Reading geometry from geometry_0005.stl …

STL file opened. Starting reading data…

Done reading file.

Message from cartesian_grid/get_stl_data.f:879

Reading geometry from geometry_0006.stl …

STL file opened. Starting reading data…

Done reading file.

Message from cartesian_grid/get_stl_data.f:1045

BC STL file(s) successfully read.

Total number of BC facets read = 15856

Number of valid facets = 15856

Number of ignored facets = 0

BC Geometry range from STL file:

X-range = -4.5000001788139343E-002 0.54500001668930054

Y-range = 0.0000000000000000 0.25000000000000000

Z-range = -4.5000001788139343E-002 4.5000001788139343E-002

The file FACETS_IGNORED.stl was successfully written and is provided for convenience (it is not used by MFiX).

From Detect_stl_along_mfix_box:

Grouping facets by BC patch…

Message from cartesian_grid/get_stl_data.f:1899

CG BC: 5 is flush with MFiX box.

It will be converted to regular BC.

Original BC type : CG_MI

New BC type : MI

Message from cartesian_grid/get_stl_data.f:1956

Number of active facets (BCs not flush with MFiX box) = 14836

The file FACETS_READ.stl was successfully written and is provided for convenience (it is not used by MFiX).

INITIALIZING VELOCITY NODES…

ESTIMATING POTENTIAL SCALAR CUT CELLS…

INTERSECTING GEOMETRY WITH SCALAR CELLS…

INTERSECTING GEOMETRY WITH U-MOMENTUM CELLS…

INTERSECTING GEOMETRY WITH V-MOMENTUM CELLS…

INTERSECTING GEOMETRY WITH W-MOMENTUM CELLS…

SETTING CUT CELL TREATMENT FLAGS…

COMPUTING INTERPOLATION FACTORS IN U-MOMENTUM CELLS…

COMPUTING INTERPOLATION FACTORS IN V-MOMENTUM CELLS…

COMPUTING INTERPOLATION FACTORS IN W-MOMENTUM CELLS…

COMPUTING 1/DX, 1/DY, 1/DZ FOR U-MOMENTUM CELLS…

COMPUTING 1/DX, 1/DY, 1/DZ FOR V-MOMENTUM CELLS…

COMPUTING 1/DX, 1/DY, 1/DZ FOR W-MOMENTUM CELLS…

FINDING MASTER CELLS FOR U-MOMENTUM CELLS…

FINDING MASTER CELLS FOR V-MOMENTUM CELLS…

FINDING MASTER CELLS FOR W-MOMENTUM CELLS…

MESH STATISTICS:

NUMBER OF CELLS = 600000

NUMBER OF STANDARD CELLS = 64963 ( 10.83 % of Total)

NUMBER OF CUT CELLS = 38404 ( 6.40 % of Total)

NUMBER OF FLUID CELLS = 103367 ( 17.23 % of Total)

NUMBER OF BLOCKED CELLS = 496633 ( 82.77 % of Total)

Cartesian grid preprocessing completed in 3.73s

DES MPI send/recv buffer: 251.6 MB

o 7710. Ghost particles/MB

o 4228. Particles/MB

o 11916. Neighbor pairs/MB

Preprocessing geometry for DES.

DES geometry preprocessing complete.

Saving Mesh connectivity and flags…

Setting master from flags…

Gather and Write MasterList…

Saving Mesh info for Scalar cells…

Saving Mesh info for U-MOMENTUM cells…

Reading mesh stats: D:\MFiX\fractureplugging\MESH_STATS.LOG

Saving Mesh info for V-MOMENTUM cells…

Saving Mesh info for W-MOMENTUM cells…

WROTE BOUNDARY IN VTK FILE : FRACTUREPLUGGING_boundary.vtk

PRE_PROCESSING COMPLETE.

From GET_STL_DATA_IS: Analyzing ISs…

IS_ID IS_TYPE

Number of IS using STL = 0

Initial DES particle array size: 4

Outflow BC defined: IJK_P_g remaining undefined.

Total number of particles in the system: 0

For mass inlet BC: 5

Boundary Area =  6.3250E-03

Total no. particles injected per solids time step =  1.03277712E-03

Total no. particles injected per second =        884

PI_FACTOR =  9.68263123E+02 PI_COUNT =     1

Start DES_MI_TIME =  1.13097335E-03

Uniform inlet velocity =  5.8557E-03

For each solid phase,

  For solid phase   1:

    No. particles injected per solids time step =  1.03277712E-03

    No. particles injected per second =        884

    Calculated inlet velocity =  5.8557E-03

Reading mesh boundary: D:\MFiX\fractureplugging\FRACTUREPLUGGING_boundary.vtk

Reading mesh: D:\MFiX\fractureplugging\FRACTUREPLUGGING_MESH.vtu

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 195 J = 81 K = 17

Epg = 1.0000 Ug = 0.18114 Vg = 0.0000 Wg = -0.56510E-02

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 201 J = 81 K = 17

Epg = 1.0000 Ug = 0.19527 Vg = 0.0000 Wg = -0.38827E-01

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 201 J = 2 K = 17

Epg = 1.0000 Ug = 0.28868 Vg = -0.10166 Wg = -0.57989E-01

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 201 J = 2 K = 17

Epg = 1.0000 Ug = 0.18432 Vg = -0.65556E-01 Wg = -0.37398E-01

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 201 J = 2 K = 17

Epg = 1.0000 Ug = 0.20840 Vg = -0.64163E-01 Wg = -0.36591E-01

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 194 J = 80 K = 17

Epg = 1.0000 Ug = 0.17696 Vg = 0.12391E-01 Wg = -0.70519E-03

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

MFiX running, simulation time: 0.000ms elapsed time: 0:01:00

Warning from utilities_mod.f:170

Velocity exceeds limit: 0.17567

in cell: I = 201 J = 2 K = 17

Epg = 1.0000 Ug = 0.26848 Vg = -0.10067 Wg = -0.57413E-01

To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

Error from iterate.f:1020

Run diverged/stalled at DT = DT_MIN. Recovery not possible!

Fatal error reported on one or more processes. The .LOG file

may contain additional information about the failure.

MFiX process has stopped

Previous MFiX run is resumable.

Have you tried the suggestion in the output?: To change the limit, adjust the scale factor MAX_INLET_VEL_FAC.

I have tried to adjust the scale factor MAX_INLET_VEL_FAC from 1 to 2, but the error still occurred after a while. I wonder if the fundamental issue might be related to my mesh. My CFD domain consists of a cylindrical wellbore and a narrow rectangular fracture. Could such a unique flow field directly using XYZ-direction mesh division lead to mesh quality problems? How should I address this? Does MFiX support importing meshes directly from other mesh generation software? If not, how does MFiX handle complex geometries?


If an approprately named .msh file is found, it will be used. Examine the mfix output for lines containing “Mesh file”.

Mesh file was not found: FRACTUREPLUGGING.msh

Mesh generation will be performed and a mesh file will be saved.

Mesh file was successfully opened: FRACTUREPLUGGING.msh

Thank you for your answer. So my understanding is that MFiX will first check whether there is a .msh file in the MFiX/fracturingsealing path. If such a file exists, MFiX will directly read the mesh file without executing the meshing strategy set in the GUI mesh panel. Is that correct? In other words, MFiX can directly import meshes generated by other software, such as Fluent, right?

Yes, if the file is in the right format. Try it.