[petsc-dev] [petsc-maint] circular dependency [nightlybuilds did not catch]

Matthew Knepley knepley at gmail.com
Sat May 4 15:24:09 CDT 2019

On Sat, May 4, 2019 at 1:49 PM Jed Brown via petsc-maint <
petsc-maint at mcs.anl.gov> wrote:

> "Smith, Barry F. via petsc-maint" <petsc-maint at mcs.anl.gov> writes:
> >   Yes you have the history exactly right, but keeping them as
> independent beasts seemed/seems impossible; except by doing something very
> cumbersome (like shoving all the PCXXX_YYY that depended on KSP into the
> KSP src directory). So the "opted" was really forced upon us.
> We could merge PC and KSP into a single class, perhaps maintaining
> separate lists by typical "role"

Luckily, this was advocated for 20 years ago:


> (the things we call PC are usually
> configured to be linear operations while the things we call KSP are
> iterative).  It would be a major change and I'm not suggesting we
> should, but it would eliminate a lot of duplication and associated
> controversy.

What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener

https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190504/57c4b05c/attachment-0001.html>

More information about the petsc-dev mailing list