-
Notifications
You must be signed in to change notification settings - Fork 2
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
Generic Block solvers #49
Merged
Merged
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
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.
The aim of this PR is the implementation of generic (linear/nonlinear), hierarchical block preconditioners.
The idea is that we want to have a preconditioner with a block structure, such that each block can be a regular solver (Direct/Iterative) or another block solver. Moreover, the iterative solvers can themselves be preconditioned.
Another difficulty is the fact that some of the blocks can be nonlinear (i.e the matrix for that block changes every time the solver is called) and possibly are NOT the system matrix (i.e the case of a preconditioner that changes at each nonlinear iteration but which requires integrating it's own components).
All in all, I have identified three types of blocks:
In addition, I also aim to implement structures that allow for efficient re-assembly of block systems: In most cases, not all the blocks in a multi-physics problem will have non-linearity. For instance, in the MHD equations only the u-u block has the Navier-Stokes nonlinear term. We would like to exploit this and only re-assemble the blocks containing that non-linearity. To this purpose:
BlockFEOperator
, which has knowledge of which blocks are nonlinear.BlockFunctional
type of object.Other stuff: