Hi Mr K,
from your email I understand that you created a second coupling manager?
So you have something like
CouplingManager<DarcyTypeTag, StokesTypeTag1> couplingManager1;
CouplingManager<DarcyTypeTag, StokesTypeTag2> couplingManager2;
?
MultiDomain currently requires a single coupling manager that knows
about all domains, with each domain having a unique domain id. In
general, this can be implemented by inheriting from two specializations
of a two-domain coupling manager. By specializations I mean specialized
for different pairs of domain ids. An example for this is the
FacetCouplingThreeDomainManager in
https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/blob/master/dumux/multidomain/facet/couplingmanager.hh
Besides only inheriting, you need to do some overload resolution efforts
in the dderived three domain coupling manager. In the above file, you
can find examples for all of this.
For the StokesDarcy two-domain coupling manager, I guess the missing
piece is that the subdomain ids cannot be defined via template
parameters but are hardcoded to 0,1,2. You could try this locally by
simply moving them into the template arguments and use those wherever
the 0,1 or 2 are hardcoded.
Cheers,
Dennis
On 24.07.20 18:30, Mr K wrote:
Hello,
I want to model porous medium with upper and lower free flow domain.
I use 2 domain darcy & stokes exercise for doing this.
I copy stokes problem and rename to stokes2 & change main.cc file
In main.cc, I struct new coupling manager with stokes2 TTag.
after making file only first of the stokes type tag recognized. and
raise error for another type tag.
how can I correct this problem?
Is there any example for 3 domain stokes - darcy - stokes ?
_______________________________________________
DuMux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
_______________________________________________
DuMux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
