[petsc-users] Some questions regarding VecNest type.
Jed Brown
jedbrown at mcs.anl.gov
Wed Oct 12 15:28:34 CDT 2011
On Wed, Oct 12, 2011 at 15:25, Vijay S. Mahadevan <vijay.m at gmail.com> wrote:
> What do you mean ? The blocks are formed in memory and handed over to
> the algebraic preconditioner (controlled at runtime). Why would the
> user have to change the preconditioner manually ? This made use of the
> block PC object in petsc-ext which I assume is replaced by FieldSplit
> ? I eventually do have to handle this elegantly and will need some
> input when I get there.
>
> If you are talking about the compile time switch, then yes, that was a
> little painful. But hopefully pure petsc will give me some peace !
>
I meant the two pieces of code. It's more to maintain and test. Needing to
choose at compile time is lame, but even if you could do it at run-time, it
would not be fun to maintain. In my opinion, we want one code where we can
do
-mat_type X -pc_type fieldsplit
and
-mat_type Y -pc_type lu
and have efficient data structures used in both cases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20111012/ca259869/attachment.htm>
More information about the petsc-users
mailing list