fixes to xfem 3d cutter mesh#32780
Open
lynnmunday wants to merge 17 commits intoidaholab:nextfrom
Open
Conversation
Contributor
|
Job Documentation, step Docs: sync website on 81e8d17 wanted to post the following: View the site here This comment will be updated on new commits. |
lynnmunday
force-pushed
the
xfem_3D_cutter_tangle
branch
5 times, most recently
from
4a5e03c to
4c99b61
Compare
Contributor
|
All jobs on 4c99b61 : invalidated by @lynnmunday |
Contributor
|
Job Coverage, step Generate coverage on 81e8d17 wanted to post the following: Framework coverageCoverage did not change Modules coverageXfem
Full coverage reportsReports
This comment will be updated on new commits. |
||||||||||||||||||||||||||
Inactive crack front nodes now get their growth direction copied from their connected active neighbor instead of zero. growFront() now grows all nodes including boundary nodes, eliminating the need for findFrontIntersection(). For REPORTER growth increment, boundary nodes use the increment from their nearest active neighbor. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…correct double cantilever results even though the test diffs.
…e elements are found, it also grows the crack using time dependent functions. It also correctly grows surface nodes. closes idaholab#32779
…ont growth Also modify domain to avoid xfem double cutting edge errors that happen intermittently. Setting map to default of true in tests that exodiff a cutter mesh because locations of the nodes will stay the same but their order may change. Only the cutter mesh can use map = true, regular xfem meshes must use map=false for exodiff because geometric matching will not work when the cut mesh produces new elements in the exact same location which causes exodiff to fail. I re-arranged the comments in the test file to be at the top.
…ent for crack front segments that contain an inactive node. Added examples for stress corrosion cracking and brittle fracture.
… with the improved surface movement. Adding tests for different cutting scenarios.
lynnmunday
force-pushed
the
xfem_3D_cutter_tangle
branch
3 times, most recently
from
1c41617 to
68753d1
Compare
When adjacent face/neighbor propagation rediscovers the same physical edge at the same parametric position, reuse the embedded node already stored on that edge instead of throwing a duplicate-edge-intersection error. Add a unit test covering the shared-edge face reuse case and assert that only one embedded cut remains on the edge -- it cannot create two edges, that would be an error. The unit test is a simplified version of what was occuring in test:solid_mechanics_basic.mesh_cutter_3d/double_cut_edge
lynnmunday
force-pushed
the
xfem_3D_cutter_tangle
branch
from
68753d1 to
de192e9
Compare
Contributor
|
Job Precheck, step Clang format on de192e9 wanted to post the following: Your code requires style changes. A patch was auto generated and copied here
Alternatively, with your repository up to date and in the top level of your repository:
|
Contributor
|
Job Test, step Results summary on 81e8d17 wanted to post the following: Framework test summaryCompared against 5b391df in job civet.inl.gov/job/3787211. No added testsRun time changes
Modules test summaryCompared against 5b391df in job civet.inl.gov/job/3787211. Added tests
Run time changes
|
Contributor
|
Job Conda moose linux on 81e8d17 : invalidated by @lynnmunday |
Contributor
|
Job Conda mac on 81e8d17 : invalidated by @lynnmunday |
Contributor
|
Job Conda rocky mpich on 81e8d17 : invalidated by @lynnmunday |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
closes #32779