You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, we need to update the MGR strategies accordingly. I can take a look
I think we need to change the way these mgr strategies are defined so that we avoid this kind of issue. We fix the ordering statically in the mgr strategies but the actual ordering of the fields is defined at execution. It can get tricky now that we start combining a lot of solvers.
Yes, we need to update the MGR strategies accordingly. I can take a look
I think we need to change the way these mgr strategies are defined so that we avoid this kind of issue. We fix the ordering statically in the mgr strategies but the actual ordering of the fields is defined at execution. It can get tricky now that we start combining a lot of solvers.
To be more precise, the ordering depends on the order in which the functions to add fields to the dofManager are called so technically we can know it before execution but I still think that it is tricky to keep track of this and, if it changes like in this case, we have no test to catch the issue.
Example 1 (conforming):
PoroElastic_conformingFracture_2d_faultSlip
switch to MGR:
run and observe:
Examples 2 (EDFM): https://github.com/GEOS-DEV/GEOS/blob/develop/inputFiles/poromechanicsFractures/SlipPermeability_embeddedFrac.xml
and SlipPermeability_pEDFM_smoke.xml
similar convergence issues observed.
The text was updated successfully, but these errors were encountered: