NAG FL Interface
d03pkf (dim1_parab_dae_keller)
1
Purpose
d03pkf integrates a system of linear or nonlinear, first-order, time-dependent partial differential equations (PDEs) in one space variable, with scope for coupled ordinary differential equations (ODEs). The spatial discretization is performed using the Keller box scheme and the method of lines is employed to reduce the PDEs to a system of ODEs. The resulting system is solved using a Backward Differentiation Formula (BDF) method or a Theta method (switching between Newton's method and functional iteration).
2
Specification
Fortran Interface
Subroutine d03pkf ( |
npde, ts, tout, pdedef, bndary, u, npts, x, nleft, nv, odedef, nxi, xi, neqn, rtol, atol, itol, norm, laopt, algopt, rsave, lrsave, isave, lisave, itask, itrace, ind, ifail) |
Integer, Intent (In) |
:: |
npde, npts, nleft, nv, nxi, neqn, itol, lrsave, lisave, itask, itrace |
Integer, Intent (Inout) |
:: |
isave(lisave), ind, ifail |
Real (Kind=nag_wp), Intent (In) |
:: |
tout, x(npts), xi(nxi), rtol(*), atol(*), algopt(30) |
Real (Kind=nag_wp), Intent (Inout) |
:: |
ts, u(neqn), rsave(lrsave) |
Character (1), Intent (In) |
:: |
norm, laopt |
External |
:: |
pdedef, bndary, odedef |
|
C Header Interface
#include <nag.h>
void |
d03pkf_ (const Integer *npde, double *ts, const double *tout, void (NAG_CALL *pdedef)(const Integer *npde, const double *t, const double *x, const double u[], const double ut[], const double ux[], const Integer *nv, const double v[], const double vdot[], double res[], Integer *ires), void (NAG_CALL *bndary)(const Integer *npde, const double *t, const Integer *ibnd, const Integer *nobc, const double u[], const double ut[], const Integer *nv, const double v[], const double vdot[], double res[], Integer *ires), double u[], const Integer *npts, const double x[], const Integer *nleft, const Integer *nv, void (NAG_CALL *odedef)(const Integer *npde, const double *t, const Integer *nv, const double v[], const double vdot[], const Integer *nxi, const double xi[], const double ucp[], const double ucpx[], const double ucpt[], double r[], Integer *ires), const Integer *nxi, const double xi[], const Integer *neqn, const double rtol[], const double atol[], const Integer *itol, const char *norm, const char *laopt, const double algopt[], double rsave[], const Integer *lrsave, Integer isave[], const Integer *lisave, const Integer *itask, const Integer *itrace, Integer *ind, Integer *ifail, const Charlen length_norm, const Charlen length_laopt) |
|
C++ Header Interface
#include <nag.h> extern "C" {
void |
d03pkf_ (const Integer &npde, double &ts, const double &tout, void (NAG_CALL *pdedef)(const Integer &npde, const double &t, const double &x, const double u[], const double ut[], const double ux[], const Integer &nv, const double v[], const double vdot[], double res[], Integer &ires), void (NAG_CALL *bndary)(const Integer &npde, const double &t, const Integer &ibnd, const Integer &nobc, const double u[], const double ut[], const Integer &nv, const double v[], const double vdot[], double res[], Integer &ires), double u[], const Integer &npts, const double x[], const Integer &nleft, const Integer &nv, void (NAG_CALL *odedef)(const Integer &npde, const double &t, const Integer &nv, const double v[], const double vdot[], const Integer &nxi, const double xi[], const double ucp[], const double ucpx[], const double ucpt[], double r[], Integer &ires), const Integer &nxi, const double xi[], const Integer &neqn, const double rtol[], const double atol[], const Integer &itol, const char *norm, const char *laopt, const double algopt[], double rsave[], const Integer &lrsave, Integer isave[], const Integer &lisave, const Integer &itask, const Integer &itrace, Integer &ind, Integer &ifail, const Charlen length_norm, const Charlen length_laopt) |
}
|
The routine may be called by the names d03pkf or nagf_pde_dim1_parab_dae_keller.
3
Description
d03pkf integrates the system of first-order PDEs and coupled ODEs
In the PDE part of the problem given by
(1), the functions
must have the general form
where
,
and
depend on
and
.
The vector
is the set of PDE solution values
and the vector
is the partial derivative with respect to
. The vector
is the set of ODE solution values
and
denotes its derivative with respect to time.
In the ODE part given by
(2),
represents a vector of
spatial coupling points at which the ODEs are coupled to the PDEs. These points may or may not be equal to some of the PDE spatial mesh points.
,
and
are the functions
,
and
evaluated at these coupling points. Each
may only depend linearly on time derivatives. Hence equation
(2) may be written more precisely as
where
,
is a vector of length
nv,
is an
nv by
nv matrix,
is an
nv by
matrix. The entries in
,
and
may depend on
,
,
,
and
. In practice you only need to supply a vector of information to define the ODEs and not the matrices
and
. (See
Section 5 for the specification of
odedef.)
The integration in time is from to , over the space interval , where and are the leftmost and rightmost points of a user-defined mesh .
The PDE system which is defined by the functions
must be specified in
pdedef.
The initial values of the functions and must be given at .
For a first-order system of PDEs, only one boundary condition is required for each PDE component
. The
npde boundary conditions are separated into
at the left-hand boundary
, and
at the right-hand boundary
, such that
. The position of the boundary condition for each component should be chosen with care; the general rule is that if the characteristic direction of
at the left-hand boundary (say) points into the interior of the solution domain, then the boundary condition for
should be specified at the left-hand boundary. Incorrect positioning of boundary conditions generally results in initialization or integration difficulties in the underlying time integration routines.
The boundary conditions have the form:
at the left-hand boundary, and
at the right-hand boundary.
Note that the functions
and
must not depend on
, since spatial derivatives are not determined explicitly in the Keller box scheme. If the problem involves derivative (Neumann) boundary conditions then it is generally possible to restate such boundary conditions in terms of permissible variables. Also note that
and
must be linear with respect to time derivatives, so that the boundary conditions have the general form:
at the left-hand boundary, and
at the right-hand boundary, where
,
,
,
,
and
depend on
and
only.
The boundary conditions must be specified in
bndary.
The problem is subject to the following restrictions:
-
(i), and must not depend on any time derivatives;
-
(ii), so that integration is in the forward direction;
-
(iii)The evaluation of the function is done approximately at the mid-points of the mesh
, for , by calling the pdedef for each mid-point in turn. Any discontinuities in the function must therefore be at one or more of the mesh points ;
-
(iv)At least one of the functions must be nonzero so that there is a time derivative present in the PDE problem.
The algebraic-differential equation system which is defined by the functions
must be specified in
odedef. You must also specify the coupling points
in the array
xi.
The parabolic equations are approximated by a system of ODEs in time for the values of
at mesh points. In this method of lines approach the Keller box scheme (see
Keller (1970)) is applied to each PDE in the space variable only, resulting in a system of ODEs in time for the values of
at each mesh point. In total there are
ODEs in time direction. This system is then integrated forwards in time using a Backward Differentiation Formula (BDF) or a Theta method.
4
References
Berzins M (1990) Developments in the NAG Library software for parabolic equations Scientific Software Systems (eds J C Mason and M G Cox) 59–72 Chapman and Hall
Berzins M, Dew P M and Furzeland R M (1989) Developing software for time-dependent problems using the method of lines and differential-algebraic integrators Appl. Numer. Math. 5 375–397
Berzins M and Furzeland R M (1992) An adaptive theta method for the solution of stiff and nonstiff differential equations Appl. Numer. Math. 9 1–19
Keller H B (1970) A new difference scheme for parabolic problems Numerical Solutions of Partial Differential Equations (ed J Bramble) 2 327–350 Academic Press
Pennington S V and Berzins M (1994) New NAG Library software for first-order partial differential equations ACM Trans. Math. Softw. 20 63–99
5
Arguments
-
1:
– Integer
Input
-
On entry: the number of PDEs to be solved.
Constraint:
.
-
2:
– Real (Kind=nag_wp)
Input/Output
-
On entry: the initial value of the independent variable .
Constraint:
.
On exit: the value of
corresponding to the solution in
u. Normally
.
-
3:
– Real (Kind=nag_wp)
Input
-
On entry: the final value of to which the integration is to be carried out.
-
4:
– Subroutine, supplied by the user.
External Procedure
-
pdedef must evaluate the functions
which define the system of PDEs.
pdedef is called approximately midway between each pair of mesh points in turn by
d03pkf.
The specification of
pdedef is:
Fortran Interface
Subroutine pdedef ( |
npde, t, x, u, ut, ux, nv, v, vdot, res, ires) |
Integer, Intent (In) |
:: |
npde, nv |
Integer, Intent (Inout) |
:: |
ires |
Real (Kind=nag_wp), Intent (In) |
:: |
t, x, u(npde), ut(npde), ux(npde), v(nv), vdot(nv) |
Real (Kind=nag_wp), Intent (Out) |
:: |
res(npde) |
|
C Header Interface
void |
pdedef_ (const Integer *npde, const double *t, const double *x, const double u[], const double ut[], const double ux[], const Integer *nv, const double v[], const double vdot[], double res[], Integer *ires) |
|
C++ Header Interface
#include <nag.h> extern "C" {
void |
pdedef_ (const Integer &npde, const double &t, const double &x, const double u[], const double ut[], const double ux[], const Integer &nv, const double v[], const double vdot[], double res[], Integer &ires) |
}
|
-
1:
– Integer
Input
-
On entry: the number of PDEs in the system.
-
2:
– Real (Kind=nag_wp)
Input
-
On entry: the current value of the independent variable .
-
3:
– Real (Kind=nag_wp)
Input
-
On entry: the current value of the space variable .
-
4:
– Real (Kind=nag_wp) array
Input
-
On entry: contains the value of the component , for .
-
5:
– Real (Kind=nag_wp) array
Input
-
On entry: contains the value of the component , for .
-
6:
– Real (Kind=nag_wp) array
Input
-
On entry: contains the value of the component , for .
-
7:
– Integer
Input
-
On entry: the number of coupled ODEs in the system.
-
8:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of the component , for .
-
9:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of component , for .
-
10:
– Real (Kind=nag_wp) array
Output
-
On exit:
must contain the
th component of
, for
, where
is defined as
i.e., only terms depending explicitly on time derivatives, or
i.e., all terms in equation
(3).
The definition of
is determined by the input value of
ires.
-
11:
– Integer
Input/Output
-
On entry: the form of
that must be returned in the array
res.
- Equation (9) must be used.
- Equation (10) must be used.
On exit: should usually remain unchanged. However, you may set
ires to force the integration routine to take certain actions, as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , d03pkf returns to the calling subroutine with the error indicator set to .
pdedef must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which
d03pkf is called. Arguments denoted as
Input must
not be changed by this procedure.
Note: pdedef should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by
d03pkf. If your code inadvertently
does return any NaNs or infinities,
d03pkf is likely to produce unexpected results.
-
5:
– Subroutine, supplied by the user.
External Procedure
-
bndary must evaluate the functions
and
which describe the boundary conditions, as given in
(5) and
(6).
The specification of
bndary is:
Fortran Interface
Subroutine bndary ( |
npde, t, ibnd, nobc, u, ut, nv, v, vdot, res, ires) |
Integer, Intent (In) |
:: |
npde, ibnd, nobc, nv |
Integer, Intent (Inout) |
:: |
ires |
Real (Kind=nag_wp), Intent (In) |
:: |
t, u(npde), ut(npde), v(nv), vdot(nv) |
Real (Kind=nag_wp), Intent (Out) |
:: |
res(nobc) |
|
C Header Interface
void |
bndary_ (const Integer *npde, const double *t, const Integer *ibnd, const Integer *nobc, const double u[], const double ut[], const Integer *nv, const double v[], const double vdot[], double res[], Integer *ires) |
|
C++ Header Interface
#include <nag.h> extern "C" {
void |
bndary_ (const Integer &npde, const double &t, const Integer &ibnd, const Integer &nobc, const double u[], const double ut[], const Integer &nv, const double v[], const double vdot[], double res[], Integer &ires) |
}
|
-
1:
– Integer
Input
-
On entry: the dimension of the array
u and the dimension of the array
ut as declared in the (sub)program from which
d03pkf is called. The number of PDEs in the system.
-
2:
– Real (Kind=nag_wp)
Input
-
On entry: the current value of the independent variable .
-
3:
– Integer
Input
-
On entry: specifies which boundary conditions are to be evaluated.
- bndary must compute the left-hand boundary condition at .
- bndary must compute the right-hand boundary condition at .
-
4:
– Integer
Input
-
On entry: specifies the number of boundary conditions at the boundary specified by
ibnd.
-
5:
– Real (Kind=nag_wp) array
Input
-
On entry:
contains the value of the component
at the boundary specified by
ibnd, for
.
-
6:
– Real (Kind=nag_wp) array
Input
-
On entry:
contains the value of the component
at the boundary specified by
ibnd, for
.
-
7:
– Integer
Input
-
On entry: the number of coupled ODEs in the system.
-
8:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of the component , for .
-
9:
– Real (Kind=nag_wp) array
Input
-
On entry: if
,
contains the value of component
, for
.
Note:
, for
, may only appear linearly as in
(7) and
(8).
-
10:
– Real (Kind=nag_wp) array
Output
-
On exit:
must contain the
th component of
or
, depending on the value of
ibnd, for
, where
is defined as
i.e., only terms depending explicitly on time derivatives, or
i.e., all terms in equation
(7), and similarly for
.
The definitions of
and
are determined by the input value of
ires.
-
11:
– Integer
Input/Output
-
On entry: the form of
(or
) that must be returned in the array
res.
- Equation (11) must be used.
- Equation (12) must be used.
On exit: should usually remain unchanged. However, you may set
ires to force the integration routine to take certain actions as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , d03pkf returns to the calling subroutine with the error indicator set to .
bndary must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which
d03pkf is called. Arguments denoted as
Input must
not be changed by this procedure.
Note: bndary should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by
d03pkf. If your code inadvertently
does return any NaNs or infinities,
d03pkf is likely to produce unexpected results.
-
6:
– Real (Kind=nag_wp) array
Input/Output
-
On entry: the initial values of the dependent variables defined as follows:
-
contain , for and , and
-
contain , for .
On exit: the computed solution
, for
and
, and
, for
, evaluated at
, as follows:
-
contain , for and , and
-
contain , for .
-
7:
– Integer
Input
-
On entry: the number of mesh points in the interval .
Constraint:
.
-
8:
– Real (Kind=nag_wp) array
Input
-
On entry: the mesh points in the space direction. must specify the left-hand boundary, , and must specify the right-hand boundary, .
Constraint:
.
-
9:
– Integer
Input
-
On entry: the number of boundary conditions at the left-hand mesh point .
Constraint:
.
-
10:
– Integer
Input
-
On entry: the number of coupled ODE components.
Constraint:
.
-
11:
– Subroutine, supplied by the NAG Library or the user.
External Procedure
-
odedef must evaluate the functions
, which define the system of ODEs, as given in
(4).
If you wish to compute the solution of a system of PDEs only (i.e.,
),
odedef must be the dummy routine
d03pek. (
d03pek is included in the NAG Library.)
The specification of
odedef is:
Fortran Interface
Subroutine odedef ( |
npde, t, nv, v, vdot, nxi, xi, ucp, ucpx, ucpt, r, ires) |
Integer, Intent (In) |
:: |
npde, nv, nxi |
Integer, Intent (Inout) |
:: |
ires |
Real (Kind=nag_wp), Intent (In) |
:: |
t, v(nv), vdot(nv), xi(nxi), ucp(npde,nxi), ucpx(npde,nxi), ucpt(npde,nxi) |
Real (Kind=nag_wp), Intent (Out) |
:: |
r(nv) |
|
C Header Interface
void |
odedef_ (const Integer *npde, const double *t, const Integer *nv, const double v[], const double vdot[], const Integer *nxi, const double xi[], const double ucp[], const double ucpx[], const double ucpt[], double r[], Integer *ires) |
|
C++ Header Interface
#include <nag.h> extern "C" {
void |
odedef_ (const Integer &npde, const double &t, const Integer &nv, const double v[], const double vdot[], const Integer &nxi, const double xi[], const double ucp[], const double ucpx[], const double ucpt[], double r[], Integer &ires) |
}
|
-
1:
– Integer
Input
-
On entry: the number of PDEs in the system.
-
2:
– Real (Kind=nag_wp)
Input
-
On entry: the current value of the independent variable .
-
3:
– Integer
Input
-
On entry: the number of coupled ODEs in the system.
-
4:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of the component , for .
-
5:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of component , for .
-
6:
– Integer
Input
-
On entry: the number of ODE/PDE coupling points.
-
7:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the ODE/PDE coupling points, , for .
-
8:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of at the coupling point , for and .
-
9:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of at the coupling point , for and .
-
10:
– Real (Kind=nag_wp) array
Input
-
On entry: if , contains the value of at the coupling point , for and .
-
11:
– Real (Kind=nag_wp) array
Output
-
On exit: if
,
must contain the
th component of
, for
, where
is defined as
i.e., only terms depending explicitly on time derivatives, or
i.e., all terms in equation
(4). The definition of
is determined by the input value of
ires.
-
12:
– Integer
Input/Output
-
On entry: the form of
that must be returned in the array
r.
- Equation (13) must be used.
- Equation (14) must be used.
On exit: should usually remain unchanged. However, you may reset
ires to force the integration routine to take certain actions, as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , d03pkf returns to the calling subroutine with the error indicator set to .
odedef must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which
d03pkf is called. Arguments denoted as
Input must
not be changed by this procedure.
Note: odedef should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by
d03pkf. If your code inadvertently
does return any NaNs or infinities,
d03pkf is likely to produce unexpected results.
-
12:
– Integer
Input
-
On entry: the number of ODE/PDE coupling points.
Constraints:
- if , ;
- if , .
-
13:
– Real (Kind=nag_wp) array
Input
-
On entry: , for , must be set to the ODE/PDE coupling points, .
Constraint:
.
-
14:
– Integer
Input
-
On entry: the number of ODEs in the time direction.
Constraint:
.
-
15:
– Real (Kind=nag_wp) array
Input
-
Note: the dimension of the array
rtol
must be at least
if
or
and at least
if
or
.
On entry: the relative local error tolerance.
Constraint:
for all relevant .
-
16:
– Real (Kind=nag_wp) array
Input
-
Note: the dimension of the array
atol
must be at least
if
or
and at least
if
or
.
On entry: the absolute local error tolerance.
Constraint:
for all relevant
.
Note: corresponding elements of
rtol and
atol cannot both be
.
-
17:
– Integer
Input
-
On entry: a value to indicate the form of the local error test.
itol indicates to
d03pkf whether to interpret either or both of
rtol or
atol as a vector or scalar. The error test to be satisfied is
, where
is defined as follows:
itol | rtol | atol | |
1 | scalar | scalar | |
2 | scalar | vector | |
3 | vector | scalar | |
4 | vector | vector | |
In the above, denotes the estimated local error for the th component of the coupled PDE/ODE system in time, , for .
The choice of norm used is defined by the argument
norm.
Constraint:
.
-
18:
– Character(1)
Input
-
On entry: the type of norm to be used.
- Maximum norm.
- Averaged norm.
If
denotes the norm of the vector
u of length
neqn, then for the averaged
norm
while for the maximum norm
See the description of
itol for the formulation of the weight vector
.
Constraint:
or .
-
19:
– Character(1)
Input
-
On entry: the type of matrix algebra required.
- Full matrix methods to be used.
- Banded matrix methods to be used.
- Sparse matrix methods to be used.
Constraint:
,
or
.
Note: you are recommended to use the banded option when no coupled ODEs are present (i.e., ).
-
20:
– Real (Kind=nag_wp) array
Input
-
On entry: may be set to control various options available in the integrator. If you wish to employ all the default options,
should be set to
. Default values will also be used for any other elements of
algopt set to zero. The permissible values, default values, and meanings are as follows:
- Selects the ODE integration method to be used. If , a BDF method is used and if , a Theta method is used. The default value is .
If , then
, for , are not used.
- Specifies the maximum order of the BDF integration formula to be used. may be , , , or . The default value is .
- Specifies what method is to be used to solve the system of nonlinear equations arising on each step of the BDF method. If a modified Newton iteration is used and if a functional iteration method is used. If functional iteration is selected and the integrator encounters difficulty, there is an automatic switch to the modified Newton iteration. The default value is .
- Specifies whether or not the Petzold error test is to be employed. The Petzold error test results in extra overhead but is more suitable when algebraic equations are present, such as
, for , for some or when there is no dependence in the coupled ODE system. If , the Petzold test is used. If , the Petzold test is not used. The default value is .
If ,
, for , are not used.
- Specifies the value of Theta to be used in the Theta integration method. . The default value is .
- Specifies what method is to be used to solve the system of nonlinear equations arising on each step of the Theta method. If , a modified Newton iteration is used and if , a functional iteration method is used. The default value is .
- Specifies whether or not the integrator is allowed to switch automatically between modified Newton and functional iteration methods in order to be more efficient. If , switching is allowed and if , switching is not allowed. The default value is .
- Specifies a point in the time direction, , beyond which integration must not be attempted. The use of is described under the argument itask. If , a value of , for , say, should be specified even if itask subsequently specifies that will not be used.
- Specifies the minimum absolute step size to be allowed in the time integration. If this option is not required, should be set to .
- Specifies the maximum absolute step size to be allowed in the time integration. If this option is not required, should be set to .
- Specifies the initial step size to be attempted by the integrator. If , the initial step size is calculated internally.
- Specifies the maximum number of steps to be attempted by the integrator in any one call. If , no limit is imposed.
- Specifies what method is to be used to solve the nonlinear equations at the initial point to initialize the values of , , and . If , a modified Newton iteration is used and if , functional iteration is used. The default value is .
and are used only for the sparse matrix algebra option, i.e., .
- Governs the choice of pivots during the decomposition of the first Jacobian matrix. It should lie in the range , with smaller values biasing the algorithm towards maintaining sparsity at the expense of numerical stability. If lies outside this range then the default value is used. If the routines regard the Jacobian matrix as numerically singular then increasing towards may help, but at the cost of increased fill-in. The default value is .
- Used as a relative pivot threshold during subsequent Jacobian decompositions (see ) below which an internal error is invoked. must be greater than zero, otherwise the default value is used. If is greater than no check is made on the pivot size, and this may be a necessary option if the Jacobian is found to be numerically singular (see ). The default value is .
-
21:
– Real (Kind=nag_wp) array
Communication Array
-
If
,
rsave need not be set on entry.
If
,
rsave must be unchanged from the previous call to the routine because it contains required information about the iteration.
-
22:
– Integer
Input
-
On entry: the dimension of the array
rsave as declared in the (sub)program from which
d03pkf is called.
Its size depends on the type of matrix algebra selected.
If , .
If , .
If , .
Where
and
are the lower and upper half bandwidths given by
such that
- for problems involving PDEs only,
- for coupled PDE/ODE problems,
Where
is defined by
- if ,
- if ,
- if ,
Where
is defined by
- if the BDF method is used,
- if the Theta method is used,
Note: when using the sparse option, the value of
lrsave may be too small when supplied to the integrator. An estimate of the minimum size of
lrsave is printed on the current error message unit if
and the routine returns with
.
-
23:
– Integer array
Communication Array
-
If
,
isave need not be set.
If
,
isave must be unchanged from the previous call to the routine because it contains required information about the iteration. In particular the following components of the array
isave concern the efficiency of the integration:
- Contains the number of steps taken in time.
- Contains the number of residual evaluations of the resulting ODE system used. One such evaluation involves evaluating the PDE functions at all the mesh points, as well as one evaluation of the functions in the boundary conditions.
- Contains the number of Jacobian evaluations performed by the time integrator.
- Contains the order of the ODE method last used in the time integration.
- Contains the number of Newton iterations performed by the time integrator. Each iteration involves residual evaluation of the resulting ODE system followed by a back-substitution using the decomposition of the Jacobian matrix.
-
24:
– Integer
Input
-
On entry: the dimension of the array
isave as declared in the (sub)program from which
d03pkf is called. Its size depends on the type of matrix algebra selected:
- if , ;
- if , ;
- if , .
Note: when using the sparse option, the value of
lisave may be too small when supplied to the integrator. An estimate of the minimum size of
lisave is printed on the current error message unit if
and the routine returns with
.
-
25:
– Integer
Input
-
On entry: the task to be performed by the ODE integrator.
- Normal computation of output values u at (by overshooting and interpolating).
- Take one step in the time direction and return.
- Stop at first internal integration point at or beyond .
- Normal computation of output values u at but without overshooting where is described under the argument algopt.
- Take one step in the time direction and return, without passing , where is described under the argument algopt.
Constraint:
, , , or .
-
26:
– Integer
Input
-
On entry: the level of trace information required from
d03pkf and the underlying ODE solver as follows:
- No output is generated.
- Only warning messages from the PDE solver are printed on the current error message unit (see x04aaf).
- Output from the underlying ODE solver is printed on the current advisory message unit (see x04abf). This output contains details of Jacobian entries, the nonlinear iteration and the time integration during the computation of the ODE system.
- Output from the underlying ODE solver is similar to that produced when , except that the advisory messages are given in greater detail.
- Output from the underlying ODE solver is similar to that produced when , except that the advisory messages are given in greater detail.
You advised to set
, unless you are experienced with
Sub-chapter D02MN.
-
27:
– Integer
Input/Output
-
On entry: indicates whether this is a continuation call or a new integration.
- Starts or restarts the integration in time.
- Continues the integration after an earlier exit from the routine. In this case, only the
arguments tout and ifail
should be reset between calls to d03pkf.
Constraint:
or .
On exit: .
-
28:
– Integer
Input/Output
-
On entry:
ifail must be set to
,
. If you are unfamiliar with this argument you should refer to
Section 4 in the Introduction to the NAG Library FL Interface 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, if you are not familiar with this argument, 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).
Errors or warnings detected by the routine:
-
On entry, at least one point in
xi lies outside
:
and
.
On entry, , , and .
Constraint: .
On entry, , and .
Constraint: .
On entry, and .
Constraint: .
On entry, and .
Constraint: corresponding elements and cannot both be .
On entry, and .
Constraint: .
On entry, .
Constraint: or .
On entry, .
Constraint: , , , or .
On entry, .
Constraint: , , or .
On entry, .
Constraint: , or .
On entry, .
Constraint: .
On entry, .
Constraint: .
On entry, , , and .
Constraint: .
On entry, ,
.
Constraint: .
On entry, .
Constraint: .
On entry, .
Constraint: or .
On entry, .
Constraint: .
On entry, .
Constraint: .
On entry, .
Constraint: .
On entry, and .
Constraint: when .
On entry, and .
Constraint: when .
On entry, on initial entry .
Constraint: on initial entry .
On entry, and .
Constraint: .
On entry, is too small:
and .
-
Underlying ODE solver cannot make further progress from the point
ts with the supplied values of
atol and
rtol.
.
-
Repeated errors in an attempted step of underlying ODE solver. Integration was successful as far as
ts:
.
In the underlying ODE solver, there were repeated error test failures on an attempted step, before completing the requested task, but the integration was successful as far as . The problem may have a singularity, or the error requirement may be inappropriate. Incorrect positioning of boundary conditions may also result in this error.
-
In setting up the ODE system an internal auxiliary was unable to initialize the derivative. This could be due to your setting
in
pdedef or
bndary.
-
Singular Jacobian of ODE system. Check problem formulation.
-
In evaluating residual of ODE system,
has been set in
pdedef,
bndary, or
odedef. Integration is successful as far as
ts:
.
-
atol and
rtol were too small to start integration.
-
ires set to an invalid value in call to
pdedef,
bndary, or
odedef.
-
Serious error in internal call to an auxiliary. Increase
itrace for further details.
-
Integration completed, but small changes in
atol or
rtol are unlikely to result in a changed solution.
The required task has been completed, but it is estimated that a small change in
atol and
rtol is unlikely to produce any change in the computed solution. (Only applies when you are not operating in one step mode, that is when
or
.)
-
Error during Jacobian formulation for ODE system. Increase
itrace for further details.
-
In solving ODE system, the maximum number of steps has been exceeded. .
-
Zero error weights encountered during time integration.
Some error weights
became zero during the time integration (see the description of
itol). Pure relative error control
was requested on a variable (the
th) which has become zero. The integration was successful as far as
.
-
When using the sparse option
lisave or
lrsave is too small:
,
.
An unexpected error has been triggered by this routine. Please
contact
NAG.
See
Section 7 in the Introduction to the NAG Library FL Interface for further information.
Your licence key may have expired or may not have been installed correctly.
See
Section 8 in the Introduction to the NAG Library FL Interface for further information.
Dynamic memory allocation failed.
See
Section 9 in the Introduction to the NAG Library FL Interface for further information.
7
Accuracy
d03pkf controls the accuracy of the integration in the time direction but not the accuracy of the approximation in space. The spatial accuracy depends on both the number of mesh points and on their distribution in space. In the time integration only the local error over a single step is controlled and so the accuracy over a number of steps cannot be guaranteed. You should therefore test the effect of varying the accuracy arguments,
atol and
rtol.
8
Parallelism and Performance
d03pkf is not thread safe and should not be called from a multithreaded user program. Please see
Section 1 in FL Interface Multithreading for more information on thread safety.
d03pkf is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
d03pkf 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.
The Keller box scheme can be used to solve higher-order problems which have been reduced to first-order by the introduction of new variables (see the example in
Section 10). In general, a second-order problem can be solved with slightly greater accuracy using the Keller box scheme instead of a finite difference scheme (see
d03pcf/d03pca or
d03phf/d03pha for example), but at the expense of increased CPU time due to the larger number of function evaluations required.
It should be noted that the Keller box scheme, in common with other central-difference schemes, may be unsuitable for some hyperbolic first-order problems such as the apparently simple linear advection equation
, where
is a constant, resulting in spurious oscillations due to the lack of dissipation. This type of problem requires a discretization scheme with upwind weighting (
d03plf for example), or the addition of a second-order artificial dissipation term.
The time taken depends on the complexity of the system and on the accuracy requested. For a given system and a fixed accuracy it is approximately proportional to
neqn.
10
Example
This example provides a simple coupled system of two PDEs and one ODE.
for
, for
. The left boundary condition at
is
and the right boundary condition at
is
The initial conditions at
are defined by the exact solution:
and the coupling point is at
.
This problem is exactly the same as the
d03phf/d03pha example problem, but reduced to first-order by the introduction of a second PDE variable (as mentioned in
Section 9).
10.1
Program Text
10.2
Program Data
10.3
Program Results