Richard Faasse

@indigocoral @avdg81 I'll split this one such that this issue is only for creating the new policies and using them in the elements. The following two AC: - The interface...

Re-opening for the second (and last) PR for this issue

This needs to be crystallized out regarding the: 1. Extra `CalculateOnIntegrationPoints` functionality 2. Geometric stiffness matrix (KG) To be taken up by @avdg81 @WPK4FEM **Geometric stiffness contribution through matrix KG**...

Issues we want to tackle/discuss later: 1. We should discuss in the team if the majority prefers else on the same or next line with respect to the closing '}'...

@mcgicjn2 After an investigation and discussions with @indigocoral and @avdg81, this is the status of this issue. I noted some background info on the process and focused on our main...

### Proposal for GeoMechanics documentation generation for github pages As the geomechanics team, we are putting significant effort into creating comprehensive documentation for our code and tests. Although this documentation...

The investigation on the github pages is concluded, resulting in a proposal that can be discussed with CIMNE, when everyone from geomechanics is available and determine the follow-up steps. Therefore,...

After a brief look at the code with @WPK4FEM, it seems that the first order prediction could be done by adding the following piece of code to the `PredictVariablesForNode` function...

For the Predict of the instance of the second order variables (e.g. displacement/rotation), we probably need to change the formulation from: ``` rNode.FastGetSolutionStepValue(instance_component) = previous_variable + this->GetDeltaTime() * previous_first_time_derivative +...

While implementing the fix, as found in the description, we encountered the following issue (and failing test): It is **not** possible, after running a single stage (which initializes the elements...