Skip to content

Let the problem cap the next time step - #7252

Open
hnil wants to merge 1 commit into
OPM:masterfrom
hnil:pr/problem-max-next-timestep
Open

Let the problem cap the next time step#7252
hnil wants to merge 1 commit into
OPM:masterfrom
hnil:pr/problem-max-next-timestep

Conversation

@hnil

@hnil hnil commented Jul 31, 2026

Copy link
Copy Markdown
Member

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.

…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>
@hnil hnil added the manual:enhancement This is an enhancement/improvent that needs to be documented in the manual label Jul 31, 2026
@hnil
hnil requested a review from totto82 July 31, 2026 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

manual:enhancement This is an enhancement/improvent that needs to be documented in the manual

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant