> This is an interesting development...
>
> One thing I would warn against is tying ourselves too close to Petsc.
> I am currently waiting on a project to get green lighted where I will
> be tying Trilinos into libMesh... where we will have access to other
> matrix free solvers (like NOX, which ca
> I agree about not tying LibMesh too much to PETSc but since there is a
> PetscNonlinearSolver class, I definitely want to use its full potential when
> solving nonlinear problems. And hence exposure to the actual snes object
> either through a property or function is necessary to have better con
k
> Cc: Vijay M; libmesh-devel@lists.sourceforge.net
> Subject: Re: [Libmesh-devel] [Libmesh-users] Support for Matrix-free
> algorithms
>
> This is an interesting development...
>
> One thing I would warn against is tying ourselves too close to Petsc.
> I am currently waiting o
bmesh-devel@lists.sourceforge.net
Subject: Re: [Libmesh-devel] [Libmesh-users] Support for Matrix-free
algorithms
This is an interesting development...
One thing I would warn against is tying ourselves too close to Petsc.
I am currently waiting on a project to get green lighted where I will
be
This is an interesting development...
One thing I would warn against is tying ourselves too close to Petsc.
I am currently waiting on a project to get green lighted where I will
be tying Trilinos into libMesh... where we will have access to other
matrix free solvers (like NOX, which can work with
Here is a really, really raw example, the comments are not clear right now,
but I wanted to keep you informed. This requires the latest svn branch to
work.
Unpack it in the ./examples directory and run make.
Run it as
$ ./ex19-dbg -snes_view -r 4
for a successive approximation which will conver
