libMesh backend #31
Draft
libMesh backend #31
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
pshriwise
force-pushed
the
libmesh-exp
branch
from
6b3e508 to
7a7c06e
Compare
…ingletons.. grumble grumble
… entirely on those. If not, then do discovery.
…r MeshIDPair hash
pshriwise
force-pushed
the
libmesh-exp
branch
from
ec1ac7d to
bd3a24f
Compare
…cyl-brick are the same
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 description will be updated as the changes evolve to be more fully-featured.
A backend for libMesh tetrahedral meshes. This is pretty experimental at the moment, but the initial tests indicate that ray tracing on the boundary of tetrahedral mesh subdomains is functional.