Dear PETSC Users,
I tried to use a Cholesky factor (MUMPS results) as a preconditioner for
KSPSolve(). An example code is pasted below. When the code runs, the log
file indicates that Job=3 (i.e. backward/forward substitution) of MUMPS is
called every time inside the loop. Is there anyway to
On Fri, Dec 5, 2014 at 2:11 PM, Evan Um eva...@gmail.com wrote:
Dear PETSC Users,
I tried to use a Cholesky factor (MUMPS results) as a preconditioner for
KSPSolve(). An example code is pasted below. When the code runs, the log
file indicates that Job=3 (i.e. backward/forward substitution)
Dear Matt,
Thanks for your quick reply. I mean avoiding MUMPS's internal back/forward
solvers (JOB=3). Does KSPSOLVE() have its own back/forward routines?
Evan
On Fri, Dec 5, 2014 at 12:20 PM, Matthew Knepley knep...@gmail.com wrote:
On Fri, Dec 5, 2014 at 2:11 PM, Evan Um eva...@gmail.com
On Fri, Dec 5, 2014 at 2:31 PM, Evan Um eva...@gmail.com wrote:
Dear Matt,
Thanks for your quick reply. I mean avoiding MUMPS's internal back/forward
solvers (JOB=3). Does KSPSOLVE() have its own back/forward routines?
1) MUMPS stores these in its own format, so code from other packages