-
Notifications
You must be signed in to change notification settings - Fork 239
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
2-fluid drag implicit scheme #428
Merged
danieljprice
merged 34 commits into
danieljprice:master
from
StephaneMichoulier:implicitforce
Jun 14, 2023
Merged
2-fluid drag implicit scheme #428
danieljprice
merged 34 commits into
danieljprice:master
from
StephaneMichoulier:implicitforce
Jun 14, 2023
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type of PR:
modification to existing code
Description:
Add the 2-fluid drag implicit scheme in phantom.
Note: Independent timesteps are not working currently. Therefore, it is not
faster than the explicit scheme with independent timesteps.
The option is currently hidden from users until a solution is found
Testing:
Dustybox, dustywaves, dustysettle and dustyshocks
Did you run the bots? yes
Did you update relevant documentation in the docs directory? yes