docs: Tutorial examples of a vertical fault using the ALM solver by jhuang2601 · Pull Request #4082 · GEOS-DEV/GEOS

jhuang2601 · 2026-06-10T20:09:45Z

This PR

documents the analytical verification of ALM solver using a slipped vertical fault problem (shear slip for frictionless fault) in porous media
documents the analytical verification of ALM solver using a stable vertical fault problem (shear stress for friction and stable fault) in porous media
compares the results with both external (splitting fault with mesh doctor) and internal (internal surface generator) workflow
benchmarks the convergence of the relative 𝐿2-error with respect to mesh resolution
adds smoke tests for both workflows to the integratedTests

dkachuma

The two examples look quite similar. Can we possibly discuss them in the same context as a comparison?

dkachuma · 2026-06-15T17:29:34Z

+     <File name="ALM_verticalFault_base.xml"/>
+  </Included>
+
+  <Constitutive>


I would expect constitutive relations to be in the base file and shared between the smoke/bench and internal/external cases. Are they actually different across these models?

Fault mechanical properties (in constitutive block) are different for the case with stable and slipped fault.

dkachuma · 2026-06-15T17:31:52Z

+      name="mesh1"
+      useGlobalIds="0"
+      nodesetNames="{ faultNodes }"
+      file="../../MESH/verticalFault_ISG_benchmark.vtu"/>


In these cases I have expected the internal workflow to be able to use the "domain" mesh from the external workflow. Are there differences between verticalFault_ISG_benchmark.vtu and Domain_verticalFault_benchmark.vtu?

Yes
The attribute faultNodes must be included in verticalFault_ISG_benchmark.vtu to define the location and extent of the fault plane, which will be used by SurfaceGenerator.
Domain_verticalFault_benchmark.vtu contains duplicated nodes after splitting the mesh with mesh-doc.

dkachuma · 2026-06-15T17:41:07Z

+For more information on defining finite elements numerical schemes,
+please see the dedicated :ref:`FiniteElement` section.
+
+The finite volume method requires the specification of a discretization scheme.


Suggested change

The finite volume method requires the specification of a discretization scheme.

The finite volume method, for the flow solver, requires the specification of a discretization scheme.

bd713

Thanks, @jhuang2601.
Along the same lines as @dkachuma, we could probably also share the scripts (especially for the analytical solution).

bd713 · 2026-06-15T18:47:33Z

+    :start-after: <!-- SPHINX_MESH -->
+    :end-before: <!-- SPHINX_MESH_END -->
+
+The vtm file ``verticalFault_ESG_benchmark.vtm`` references two separate mesh files: the damain mesh ``Domain_verticalFault_benchmark.vtu`` and the fault mesh ``Fault_verticalFault_benchmark.vtu``, which are generated prior to running the GEOS simulation. The ``mesh doctor`` module provides a convenient way to prepare these meshes. For this case, functions ``generateFractures`` and ``generateGlobalIds`` are used (more information here: `mesh doctor  <https://geosx-geosx.readthedocs-hosted.com/projects/geosx-geospythonpackages/en/latest/mesh-doctor.html#>`__).


Suggested change

The vtm file ``verticalFault_ESG_benchmark.vtm`` references two separate mesh files: the damain mesh ``Domain_verticalFault_benchmark.vtu`` and the fault mesh ``Fault_verticalFault_benchmark.vtu``, which are generated prior to running the GEOS simulation. The ``mesh doctor`` module provides a convenient way to prepare these meshes. For this case, functions ``generateFractures`` and ``generateGlobalIds`` are used (more information here: `mesh doctor <https://geosx-geosx.readthedocs-hosted.com/projects/geosx-geospythonpackages/en/latest/mesh-doctor.html#>`__).

The vtm file ``verticalFault_ESG_benchmark.vtm`` references two separate mesh files: the domain mesh ``Domain_verticalFault_benchmark.vtu`` and the fault mesh ``Fault_verticalFault_benchmark.vtu``, which are generated prior to running the GEOS simulation. The ``mesh doctor`` module provides a convenient way to prepare these meshes. For this case, functions ``generateFractures`` and ``generateGlobalIds`` are used (more information here: `mesh doctor <https://geosx-geosx.readthedocs-hosted.com/projects/geosx-geospythonpackages/en/latest/mesh-doctor.html#>`__).

bd713 · 2026-06-15T18:52:40Z

