[petsc-dev] attaching field information to PetscLayout?

[Jed Brown]

On Sun, May 15, 2011 at 22:39, Dmitry Karpeev <karpeev at mcs.anl.gov> wrote:

> Should overlapping splits and splits on subcommunictors be
> allowed within PetscLayout?
>

Is there something useful you can do with overlapping splits without knowing
whether they overlap and without also having access to non-overlapping
splits. PCASM treats the overlapping and non-overlapping decomposition as
separate entities. I'm not opposed to having information about overlapping
splits in PetscLayout, but if it's going to be used in a semantically
different way, then perhaps it should be treated that way when stored in
PetscLayout.

Do you have thoughts on managing something like PCFieldSplit for low-Mach
Euler? Where should the code for that sort of transformation (involving
linearized equation of state) reside? What should the MatGetSubMatrix() or
MatGetSchurComplement() look like when the requested subspace involves this
transformation?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110515/a8d20bb7/attachment.html>