-
Notifications
You must be signed in to change notification settings - Fork 99
Feature/oduran/test fem stress consistency #3957
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
OmarDuran
wants to merge
106
commits into
develop
Choose a base branch
from
feature/oduran/test_fem_stress_consistency
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+3,876
−241
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…l surfaceGenerator
This was
linked to
issues
Feb 6, 2026
Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp Update SolidMechanicsAugmentedLagrangianContact.cpp wip: solution Update SolidMechanicsAugmentedLagrangianContact.cpp
* split out SurfaceElementRegion set update to post split * try to reserve maps in node manager * update LvArray submodule hash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new integration test, to verify the consistency of the Finite Element Method implementation in GEOS. The test focuses on stress transmission across fractured domains using the SurfaceGenerator class.
The test ensures that the mechanical solvers preserve stress equilibrium and correctly handle contact/interface conditions across different mesh types and fracture configurations.
The physical setup is a pure compression case with no shear induced by the boundary conditions. As a result, the stress field is constant, which allows for direct verification: for volume elements, the averaged computed stress tensor is checked against the applied boundary tractions, and for fracture surfaces, the traction vector 𝑡 = 𝜎⋅𝑛 is projected from neighboring volume cells onto fracture faces, is computed and verified on both fracture sides against the expected traction.
The figures show (top-left) a structured hexahedral mesh, (top-right) a structured tetrahedral mesh, (bottom-left) a hexahedral mesh with curved fractures, and (bottom-right) a tetrahedral mesh with curved fractures.
Fracture leading orientations:
f1: normal aligned with the x-axis
f2: normal aligned with the y-axis
f3: normal aligned with the z-axis
The test covers all combinations of fractures:
f1 -meshes:







f2 -meshes:
f3 -meshes:
f1-f2 -meshes:
f2-f3 -meshes:
f1-f3 -meshes:
f1-f2-f3 -meshes: