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

Geo/add time step executor #11649

Merged
merged 18 commits into from
Oct 5, 2023
Merged

Geo/add time step executor #11649

merged 18 commits into from
Oct 5, 2023

Conversation

WPK4FEM
Copy link
Contributor

@WPK4FEM WPK4FEM commented Oct 3, 2023

An executor to perform a single time step for GeoMechanical Analysis

It uses:

  • a solving strategy
  • a list of process references

and gives back

  • a time step end state containing the time, the convergence state and the number of iterations used.

7 unit tests for checking basic behavior are added.

@WPK4FEM WPK4FEM added the GeoMechanics Issues related to the GeoMechanicsApplication label Oct 3, 2023
@WPK4FEM WPK4FEM requested review from avdg81 and rfaasse October 3, 2023 08:44
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.

Looks very clear to me! I have some suggestions for improvements, but in general it looks good to me!

@rfaasse rfaasse self-requested a review October 4, 2023 07:28
rfaasse
rfaasse previously approved these changes Oct 4, 2023
@rfaasse rfaasse self-requested a review October 4, 2023 07:28
@WPK4FEM WPK4FEM force-pushed the geo/add-time-step-executor branch from e4e2ecf to cb74f2c Compare October 4, 2023 07:55
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.

This looks really nice Wijtze Pieter! I have several minor remarks which may help to make the code even more elegant. See for yourself whether my comments make sense. Thanks!

avdg81 and others added 16 commits October 4, 2023 13:45
- For now, running a time step only returns a non-converged exit status.
- Added a unit test for this class.
When the time step executer is requested to run, it returns whether the
solving strategy converged or not.
When `Run()` is called the executer visits all processes and initializes
the solution step as well as finalizes it.
- Extracted the solver's convergence state from the class template
  `TimeStepExecuter`, since there was one definition for each template
  instantiation. That was rather inconvenient.
- Added a new data structure that keeps the state at the end of a time
  step. It encompasses the convergence state as well as the number of
  nonlinear iterations.
In this way, we will know to which time step the other data applies.
@WPK4FEM WPK4FEM force-pushed the geo/add-time-step-executor branch from cb74f2c to 0fcb137 Compare October 4, 2023 11:55
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.

I think this one is ready to go.

@avdg81 avdg81 merged commit 970d762 into master Oct 5, 2023
@avdg81 avdg81 deleted the geo/add-time-step-executor branch October 5, 2023 08:28
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 carrying out a single time step
3 participants