While playing around with step-17 using PETSc solvers, I found that via command line I could only control the preconditioners and not the solvers. This seems like a major bug and is not in the philosophy of what the PETSc solvers provide. Adding the KSPSetOptions remedies this but I just wanted to know if there was a reason to ever not include this or perhaps remove the call that existed previously.
The original reason is that in deal.II we typically do things explicitly, in the source code, rather than on the command line. Consequently, we have separate classes for all kinds of PETSc solvers. But that of course doesn't mean that we have to continue doing so. Before I apply your patch, do you know what happens if you use PETScWrappers::SolverCG but then select something else on the command line? Best W. _______________________________________________ dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii
