NAG Library Routine Document
d02gbf
(bvp_fd_lin_gen)
1
Purpose
d02gbf solves a general linear twopoint boundary value problem for a system of ordinary differential equations, using a deferred correction technique.
2
Specification
Fortran Interface
Subroutine d02gbf ( 
a,
b,
n,
tol,
fcnf,
fcng,
c,
d,
gam,
mnp,
x,
y,
np,
w,
lw,
iw,
liw,
ifail) 
Integer, Intent (In)  :: 
n,
mnp,
lw,
liw  Integer, Intent (Inout)  :: 
np,
ifail  Integer, Intent (Out)  :: 
iw(liw)  Real (Kind=nag_wp), Intent (In)  :: 
a,
b,
tol  Real (Kind=nag_wp), Intent (Inout)  :: 
c(n,n),
d(n,n),
gam(n),
x(mnp)  Real (Kind=nag_wp), Intent (Out)  :: 
y(n,mnp),
w(lw)  External  :: 
fcnf,
fcng 

C Header Interface
#include nagmk26.h
void 
d02gbf_ (
const double *a,
const double *b,
const Integer *n,
const double *tol,
void (NAG_CALL *fcnf)(
const double *x,
double f[]),
void (NAG_CALL *fcng)(
const double *x,
double g[]),
double c[],
double d[],
double gam[],
const Integer *mnp,
double x[],
double y[],
Integer *np,
double w[],
const Integer *lw,
Integer iw[],
const Integer *liw,
Integer *ifail) 

3
Description
d02gbf solves a linear twopoint boundary value problem for a system of
$\mathit{n}$ ordinary differential equations in the interval [
$a,b$]. The system is written in the form
and the boundary conditions are written in the form
Here
$F\left(x\right)$,
$C$ and
$D$ are
$\mathit{n}$ by
$\mathit{n}$ matrices, and
$g\left(x\right)$ and
$\gamma $ are
$\mathit{n}$component vectors. The approximate solution to
(1) and
(2) is found using a finite difference method with deferred correction. The algorithm is a specialization of that used in subroutine
d02raf which solves a nonlinear version of
(1) and
(2). The nonlinear version of the algorithm is described fully in
Pereyra (1979).
You supply an absolute error tolerance and may also supply an initial mesh for the construction of the finite difference equations (alternatively a default mesh is used). The algorithm constructs a solution on a mesh defined by adding points to the initial mesh. This solution is chosen so that the error is everywhere less than your tolerance and so that the error is approximately equidistributed on the final mesh. The solution is returned on this final mesh.
If the solution is required at a few specific points then these should be included in the initial mesh. If, on the other hand, the solution is required at several specific points, then you should use the interpolation routines provided in
Chapter E01 if these points do not themselves form a convenient mesh.
4
References
Pereyra V (1979) PASVA3: An adaptive finitedifference Fortran program for first order nonlinear, ordinary boundary problems Codes for Boundary Value Problems in Ordinary Differential Equations. Lecture Notes in Computer Science (eds B Childs, M Scott, J W Daniel, E Denman and P Nelson) 76 Springer–Verlag
5
Arguments
 1: $\mathbf{a}$ – Real (Kind=nag_wp)Input

On entry: $a$, the lefthand boundary point.
 2: $\mathbf{b}$ – Real (Kind=nag_wp)Input

On entry: $b$, the righthand boundary point.
Constraint:
${\mathbf{b}}>{\mathbf{a}}$.
 3: $\mathbf{n}$ – IntegerInput

On entry: the number of equations; that is
$\mathit{n}$ is the order of system
(1).
Constraint:
${\mathbf{n}}\ge 2$.
 4: $\mathbf{tol}$ – Real (Kind=nag_wp)Input

On entry: a positive absolute error tolerance. If
is the final mesh,
$z\left(x\right)$ is the approximate solution from
d02gbf and
$y\left(x\right)$ is the true solution of equations
(1) and
(2) then, except in extreme cases, it is expected that
where
Constraint:
${\mathbf{tol}}>0.0$.
 5: $\mathbf{fcnf}$ – Subroutine, supplied by the user.External Procedure

fcnf must evaluate the matrix
$F\left(x\right)$ in
(1) at a general point
$x$.
The specification of
fcnf is:
Fortran Interface
Real (Kind=nag_wp), Intent (In)  :: 
x  Real (Kind=nag_wp), Intent (Out)  :: 
f(*) 

