-
Notifications
You must be signed in to change notification settings - Fork 38
bugfix: min_steady_timesteps in lbpm_color_simulator #107
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
jeremyfirst22
wants to merge
1
commit into
OPM:dev
Choose a base branch
from
jeremyfirst22:bugfix-min-steady-timesteps
base: dev
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.
Open
Changes from all commits
Commits
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
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.
why add
analysis_intervalhere? The previous logic is simply comparing the relative change in the capillary number. This change will alter the interpretation oftoleranceUh oh!
There was an error while loading. Please reload this page.
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.
@JamesEMcClure I added the
analysis_intervalhere to make thetolerancerelative to each simulation step, and independent of the number of steps between evaluating the capillary number.i.e., if the simulation is not changing by greater than 1% per step, we consider the simulation converged. Not if the simulation is changing by 1% per analysis interval.
The idea was that you should be free to change the
analysis_intervalwithout having to adjust thetolerancein kind to achieve the same results.I agree this changes the interpretation of
tolerance, but since theCa_previouswas never updated anyway (i.e.,tolerancewas never used), I figured I was free to update the interpretation. But 1% per step is an extremely loose default. If you'd like, I will update the default to be consistent with the previous interpretation (1% / 1000 steps)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.
@JamesEMcClure I went ahead and make this change, and updated the default
toleranceto 1e-5 so that is consistent with the old interpretation of the default (i..e, 0.01 over the default 1000 steps).Let me know if you have any other comments on this one.