[petsc-dev] Should we replace hypre PILUT with hypre Euclid?

Matthew Knepley knepley at gmail.com
Tue Jul 17 13:58:36 CDT 2018


On Tue, Jul 17, 2018 at 2:55 PM Jed Brown <jed at jedbrown.org> wrote:

> PETSc had a Euclid interface until Barry removed it.
>
>
> https://bitbucket.org/petsc/petsc/commits/22b6d1ca80e4f79123036fb6afd7eb4463b3692a
>
> See also
>
> https://www.mail-archive.com/petsc-users@mcs.anl.gov/msg33196.html


I would also add that it is considerate of Hypre to have such a terrible
ILUT implementation
because it reminds you that you should never ever ever use ILUT.

  Matt


>
> Fande Kong <fdkong.jd at gmail.com> writes:
>
> > Hi Developers,
> >
> > The hypre user manual  has this statement (page 63):
> >
> > "Note: this code is no longer supported by the hypre team. We recommend
> to
> > use Euclid instead,
> > which is more versatile and in general more efficient, especially when
> used
> > with many processors."
> >
> >
> >
> https://computation.llnl.gov/sites/default/files/public/hypre-2.11.2_usr_manual.pdf
> >
> >
> >
> > It may be a good idea to upgrade PETSc interface to use Euclid instead of
> > PILUT??
> >
> >
> > Fande,
>


-- 
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.caam.rice.edu/~mk51/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20180717/3b5a3fd0/attachment.html>


More information about the petsc-dev mailing list