Visco Modified CamClay model: Triaxial Driver versus Semi-Analytical Solution
This example uses the Triaxial Driver to simulate a visco-elasto-plastic oedometric compression test of a Visco Modified CamClay solid. Oedometric condition with zero lateral strain together with loading/unloading axial strain periods are imposed. Semi-analytical results for the mean and shear stress variations and can be established, considering the Perzyna approach, for the imposed oedometric boundary conditions as (Runesson et al. 1999) :
where and are elastic bulk and shear moduli, is the plastic potential and is the visco-plastic multiplier that can be approximated by:
in which is the time increment, is the relaxation time, is the stress function defining the visco-plastic yield surface and is the hardening rate defined by:
These solutions are implemented in a Python script associated to this example for verifying GEOS results.
This validation example uses two GEOS xml files that are located at:
It also uses a set of table files located at:
A Python script for the semi-analytical solutions presented above as well as for post-processing the GEOS results is provided at:
For this example, we focus on the
Task and the
The imposed axial strain loading/unloading periods, the lateral zero strain, and the initial stress are defined in the
Task block as:
The elasto-visco-plastic parameters are defined as:
All constitutive parameters such as density, viscosity, and the bulk and shear moduli are specified in the International System of Units.
A comparison between GEOS results and semi-analytical results
The simulation results are saved in a text file, named
ViscoModifiedCamClayResults.txt. A comparison between the results given by the TriaxialDriver solver in GEOS and the semi-analytical results presented above is shown below. The discrepancy between these results may due to the difference between the Duvaut-Lions approach and the Perzyna approach for time dependant behavior when applying for the Modified CamClay model as discussed by Runesson et al. (1999).
To go further
Feedback on this example
For any feedback on this example, please submit a GitHub issue on the project’s GitHub page.