Skip to content

3D support for subcell limiting#2572

Draft
bennibolm wants to merge 36 commits intotrixi-framework:mainfrom
bennibolm:3d-subcell-limiting
Draft

3D support for subcell limiting#2572
bennibolm wants to merge 36 commits intotrixi-framework:mainfrom
bennibolm:3d-subcell-limiting

Conversation

@bennibolm
Copy link
Copy Markdown
Contributor

@bennibolm bennibolm commented Sep 17, 2025

Add 3d support for subcell limiting on P4estMesh

Mergeable features

Treemesh features:

@bennibolm bennibolm added the enhancement New feature or request label Sep 17, 2025
@github-actions
Copy link
Copy Markdown
Contributor

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

  • The PR has a single goal that is clear from the PR title and/or description.
  • All code changes represent a single set of modifications that logically belong together.
  • No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

  • The code can be understood easily.
  • Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
  • There are no redundancies that can be removed by simple modularization/refactoring.
  • There are no leftover debug statements or commented code sections.
  • The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

  • New functions and types are documented with a docstring or top-level comment.
  • Relevant publications are referenced in docstrings (see example for formatting).
  • Inline comments are used to document longer or unusual code sections.
  • Comments describe intent ("why?") and not just functionality ("what?").
  • If the PR introduces a significant change or new feature, it is documented in NEWS.md with its PR number.

Testing

  • The PR passes all tests.
  • New or modified lines of code are covered by tests.
  • New or modified tests run in less then 10 seconds.

Performance

  • There are no type instabilities or memory allocations in performance-critical parts.
  • If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

  • The correctness of the code was verified using appropriate tests.
  • If new equations/methods are added, a convergence test has been run and the results
    are posted in the PR.

Created with ❤️ by the Trixi.jl community.

@codecov
Copy link
Copy Markdown

codecov bot commented Sep 17, 2025

Codecov Report

❌ Patch coverage is 9.35024% with 572 lines in your changes missing coverage. Please review.
✅ Project coverage is 95.89%. Comparing base (e6a0a8f) to head (186cc43).
⚠️ Report is 19 commits behind head on main.

Files with missing lines Patch % Lines
src/solvers/dgsem_tree/dg_3d_subcell_limiters.jl 0.00% 310 Missing ⚠️
src/solvers/dgsem_p4est/dg_3d_subcell_limiters.jl 0.00% 213 Missing ⚠️
src/equations/ideal_glm_mhd_3d.jl 0.00% 49 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2572      +/-   ##
==========================================
- Coverage   97.05%   95.89%   -1.15%     
==========================================
  Files         606      606              
  Lines       47371    48002     +631     
==========================================
+ Hits        45972    46031      +59     
- Misses       1399     1971     +572     
Flag Coverage Δ
unittests 95.89% <9.35%> (-1.15%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@DanielDoehring
Copy link
Copy Markdown
Member

This is huge - could we maybe do euler only first to get a feeling for this?

@bennibolm
Copy link
Copy Markdown
Contributor Author

This is huge - could we maybe do euler only first to get a feeling for this?

Yes, the plan is not to merge everything at once. First, Euler and probably only one limiting option.

@bennibolm bennibolm force-pushed the 3d-subcell-limiting branch 3 times, most recently from 1911c38 to 691c88f Compare October 27, 2025 09:02
@bennibolm bennibolm force-pushed the 3d-subcell-limiting branch 2 times, most recently from 6a05152 to a1e4497 Compare November 19, 2025 16:40
@bennibolm bennibolm force-pushed the 3d-subcell-limiting branch from b4904bf to e6105a9 Compare December 3, 2025 15:26
@bennibolm bennibolm force-pushed the 3d-subcell-limiting branch from 9f3ecd0 to a27b8fc Compare January 21, 2026 08:59
bennibolm and others added 8 commits February 26, 2026 11:49
* Add full 3d implementation on P4estMesh

* Add 3d positivity limiting for nonlinear variables

* Implement suggestions

* Reduce allowed allocs in test

* Increase allocs number again

* Add 3d TreeMesh implementation

* Adapt test

* Remove `TreeMesh`from `calc_bounds_two_sided_boundary!`

* fmt

* Fix test after fixing bug in last commit

* Update examples/tree_3d_dgsem/elixir_euler_sedov_blast_wave_sc_subcell.jl

* Adapt test numbers

* Remove doubled functions

* Fix elixir and add TreeMesh to `volume_integral_kernel!`

* Rename variable e to e_total
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants