-
Notifications
You must be signed in to change notification settings - Fork 115
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
Convert parameter to elixir for 2D Euler tests #229
Conversation
I am getting the same weird amr error behaviour as @gregorgassner for #230 . The blob + amr test keeps failing for this reason |
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.
Looks good in general, thanks!
I just realized that some Euler examples use split_shockcapturing
instead of just shockcapturing
(what we use for most other examples). Could you please rename the corresponding .toml
and .jl
files?
Okay, I can rename such cases. Basically because shock capturing => split form in our current form, but future shock capturing strategies may not use the split form. Should I also add Update: I realized looking at the naming that the euler + gravity blast wave should also have |
renaming did not commit the right amr_callback
Codecov Report
@@ Coverage Diff @@
## dev #229 +/- ##
=======================================
Coverage 89.59% 89.59%
=======================================
Files 60 60
Lines 10485 10485
=======================================
Hits 9394 9394
Misses 1091 1091
Continue to review full report at Codecov.
|
For me, just using
For me, just using
I don't think we need |
We discussed the naming issue at yesterday's meeting. Our conclusion was that we stick to |
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.
A few minor comments, but the whole looks good to me...
Okay, I renamed the files of the elixirs consistently now (I think). @sloede can you double check that I did not miss any? I will update the |
I created #244 for this to track the discussion on naming the files. I think optimally we should figure out #244 and then put the changes in here, but if your strapped for time, just finish this PR and we'll figure out #244 next week. |
I am strapped for time ;) . So should I not worry about the |
Yes. |
Addresses more files in #219