Skip to content
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

Add support for non nonconservative equations to subcell-limiting #116

Conversation

amrueda
Copy link
Collaborator

@amrueda amrueda commented Oct 13, 2023

No description provided.

amrueda and others added 22 commits October 5, 2023 17:47
…ative systems

-> A working version of this implementation is added for the GLM-MHD system
-> The flux-differencing formula requires non-conservative terms of the
   form (local * symmetric)... I modified equations/ideal_glm_mhd_2d.jl and
   solvers/dgsem_tree/dg_2d.jl to make it work
-> In this first implementation, we only use the Powell term and
   deactivate the GLM term
…he modified Powell source term. This was needed due to incompatibility on non-conforming meshes.
Co-authored-by: Hendrik Ranocha <ranocha@users.noreply.github.com>
@github-actions
Copy link

github-actions bot commented Oct 13, 2023

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.

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.

amrueda and others added 24 commits October 23, 2023 15:23
Co-authored-by: Benjamin Bolm <74359358+bennibolm@users.noreply.github.com>
…ation

Co-authored-by: Benjamin Bolm <74359358+bennibolm@users.noreply.github.com>
Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>
Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>
…vative equations

Co-authored-by: Benjamin Bolm <74359358+bennibolm@users.noreply.github.com>
* Clean branch

* Un-Comment

* un-comment

* test coarsen

* remove redundancy

* Remove support for passive terms

* expand resize

* comments

* format

* Avoid code duplication

* Update src/callbacks_step/amr_dg1d.jl

Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>

* comment

* comment & format

* Try to increase coverage

* Slightly more expressive names

* Apply suggestions from code review

* add specifier for 1d

* Structs for resizing parabolic helpers

* check if mortars are present

* reuse `reinitialize_containers!`

* resize calls for parabolic helpers

* update analysis callbacks

* Velocities for compr euler

* Init container

* correct copy-paste error

* resize each dim

* add dispatch

* Add AMR for shear layer

* USe only amr shear layer

* first steps towards p4est parabolic amr

* Add tests

* remove plots

* Format

* remove redundant line

* platform independent tests

* No need for different flux_viscous comps after adding container_viscous to p4est

* Laplace 3d

* Longer times to allow converage to hit coarsen!

* Increase testing of Laplace 3D

* Add tests for velocities

* remove comment

* Add comments

* Remove some specializations

* Add comments

* Use tuple for outer, fixed size datastruct for internal quantities

* Format

* Add comments

* Update examples/tree_2d_dgsem/elixir_navierstokes_shearlayer_amr.jl

Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>

* Update src/Trixi.jl

Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>

* Move velocity into elixir

* remove tests

* Remove deprecated comments

* Add news

---------

Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>
Co-authored-by: Jesse Chan <1156048+jlchan@users.noreply.github.com>
* format test

* move D_SBP = ... outside of at-test_trixi_include

* fix definition of SBP operators in tests (global)

* do not indent all test files

* fix typo

* check formatting of test
…ork#1670)

Co-authored-by: Hendrik Ranocha <mail@ranocha.de>
Co-authored-by: Benjamin Bolm <74359358+bennibolm@users.noreply.github.com>
Co-authored-by: Michael Schlottke-Lakemper <michael@sloede.com>
Co-authored-by: Benjamin Bolm <74359358+bennibolm@users.noreply.github.com>
@bennibolm bennibolm merged commit bd781ec into bennibolm:subcell-limiting Nov 2, 2023
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants