Skip to content

Validate PlotData2D with LinearScalarAdvectionEquation3D #2377

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

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

Conversation

midsorbet
Copy link

I am trying to get started on #2335 based off of #2334 and #2340.

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
Contributor

@DanielDoehring DanielDoehring left a comment

Choose a reason for hiding this comment

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

Thanks for taking the initiative! I added a couple small first comments

Copy link

codecov bot commented Apr 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.95%. Comparing base (442fb2c) to head (532ca9f).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2377   +/-   ##
=======================================
  Coverage   96.95%   96.95%           
=======================================
  Files         504      504           
  Lines       41721    41721           
=======================================
  Hits        40448    40448           
  Misses       1273     1273           
Flag Coverage Δ
unittests 96.95% <ø> (ø)

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.

@midsorbet midsorbet requested a review from DanielDoehring May 5, 2025 04:14
@@ -691,6 +691,58 @@ end
end
end
end

@trixi_testset "PlotData2D" begin
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
@trixi_testset "PlotData2D" begin
@trixi_testset "PlotData1D and PlotData2D from 3D simulation" begin

Comment on lines +712 to +715
c = 1.0;
A = 0.5;
L = 2;
f = 1 / L;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
c = 1.0;
A = 0.5;
L = 2;
f = 1 / L;
c = 1.0
A = 0.5
L = 2
f = 1 / L

Comment on lines +726 to +727
sol = solve(ode, ode_solver; dt = 1.0, adaptive = false,
save_everystep = false)
Copy link
Member

Choose a reason for hiding this comment

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

Where is the ode defined?

Comment on lines +732 to +743
for i in eachindex(pd.x)
x = SVector(pd.x[i], pd.y[i], 0.0)
u = initial_condition(x, 0.1, equations)[1]
@test isapprox(pd.data[1][i], u, atol = 0.9)
end

pd = @inferred PlotData1D(ode.u0, ode.p, slice = :z)
for i in eachindex(pd.x)
x = SVector(0, 0, pd.x[i])
u = initial_condition(x, 0.1, equations)[1]
@test isapprox(pd.data[1], u, atol = 0.5)
end
Copy link
Member

Choose a reason for hiding this comment

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

The tolerances are quite large. Maybe the time integration method should be adapted to get better results?

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.

3 participants