+    :start-after: <!-- SPHINX_MESH -->
+    :end-before: <!-- SPHINX_MESH_END -->
+
+The vtm file ``verticalFault_ESG_benchmark.vtm`` references two separate mesh files: the damain mesh ``Domain_verticalFault_benchmark.vtu`` and the fault mesh ``Fault_verticalFault_benchmark.vtu``, which are generated prior to running the GEOS simulation. The ``mesh doctor`` module provides a convenient way to prepare these meshes. For this case, functions ``generateFractures`` and ``generateGlobalIds`` are used (more information here: `mesh doctor  <https://geosx-geosx.readthedocs-hosted.com/projects/geosx-geospythonpackages/en/latest/mesh-doctor.html#>`__).


Suggested change

The vtm file ``verticalFault_ESG_benchmark.vtm`` references two separate mesh files: the damain mesh ``Domain_verticalFault_benchmark.vtu`` and the fault mesh ``Fault_verticalFault_benchmark.vtu``, which are generated prior to running the GEOS simulation. The ``mesh doctor`` module provides a convenient way to prepare these meshes. For this case, functions ``generateFractures`` and ``generateGlobalIds`` are used (more information here: `mesh doctor <https://geosx-geosx.readthedocs-hosted.com/projects/geosx-geospythonpackages/en/latest/mesh-doctor.html#>`__).

The vtm file ``verticalFault_ESG_benchmark.vtm`` references two separate mesh files: the domain mesh ``Domain_verticalFault_benchmark.vtu`` and the fault mesh ``Fault_verticalFault_benchmark.vtu``, which are generated prior to running the GEOS simulation. The ``mesh doctor`` module provides a convenient way to prepare these meshes. For this case, functions ``generateFractures`` and ``generateGlobalIds`` are used (more information here: `mesh doctor <https://geosx-geosx.readthedocs-hosted.com/projects/geosx-geospythonpackages/en/latest/mesh-doctor.html#>`__).

jhuang2601 · 2026-06-18T19:38:20Z

The two examples look quite similar. Can we possibly discuss them in the same context as a comparison?

As different fault modes (static vs slip), fault mechanical properties and resulting parameters (stress vs displacementJump) are used for two cases, I have to separate them into two examples to avoid confusion.

jhuang2601 · 2026-06-18T19:51:59Z

Thanks, @jhuang2601. Along the same lines as @dkachuma, we could probably also share the scripts (especially for the analytical solution).

Yes, generate_analytical.py has already been pushed.

add xml files for benchmark examples

028502d

jhuang2601 self-assigned this Jun 10, 2026

jhuang2601 mentioned this pull request Jun 10, 2026

Tutorial example for fault slippage #2958

Closed

2 tasks

jhuang2601 added type: documentation EPIC - FF/Contact Contact mechanics labels Jun 10, 2026

jhuang2601 added 2 commits June 12, 2026 12:23

add rst file and script for slipped case

52cb65a

add rst file and script for stable case

5996f13

jhuang2601 marked this pull request as ready for review June 12, 2026 18:03

jhuang2601 requested review from OmarDuran, bd713, castelletto1, dkachuma, herve-gross, joshua-white and rrsettgast as code owners June 12, 2026 18:03

jhuang2601 and others added 5 commits June 12, 2026 13:03

Merge branch 'develop' into docs/jhuang/verticalFault

bf7ae59

update keyword for Coulomb

2528327

some fix

e467d0d

update python script

d79f70f

reduce fig size

228b114

jhuang2601 changed the title ~~docs: tutorial example with a vertical fault~~ docs: Tutorial examples of a vertical fault using the ALM solver Jun 12, 2026

jhuang2601 added ci: run CUDA builds Allows to triggers (costly) CUDA jobs ci: run integrated tests Allows to run the integrated tests in GEOS CI ci: run code coverage enables running of the code coverage CI jobs labels Jun 12, 2026

add smoke tests to integratedTests

b6ef64a

dkachuma reviewed Jun 15, 2026

View reviewed changes

bd713 reviewed Jun 15, 2026

View reviewed changes

herve-gross approved these changes Jun 15, 2026

View reviewed changes

address review comments

ab8b1fe

Merge branch 'develop' into docs/jhuang/verticalFault

71cf518

	The finite volume method requires the specification of a discretization scheme.
	The finite volume method, for the flow solver, requires the specification of a discretization scheme.

Uh oh!

Conversation

jhuang2601 commented Jun 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dkachuma left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

dkachuma Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

jhuang2601 Jun 18, 2026

Choose a reason for hiding this comment

Uh oh!

dkachuma Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

jhuang2601 Jun 18, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

dkachuma Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

bd713 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

bd713 Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

bd713 Jun 15, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jhuang2601 commented Jun 18, 2026

Uh oh!

jhuang2601 commented Jun 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

jhuang2601 commented Jun 10, 2026 •

edited

Loading