Reference documentation for deal.II version Git 4abc4a1666 20200704 19:58:34 +0200

#include <deal.II/lac/petsc_solver.h>
Classes  
struct  AdditionalData 
Public Member Functions  
SolverPreOnly (SolverControl &cn, const MPI_Comm &mpi_communicator=PETSC_COMM_SELF, const AdditionalData &data=AdditionalData())  
Public Member Functions inherited from PETScWrappers::SolverBase  
SolverBase (SolverControl &cn, const MPI_Comm &mpi_communicator)  
virtual  ~SolverBase ()=default 
void  solve (const MatrixBase &A, VectorBase &x, const VectorBase &b, const PreconditionerBase &preconditioner) 
virtual void  reset () 
void  set_prefix (const std::string &prefix) 
SolverControl &  control () const 
void  initialize (const PreconditionerBase &preconditioner) 
Protected Member Functions  
virtual void  set_solver_type (KSP &ksp) const override 
Protected Attributes  
const AdditionalData  additional_data 
Protected Attributes inherited from PETScWrappers::SolverBase  
SolverControl &  solver_control 
const MPI_Comm  mpi_communicator 
std::string  prefix_name 
An implementation of the solver interface using the PETSc PREONLY solver. Actually this is NOT a real solution algorithm. solve() only applies the preconditioner once and returns immediately. Its only purpose is to provide a solver object, when the preconditioner should be used as a real solver. It is very useful in conjunction with the complete LU decomposition preconditioner PreconditionLU
, which in conjunction with this solver class becomes a direct solver.
Definition at line 857 of file petsc_solver.h.
PETScWrappers::SolverPreOnly::SolverPreOnly  (  SolverControl &  cn, 
const MPI_Comm &  mpi_communicator = PETSC_COMM_SELF , 

const AdditionalData &  data = AdditionalData() 

) 
Constructor. In contrast to deal.II's own solvers, there is no need to give a vector memory object. However, PETSc solvers want to have an MPI communicator context over which computations are parallelized. By default, PETSC_COMM_SELF
is used here, but you can change this. Note that for single processor (nonMPI) versions, this parameter does not have any effect.
The last argument takes a structure with additional, solver dependent flags for tuning.
Note that the communicator used here must match the communicator used in the system matrix, solution, and right hand side object of the solve to be done with this solver. Otherwise, PETSc will generate hard to track down errors, see the documentation of the SolverBase class.
Definition at line 592 of file petsc_solver.cc.

overrideprotectedvirtual 
Function that takes a Krylov Subspace Solver context object, and sets the type of solver that is appropriate for this class.
Implements PETScWrappers::SolverBase.
Definition at line 601 of file petsc_solver.cc.

protected 
Store a copy of the flags for this particular solver.
Definition at line 890 of file petsc_solver.h.