Mandel’s Problem

Context

In this example, we use the coupled solvers in GEOS to solve Mandel’s 2D consolidation problem, a classic benchmark in poroelasticity. The analytical solution (Cheng and Detournay, 1988) is employed to verify the accuracy of the modeling predictions on induced pore pressure and the corresponding settlement. In this example, the TimeHistory function and a Python script are used to output and post-process multi-dimensional data (pore pressure and displacement field).

Input file

This example uses no external input files and everything required is contained within two GEOS input files located at:

inputFiles/poromechanics/PoroElastic_Mandel_base.xml
inputFiles/poromechanics/PoroElastic_Mandel_benchmark_fim.xml

Description of the case

We simulate the consolidation of a poroelastic slab between two rigid and impermeable plates subjected to a constant normal force. The slab is assumed to be fully saturated, homogeneous, isotropic, and infinitely long in the y-direction. We apply a uniform compressive load in the vertical direction. This force leads to a change of pore pressure and mechanical deformations of the sample, evolving with time due to fluid diffusion and coupling effects. The numerical model represents a plane strain deformation and lateral drainage without confinement, showing only a quarter of the computational domain in the x-z plane (the rest follows by symmetry).

../../../../../../_images/sketch4.png

Fig. 75 Sketch of the problem

In this example, we set up and solve a poroelastic model to obtain the temporal and spatial solutions of pore pressure (p(x,z,t)) and displacement field (u_z(x,z,t)) for Mandel’s problem. These modeling predictions are validated against corresponding analytical solution (Cheng and Detournay, 1988).

p(x,z,t) = 2 p_0 \sum_{n=1}^{\infty}
         \frac{ \text{sin} \alpha_{n} } { \alpha_{n} - {\text{sin} \alpha_{n}} {\text{cos} \alpha_{n}} } \left( \text{cos} {\frac{\alpha_{n} x}{a}} - \text{cos} \alpha_{n} \right)
         \text{exp} \left( -\frac{ {\alpha_{n}}^2 c t}{a^2} \right)

u_z(x,z,t) = \left[ -\frac{F \left( 1 - \nu \right)}{2Ga} + \frac{F \left( 1 - \nu_{u} \right)}{Ga} \sum_{n=1}^{\infty} \frac{  {\text{sin} \alpha_{n}} {\text{cos} \alpha_{n}} } { \alpha_{n} - {\text{sin} \alpha_{n}} {\text{cos} \alpha_{n}} } \text{exp} \left( -\frac{{\alpha_{n}}^2 c t}{a^2} \right) \right] z

with \alpha_{n} denoting the positive roots of the following equation:

\text{tan} \alpha_{n} = \frac{1- \nu}{\nu_{u}-\nu} \alpha_{n}

Upon sudden application of the vertical load, the instantaneous overpressure (p_0(x,z)) and settlement (u_{z,0}(x,z) and u_{x,0}(x,z)) across the sample are derived from the Skempton effect:

p_0(x,z) = \frac{1}{3a} B \left( 1 + \nu_{u} \right) F

u_{z,0}(x,z) = -\frac{F \left( 1 - \nu_{u} \right)}{2G} \frac{z}{a}

u_{x,0}(x,z) = \frac{F \nu_{u} }{2G} \frac{x}{a}

where \nu and \nu_{u} are the drained and undrained Poisson’s ratio respectively, c is the consolidation coefficient, B is Skempton’s coefficient, G is the shear modulus, and F is the applied force.

For this example, we focus on the Mesh, the Constitutive, and the FieldSpecifications tags.

Mesh

The following figure shows the mesh used in this problem.

../../../../../../_images/mesh8.png

Fig. 76 Generated mesh

This mesh was created using the internal mesh generator as parametrized in the InternalMesh XML tag. The structured mesh contains 20 x 1 x 20 eight-node brick elements in the x, y, and z directions respectively. Such eight-node hexahedral elements are defined as C3D8 elementTypes, and their collection forms a mesh with one group of cell blocks named here cb1.

  <Mesh>
    <InternalMesh
      name="mesh1"
      elementTypes="{ C3D8 }"
      xCoords="{ 0.0, 1.0 }"
      yCoords="{ 0.0, 0.1 }"
      zCoords="{ 0.0, 1.0 }"
      nx="{ 20 }"
      ny="{ 1 }"
      nz="{ 20 }"
      cellBlockNames="{ cb1 }"/>
  </Mesh>

Solid mechanics solver

