Update TimeStepper to enable fixed point iterations #14
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
Previously, we took the timestep from OpenFOAM and used that to set dt on the MOOSE mesh. This makes sense, but to get MOOSE's Picard iterations working, a multiapp, we need to be able to set the OpenFOAM timestep from the MOOSE solve.
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.
Summary
Updates the
FoamTimeStepperto take time parameters from MOOSE and set them on the OpenFOAM problem. This is in contrast to what we previously had, where the time step and limits were taken from OpenFOAM and set on the MOOSE solve.This change is mainly to enable the use of fixed point iterations for multiapps, where MOOSE may want to change the time/time-step and the OpenFOAM solve needs to be updated to reflect this.
Checklist