Re: [petsc-dev] Recover from TS failure

2017-11-02 Thread Mark Adams
> > > >This is absolute nonsense. No way should you or do you need to do this. > TS can/is suppose to handle failures in the solver cleanly. We need a > reproducible result where it does not handle it correctly and then we fix > the problem > > No problem, Jed gave me the magic incantations :)

Re: [petsc-dev] Recover from TS failure

2017-11-02 Thread Smith, Barry F.
> On Nov 1, 2017, at 1:13 PM, Mark Adams wrote: > > Yea, I don't understand the linear solve error: > > -ts_monitor -ts_type beuler -pc_type lu -pc_factor_mat_solver_package mumps > -ksp_type preonly -snes_monitor -snes_rtol 1.e-10 -snes_stol 1.e-10 > -snes_converged_reason -snes_atol 1.e-18

Re: [petsc-dev] PETSc communicators with MPI in Fortran

2017-11-02 Thread Smith, Barry F.
> On Oct 31, 2017, at 6:00 PM, Neelam Patel wrote: > > Hello PETSc users, > > Working in Fortran, I created 2 disjoint communicators with MPI_Group > operations using PETSC_COMM_WORLD as the "base" comm. I created parallel > vectors on each communicator, and set values in them equal to their

Re: [petsc-dev] SLEPc failure

2017-11-02 Thread Jose E. Roman
Could you please try the following modified function? It should replace the one in $SLEPC_DIR/include/slepc/private/bvimpl.h Thanks. PETSC_STATIC_INLINE PetscErrorCode BV_SafeSqrt(BV bv,PetscScalar alpha,PetscReal *res) { PetscErrorCode ierr; PetscReal absal,realp; PetscFunctionBegin