[petsc-users] KSP no longer returning NaNs?

[Kirk, Benjamin (JSC-EG311)]

Hello -

I've been using PETSc 3.1 for quite a while now and have been hesitant to
upgrade because of some new behavior I found in 3.2.  Let me explain...

In petsc-3.1, if the KSP encountered a NaN it would return it to the
application code.  We actually liked this feature because it gives us an
opportunity to catch the NaN and attempt recovery, in our case by decreasing
the time step and trying again.

It seems in petsc-3.2, however, that PETSc itself aborts internally, so we
are unable to recover from the situation.

Is there any way to get the old behavior back?

Thanks,

-Ben