You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes we want to benefit from the behavior of multiple time steppers, but save for re-implementing what s missing (for example IterationAdaptiveDT did that), you cant mix & match
allow timestepper action to create multiple timesteppers (force the selection of one if multiple)
add a composition rule time stepper that can call the others
max step, min step, average of steppers' step, times to hit absolutely (or with a tolerance?), periods of validity for each composed stepper etc
The periods of validity could be a parameter of each stepper instead
This would be a lot less intrusive than the Stepper system designed by @friedmud in #8127
Impact
Reaching full & final capability for time steppers?
The text was updated successfully, but these errors were encountered:
Reason
Sometimes we want to benefit from the behavior of multiple time steppers, but save for re-implementing what s missing (for example IterationAdaptiveDT did that), you cant mix & match
Tied to #8127 and #3858
Design
max step, min step, average of steppers' step, times to hit absolutely (or with a tolerance?), periods of validity for each composed stepper etc
The periods of validity could be a parameter of each stepper instead
This would be a lot less intrusive than the Stepper system designed by @friedmud in #8127
Impact
Reaching full & final capability for time steppers?
The text was updated successfully, but these errors were encountered: