Since #14, we set the time step in OpenFOAM via the MOOSE input file. This was part of trying to get Picard Iterations working (#21 also needs to be done before Picard Iterations will work).
This does however mean that we can't use OpenFOAM's adaptive time-stepping.
Subcycling should Just Work™️ with multiapps, as MOOSE can sync the parent app to the subapp as long as MOOSE is aware of the timesteps that OpenFOAM is taking.
I haven't quite worked out what the ideal behaviour for the time stepper is, so part of this issue is requirement gathering on what we need Hippo to do.
Outputs
A decision on the behaviour of the time stepper, recorded as a comment on this issue.
Description
Since #14, we set the time step in OpenFOAM via the MOOSE input file. This was part of trying to get Picard Iterations working (#21 also needs to be done before Picard Iterations will work).
This does however mean that we can't use OpenFOAM's adaptive time-stepping.
Subcycling should Just Work™️ with multiapps, as MOOSE can sync the parent app to the subapp as long as MOOSE is aware of the timesteps that OpenFOAM is taking.
I haven't quite worked out what the ideal behaviour for the time stepper is, so part of this issue is requirement gathering on what we need Hippo to do.
Outputs