Remove doubled saving of subcell limiting factors#2588
Merged
DanielDoehring merged 8 commits intotrixi-framework:mainfrom Sep 30, 2025
Merged
Remove doubled saving of subcell limiting factors#2588DanielDoehring merged 8 commits intotrixi-framework:mainfrom
DanielDoehring merged 8 commits intotrixi-framework:mainfrom
Conversation
bennibolm
commented
Sep 25, 2025
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2588 +/- ##
=======================================
Coverage 96.79% 96.79%
=======================================
Files 525 525
Lines 42708 42699 -9
=======================================
- Hits 41337 41329 -8
+ Misses 1371 1370 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
Author
|
I just noticed that it is not necessary to set the antidiffusive flux at the interfaces to zero in each Trixi.jl/src/solvers/dgsem_tree/dg_2d_subcell_limiters.jl Lines 685 to 693 in e842dd2 Note: Continued in #2589 |
Contributor
Author
|
@DanielDoehring Could you please take a look at this? |
DanielDoehring
added a commit
to DanielDoehring/Trixi.jl
that referenced
this pull request
Feb 19, 2026
* Remove `alpha1` and `alpha2` * Adapt comment * Apply suggestions from code review * Apply suggestions from code review * Update src/callbacks_stage/subcell_limiter_idp_correction_2d.jl * Update src/callbacks_stage/subcell_limiter_idp_correction_2d.jl --------- Co-authored-by: Daniel Doehring <daniel.doehring@rwth-aachen.de> Co-authored-by: Daniel Doehring <doehringd2@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before we had
alpha,alpha1andalpha2inContainerSubcellLimiterIDP2D.In
alpha, we saved the node-wise limiting factor. Inalpha1andalpha2, basically, we only saved the maximum limiting factor between two nodes, which was used only once afterward.
This was convenient since we didn't need any
ifclause later in the correction stage.In this PR, I removed
alpha1andalpha2and compute the maximum when actually needed.Moreover, to have the nice flux-differencing update in the correction stage
we calculated e.g.
for every node, although
antidiffusive_flux1was zero at the element interfaces (i=1ori=nnodes+1).To avoid unnecessary access to and further computation with zero entries, we directly use zero vectors in those cases now.
With that, we can keep the nice flux-differencing update from above.