Conversation
Member
Author
|
This should be ready, but we need to wait until the breaking release of Trixi.jl is out to let CI run. |
ranocha
previously approved these changes
Feb 7, 2026
Member
ranocha
left a comment
ranocha
left a comment
There was a problem hiding this comment.
LGTM. We will trigger CI once the Trixi.jl v0.15 has been released.
ranocha
approved these changes
Feb 7, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #141 +/- ##
=======================================
Coverage 97.10% 97.10%
=======================================
Files 33 33
Lines 4558 4558
=======================================
Hits 4426 4426
Misses 132 132 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
2 participants
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.
This unifies the boundary conditions across mesh types, i.e.,
NamedTuples is used everywhere. See trixi-framework/Trixi.jl#2761.