[petsc-dev] Naming for PCFieldSplitSetSchurPrecondition()

2011-06-09 Thread Jed Brown
matrix S and then MatGetSchurComplement() would return it for the preconditioning matrix. Is this nuts? -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110609/8c91c0f2/attachment.html>

[petsc-dev] Naming for PCFieldSplitSetSchurPrecondition()

2011-06-09 Thread Barry Smith
So you are suggesting totally removing PCFieldSplitSetSchurPrecondition() and instead having the user call MatSetApproximateSchurComplement() if they wish to provide a matrix? Sounds ok to me. Barry On Jun 9, 2011, at 4:21 PM, Jed Brown wrote: > I noticed your developer note. The f

[petsc-dev] Naming for PCFieldSplitSetSchurPrecondition()

2011-06-09 Thread Matthew Knepley
p://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110609/6ea12ffc/attachment.html>

[petsc-dev] Naming for PCFieldSplitSetSchurPrecondition()

2011-06-09 Thread Barry Smith
On Jun 9, 2011, at 5:50 PM, Jed Brown wrote: > On Fri, Jun 10, 2011 at 00:47, Barry Smith wrote: > So you are suggesting totally removing PCFieldSplitSetSchurPrecondition() and > instead having the user call MatSetApproximateSchurComplement() if they wish > to provide a matrix? > > Yeah, tho

[petsc-dev] Naming for PCFieldSplitSetSchurPrecondition()

2011-06-09 Thread Barry Smith
On Jun 9, 2011, at 6:08 PM, Jed Brown wrote: > On Fri, Jun 10, 2011 at 01:01, Barry Smith wrote: > Absolutely, by default MatGetSchurComplement() should be providing the > diagonal block if something else is not given by the user. This way the > fieldsplit can just call MatGetSchurComplement()