-
Notifications
You must be signed in to change notification settings - Fork 126
Add unstable_check
for custom SSP method
#2445
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
bennibolm
wants to merge
8
commits into
trixi-framework:main
Choose a base branch
from
bennibolm:SSPmethod-unstablecheck
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+60
−33
Open
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
a983dbe
Add `unstable_check` for custom SSP method
bennibolm c5dc938
Merge branch 'main' into SSPmethod-unstablecheck
bennibolm 3638b8d
Implement suggestion
bennibolm f81a2fb
Use allreduce!
bennibolm 9218021
Add unstable_check as parameter of solve()
bennibolm f5f262f
Merge branch 'main' into SSPmethod-unstablecheck
DanielDoehring aec4988
Merge branch 'main' into SSPmethod-unstablecheck
ranocha 6e1fbb7
Merge branch 'main' into SSPmethod-unstablecheck
bennibolm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
If we export it, it becomes part of our public API (although it is not documented...). However, I do not think this is a good idea right now since it can be easily confused with
ode_unstable_check
. I see two options right now: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.
Okay, that's true.
I'm completely fine with the first option. But how would that look like in your opinion? Rename it to something like
unstable_check_SSPRK
, have an optional parameterunstable_check = nothing
forsolve()
of the custom time integrators and addunstable_check = unstable_check_SSRK
to every elixir, where it's needed?Or really removing the parameter
unstable_check
from the solve function and hardcode it into the SSPRK method?