C Header Interface
#include nagmk26.h
void 
fcnf (
const double *x,
double f[]) 

In the description of the arguments of
d02gbf below,
$\mathit{n}$ denotes the actual value of
n in the call of
d02gbf.
 1: $\mathbf{x}$ – Real (Kind=nag_wp)Input

On entry: $x$, the value of the independent variable.
 2: $\mathbf{f}\left(*\right)$ – Real (Kind=nag_wp) arrayOutput

On exit:
${\mathbf{f}}\left(\mathit{n}\times \left(\mathit{i}1\right)+\mathit{j}\right)$ must contain the
$\left(\mathit{i},\mathit{j}\right)$th element of the matrix
$F\left(x\right)$, for
$\mathit{i}=1,2,\dots ,\mathit{n}$ and
$\mathit{j}=1,2,\dots ,\mathit{n}$. (See
Section 10 for an example.)
fcnf must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which
d02gbf is called. Arguments denoted as
Input must
not be changed by this procedure.
Note: fcnf should not return floatingpoint NaN (Not a Number) or infinity values, since these are not handled by
d02gbf. If your code inadvertently
does return any NaNs or infinities,
d02gbf is likely to produce unexpected results.
 6: $\mathbf{fcng}$ – Subroutine, supplied by the user.External Procedure

fcng must evaluate the vector
$g\left(x\right)$ in
(1) at a general point
$x$.
The specification of
fcng is:
Fortran Interface
Real (Kind=nag_wp), Intent (In)  :: 
x  Real (Kind=nag_wp), Intent (Out)  :: 
g(*) 

C Header Interface
#include nagmk26.h
void 
fcng (
const double *x,
double g[]) 

In the description of the arguments of
d02gbf below,
$\mathit{n}$ denotes the actual value of
n in the call of
d02gbf.
 1: $\mathbf{x}$ – Real (Kind=nag_wp)Input

On entry: $x$, the value of the independent variable.
 2: $\mathbf{g}\left(*\right)$ – Real (Kind=nag_wp) arrayOutput

On exit: the
$\mathit{i}$th element of the vector
$g\left(x\right)$, for
$\mathit{i}=1,2,\dots ,\mathit{n}$. (See
Section 10 for an example.)
fcng must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which
d02gbf is called. Arguments denoted as
Input must
not be changed by this procedure.
Note: fcng should not return floatingpoint NaN (Not a Number) or infinity values, since these are not handled by
d02gbf. If your code inadvertently
does return any NaNs or infinities,
d02gbf is likely to produce unexpected results.
 7: $\mathbf{c}\left({\mathbf{n}},{\mathbf{n}}\right)$ – Real (Kind=nag_wp) arrayInput/Output
 8: $\mathbf{d}\left({\mathbf{n}},{\mathbf{n}}\right)$ – Real (Kind=nag_wp) arrayInput/Output
 9: $\mathbf{gam}\left({\mathbf{n}}\right)$ – Real (Kind=nag_wp) arrayInput/Output

On entry: the arrays
c and
d must be set to the matrices
$C$ and
$D$ in
(2)).
gam must be set to the vector
$\gamma $ in
(2).
On exit: the rows of
c and
d and the components of
gam are reordered so that the boundary conditions are in the order:
(i) 
conditions on $y\left(a\right)$ only; 
(ii) 
condition involving $y\left(a\right)$ and $y\left(b\right)$; and 
(iii) 
conditions on $y\left(b\right)$ only. 
The routine will be slightly more efficient if the arrays
c,
d and
gam are ordered in this way before entry, and in this event they will be unchanged on exit.
Note that the problems
(1) and
(2) must be of boundary value type, that is neither
$C$ nor
$D$ may be identically zero. Note also that the rank of the matrix
$\left[C,D\right]$ must be
$\mathit{n}$ for the problem to be properly posed. Any violation of these conditions will lead to an error exit.
 10: $\mathbf{mnp}$ – IntegerInput

On entry: the maximum permitted number of mesh points.
Constraint:
${\mathbf{mnp}}\ge 32$.
 11: $\mathbf{x}\left({\mathbf{mnp}}\right)$ – Real (Kind=nag_wp) arrayInput/Output

