Skip to content

[PL/TRM] Hold data in tuples, not structs

Christoph Lehmann requested to merge chleh/ogs:trm-data-in-tuples into master

Follow-up of !4916 (merged)

In this MR

  1. Constitutive data of the TRM process will be organized in tuples instead of structs.
  2. The eval() machinery of !4916 (merged) will be used to invoke the constitutive models in TRM.
    In most of the commits in this MR I use apply() instead of eval(), because I renamed the method lately, when preparing !4916 (merged). Sorry for the inconvenience.
  3. On the fly some small changes are done:
    • Unification of stateless mechanics data among both TRM constitutive settings.
    • Separation of mechanical strain data.
      This also enables IP/extrapolated I/O for mechanical strain! (In TRM currently not effective for restart, because explicitely overwritten in setInitialConditionsConcrete().)
    • More convenient handling of previous states with PrevStateOf<>.

The refactorings (1.) and (2.) both span multiple commits, each of which do pretty similar things.
Theoretically, this MR could be split into two. One for (1.) and (3.) and one for (2.), but I thought it might be more efficient to have everything in one MR, especially since (2.) does not add very much. I hope you agree.

TODO

  • unit tests for PrevStateOf<>
  1. Feature description was added to the changelog
  2. Tests covering your feature were added?
  3. Any new feature or behaviour change was documented?
Edited by Christoph Lehmann

Merge request reports