-
Notifications
You must be signed in to change notification settings - Fork 177
RestrictedFunctionSpace: support Fieldsplit, multigrid, and python PC #4169
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
Conversation
4193431 to
1b20212
Compare
9df7a04 to
7a07dff
Compare
9a449c5 to
f165b4b
Compare
…eproject/firedrake into pbrubeck/fix/restricted-dmhooks
rckirby
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: There are similar (I think) issues if we try to use Firedrake preconditioners inside of the reduced space snes VI solvers. Is there any way to connect some of this work to that case? (Of course, the information about restriction is coming from inside a SNES instead of outside in Firedrake in that case).
connorjward
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please split some of this out into another PR. And @ksagiyam can review
4a1d57d to
ddc189a
Compare
Description
This PR adds support for pc_type
fieldsplit,mg, andpythonwithRestrictedFunctionSpace.Apparently setting name of the RFS also changes the name of the split in the PETSc solver option.
With the default name, the options prefix becomes
fieldsplit_Restricted_on_boundary, instead offieldsplit_x.This PR ensures that the restricted spaces that are created within solvers preserve the name of the unrestricted parent space so that the same set of fieldsplit options works for both
restrict=Falseandrestrict=True.