[petsc-dev] PCGAMG: set default type (AGG); PCSetUp_GAMG crashes if not set
Matthew Knepley
knepley at gmail.com
Wed Oct 30 11:38:16 CDT 2013
On Wed, Oct 30, 2013 at 11:15 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> Matthew Knepley <knepley at gmail.com> writes:
> >> True, but if you do that, you could also mark all those instances and
> >> remove them automatically.
> >>
> >
> > True.
>
> So should we mark them and remove them automatically, getting rid of
> this extra thing to remember and another likely place for merge
> conflicts? Are there any circumstances where that would be surprising?
>
The only confusing thing I see is if we wanted them not set back to NULL,
but
to a "default" function. I think we should outlaw that.
Matt
--
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131030/e49144b1/attachment.html>
More information about the petsc-dev
mailing list