NAG Library Routine Document
D02TZF
1 Purpose
D02TZF returns information about the solution of a general two-point boundary value problem computed by
D02TLF.
2 Specification
INTEGER |
MXMESH, NMESH, IPMESH(MXMESH), IERMX, IJERMX, ICOMM(*), IFAIL |
REAL (KIND=nag_wp) |
MESH(MXMESH), ERMX, RCOMM(*) |
|
3 Description
D02TZF and its associated routines (
D02TLF,
D02TVF,
D02TXF and
D02TYF) solve the two-point boundary value problem for a nonlinear mixed order system of ordinary differential equations
over an interval
subject to
(
) nonlinear boundary conditions at
and
(
) nonlinear boundary conditions at
, where
. Note that
is the
th derivative of the
th solution component. Hence
. The left boundary conditions at
are defined as
and the right boundary conditions at
as
where
and
First,
D02TVF must be called to specify the initial mesh, error requirements and other details. Then,
D02TLF can be used to solve the boundary value problem. After successful computation, D02TZF can be used to ascertain details about the final mesh.
D02TYF can be used to compute the approximate solution anywhere on the interval
using interpolation.
The routines are based on modified versions of the codes COLSYS and COLNEW (see
Ascher et al. (1979) and
Ascher and Bader (1987)). A comprehensive treatment of the numerical solution of boundary value problems can be found in
Ascher et al. (1988) and
Keller (1992).
4 References
Ascher U M and Bader G (1987) A new basis implementation for a mixed order boundary value ODE solver SIAM J. Sci. Stat. Comput. 8 483–500
Ascher U M, Christiansen J and Russell R D (1979) A collocation solver for mixed order systems of boundary value problems Math. Comput. 33 659–679
Ascher U M, Mattheij R M M and Russell R D (1988) Numerical Solution of Boundary Value Problems for Ordinary Differential Equations Prentice–Hall
Cole J D (1968) Perturbation Methods in Applied Mathematics Blaisdell, Waltham, Mass.
Keller H B (1992) Numerical Methods for Two-point Boundary-value Problems Dover, New York
5 Parameters
- 1: – INTEGERInput
-
On entry: the maximum number of points allowed in the mesh.
Constraint:
this must be identical to the value supplied for the parameter
MXMESH in the prior call to
D02TVF.
- 2: – INTEGEROutput
-
On exit: the number of points in the mesh last used by
D02TLF.
- 3: – REAL (KIND=nag_wp) arrayOutput
-
On exit:
contains the
th point of the mesh last used by
D02TLF, for
.
will contain
and
will contain
. The remaining elements of
MESH are not initialized.
- 4: – INTEGER arrayOutput
-
On exit:
specifies the nature of the point
, for
, in the final mesh computed by
D02TLF.
- Indicates that the th point is a fixed point and was used by the solver before an extrapolation-like error test.
- Indicates that the th point was used by the solver before an extrapolation-like error test.
- Indicates that the th point was used by the solver only as part of an extrapolation-like error test.
The remaining elements of
IPMESH are initialized to
.
See
Section 9 for advice on how these values may be used in conjunction with a continuation process.
- 5: – REAL (KIND=nag_wp)Output
-
On exit: an estimate of the maximum error in the solution computed by
D02TLF, that is
where
is the approximate solution for the
th solution component. If
D02TLF returned successfully with
, then
ERMX will be less than
where
TOLS contains the error requirements as specified in
Sections 3 and
5 in D02TVF.
If
D02TLF returned with
, then
ERMX will be greater than
.
If
D02TLF returned any other value for
IFAIL
then an error estimate is not available and
ERMX is initialized to
.
- 6: – INTEGEROutput
-
On exit: indicates the mesh sub-interval where the value of
ERMX has been computed, that is
.
If an estimate of the error is not available then
IERMX is initialized to
.
- 7: – INTEGEROutput
-
On exit: indicates the component
(
) of the solution for which
ERMX has been computed, that is the approximation of
on
is estimated to have the largest error of all components
over mesh sub-intervals defined by
MESH.
If an estimate of the error is not available then
IJERMX is initialized to
.
- 8: – REAL (KIND=nag_wp) arrayCommunication Array
-
Note: the dimension of this array is dictated by the requirements of associated functions that must have been previously called. This array
must be the same array passed as argument
RCOMM in the previous call to
D02TLF.
On entry: this must be the same array as supplied to
D02TLF and
must remain unchanged between calls.
On exit: contains information about the solution for use on subsequent calls to associated routines.
- 9: – INTEGER arrayCommunication Array
-
Note: the dimension of this array is dictated by the requirements of associated functions that must have been previously called. This array
must be the same array passed as argument
ICOMM in the previous call to
D02TLF.
On entry: this must be the same array as supplied to
D02TLF and
must remain unchanged between calls.
On exit: contains information about the solution for use on subsequent calls to associated routines.
- 10: – INTEGERInput/Output
-
On entry:
IFAIL must be set to
,
. If you are unfamiliar with this parameter you should refer to
Section 3.3 in the Essential Introduction for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value
is recommended. If the output of error messages is undesirable, then the value
is recommended. Otherwise, because for this routine the values of the output parameters may be useful even if
on exit, the recommended value is
.
When the value is used it is essential to test the value of IFAIL on exit.
On exit:
unless the routine detects an error or a warning has been flagged (see
Section 6).
6 Error Indicators and Warnings
If on entry
or
, explanatory error messages are output on the current error message unit (as defined by
X04AAF).
Note: D02TZF may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the routine:
-
On entry, an illegal value for
MXMESH was specified, or an invalid call to D02TZF was made, for example without a previous call to the solver routine
D02TLF.
-
The solver routine
D02TLF did not converge to a solution or did not satisfy the error requirements. The last mesh computed by
D02TLF has been returned by D02TZF. This mesh should be treated with extreme caution as nothing can be said regarding its quality or suitability for any subsequent computation.
An unexpected error has been triggered by this routine. Please
contact
NAG.
See
Section 3.8 in the Essential Introduction for further information.
Your licence key may have expired or may not have been installed correctly.
See
Section 3.7 in the Essential Introduction for further information.
Dynamic memory allocation failed.
See
Section 3.6 in the Essential Introduction for further information.
7 Accuracy
Not applicable.
8 Parallelism and Performance
Not applicable.
Note that:
- if D02TLF returned , or then it will always be the case that ;
- if D02TLF returned or then it will always be the case that
, for (even ) and
or , for (odd );
- if D02TLF returned then it will always be the case that
, for .
If D02TZF returns
, then examination of the mesh may provide assistance in determining a suitable starting mesh for
D02TVF in any subsequent attempts to solve similar problems.
If the problem being treated by
D02TLF is one of a series of related problems (for example, as part of a continuation process), then the values of
IPMESH and
MESH may be suitable as input parameters to
D02TXF. Using the mesh points not involved in the extrapolation error test is usually appropriate.
IPMESH and
MESH should be passed unchanged to
D02TXF but
NMESH should be replaced by
.
If D02TZF returns
, nothing can be said regarding the quality of the mesh returned. However, it may be a useful starting mesh for
D02TVF in any subsequent attempts to solve the same problem.
If
D02TLF returns
, this corresponds to the solver requiring more than
MXMESH mesh points to satisfy the error requirements. If
MXMESH can be increased and the preceding call to
D02TLF was not part, or was the first part, of a continuation process then the values in
MESH may provide a suitable mesh with which to initialize a subsequent attempt to solve the same problem. If it is not possible to provide more mesh points then relaxing the error requirements by setting
to
ERMX might lead to a successful solution. It may be necessary to reset the other components of
TOLS. Note that resetting the tolerances can lead to a different sequence of meshes being computed and hence to a different solution being computed.
10 Example
The following example is used to illustrate the use of fixed mesh points, simple continuation and numerical approximation of a Jacobian. See also
D02TLF,
D02TVF,
D02TXF and
D02TYF, for the illustration of other facilities.
Consider the Lagerstrom–Cole equation
with the boundary conditions
where
is small and positive. The nature of the solution depends markedly on the values of
. See
Cole (1968).
We choose
for which the solution is known to have corner layers at
. We choose an initial mesh of seven points
and ensure that the points
near the corner layers are fixed, that is the corresponding elements of the array
IPMESH are set to
. First we compute the solution for
using in
GUESS the initial approximation
which satisfies the boundary conditions. Then we use simple continuation to compute the solution for
. We use the suggested values for
NMESH,
IPMESH and
MESH in the call to
D02TXF prior to the continuation call, that is only every second point of the preceding mesh is used and the fixed mesh points are retained.
Although the analytic Jacobian for this system is easy to evaluate, for illustration the procedure
FJAC uses central differences and calls to
FFUN to compute a numerical approximation to the Jacobian.
10.1 Program Text
Program Text (d02tzfe.f90)
10.2 Program Data
Program Data (d02tzfe.d)
10.3 Program Results
Program Results (d02tzfe.r)