On entry: if
${\mathbf{np}}\ge 4$ (see
np), the first
np elements must define an initial mesh. Otherwise the elements of
$x$ need not be set.
On exit:
${\mathbf{x}}\left(1\right),{\mathbf{x}}\left(2\right),\dots ,{\mathbf{x}}\left({\mathbf{np}}\right)$ define the final mesh (with the returned value of
np) satisfying the relation
(4).
 12: $\mathbf{y}\left({\mathbf{n}},{\mathbf{mnp}}\right)$ – Real (Kind=nag_wp) arrayOutput

On exit: the approximate solution
$z\left(x\right)$ satisfying
(3), on the final mesh, that is
where
np is the number of points in the final mesh.
The remaining columns of
y are not used.
 13: $\mathbf{np}$ – IntegerInput/Output

On entry: determines whether a default mesh or usersupplied mesh is used.
 ${\mathbf{np}}=0$
 A default value of $4$ for np and a corresponding equispaced mesh ${\mathbf{x}}\left(1\right),{\mathbf{x}}\left(2\right),\dots ,{\mathbf{x}}\left({\mathbf{np}}\right)$ are used.
 ${\mathbf{np}}\ge 4$
 You must define an initial mesh x as in (4).
On exit: the number of points in the final (returned) mesh.
 14: $\mathbf{w}\left({\mathbf{lw}}\right)$ – Real (Kind=nag_wp) arrayWorkspace
 15: $\mathbf{lw}$ – IntegerInput

On entry: the dimension of the array
w as declared in the (sub)program from which
d02gbf is called.
Constraint:
${\mathbf{lw}}\ge {\mathbf{mnp}}\times \left(3{{\mathbf{n}}}^{2}+5{\mathbf{n}}+2\right)+3{{\mathbf{n}}}^{2}+5{\mathbf{n}}$.
 16: $\mathbf{iw}\left({\mathbf{liw}}\right)$ – Integer arrayWorkspace
 17: $\mathbf{liw}$ – IntegerInput

On entry: the dimension of the array
iw as declared in the (sub)program from which
d02gbf is called.
Constraint:
${\mathbf{liw}}\ge {\mathbf{mnp}}\times \left(2{\mathbf{n}}+1\right)+{\mathbf{n}}$.
 18: $\mathbf{ifail}$ – IntegerInput/Output

For this routine, the normal use of
ifail is extended to control the printing of error and warning messages as well as specifying hard or soft failure (see
Section 3.4 in How to Use the NAG Library and its Documentation).
On entry:
ifail must be set to a value with the decimal expansion
$\mathit{cba}$, where each of the decimal digits
$c$,
$b$ and
$a$ must have a value of
$0$ or
$1$.
$a=0$ 
specifies hard failure, otherwise soft failure; 
$b=0$ 
suppresses error messages, otherwise error messages will be printed (see Section 6); 
$c=0$ 
suppresses warning messages, otherwise warning messages will be printed (see Section 6). 
The recommended value for inexperienced users is $110$ (i.e., hard failure with all messages printed).
On exit:
${\mathbf{ifail}}={\mathbf{0}}$ unless the routine detects an error or a warning has been flagged (see
Section 6).
6
Error Indicators and Warnings
If on entry
${\mathbf{ifail}}=0$ or
$1$, explanatory error messages are output on the current error message unit (as defined by
x04aaf).
Errors or warnings detected by the routine:
 ${\mathbf{ifail}}=1$

One or more of the arguments
n,
tol,
np,
mnp,
lw or
liw is incorrectly set,
${\mathbf{b}}\le {\mathbf{a}}$ or the condition
(4) on
x is not satisfied.
 ${\mathbf{ifail}}=2$

There are three possible reasons for this error exit to be taken:
(i) 
one of the matrices $C$ or $D$ is identically zero (that is, the problem is of initial value and not boundary value type). In this case, ${\mathbf{iw}}\left(1\right)=0$ on exit; 
(ii) 
a row of $C$ and the corresponding row of $D$ are identically zero (that is, the boundary conditions are rank deficient). In this case, on exit ${\mathbf{iw}}\left(1\right)$ contains the index of the first such row encountered; and 
(iii) 
more than $\mathit{n}$ of the columns of the $\mathit{n}$ by $2\mathit{n}$ matrix $\left[C,D\right]$ are identically zero (that is, the boundary conditions are rank deficient). In this case, on exit ${\mathbf{iw}}\left(1\right)$ contains minus the number of nonidentically zero columns. 
 ${\mathbf{ifail}}=3$

