Let the problem cap the next time step - #7252
Open
hnil wants to merge 1 commit into
Open
Conversation
…me step New virtual FvBaseProblem::maxNextTimeStepSize() (default: no limit). The adaptive-time-stepping tuning updater seeds its suggested next step from this problem limit, so a problem (e.g. a geomechanical fracture model that throttles growth per step) can cap the following sub step without touching the TUNING machinery. Schedule-driven TUNING values are combined with the problem limit as before. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Adds a defaulted virtual
FvBaseProblem::maxNextTimeStepSize()(default: no limit) and combines it with the TUNING-derived suggestion. No behaviour change unless a problem overrides it; opm-flowgeomechanics uses it to throttle fracture growth per step.