Reintroduce to_petsc_local_numbering
#3060
Merged
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
ksagiyam
previously approved these changes
Aug 14, 2023
Thanks to @ksagiyam Co-authored-by: ksagiyam <[email protected]>
ksagiyam
approved these changes
Aug 14, 2023
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.
Hi all. I decided to take the metric-based mesh adaptation stuff out of #2796 and put it in a new repo: https://github.com/pyroteus/animate. However, it will still need the
to_petsc_local_numberingfunction that was removed from Firedrake at some point. Would you be willing to put this updated version back in?The PR also contains some minor fixes for the PETSc interface docs (introduced by me I think).