I am experiencing an issue with the DMP solver in MFIX on a virtual machine running Ubuntu 22.04.5 LTS, based on Windows 7. Initially, I can compile DMP solver and run the GSP tutorial case without any problems. However, if I interrupt the simulation and attempt to restart the case, I encounter errors that seem related to parallel processing.
Details:
System: Ubuntu 22.04.5 LTS (Virtual Machine on Windows 7)
MFIX Version: 24.3.1
Issue: Restarting a case after interruption causes errors in parallel runs.
Observations:
The problem occurs only with parallel runs.
Single-core computations do not have restart issues.
DEM & SQP parallel computations and restarts function correctly.
Thanks for the bug report, I will look into this. Can you tell me a little more about how you are running this? Are you resuming after the run reaches tstop, are you pressing “stop” or otherwise killing the process, or are you using the “pause” button in the MFiX GUI? And what parameters, if any, are you changing before resuming?
I am running the case using the MFIX GUI. I first use the “pause” button, then “stop,” and finally attempt to “resume” the case. I have not changed any simulation parameters, including the number of cores used for the DMP run.
I initially discovered this issue while running my own GSP case and then confirmed it by testing the tutorial GSP case, where the same problem occurred.
Please let me know if you need any more information.
I don’t have a solution yet but here are a few comments:
It has nothing to do with the virtual machine. I get the same result running on Linux
If I pause the simulation via the pause button, then resume by pressing the run button, without stopping it, the job resumes without problems.
If I stop the job then try running with “Resume previous MFiX run” selected, I also get a crash. So pausing is not the root problem.
I get the same crash if I stop the simulation by writing an MFIX.STOP file in the run directory, so the problem is not the way the GUI stops the job (using a different mechanism, via the HTTP interface).
I will let you know as we make progress on this issue. Thank you very much for the bug report.
Thank you for your response. I would appreciate it if you could guide me on how to fix the bug. Should I add an additional udf file in the project directory? Please let me know the steps involved.
you should be able to find a editor tab from the left bottom corner, click editor
then from the left side you can find a MFIX source with a search bar underneath.
type read_res0_des.f and you should see a file in the dir tree, click that file and copy to project directory for editing.
then in line 25: put use mpi_utility, only: global_all_max
then in line 122: add CALL GLOBAL_ALL_MAX(NGluedParticles)
save and build the solver, this should fix the restart issue. Please let me know if the issue persists.