-
Notifications
You must be signed in to change notification settings - Fork 113
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
Make Taal pass Taam tests #267
Conversation
…t*, and not *per direction*)
These use constant velocities like |
Thanks, this was the case - I had forgotten to update the CFLs. Fixed in d6ad86f |
I've ported the new AMR controller from #266 to |
Resolve CFL magic
…t, last file standing!
Co-authored-by: Hendrik Ranocha <ranocha@users.noreply.github.com>
Port & mix last 3D elixirs
test/test_examples_2d.jl
Outdated
@testset "taal-confirmed elixir_advection_timeintegration.jl" begin | ||
test_trixi_include(joinpath(EXAMPLES_DIR, "elixir_advection_timeintegration.jl"), | ||
@test_trixi_include(joinpath(EXAMPLES_DIR, "elixir_advection_timeintegration.jl"), | ||
l2 = [9.144681765639205e-6], | ||
linf = [6.437440532547356e-5]) | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When sorting the tests, I would like to make this test without modifications the first one and check the other time integration methods afterwards.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
The idea for this PR is to make Taal pass all Taam tests. That is, we use the same number of analysis nodes in Taal as for Taam, and we temporarily switch to the old time step calculation scheme. Then, we confirm that Taal passes all Taam tests by exactly copying the Taam error norms.
Once we created elixirs for all Taam tests, i.e., formally have at least the same level of coverage (feature-wise) as we did before, we can decide to switch back to the new time step calculation scheme (and possibly also change the number of analysis nodes again).
While this might result in more work (since we have to re-run all tests in the end to get new reference values for Taal after we switch the time step calculation), it gives us the guarantee that Taal produces exactly (up to machine precision) the same results as for Taam for all tests.
To ensure that no test is accidentally left behind, all
@testset
names in Taal and Taam are prefixed bytaal-check-me
. If, for a given test, the reference values from Taam are copied to the Taal test file and it is confirmed that the results match, this should be changed totaal-confirmed
. In the end, we should only have tests withtaal-confirmed
in all test files (at least for the parameter file/elixir tests), and can delete it when we switch the time step calculation scheme.Notes
Code that needs to be updated/adapted after all tests are synchronized is marked by
# FIXME Taal restore after Taam sync
TODO
master
master
todev
dev
to here?In that case: Also fix
calcflux
(see below), since references will change anyways...examples/3d/elixir_euler_blob_amr.jl
once PositivityPreservingLimiterZhangShu #274 is merged.After action cleanup
calcflux
(c6f4cf4), this will need done for 1D, 2D, and 3Dc_h
for MHD