The routine has failed to find a solution to the specified accuracy. There are a variety of possible reasons including:
(i) 
the boundary conditions are rank deficient, which may be indicated by the message that the Jacobian is singular. However this is an unlikely explanation for the error exit as all rank deficient boundary conditions should lead instead to error exits with either ${\mathbf{ifail}}={\mathbf{2}}$ or ${\mathbf{5}}$; see also (iv); 
(ii) 
not enough mesh points are permitted in order to attain the required accuracy. This is indicated by ${\mathbf{np}}={\mathbf{mnp}}$ on return from a call to d02gbf. This difficulty may be aggravated by a poor initial choice of mesh points; 
(iii) 
the accuracy requested cannot be attained on the computer being used; and 
(iv) 
an unlikely combination of values of $Fx$ has led to a singular Jacobian. The error should not persist if more mesh points are allowed. 
 ${\mathbf{ifail}}=4$

A serious error has occurred in a call to d02gbf. Check all array subscripts and subroutine argument lists in calls to d02gbf. Seek expert help.
 ${\mathbf{ifail}}=5$

There are two possible reasons for this error exit which occurs when checking the rank of the boundary conditions by reduction to a row echelon form:
(i) 
at least one row of the $\mathit{n}$ by $2\mathit{n}$ matrix $\left[C,D\right]$ is a linear combination of the other rows and hence the boundary conditions are rank deficient. The index of the first such row encountered is given by ${\mathbf{iw}}\left(1\right)$ on exit; and 
(ii) 
as (i) but the rank deficiency implied by this error exit has only been determined up to a numerical tolerance. Minus the index of the first such row encountered is given by ${\mathbf{iw}}\left(1\right)$ on exit. 
In case
(ii) there is some doubt as to the rank deficiency of the boundary conditions. However even if the boundary conditions are not rank deficient they are not posed in a suitable form for use with this routine.
For example, if
and
$\epsilon $ is small enough, this error exit is likely to be taken. A better form for the boundary conditions in this case would be
 ${\mathbf{ifail}}=99$
An unexpected error has been triggered by this routine. Please
contact
NAG.
See
Section 3.9 in How to Use the NAG Library and its Documentation for further information.
 ${\mathbf{ifail}}=399$
Your licence key may have expired or may not have been installed correctly.
See
Section 3.8 in How to Use the NAG Library and its Documentation for further information.
 ${\mathbf{ifail}}=999$
Dynamic memory allocation failed.
See
Section 3.7 in How to Use the NAG Library and its Documentation for further information.
7
Accuracy
The solution returned by the routine will be accurate to your tolerance as defined by the relation
(3) except in extreme circumstances. If too many points are specified in the initial mesh, the solution may be more accurate than requested and the error may not be approximately equidistributed.
8
Parallelism and Performance
d02gbf is not thread safe and should not be called from a multithreaded user program. Please see
Section 3.12.1 in How to Use the NAG Library and its Documentation for more information on thread safety.
d02gbf 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 implementationspecific information.
The time taken by d02gbf depends on the difficulty of the problem, the number of mesh points (and meshes) used and the number of deferred corrections.
You are strongly recommended to set
ifail to obtain selfexplanatory error messages, and also monitoring information about the course of the computation. You may select the unit numbers on which this output is to appear by calls of
x04aaf (for error messages) or
x04abf (for monitoring information) – see
Section 10 for an example. Otherwise the default unit numbers will be used, as specified in the
Users' Note.
In the case where you wish to solve a sequence of similar problems, the final mesh from solving one case is strongly recommended as the initial mesh for the next.
10
Example
This example solves the problem (written as a firstorder system)
with boundary conditions
for the cases
$\epsilon ={10}^{1}$ and
$\epsilon ={10}^{2}$ using the default initial mesh in the first case, and the final mesh of the first case as initial mesh for the second (more difficult) case. We give the solution and the error at each mesh point to illustrate the accuracy of the method given the accuracy request
${\mathbf{tol}}=\text{1.0E\u22123}$.
Note the call to
x04abf prior to the call to
d02gbf.
10.1
Program Text
Program Text (d02gbfe.f90)
10.2
Program Data
Program Data (d02gbfe.d)
10.3
Program Results
Program Results (d02gbfe.r)