The routine may be called by the names f07fqf, nagf_lapacklin_zcposv or its LAPACK name zcposv.
3Description
f07fqf first attempts to factorize the matrix in reduced precision and use this factorization within an iterative refinement procedure to produce a solution with full precision normwise backward error quality (see below). If the approach fails the method switches to a full precision factorization and solve.
The iterative refinement can be more efficient than the corresponding direct full precision algorithm. Since the strategy implemented by f07fqf must perform iterative refinement on each right-hand side, any efficiency gains will reduce as the number of right-hand sides increases. Conversely, as the matrix size increases the cost of these iterative refinements become less significant relative to the cost of factorization. Thus, any efficiency gains will be greatest for a very small number of right-hand sides and for large matrix sizes. The cut-off values for the number of right-hand sides and matrix size, for which the iterative refinement strategy performs better, depends on the relative performance of the reduced and full precision factorization and back-substitution. f07fqf always attempts the iterative refinement strategy first; you are advised to compare the performance of f07fqf with that of its full precision counterpart f07fnf to determine whether this strategy is worthwhile for your particular problem dimensions.
The iterative refinement process is stopped if where iter is the number of iterations carried out thus far. The process is also stopped if for all right-hand sides we have
where is the -norm of the residual, is the -norm of the solution, is the -norm of the matrix and is the machine precision returned by x02ajf.
4References
Anderson E, Bai Z, Bischof C, Blackford S, Demmel J, Dongarra J J, Du Croz J J, Greenbaum A, Hammarling S, McKenney A and Sorensen D (1999) LAPACK Users' Guide (3rd Edition) SIAM, Philadelphia https://www.netlib.org/lapack/lug
Golub G H and Van Loan C F (1996) Matrix Computations (3rd Edition) Johns Hopkins University Press, Baltimore
Higham N J (2002) Accuracy and Stability of Numerical Algorithms (2nd Edition) SIAM, Philadelphia
5Arguments
1: – Character(1)Input
On entry: specifies whether the upper or lower triangular part of is stored.
The upper triangular part of is stored.
The lower triangular part of is stored.
Constraint:
or .
2: – IntegerInput
On entry: , the number of linear equations, i.e., the order of the matrix .
Constraint:
.
3: – IntegerInput
On entry: , the number of right-hand sides, i.e., the number of columns of the matrix .
Constraint:
.
4: – Complex (Kind=nag_wp) arrayInput/Output
Note: the second dimension of the array a
must be at least
.
On entry: the Hermitian positive definite matrix .
If , the upper triangular part of must be stored and the elements of the array below the diagonal are not referenced.
If , the lower triangular part of must be stored and the elements of the array above the diagonal are not referenced.
On exit: if iterative refinement has been successfully used ( and , see iter), then a is unchanged. If full precision factorization has been used ( and , see iter), then the array contains the factor or from the Cholesky factorization or .
5: – IntegerInput
On entry: the first dimension of the array a as declared in the (sub)program from which f07fqf is called.
Constraint:
.
6: – Complex (Kind=nag_wp) arrayInput
Note: the second dimension of the array b
must be at least
.
On entry: the right-hand side matrix .
7: – IntegerInput
On entry: the first dimension of the array b as declared in the (sub)program from which f07fqf is called.
Constraint:
.
8: – Complex (Kind=nag_wp) arrayOutput
Note: the second dimension of the array x
must be at least
.
On exit: if , the solution matrix .
9: – IntegerInput
On entry: the first dimension of the array x as declared in the (sub)program from which f07fqf is called.
Constraint:
.
10: – Complex (Kind=nag_wp) arrayWorkspace
11: – Complex (Kind=nag_rp) arrayWorkspace
Note: this array is utilized in the reduced precision computation, consequently its type nag_rp reflects this usage.
12: – Real (Kind=nag_wp) arrayWorkspace
13: – IntegerOutput
On exit: information on the progress of the interative refinement process.
Iterative refinement has failed for one of the reasons given below, full precision factorization has been performed instead.
The routine fell back to full precision for implementation- or machine-specific reasons.
Narrowing the precision induced an overflow, the routine fell back to full precision.
An intermediate reduced precision factorization failed.
The maximum permitted number of iterations was exceeded.
Iterative refinement has been sucessfully used. iter returns the number of iterations.
14: – IntegerOutput
On exit: unless the routine detects an error (see Section 6).
6Error Indicators and Warnings
If , argument had an illegal value. An explanatory message is output, and execution of the program is terminated.
The leading minor of order of is not positive definite, so the factorization could not be completed, and the solution has not been computed.
7Accuracy
For each right-hand side vector , the computed solution is the exact solution of a perturbed system of equations , where
if , ;
if , ,
is a modest linear function of , and is the machine precision. See Section 10.1 of Higham (2002) for further details.
An approximate error bound for the computed solution is given by
where , the condition number of with respect to the solution of the linear equations. See Section 4.4 of Anderson et al. (1999) for further details.
8Parallelism and Performance
f07fqf is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
f07fqf makes calls to BLAS and/or LAPACK routines, which may be threaded within the vendor library used by this implementation. Consult the documentation for the vendor library for further information.
Please consult the X06 Chapter Introduction for information on how to control and interrogate the OpenMP environment used within this routine. Please also consult the Users' Note for your implementation for any additional implementation-specific information.