-
Notifications
You must be signed in to change notification settings - Fork 109
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
specialize calc_boundary_flux!
for nonconservative terms for DGMulti
#1431
Conversation
Feel free to request a review from me when you're ready 🙂 @andrewwinters5000 should also have a look, I think, since he is our nonconservative specialist |
Thanks! Still running into some bugs at the moment. |
Codecov Report
@@ Coverage Diff @@
## main #1431 +/- ##
===========================================
+ Coverage 25.73% 94.77% +69.05%
===========================================
Files 357 358 +1
Lines 29408 29643 +235
===========================================
+ Hits 7566 28094 +20528
+ Misses 21842 1549 -20293
Flags with carried forward coverage won't be shown. Click here to find out more.
|
DGMulti
DGMulti
How can I test this? Right now I get
when trying to run the |
@sloede sorry, I forgot to import some routines from LinearAlgebra.jl. They are loaded by default in my |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With these two changes, I get the allocations in
@time Trixi.calc_single_boundary_flux!(semi.cache, t, first(boundary_conditions), first(keys(boundary_conditions)), Trixi.have_nonconservative_terms(equations), mesh, equations, semi.solver)
from
0.000205 seconds (1.40 k allocations: 70.562 KiB)
down to
0.000038 seconds (6 allocations: 2.672 KiB)
Thus there's certainly some funny business still going on, but less than there was before...
Filed an issue for implementing BCs on non-conservative terms. #1445 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Should be fine, I think. It would be great if @andrewwinters5000 could have a look, too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Should be fine, I think. It would be great if @andrewwinters5000 could have a look, too
@ranocha @sloede is the failure of MPI on Ubuntu spurious? The stacktrace is WARNING: replacing module TrixiTestModule.
[ Info: Testset elixir_advection_amr.jl finished in 87.166008962 seconds.
WARNING: replacing module TrixiTestModule.
════════════════════════════════════════════════════════════════════════════════════════════════════
/home/runner/work/Trixi.jl/Trixi.jl/examples/p4est_3d_dgsem/elixir_advection_amr_unstructured_curved.jl
signal (15): Terminated
in expression starting at /home/runner/work/Trixi.jl/Trixi.jl/test/runtests.jl:9
signal (15): Terminated
in expression starting at /home/runner/work/_actions/julia-actions/julia-runtest/v1/test_harness.jl:7
epoll_wait at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
epoll_wait at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 3368 RUNNING AT fv-az446-880
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
Error: The operation was canceled. |
No, it was already noted by @ranocha here: #1316 (comment) This seems to be either a CI bug or an upstream bug. |
Thanks! Is it OK to merge this then? |
I'd like to see coverage... let's give it one more try (maybe issues on https://www.githubstatus.com/ might b related?) |
DGMulti
calc_boundary_flux!
for nonconservative terms for DGMulti
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrewwinters5000 Do you have some time for a review?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall everything looks fine. I just left a few comments specifically regarding the (perhaps unused) BoundaryConditionDoNothing
and BoundaryConditionDirichlet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good from my end.
I'm ok with merging this content-wise, but is out coverage system broken? I haven't looked at it for a while, but now I see that we are <95% (we were at 97%, weren't we), but when looking at e.g. coveralls, everything seems to be untested in one particular file - that can't be right, can it? |
CI has been broken for some reasons and I'm not sure whether we can trust it here. I propose to merge this now and check the coverage on |
This PR enables for
IdealGlmMhdEquations2D
the following:BoundaryConditionDirichlet
,BoundaryConditionDoNothing
, and a custom slip wall type boundary condition which is defined within the elixirexamples/dgmulti_2d/elixir_mhd_reflective_BCs.jl
.IMO there are a few design issues still (see my initial review below).