<p>Dear PETSc Developers:</p><p>I have checked the differerence between 2.3.3 and 3.0.0 in using external package. </p><p>Now, we don't need to use Matconvert() to convert the matrix to the type suitable for external package, just to use MatGetFactor(). </p>
<p>The following codes are the realization of MatSolveXXX() after calling MatGetFactor().</p><p>53: MatFactorInfoInitialize(&info);</p><p>54: MatGetFactor(C,MAT_SOLVER_PETSC,MAT_FACTOR_LU,&A);<br></p> 55: MatLUFactorSymbolic(A,C,row,col,&info);<br>
56: MatLUFactorNumeric(A,C,&info);<br><p> 57: MatSolveTranspose(A,b,x);</p><p>I have checked the description to MatSolveXXX() or MatMatSolve(). <br></p><p>"Notes<br>Most users should employ the simplified KSP interface for linear solvers instead of working directly with matrix algebra routines such as this. See, e.g., KSPCreate()."</p>
<p>You advise to use KSP interface for calling MatSolveXXX(). I am wondering if it is ok to directly call MatSolveXX(), why need KSP interface? thanks a lot.</p><p>Regards,</p><p>Yujie<br><br></p><br>