GEOS is a multi-physics platform. Different combinations of physics solvers available in the code can be applied in different regions of the domain and be functional at different stages of the simulation. The Solvers tag in the XML file is used to list and parameterize these solvers.

To specify a coupling between two different solvers, we define and characterize each single-physics solver separately. Then, we customize a coupling solver between these single-physics solvers as an additional solver. This approach allows for generality and flexibility in constructing multi-physics solvers. The order of specifying these solvers is not restricted in GEOS. Note that end-users should give each single-physics solver a meaningful and distinct name, as GEOS will recognize these single-physics solvers based on their customized names and create user-expected coupling.

As demonstrated in this example, to setup a poromechanical coupling, we need to define three different solvers in the XML file:

  • the mechanics solver, a solver of type SolidMechanicsLagrangianSSLE called here lagsolve (more information here: Solid Mechanics Solver),

  • the single-phase flow solver, a solver of type SinglePhaseFVM called here SinglePhaseFlow (more information on these solvers at Singlephase Flow Solver),

  • the coupling solver (SinglePhasePoromechanics) that will bind the two single-physics solvers above, which is named as poroSolve (more information at Poromechanics Solver).

The two single-physics solvers are parameterized as explained in their corresponding documentation pages. We focus on the coupling solver in this example. The solver poroSolve uses a set of attributes that specifically describe the coupling process within a poromechanical framework. For instance, we must point this solver to the designated fluid solver (here: SinglePhaseFlow) and solid solver (here: lagsolve). These solvers interact through the porousMaterialNames="{ shale }" with all the constitutive models. We specify the discretization method (FE1, defined in the NumericalMethods section), and the target regions (here, we only have one, Domain). More parameters are required to characterize a coupling procedure (more information at Poromechanics Solver). In this way, the two single-physics solvers will be simultaneously called and executed for solving Mandel’s problem here.

Constitutive laws

For this problem, we simulate the poroelastic deformation of a slab under uniaxial compression. A homogeneous and isotropic domain with one solid material is assumed, and its mechanical properties and associated fluid rheology are specified in the Constitutive section. PorousElasticIsotropic model is used to describe the mechanical behavior of shaleSolid when subjected to loading. The single-phase fluid model CompressibleSinglePhaseFluid is selected to simulate the response of water upon consolidation.

  <Constitutive>
    <PorousElasticIsotropic
      name="shale"
      solidModelName="shaleSolid"
      porosityModelName="shalePorosity"
      permeabilityModelName="shalePerm"/>

    <ElasticIsotropic
      name="shaleSolid"
      defaultDensity="0"
      defaultBulkModulus="6.6667e7"
      defaultShearModulus="4.0e7"/>

    <BiotPorosity
      name="shalePorosity"
      grainBulkModulus="1.0e27"
      defaultReferencePorosity="0.375"/>

    <ConstantPermeability
      name="shalePerm"
      permeabilityComponents="{ 1.0e-12, 0.0, 1.0e-12 }"/>

    <CompressibleSinglePhaseFluid
      name="water"
      defaultDensity="1000"
      defaultViscosity="0.001"
      referencePressure="0.000"
      referenceDensity="1"
      compressibility="4.4e-10"
      referenceViscosity="0.001"
      viscosibility="0.0"/>
  </Constitutive>

All constitutive parameters such as density, viscosity, bulk modulus, and shear modulus are specified in the International System of Units.

Time history function

In the Tasks section, PackCollection tasks are defined to collect time history information from fields. Either the entire field or specified named sets of indices in the field can be collected. In this example, pressureCollection and displacementCollection tasks are specified to output the time history of pore pressure fieldName="pressure" and displacement field fieldName="totalDisplacement" across the computational domain.

  <Tasks>
    <PackCollection
      name="pressureCollection"
      objectPath="ElementRegions/Domain/cb1"
      fieldName="pressure"/>

    <PackCollection
      name="displacementCollection"
      objectPath="nodeManager" 
      fieldName="totalDisplacement"/>  
  </Tasks>

These two tasks are triggered using the Event manager with a PeriodicEvent defined for these recurring tasks. GEOS writes two files named after the string defined in the filename keyword and formatted as HDF5 files (displacement_history.hdf5 and pressure_history.hdf5). The TimeHistory file contains the collected time history information from each specified time history collector. This information includes datasets for the simulation time, element center, and the time history information. A Python script is prepared to read and plot any specified subset of the time history data for verification and visualization.

Initial and boundary conditions

