Skip to content

Mesh stitching fixes for NodeElems #2103

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

Merged
merged 2 commits into from
Apr 17, 2019
Merged

Conversation

jwpeterson
Copy link
Member

The code would previously compute an h_min value of 0 in cases where the first elem in the mesh was a NodeElem, thereby causing all subsequent relative distance checks to fail.

Jonas Ballani and others added 2 commits April 17, 2019 08:46
We only set h_min in this way if it has not been previously
updated. This ensures that h_min is the min over both meshes being
stitched.

Co-authored-by: John W. Peterson <[email protected]>
@jwpeterson jwpeterson merged commit 2c772e0 into libMesh:master Apr 17, 2019
@jwpeterson
Copy link
Member Author

This can also be backported to 1.4.1 (#2029).

@jwpeterson jwpeterson deleted the stitch_fix branch April 18, 2019 13:18
jwpeterson added a commit to jwpeterson/libmesh that referenced this pull request Apr 19, 2019
* Search only active elements as was done previously.
* If the linear search ends in failure, fall back on using h_min==1
  rather than repeating the linear search for every node in the node
  list.
jwpeterson added a commit that referenced this pull request Apr 19, 2019
jwpeterson added a commit that referenced this pull request Apr 19, 2019
* Search only active elements as was done previously.
* If the linear search ends in failure, fall back on using h_min==1
  rather than repeating the linear search for every node in the node
  list.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants