-
Notifications
You must be signed in to change notification settings - Fork 51
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
Interior boundary cracks for meshes #261
Merged
Merged
Conversation
This file contains 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
sebastiangrimberg
added
enhancement
New feature or request
amr
Related to adaptive mesh refinement (AMR)
mesh
Related to meshes and mesh generation
labels
Jun 6, 2024
sebastiangrimberg
force-pushed
the
sjg/mesh-simplex-dev
branch
from
June 10, 2024 18:20
789a272
to
b2f178a
Compare
sebastiangrimberg
force-pushed
the
sjg/mesh-simplex-dev
branch
from
June 20, 2024 00:58
b2f178a
to
0a3dc8f
Compare
sebastiangrimberg
force-pushed
the
sjg/bdr-mesh-crack
branch
2 times, most recently
from
June 20, 2024 01:07
cbcd40f
to
41b89ad
Compare
sebastiangrimberg
changed the base branch from
sjg/mesh-simplex-dev
to
sjg/lumped-ports-bbox
June 20, 2024 01:09
sebastiangrimberg
force-pushed
the
sjg/bdr-mesh-crack
branch
from
June 20, 2024 01:25
41b89ad
to
80e6e9e
Compare
sebastiangrimberg
force-pushed
the
sjg/lumped-ports-bbox
branch
3 times, most recently
from
June 26, 2024 21:17
2060846
to
a6e8725
Compare
sebastiangrimberg
added a commit
that referenced
this pull request
Jun 26, 2024
Fix oriented bounding box calculation for lumped ports, in preparation for #261
sebastiangrimberg
force-pushed
the
sjg/bdr-mesh-crack
branch
2 times, most recently
from
July 1, 2024 16:17
dccc3f2
to
f0705b9
Compare
sebastiangrimberg
force-pushed
the
sjg/bdr-mesh-crack
branch
from
July 11, 2024 21:45
f0705b9
to
afb717c
Compare
…in interior boundaries (one element wide)
…ments via improved tetrahedra marking
…internal boundaries
…unt for corner cases of edges requiring refinement, and fix the renumbering and duplication of boundary elements for cracking
hughcars
force-pushed
the
sjg/bdr-mesh-crack
branch
from
July 19, 2024 17:17
afb717c
to
4f99688
Compare
hughcars
changed the title
[WIP] Interior boundary cracks for meshes
Interior boundary cracks for meshes
Aug 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
amr
Related to adaptive mesh refinement (AMR)
enhancement
New feature or request
mesh
Related to meshes and mesh generation
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.
See https://www.sciencedirect.com/science/article/pii/S0965997814000660, or https://gitlab.onelab.info/gmsh/gmsh/blob/master/examples/api/crack3d.py in Gmsh. Enabled with the
"CrackInternalBoundaryElements"
configuration file parameter (on by default, off to restore previous behavior).Implications for postprocessing of interior boundaries: For now we have removed the
"Side"
configuration file parameter and upgraded the surface dielectric loss postprocessing to automatically detect the right side for evaluating the fields based on the MA/MS/SA characteristic. All other interior boundaries use the average of the field on both sides which makes sense mostly. The case this doesn't work is visualization in ParaView of the boundary data collection, where for cracked internal boundary elements you have two elements directly on top of each other which need to be separated by some positive distance in order for ParaView to display the data on each "side" correctly. This is a WIP...