Open
Conversation
and PETScNonLinearSolvers for supporting FieldSplit
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
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.
I have tried to extend the ability of the package to manage
PCFieldSplitoptions in PETSc forMultiFields.I have added the new ´IS´ PETSc type and several C functions for using the new type.
Looking at the code, I collect the global ID of the equations/dof for each processor of each field.
A new struct
PETScFieldSplithas been created. The user can easily specify the fields and a tag name to identify the fields,such as:
any constructive comments to improve/expand functionality are very welcome