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

WIP: Enable save solution with time intervals for SimpleIntegratirSSP #7

Closed
wants to merge 17 commits into from

Conversation

amrueda
Copy link
Owner

@amrueda amrueda commented Oct 18, 2023

No description provided.

@github-actions
Copy link

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.

@coveralls
Copy link

coveralls commented Dec 12, 2023

Pull Request Test Coverage Report for Build 7200650353

  • 246 of 253 (97.23%) changed or added relevant lines in 34 files are covered.
  • 2 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.008%) to 96.245%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/equations/ideal_glm_mhd_1d.jl 5 6 83.33%
src/solvers/dgsem_unstructured/sort_boundary_conditions.jl 0 1 0.0%
src/visualization/recipes_plots.jl 0 1 0.0%
src/solvers/fdsbp_unstructured/fdsbp_2d.jl 94 96 97.92%
src/time_integration/methods_SSP.jl 23 25 92.0%
Files with Coverage Reduction New Missed Lines %
src/callbacks_step/save_solution.jl 1 90.0%
src/solvers/dgsem_unstructured/sort_boundary_conditions.jl 1 91.11%
Totals Coverage Status
Change from base Build 6943953828: 0.008%
Covered Lines: 33754
Relevant Lines: 35071

💛 - Coveralls

@amrueda amrueda closed this Dec 6, 2024
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.

3 participants