Next, we specify two fields:

  • The initial value (the displacements, effective stress, and pore pressure have to be initialized, corresponding to the undrained response),

  • The boundary conditions (the vertical displacement applied at the loaded boundary and the constraints of the outer boundaries have to be set).

In this example, the analytical z-displacement is applied at the top surface (zpos) of computational domain to enforce the rigid plate condition. The lateral surface (xpos) is traction-free and allows drainage. The remaining parts of the outer boundaries are subjected to roller constraints. These boundary conditions are set up through the FieldSpecifications section.

  <FieldSpecifications>
    <FieldSpecification
      name="initialPressure"
      initialCondition="1"
      setNames="{ all }"
      objectPath="ElementRegions/Domain/cb1"
      fieldName="pressure"
      scale="4934.86"/>

    <FieldSpecification
      name="initial_sigma_x"
      initialCondition="1"
      setNames="{ all }"
      objectPath="ElementRegions"
      fieldName="shaleSolid_stress"
      component="0"
      scale="4934.86"/>
    <FieldSpecification
      name="initial_sigma_y"
      initialCondition="1"
      setNames="{ all }"
      objectPath="ElementRegions"
      fieldName="shaleSolid_stress"
      component="1"
      scale="4934.86"/>
    <FieldSpecification
      name="initial_sigma_z"
      initialCondition="1"
      setNames="{ all }"
      objectPath="ElementRegions"
      fieldName="shaleSolid_stress"
      component="2"
      scale="4934.86"/>
    
    <FieldSpecification
      name="xInitialDisplacement"
      initialCondition="1"
      setNames="{ all }"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="0"
      scale="1.0"
      functionName="initialUxFunc"/>

    <FieldSpecification
      name="yInitialDisplacement"
      initialCondition="1"
      setNames="{ all }"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="1"
      scale="0.0"/>

    <FieldSpecification
      name="zInitialDisplacement"
      initialCondition="1"
      setNames="{ all }"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="2"
      scale="1.0"
      functionName="initialUzFunc"/>

    <FieldSpecification
      name="xnegconstraint"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="0"
      scale="0.0"
      setNames="{ xneg }"/>

    <FieldSpecification
      name="yconstraint"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="1"
      scale="0.0"
      setNames="{ yneg, ypos }"/>

    <FieldSpecification
      name="zconstraint"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="2"
      scale="0.0"
      setNames="{ zneg }"/>

    <FieldSpecification
      name="NormalDisplacement"
      objectPath="nodeManager"
      fieldName="totalDisplacement"
      component="2"
      scale="-1.0e-5"
      setNames="{ zpos }"
      functionName="loadFunction"/>
  
    <FieldSpecification
      name="boundaryPressure"
      objectPath="faceManager"
      fieldName="pressure"
      scale="0.0"
      setNames="{ xpos }"/>
  </FieldSpecifications>

The parameters used in the simulation are summarized in the following table. Note that traction has a negative value, due to the negative sign convention for compressive stresses in GEOS.

Symbol

Parameter

Unit

Value

K

Bulk Modulus

[MPa]

66.667

G

Shear Modulus

[MPa]

40.0

F

Force per Unit Length

[N/m]

-104

\phi

Porosity

[-]

0.375

K_s

Grain Bulk Modulus

[Pa]

1027

\rho_f

Fluid density

[kg/m3]

103

c_f

Fluid compressibility

[Pa-1]

4.4x10-10

\kappa

Permeability

[m2]

10-12

\mu

Fluid viscosity

[Pa s]

10-3

2a

Slab Length

[m]

2.0

2b

Slab Height

[m]

2.0

Inspecting results

We request VTK-format output files and use Paraview to visualize the results. The following figure shows the distribution of pore pressure (p(x,z,t)) at t=10 s within the computational domain.

../../../../../../_images/pressure2.png

Fig. 77 Simulation result of pore pressure at t=10 s

The next figure shows the distribution of vertical displacement (u_z(x,z,t)) at t=10 s.

../../../../../../_images/disp.png

Fig. 78 Simulation result of vertical displacement at t=10 s

The figure below compares the results from GEOS (marks) and the corresponding analytical solution (lines) for the pore pressure along the x-direction and vertical displacement along the z-direction. GEOS reliably captures the short-term Mandel-Cryer effect and shows excellent agreement with the analytical solution at various times.

(Source code)

../../../../../../_images/mandelFigure.png

To go further

Feedback on this example

For any feedback on this example, please submit a GitHub issue on the project’s GitHub page.