The spouted bed geometry was drawn with 3 boxes in mfix, but did not work

MFiX
#1

image
image183×675 8.19 KB

image
image324×730 11.5 KB

I tried to use three boxes to draw the spouted bed geometry, but the mfix error, there is no specific reason, I think it may be their own entrance and wall boundary condition settings, can anyone help me? Thank you
geometry_0003.stl (1.6 MB)
spout.mfx (15.1 KB)
geometry_0003.stl (1.6 MB)

error message：
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.

Backtrace for this error:
#0 0x7f000e0bf20f in ???
#1 0x7effc1101ea8 in __dgtsv_mod_MOD_dgtsv
at /usr/local/src/conda/mfix-solver-21.1.4/model/DGTSV.f:190
#2 0x7effc0ff3114 in __leqsol_MOD_leq_iksweep
at /usr/local/src/conda/mfix-solver-21.1.4/model/leqsol_mod.f:815
#3 0x7effc0ff4131 in __leqsol_MOD_leq_msolve
at /usr/local/src/conda/mfix-solver-21.1.4/model/leqsol_mod.f:412
#4 0x7effc11c4401 in __leq_bicgs_mod_MOD_leq_bicgs0
at /usr/local/src/conda/mfix-solver-21.1.4/model/leq_bicgs.f:392
#5 0x7effc11c52a1 in __leq_bicgs_mod_MOD_leq_bicgs
at /usr/local/src/conda/mfix-solver-21.1.4/model/leq_bicgs.f:91
#6 0x7effc10663be in __solve_lin_eq_mod_MOD_solve_lin_eq
at /usr/local/src/conda/mfix-solver-21.1.4/model/solve_lin_eq.f:165
#7 0x7effc106a5e9 in v_m_star
at /usr/local/src/conda/mfix-solver-21.1.4/model/solve_vel_star.f:515
#8 0x7effc106a5e9 in __solve_vel_star_mod_MOD_solve_vel_star
at /usr/local/src/conda/mfix-solver-21.1.4/model/solve_vel_star.f:136
#9 0x7effc0e5d4d0 in _iterate_MOD_do_iteration
at /usr/local/src/conda/mfix-solver-21.1.4/pymfix/iterate.f90:255
#10 0x7effc0ff5a7d in run_fluid
at /usr/local/src/conda/mfix-solver-21.1.4/model/mfix.f:188
#11 0x7effc0ff5a7d in run_mfix
at /usr/local/src/conda/mfix-solver-21.1.4/model/mfix.f:142
#12 0x7effc0e60296 in __main_MOD_run_mfix0
at /usr/local/src/conda/mfix-solver-21.1.4/pymfix/main.f90:82
#13 0x7effc0e535f7 in f2py_rout_mfixsolver_main_run_mfix0
at /usr/local/src/conda/mfix-solver-21.1.4/f2pywrappers/mfixsolvermodule.c:1270
#14 0x556e6bded11a in _PyObject_FastCallKeywords
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:199
#15 0x556e6bded590 in call_function
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:4619
#16 0x556e6be046d4 in _PyEval_EvalFrameDefault
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:3093
#17 0x556e6bdd0757 in PyEval_EvalFrameEx
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:547
#18 0x556e6bdd0757 in function_code_fastcall
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:283
#19 0x556e6bdd0757 in _PyFunction_FastCallKeywords
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:408
#20 0x556e6bded3a4 in call_function
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:4616
#21 0x556e6be01119 in _PyEval_EvalFrameDefault
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:3110
#22 0x556e6bdd0757 in PyEval_EvalFrameEx
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:547
#23 0x556e6bdd0757 in function_code_fastcall
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:283
#24 0x556e6bdd0757 in _PyFunction_FastCallKeywords
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:408
#25 0x556e6bded3a4 in call_function
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:4616
#26 0x556e6be01119 in _PyEval_EvalFrameDefault
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:3110
#27 0x556e6bda3446 in PyEval_EvalFrameEx
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/ceval.c:547
#28 0x556e6bda3446 in function_code_fastcall
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:283
#29 0x556e6bda3446 in _PyFunction_FastCallDict
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:322
#30 0x556e6bdafaad in _PyObject_Call_Prepend
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:906
#31 0x556e6bdafaad in method_call
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/classobject.c:309
#32 0x556e6bda3e9c in PyObject_Call
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Objects/call.c:245
#33 0x556e6be45b32 in t_bootstrap
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Modules/_threadmodule.c:994
#34 0x556e6bcbb118 in pythread_wrapper
at /home/builder/ktietz/cos6/ci_cos6/python_1622835739569/work/Python/thread_pthread.h:174
#35 0x7f000e276608 in ???
#36 0x7f000e19b292 in ???
#37 0xffffffffffffffff in ???
Process exit /home/gxy/.miniconda3/envs/mfix-21.1.4/bin/mfixsolver -s -f /home/gxy/mfix/spout/zhang/spout/spout.mfx
Previous MFiX run is resumable. Reset job to edit model
MFiX process has stopped

Floating-point invalid operation / erroneous arithmetic operation
A code error when i run a case with tfm
#2

This is an interesting error. The file DGTSV.f where the error is happening is new code, added (by me) to version 21.1. This is a modified algorithm for solving tridiagonal matrix systems which we found was up to 30% faster than the old DGTSV algorithm in ODEPACK. In our testing, we found we got numerically identical results, so we switched over. I’m not sure if your error is related to the new code or if it still would have happened with the old code. I’ll take a look at this as soon as I can, but I’m going to be out of the office for a few days so it might not be until next week. The big question is how we got to a zero-divide.

– Charles

1 Like
#3

Did you check the quality of your mesh?

1 Like
#4

This model fails with both the new DGTSV code and the old ODEPACK routine, but the failure is different in both cases - we get a zero-divide with the new code, and with the old code a bunch of leq_iksweep 0 messages culiminating in a divergence. So it’s not the new tridiagonal algorithm that is causing the problem.

1 Like