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

More efficient PERK implementation #2180

Merged
merged 14 commits into from
Dec 1, 2024

Conversation

DanielDoehring
Copy link
Contributor

Essentially this bundles some functions and reduces the number of assignments at the expense of repeated arithmetic operations.

@warisa-r can you take a first look?

@DanielDoehring DanielDoehring added performance We are greedy refactoring Refactoring code without functional changes labels Nov 27, 2024
Copy link
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.

Copy link

codecov bot commented Nov 27, 2024

Codecov Report

Attention: Patch coverage is 94.64286% with 3 lines in your changes missing coverage. Please review.

Project coverage is 96.39%. Comparing base (824f7a8) to head (51a2103).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...xplicit_runge_kutta/paired_explicit_runge_kutta.jl 76.92% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2180      +/-   ##
==========================================
+ Coverage   96.37%   96.39%   +0.02%     
==========================================
  Files         483      483              
  Lines       38333    38320      -13     
==========================================
- Hits        36943    36938       -5     
+ Misses       1390     1382       -8     
Flag Coverage Δ
unittests 96.39% <94.64%> (+0.02%) ⬆️

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.

Copy link
Contributor

@warisa-r warisa-r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new functions look more compact and are valid for s = e, the only relevant case for single methods as you mentioned before. However, should we also document that standalone methods only handle s = e? #2146

@DanielDoehring
Copy link
Contributor Author

The new functions look more compact and are valid for s = e, the only relevant case for single methods as you mentioned before. However, should we also document that standalone methods only handle s = e? #2146

Yes, if this not mentioned yet explicitly we should do that 👍

@warisa-r
Copy link
Contributor

The new functions look more compact and are valid for s = e, the only relevant case for single methods as you mentioned before. However, should we also document that standalone methods only handle s = e? #2146

Yes, if this not mentioned yet explicitly we should do that 👍

Done!

Copy link
Member

@JoshuaLampert JoshuaLampert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just have a few small questions.

Copy link
Member

@JoshuaLampert JoshuaLampert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@DanielDoehring DanielDoehring enabled auto-merge (squash) December 1, 2024 14:59
@DanielDoehring DanielDoehring merged commit 863795e into trixi-framework:main Dec 1, 2024
36 of 37 checks passed
@DanielDoehring DanielDoehring deleted the MoreEfficientPERK branch December 1, 2024 16:23
@torrilhon
Copy link
Contributor

Please note #1880 ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance We are greedy refactoring Refactoring code without functional changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants