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 test coverage for Non-conservative BC do nothing #2269

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

MarcoArtiano
Copy link
Contributor

No description provided.

Copy link
Contributor

github-actions bot commented Feb 7, 2025

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.

Copy link

codecov bot commented Feb 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.88%. Comparing base (ba30bb3) to head (d6f99fc).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2269      +/-   ##
==========================================
+ Coverage   96.88%   96.88%   +0.01%     
==========================================
  Files         490      490              
  Lines       39491    39491              
==========================================
+ Hits        38257    38260       +3     
+ Misses       1234     1231       -3     
Flag Coverage Δ
unittests 96.88% <ø> (+0.01%) ⬆️

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.

@MarcoArtiano
Copy link
Contributor Author

MarcoArtiano commented Feb 7, 2025

By the way, Base.isapprox don't accept tuples, so we might define a new method for it, for instance

function Base.isapprox(x::Tuple, y::Tuple;
    atol::Real=0, rtol::Real=rtoldefault(x,y,atol),
    nans::Bool=false, norm::Function=abs)
x′, = promote(x)
y′, = promote(y)
x == y ||
(all(isfinite.(x)) && all(isfinite.(y)) && Trixi.norm.(x .- y) <= max(ntuple(_ -> atol, length(x)), rtol.*max(Trixi.norm.(x′), Trixi.norm.(y′)))) ||
(nans && isnan(x) && isnan(y))
end

to keep everything cleaner, so that

test_bc_out = boundary_condition_do_nothing(u, outward_direction, x, t,
                                                    surface_fluxes,
                                                    equations)
        @test surface_fluxes[1](u, outward_direction, equations) ≈ test_bc_[1]
        @test surface_fluxes[2](u, outward_direction, equations) ≈ test_bc_[2]

will look like

@test surface_fluxes(u, outward_direction, equations)  ≈ boundary_condition_do_nothing(u, outward_direction, x, t,
                                                    surface_fluxes,
                                                    equations)

@ranocha
Copy link
Member

ranocha commented Feb 7, 2025

We should not do that since that's type piracy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants