hello everyone:
the mfix-dem 22.2.2 is used in win10 OS, the simulation suddenly stops without any prompts.
the case is uploaded below:
wangshuai-1_2025-06-12T193155.542186.zip (511.1 KB)
The LOG file says a particle went out of bound:
>>>>>-----------------------------------------------------------------
MESSAGE from des\\check_cell_movement.f:138
Error 1100: Particles detected in a ghost cell:
Particle 93 moved into cell with K index 3
Z-Position: 0.1013E-02 Z-Velocity: 7.755
Particle 279 moved into cell with K index 3
Z-Position: 0.1013E-02 Z-Velocity: 7.755
This is a fatal error. A particle output file (vtp) will be written
to aid debugging.
<<<<<-----------------------------------------------------------------
>>>>>#################################################################
ERROR from des\\check_cell_movement.f:180
<<<<<#################################################################
**********************************************************************
Fatal error reported on PE 0. The .LOG file may contain
additional information about the failure.
**********************************************************************
Try to increase the spring stiffness or delete rogue particles (Solids>DEM pane).
I also recommend you install the latest version (25.1.2).
thanks for your reply jeff,
I checke the button in dem pane to remove the rogue particles.
but the same problem occured. the case as below:
test-ws_2025-06-12T223540.503613.zip (872.8 KB)
If you were running in the MFiX GUI the “Error” should have triggered a popup. But there seems to be something slightly misformatted about the error message, the “ERROR” text is empty, and the details about the rogue particle are in the previous “MESSAGE” (which does not trigger a popup, but should be visible if you scroll through the “Messages” in the MFiX message popup, or click on the “Errors / Warnings / Messages” at the bottom-right of the GUI.
Hi cgw,
What should I do to avoid the generation of rogue particles?
The first step is, as Jeff suggested, to upgrade to MFiX 25.1.2 (the latest version).
Running your case with this version, the message looks like this:
This does not cause the solver to exit, the particle is removed, and some suggestions are given.
I am running this case on Linux with 25.1.2 and it has not triggered the error (currently at time=0.3s). Your Hamaker constant is really large though (3.45E-12 J). It is typically in the range 1E-19 to 1E-20 J. Not sure if this is the source of your issue.
Ran to conclusion for me (25.1.2, Linux)
Simulation start time = 0.0000s
Simulation time reached = 1.000s
Elapsed real time = 43.82m
Time spent in I/O = 2.274s
Because I want to simulate particles with a diameter of 10um to observe agglomeration.
However, the consumption time of 10um particles is too long, so 1mm particles are used as the object. In order to achieve equivalent agglomeration effect, the van der Waals force was amplified. So theHamaker constant is proportional magnificated.
hi cgw,
you run the case in 25.1.2, and successfully obtain the results?
can you up load the case, please?
It’s exactly the case you uploaded, I did not change anything.
Please upgrade your MFiX to 25.1.2. Thanks.