PUMI related additions to PyMFEM #32
Draft
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
This constructor takes an apf::Mesh2 (PUMI mesh) as an input. This helps create a ParMesh object properly.
3 tasks
The default call with refine=1 causes issues in ReorientTetMesh during consistency check.
Author
|
@sshiraiwa should I merge the changes from https://github.com/mfem/PyMFEM/tree/mfem_42_dev and test my workflow? |
Member
|
Net yet. Let me run the test on my side first. |
Member
|
Hi @mortezah, I ran my standard test with the MFEM_42 branch. Please try it, but make sure |
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.
This is PR includes a couple of minor changes to bring in PUMI mesh adapt to PyMFEM. Note that this will require the build of PUMI with python wrappers.
Todo: