It sounds like you need to write a new PC implementation, possibly reusing pieces of PCASM. Then you have control of what is being set up and when. Otherwise you are essentially hacking PCASM and using its internal subsolvers, which are only available after PCSetUp(). PCCOMPOSITE doesn't look like the right framework for this.
Dmitry. On Tue, May 22, 2012 at 5:23 AM, Hui Zhang <mike.hui.zhang at hotmail.com>wrote: > Hi, > > I have got a new question. I'm now constructing a PCComposite from PCASM > and another PCKSP (coarse > problem). And construction of PCKSP needs to use the subksp's of PCASM. So > I need to PCSetUp on the > PCASM, right? But the KSP using PCComposite would setup PCASM again. How > can I avoid twice setup > of PCASM ? > > Thanks, > Hui > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120522/6f0cb7be/attachment.html>
