PorousFlowSink: libMesh error in ThreadedElementLoopBase:Assertion `i < _val.size()' failed. #29131
Replies: 1 comment 12 replies
-
I've seen that in my test-model above the error seems to be triggered in line 94 of IntegratedBC.C: moose/framework/src/bcs/IntegratedBC.C Lines 90 to 95 in 37b999b Here, Similar are ... ... line 117 + 118 moose/framework/src/bcs/IntegratedBC.C Lines 116 to 120 in 37b999b ... line 161 + 162 moose/framework/src/bcs/IntegratedBC.C Lines 158 to 164 in 37b999b ... line 176 moose/framework/src/bcs/IntegratedBC.C Lines 175 to 178 in 37b999b |
Beta Was this translation helpful? Give feedback.
-
Dear Moose Community,
I'm trying to realize a hydro-mechanical coupled simulation using the
PorousFlowSink
to define boundary conditions:PorousFlowSink
is active on is re-assinged to an 'inactive' subdomain via aTimedSubdomainModifier
, I get the following message in DBG-mode and the model will not converge:OPT-mode will work as expected and the model will converge.
I can circumvent this message (and non-convergence) in DBG-mode by deactivating the
PorousFlowSink
using aTimesEnableControl
. But this feels a little unnecessary and adds some complexity to the model I'd like to avoid.Furthermore, other boundary conditions (e.g.
DirichletBC
) will not produce any problems even if the boundary (or parts of it) they live on is re-assigned to an 'inactive' subdomain.I'd tried to understand what exactly is the problem for Moose but did not succeed. It is even unclear to me if this is a problem in Moose or in libmesh.
Could you please comment on this behaviour:
Thanks in advance!
Please find a simple test-model below (run-time should be fast)
input-file
This model will fail in DBG-mode. Uncomment the
TimesEnableControl
to make it converge.The stack trace from bdg looks like:
PS: here a similar error is described #9659
Beta Was this translation helpful? Give feedback.
All reactions