Re: [Libmesh-devel] convergence reason in PETSc nonlinear solver

2011-03-03 Thread Vijay S. Mahadevan
Roy, I think it would be advisable that all libMesh users update themselves to atleast petsc/slepc 3.0-p0. There are so many fixes/changes from 2.3.3.->3.0 that it feels like they dont utilize the full potential of the solvers. Of course, the petsc_macro preprocessor routines would shield the user

Re: [Libmesh-devel] convergence reason in PETSc nonlinear solver

2011-03-03 Thread Roy Stogner
On Thu, 3 Mar 2011, Roman Vetter wrote: >>> 1. Replace the contents of PetscLinearSolver::print_converged_reason() by >>> >>> KSPConvergedReason reason; >>> KSPGetConvergedReason(_ksp, &reason); >>> libMesh::out << "Linear solver convergence/divergence reason: " << >>> KSPConvergedReasons[reason

Re: [Libmesh-devel] convergence reason in PETSc nonlinear solver

2011-03-03 Thread Roman Vetter
>> 1. Replace the contents of PetscLinearSolver::print_converged_reason() by >> >> KSPConvergedReason reason; >> KSPGetConvergedReason(_ksp, &reason); >> libMesh::out << "Linear solver convergence/divergence reason: " << >> KSPConvergedReasons[reason] << std::endl; >> >> or similar. > > This sounds

Re: [Libmesh-devel] VTK output fails in parallel

2011-03-03 Thread Roman Vetter
> There's another test where we die with an error: mixed-order elements. > E.g. ex11 with VTKIO dies screaming as soon as VTKIO::solution_to_vtk > hits a side node on a QUAD9, when it expects to see two velocity > components plus one pressure component but it only sees one pressure > component. I