-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial support for surface coupling of two systems #1452
Conversation
….jl into sc/coupled_to_main
….jl into sc/coupled-reduced
I am slightly worried why My only explanation is that we accidentally implemented a more specific method that matches better than the one before, but somehow there's no complaint that something isn't working right 🤷♂️. Can anyone tell what's going on here? |
…t multi-system aware)
Hopefully fixed in a69bf66. |
Co-authored-by: Hendrik Ranocha <[email protected]>
Since this PR is heavily based on #553, we should give appropriate credit. Whoever merges this, please add the following lines to the commit message:
@bennibolm @efaulhaber @NichtLucas Please update your email addresses with your GH email address in this post here directly such that the commits are appropriately attributed to you. |
The reduced code coverage seems to be related to code that is not part of this PR. Should we then go ahead with the merge? |
Let's wait for the formatting PR first, please |
@SimonCan I just merged Note: It would be also great if you could also verify that the formatter did not do something ugly with your changes that we should fix before merging to |
@sloede , according to my local tests using coupling and AnalysisCallback it works. Github's tests also seem to go through. |
This adds a set of boundary coupling to Trixi.jl. A full set of boundary fluxes will be added after this merge.
This PR is based on the excellent work done by @efaulhaber @bennibolm @NichtLucas in #553.
Related issue tracker: #1520