Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GeoMechanicsApplication] Geo/time step loop #11677

Merged
merged 26 commits into from
Oct 16, 2023
Merged

Conversation

WPK4FEM
Copy link
Contributor

@WPK4FEM WPK4FEM commented Oct 12, 2023

TIme loop executor that performs the stepping loop and for each step the cycle loop using TimeStepExecutor and StrategyWrapper..

Contains:

  • Unit tests for all developed components
  • CloneTimeStep for claiming variable space at start of step
  • RestorePosistionsAndDOFVectorToStartOfStep for enabeling the cycling mechanism
  • SaveTotalDsplacementFieldAtStartOfStage and AccumulateTotalDisplacementField for keeping track of displacement accumulation over stages
  • OutputProces to enable output at the end of each step

WPK4FEM and others added 16 commits October 9, 2023 13:19
…ormedStatesAfterRunning. Removed template argument from TimeLoopExecutor class.
…dded test for running and terminating a loop with a non-converging solver strategy.
…of the time passed. Added a test on end time after N steps.
…ed ). Passed solver strategy to time step executor.
…crementor with a fixed number of cycles per step. Added RunCycle and RunCycleLoop to the time loop executor.
Also added the `explicit` keyword to a single-argument constructor.
Given a prescribed time incrementor that keeps four time increments and
a solver strategy that always converges, we expect to get four converged
time step end states, where each one just required a single cycle. Also
the time values are validated for each time step end state.

Furthermore added a helper function to build a converged end state.
Now that the strategy wrapper is a member of the time loop executor, we
can set the end time and the time increment in their "global" variables.
Internally, this is done via the model part. The reason we set these
variables explicitly is that processes may rely on having this
information available.
Extended the API of class `StrategyWrapper` such that we can increment
the step number and get the step number upon request.
…for restoring to the initial situation of a step to enable cycling of the step.
…entField implemented and unit tests provided.
@WPK4FEM WPK4FEM added the GeoMechanics Issues related to the GeoMechanicsApplication label Oct 12, 2023
@WPK4FEM WPK4FEM self-assigned this Oct 12, 2023
Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice readable and clean code (and of course well-tested)!

I think there is the possibility for some more clean-up of the tests and there are some discussion points about the structure.

@WPK4FEM WPK4FEM linked an issue Oct 12, 2023 that may be closed by this pull request

class Process;

class TimeLoopExecutorInterface{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@avdg81 We discussed we didn't want Interface in the name, but @WPK4FEM and I could not think of a suitable pair of names for the interface + implementation of the time loop executor. If you have a suggestion, please let us know!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I don't have a better suggestion either. Let's keep the class names as they are now.

@WPK4FEM WPK4FEM requested a review from rfaasse October 13, 2023 09:27
Copy link
Contributor

@avdg81 avdg81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clear and clean code. Good job! I have several comments, most of which are very minor.


class Process;

class TimeLoopExecutorInterface{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I don't have a better suggestion either. Let's keep the class names as they are now.

@WPK4FEM WPK4FEM requested a review from avdg81 October 16, 2023 06:30
Copy link
Contributor

@rfaasse rfaasse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for implementing the changes and the collaboration on this one! It turned out nicely, so from my side, it's ready to be merged

@WPK4FEM WPK4FEM merged commit f71b2f6 into master Oct 16, 2023
9 of 11 checks passed
@WPK4FEM WPK4FEM deleted the geo/time-step-loop branch October 16, 2023 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GeoMechanics Issues related to the GeoMechanicsApplication
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[GeoMechanicsApplication] Add a class for running a time loop
3 participants