On Thu Feb 19 2015 at 12:59:12 PM Barry Smith bsm...@mcs.anl.gov wrote:
On Feb 19, 2015, at 1:56 PM, Dmitry Karpeyev karp...@mcs.anl.gov
wrote:
On Thu Feb 19 2015 at 12:41:59 PM Barry Smith bsm...@mcs.anl.gov
wrote:
Yeah, that sounds like a good fix, except for this: we have to
All the Krylov methods are supposed to use the routines KSP_MatMult(),
KSP_PCApply() etc and not the MatMult(), PCApply() etc directly (I'm fixing
some that don't as we speak).
I propose that these KSP_xxx() routines have code like
MatGetFailure(mat,failure);
if (failure)
On Feb 19, 2015, at 1:56 PM, Dmitry Karpeyev karp...@mcs.anl.gov wrote:
On Thu Feb 19 2015 at 12:41:59 PM Barry Smith bsm...@mcs.anl.gov wrote:
Yeah, that sounds like a good fix, except for this: we have to make sure all
ranks diverge with this failure so that the user can retry the
On Feb 19, 2015, at 2:06 PM, Dmitry Karpeyev karp...@mcs.anl.gov wrote:
On Thu Feb 19 2015 at 12:59:12 PM Barry Smith bsm...@mcs.anl.gov wrote:
On Feb 19, 2015, at 1:56 PM, Dmitry Karpeyev karp...@mcs.anl.gov wrote:
On Thu Feb 19 2015 at 12:41:59 PM Barry Smith
I wanted to revive this thread and move it to petsc-dev. This problem seems
to be harder than I realized.
Suppose MatMult inside KSPSolve() inside SNESSolve() cannot compute a valid
output vector.
For example, it's a MatMFFD and as part of its function evaluation it has
to evaluate an
No problem on our end with MatSetFailure() being collective... we can
guarantee that easily.
Thanks for working on this! This has been a high priority feature request
for a while.
Derek
On Thu, Feb 19, 2015 at 3:41 PM Barry Smith bsm...@mcs.anl.gov wrote:
On Feb 19, 2015, at 2:06 PM, Dmitry
