NAG Library Routine Document
D03PHF/D03PHA
1 Purpose
D03PHF/D03PHA integrates a system of linear or nonlinear parabolic partial differential equations (PDEs) in one space variable, with scope for coupled ordinary differential equations (ODEs). The spatial discretization is performed using finite differences, 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 method or a Theta method (switching between Newton's method and functional iteration).
D03PHA is a version of D03PHF that has additional parameters in order to make it safe for use in multithreaded applications (see
Section 5).
2 Specification
2.1 Specification for D03PHF
SUBROUTINE D03PHF ( |
NPDE, M, TS, TOUT, PDEDEF, BNDARY, U, NPTS, X, NCODE, ODEDEF, NXI, XI, NEQN, RTOL, ATOL, ITOL, NORM, LAOPT, ALGOPT, RSAVE, LRSAVE, ISAVE, LISAVE, ITASK, ITRACE, IND, IFAIL) |
INTEGER |
NPDE, M, NPTS, NCODE, NXI, NEQN, ITOL, LRSAVE, ISAVE(LISAVE), LISAVE, ITASK, ITRACE, IND, IFAIL |
REAL (KIND=nag_wp) |
TS, TOUT, U(NEQN), X(NPTS), XI(NXI), RTOL(*), ATOL(*), ALGOPT(30), RSAVE(LRSAVE) |
CHARACTER(1) |
NORM, LAOPT |
EXTERNAL |
PDEDEF, BNDARY, ODEDEF |
|
2.2 Specification for D03PHA
SUBROUTINE D03PHA ( |
NPDE, M, TS, TOUT, PDEDEF, BNDARY, U, NPTS, X, NCODE, ODEDEF, NXI, XI, NEQN, RTOL, ATOL, ITOL, NORM, LAOPT, ALGOPT, RSAVE, LRSAVE, ISAVE, LISAVE, ITASK, ITRACE, IND, IUSER, RUSER, CWSAV, LWSAV, IWSAV, RWSAV, IFAIL) |
INTEGER |
NPDE, M, NPTS, NCODE, NXI, NEQN, ITOL, LRSAVE, ISAVE(LISAVE), LISAVE, ITASK, ITRACE, IND, IUSER(*), IWSAV(505), IFAIL |
REAL (KIND=nag_wp) |
TS, TOUT, U(NEQN), X(NPTS), XI(NXI), RTOL(*), ATOL(*), ALGOPT(30), RSAVE(LRSAVE), RUSER(*), RWSAV(1100) |
LOGICAL |
LWSAV(100) |
CHARACTER(1) |
NORM, LAOPT |
CHARACTER(80) |
CWSAV(10) |
EXTERNAL |
PDEDEF, BNDARY, ODEDEF |
|
3 Description
D03PHF/D03PHA integrates the system of parabolic-elliptic equations and coupled ODEs
where
(1) defines the PDE part and
(2) generalizes the coupled ODE part of the problem.
In
(1),
and
depend on
,
,
,
and
;
depends on
,
,
,
,
and
linearly on
. 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
(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 the equation
(2) may be written more precisely as
where
,
is a vector of length
NCODE,
is an
NCODE by
NCODE matrix,
is an
NCODE by
matrix and 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 coordinate system in space is defined by the values of ; for Cartesian coordinates, for cylindrical polar coordinates and for spherical polar coordinates.
The PDE system which is defined by the functions
,
and
must be specified in
PDEDEF.
The initial values of the functions and must be given at .
The functions
which may be thought of as fluxes, are also used in the definition of the boundary conditions. The boundary conditions must have the form
where
or
.
The boundary conditions must be specified in
BNDARY. The function
may depend
linearly on
.
The problem is subject to the following restrictions:
(i) |
In (1), , for , may only appear linearly in the functions
, for , with a similar restriction for ; |
(ii) |
and the flux must not depend on any time derivatives; |
(iii) |
, so that integration is in the forward direction; |
(iv) |
the evaluation of the terms , and is done approximately at the mid-points of the mesh , for , by calling the PDEDEF for each mid-point in turn. Any discontinuities in these functions must therefore be at one or more of the mesh points ; |
(v) |
at least one of the functions must be nonzero so that there is a time derivative present in the PDE problem; |
(vi) |
if and , which is the left boundary point, then it must be ensured that the PDE solution is bounded at this point. This can be done by either specifying the solution at or by specifying a zero flux there, that is and . See also Section 9 below. |
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. For simple problems in Cartesian coordinates, this system is obtained by replacing the space derivatives by the usual central, three-point finite difference formula. However, for polar and spherical problems, or problems with nonlinear coefficients, the space derivatives are replaced by a modified three-point formula which maintains second order accuracy. In total there are ODEs in the 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
Skeel R D and Berzins M (1990) A method for the spatial discretization of parabolic equations in one space variable SIAM J. Sci. Statist. Comput. 11(1) 1–32
5 Parameters
- 1: – INTEGERInput
-
On entry: the number of PDEs to be solved.
Constraint:
.
- 2: – INTEGERInput
-
On entry: the coordinate system used:
- Indicates Cartesian coordinates.
- Indicates cylindrical polar coordinates.
- Indicates spherical polar coordinates.
Constraint:
, or .
- 3: – REAL (KIND=nag_wp)Input/Output
-
On entry: the initial value of the independent variable .
On exit: the value of
corresponding to the solution values in
U. Normally
.
Constraint:
.
- 4: – REAL (KIND=nag_wp)Input
-
On entry: the final value of to which the integration is to be carried out.
- 5: – SUBROUTINE, supplied by the user.External Procedure
-
PDEDEF must evaluate the functions
,
and
which define the system of PDEs. The functions may depend on
,
,
,
and
.
may depend linearly on
.
PDEDEF is called approximately midway between each pair of mesh points in turn by D03PHF/D03PHA.
The specification of
PDEDEF
for D03PHF is:
SUBROUTINE PDEDEF ( |
NPDE, T, X, U, UX, NCODE, V, VDOT, P, Q, R, IRES) |
INTEGER |
NPDE, NCODE, IRES |
REAL (KIND=nag_wp) |
T, X, U(NPDE), UX(NPDE), V(NCODE), VDOT(NCODE), P(NPDE,NPDE), Q(NPDE), R(NPDE) |
|
The specification of
PDEDEF
for D03PHA is:
SUBROUTINE PDEDEF ( |
NPDE, T, X, U, UX, NCODE, V, VDOT, P, Q, R, IRES, IUSER, RUSER) |
INTEGER |
NPDE, NCODE, IRES, IUSER(*) |
REAL (KIND=nag_wp) |
T, X, U(NPDE), UX(NPDE), V(NCODE), VDOT(NCODE), P(NPDE,NPDE), Q(NPDE), R(NPDE), RUSER(*) |
|
- 1: – INTEGERInput
-
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) arrayInput
-
On entry: contains the value of the component , for .
- 5: – REAL (KIND=nag_wp) arrayInput
-
On entry: contains the value of the component , for .
- 6: – INTEGERInput
-
On entry: the number of coupled ODEs in the system.
- 7: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of the component , for .
- 8: – REAL (KIND=nag_wp) arrayInput
-
On entry: if
,
contains the value of component
, for
.
Note:
, for , may only appear linearly in
, for .
- 9: – REAL (KIND=nag_wp) arrayOutput
-
On exit: must be set to the value of , for and .
- 10: – REAL (KIND=nag_wp) arrayOutput
-
On exit: must be set to the value of , for .
- 11: – REAL (KIND=nag_wp) arrayOutput
-
On exit: must be set to the value of , for .
- 12: – INTEGERInput/Output
-
On entry: set to .
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 , then D03PHF/D03PHA returns to the calling subroutine with the error indicator set to .
- Note: the following are additional parameters for specific use with D03PHA. Users of D03PHF therefore need not read the remainder of this description.
- 13: – INTEGER arrayUser Workspace
- 14: – REAL (KIND=nag_wp) arrayUser Workspace
-
PDEDEF is called with the parameters
IUSER and
RUSER as supplied to D03PHF/D03PHA. You are free to use the arrays
IUSER and
RUSER to supply information to
PDEDEF as an alternative to using COMMON global variables.
PDEDEF must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which D03PHF/D03PHA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 6: – SUBROUTINE, supplied by the user.External Procedure
-
BNDARY must evaluate the functions
and
which describe the boundary conditions, as given in
(4).
The specification of
BNDARY
for D03PHF is:
SUBROUTINE BNDARY ( |
NPDE, T, U, UX, NCODE, V, VDOT, IBND, BETA, GAMMA, IRES) |
INTEGER |
NPDE, NCODE, IBND, IRES |
REAL (KIND=nag_wp) |
T, U(NPDE), UX(NPDE), V(NCODE), VDOT(NCODE), BETA(NPDE), GAMMA(NPDE) |
|
The specification of
BNDARY
for D03PHA is:
SUBROUTINE BNDARY ( |
NPDE, T, U, UX, NCODE, V, VDOT, IBND, BETA, GAMMA, IRES, IUSER, RUSER) |
INTEGER |
NPDE, NCODE, IBND, IRES, IUSER(*) |
REAL (KIND=nag_wp) |
T, U(NPDE), UX(NPDE), V(NCODE), VDOT(NCODE), BETA(NPDE), GAMMA(NPDE), RUSER(*) |
|
- 1: – INTEGERInput
-
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) arrayInput
-
On entry:
contains the value of the component
at the boundary specified by
IBND, for
.
- 4: – REAL (KIND=nag_wp) arrayInput
-
On entry:
contains the value of the component
at the boundary specified by
IBND, for
.
- 5: – INTEGERInput
-
On entry: the number of coupled ODEs in the system.
- 6: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of the component , for .
- 7: – REAL (KIND=nag_wp) arrayInput
-
On entry: if
,
contains the value of component
, for
.
Note:
, for , may only appear linearly in
, for .
- 8: – INTEGERInput
-
On entry: specifies which boundary conditions are to be evaluated.
- BNDARY must set up the coefficients of the left-hand boundary, .
- BNDARY must set up the coefficients of the right-hand boundary, .
- 9: – REAL (KIND=nag_wp) arrayOutput
-
On exit:
must be set to the value of
at the boundary specified by
IBND, for
.
- 10: – REAL (KIND=nag_wp) arrayOutput
-
On exit:
must be set to the value of
at the boundary specified by
IBND, for
.
- 11: – INTEGERInput/Output
-
On entry: set to .
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 , then D03PHF/D03PHA returns to the calling subroutine with the error indicator set to .
- Note: the following are additional parameters for specific use with D03PHA. Users of D03PHF therefore need not read the remainder of this description.
- 12: – INTEGER arrayUser Workspace
- 13: – REAL (KIND=nag_wp) arrayUser Workspace
-
BNDARY is called with the parameters
IUSER and
RUSER as supplied to D03PHF/D03PHA. You are free to use the arrays
IUSER and
RUSER to supply information to
BNDARY as an alternative to using COMMON global variables.
BNDARY must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which D03PHF/D03PHA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 7: – REAL (KIND=nag_wp) arrayInput/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 .
- 8: – INTEGERInput
-
On entry: the number of mesh points in the interval .
Constraint:
.
- 9: – REAL (KIND=nag_wp) arrayInput
-
On entry: the mesh points in the space direction. must specify the left-hand boundary, , and must specify the right-hand boundary, .
Constraint:
.
- 10: – INTEGERInput
-
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
(3).
If you wish to compute the solution of a system of PDEs only (
),
ODEDEF must be the dummy routine D03PCK for D03PHF (or D53PCK for D03PHA). D03PCK and D53PCK are included in the NAG Library.
The specification of
ODEDEF
for D03PHF is:
SUBROUTINE ODEDEF ( |
NPDE, T, NCODE, V, VDOT, NXI, XI, UCP, UCPX, RCP, UCPT, UCPTX, F, IRES) |
INTEGER |
NPDE, NCODE, NXI, IRES |
REAL (KIND=nag_wp) |
T, V(NCODE), VDOT(NCODE), XI(NXI), UCP(NPDE,*), UCPX(NPDE,*), RCP(NPDE,*), UCPT(NPDE,*), UCPTX(NPDE,*), F(NCODE) |
|
The specification of
ODEDEF
for D03PHA is:
SUBROUTINE ODEDEF ( |
NPDE, T, NCODE, V, VDOT, NXI, XI, UCP, UCPX, RCP, UCPT, UCPTX, F, IRES, IUSER, RUSER) |
INTEGER |
NPDE, NCODE, NXI, IRES, IUSER(*) |
REAL (KIND=nag_wp) |
T, V(NCODE), VDOT(NCODE), XI(NXI), UCP(NPDE,*), UCPX(NPDE,*), RCP(NPDE,*), UCPT(NPDE,*), UCPTX(NPDE,*), F(NCODE), RUSER(*) |
|
- 1: – INTEGERInput
-
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: – INTEGERInput
-
On entry: the number of coupled ODEs in the system.
- 4: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of the component , for .
- 5: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of component , for .
- 6: – INTEGERInput
-
On entry: the number of ODE/PDE coupling points.
- 7: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the ODE/PDE coupling points, , for .
- 8: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of at the coupling point , for and .
- 9: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of at the coupling point , for and .
- 10: – REAL (KIND=nag_wp) arrayInput
-
On entry: contains the value of the flux at the coupling point , for and .
- 11: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , contains the value of at the coupling point , for and .
- 12: – REAL (KIND=nag_wp) arrayInput
-
On entry: contains the value of at the coupling point , for and .
- 13: – REAL (KIND=nag_wp) arrayOutput
-
On exit:
must contain the
th component of
, for
, where
is defined as
or
The definition of
is determined by the input value of
IRES.
- 14: – INTEGERInput/Output
-
On entry: the form of
that must be returned in the array
F.
- Equation (5) must be used.
- Equation (6) 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 , then D03PHF/D03PHA returns to the calling subroutine with the error indicator set to .
- Note: the following are additional parameters for specific use with D03PHA. Users of D03PHF therefore need not read the remainder of this description.
- 15: – INTEGER arrayUser Workspace
- 16: – REAL (KIND=nag_wp) arrayUser Workspace
-
ODEDEF is called with the parameters
IUSER and
RUSER as supplied to D03PHF/D03PHA. You are free to use the arrays
IUSER and
RUSER to supply information to
ODEDEF as an alternative to using COMMON global variables.
ODEDEF must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which D03PHF/D03PHA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 12: – INTEGERInput
-
On entry: the number of ODE/PDE coupling points.
Constraints:
- if , ;
- if , .
- 13: – REAL (KIND=nag_wp) arrayInput
-
On entry: if , , for , must be set to the ODE/PDE coupling points.
Constraint:
.
- 14: – INTEGERInput
-
On entry: the number of ODEs in the time direction.
Constraint:
.
- 15: – REAL (KIND=nag_wp) arrayInput
-
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) arrayInput
-
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: – INTEGERInput
-
On entry: a value to indicate the form of the local error test.
ITOL indicates to D03PHF/D03PHA 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 parameter
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) arrayInput
-
On entry: may be set to control various options available in the integrator. If you wish to employ all the default options, then
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, then 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 , then the Petzold test is used. If , then the Petzold test is not used. The default value is .
If , then
, 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 , then switching is allowed and if , then 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 parameter 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 , then the initial step size is calculated internally.
- Specifies the maximum number of steps to be attempted by the integrator in any one call. If , then 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, .
- 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 .
- Is used as a relative pivot threshold during subsequent Jacobian decompositions (see ) below which an internal error is invoked. 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) arrayCommunication 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: – INTEGERInput
-
On entry: the dimension of the array
RSAVE as declared in the (sub)program from which D03PHF/D03PHA is called.
Constraint:
If , .
If , .
If , .
Where
| is the lower or upper half bandwidths such that , for PDE problems only (no coupled ODEs); or , for coupled PDE/ODE problems. |
| |
| |
Note: when
, 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 arrayCommunication Array
-
If
,
ISAVE need not be set on entry.
If
,
ISAVE must be unchanged from the previous call to the routine because it contains required information about the iteration. In particular:
- Contains the number of steps taken in time.
- Contains the number of residual evaluations of the resulting ODE system used. One such evaluation involves computing 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 last backward differentiation formula method used.
- Contains the number of Newton iterations performed by the time integrator. Each iteration involves an ODE residual evaluation followed by a back-substitution using the decomposition of the Jacobian matrix.
- 24: – INTEGERInput
-
On entry: the dimension of the array
ISAVE as declared in the (sub)program from which D03PHF/D03PHA 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: – INTEGERInput
-
On entry: specifies the task to be performed by the ODE integrator.
- Normal computation of output values U at .
- One step 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 parameter ALGOPT.
- Take one step in the time direction and return, without passing , where is described under the parameter ALGOPT.
Constraint:
, , , or .
- 26: – INTEGERInput
-
On entry: the level of trace information required from D03PHF/D03PHA and the underlying ODE solver.
ITRACE may take the value
,
,
,
or
.
- 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.
If , then is assumed and similarly if , then is assumed.
The advisory messages are given in greater detail as
ITRACE increases. You are advised to set
, unless you are experienced with
sub-chapter D02M–N.
- 27: – INTEGERInput/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 parameters TOUT and IFAIL should be reset between calls to D03PHF/D03PHA.
Constraint:
or .
On exit: .
- 28: – INTEGERInput/Output
-
Note: for D03PHA, IFAIL does not occur in this position in the parameter list. See the additional parameters described below.
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, if you are not familiar with this parameter, 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).
- Note: the following are additional parameters for specific use with D03PHA. Users of D03PHF therefore need not read the remainder of this description.
- 28: – INTEGER arrayUser Workspace
- 29: – REAL (KIND=nag_wp) arrayUser Workspace
-
IUSER and
RUSER are not used by D03PHF/D03PHA, but are passed directly to
PDEDEF,
BNDARY and
ODEDEF and may be used to pass information to these routines as an alternative to using COMMON global variables.
- 30: – CHARACTER(80) arrayCommunication Array
-
- 31: – LOGICAL arrayCommunication Array
-
- 32: – INTEGER arrayCommunication Array
-
- 33: – REAL (KIND=nag_wp) arrayCommunication Array
-
- 34: – INTEGERInput/Output
-
Note: see the parameter description for
IFAIL above.
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, | is too small, |
or | , , , or , |
or | , or , |
or | at least one of the coupling points defined in array XI is outside the interval [], |
or | and , |
or | , |
or | , |
or | or , |
or | , or , |
or | , , or , |
or | or , |
or | mesh points are badly ordered, |
or | LRSAVE is too small, |
or | LISAVE is too small, |
or | NCODE and NXI are incorrectly defined, |
or | , |
or | either an element of RTOL or , |
or | all the elements of RTOL and ATOL are zero. |
-
The underlying ODE solver cannot make any further progress, with the values of
ATOL and
RTOL, across the integration range from the current point
. The components of
U contain the computed values at the current point
.
-
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.
-
In setting up the ODE system, the internal initialization routine was unable to initialize the derivative of the ODE system. This could be due to the fact that
IRES was repeatedly set to
in at least
PDEDEF,
BNDARY or
ODEDEF, when the residual in the underlying ODE solver was being evaluated.
-
In solving the ODE system, a singular Jacobian has been encountered. You should check your problem formulation.
-
When evaluating the residual in solving the ODE system,
IRES was set to
in at least
PDEDEF,
BNDARY or
ODEDEF. Integration was successful as far as
.
-
The values of
ATOL and
RTOL are so small that the routine is unable to start the integration in time.
-
In one of
PDEDEF,
BNDARY or
ODEDEF,
IRES was set to an invalid value.
- (D02NNF)
-
A serious error has occurred in an internal call to the specified routine. Check the problem specification and all parameters and array dimensions. Setting
may provide more information. If the problem persists, contact
NAG.
-
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
.)
-
An error occurred during Jacobian formulation of the ODE system (a more detailed error description may be directed to the current error message unit). If using the sparse matrix algebra option, the values of and may be inappropriate.
-
In solving the ODE system, the maximum number of steps specified in have been taken.
-
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
.
-
The flux function was detected as depending on time derivatives, which is not permissible.
-
When using the sparse option, the value of
LISAVE or
LRSAVE was not sufficient (more detailed information may be directed to the current error message unit).
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
D03PHF/D03PHA 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 parameters
ATOL and
RTOL.
8 Parallelism and Performance
D03PHF/D03PHA is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
D03PHF/D03PHA 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 parameter specification allows you to include equations with only first-order derivatives in the space direction but there is no guarantee that the method of integration will be satisfactory for such systems. The position and nature of the boundary conditions in particular are critical in defining a stable problem. It may be advisable in such cases to reduce the whole system to first-order and to use the Keller box scheme routine
D03PKF.
The time taken depends on the complexity of the parabolic 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 one PDE and one ODE.
for
;
;
.
The left boundary condition at
is
The right boundary condition at
is
The initial conditions at
are defined by the exact solution:
and the coupling point is at
.
10.1 Program Text
Note: the following programs illustrate the use of D03PHF and D03PHA.
Program Text (d03phfe.f90)
Program Text (d03phae.f90)
10.2 Program Data
Program Data (d03phfe.d)
Program Data (d03phae.d)
10.3 Program Results
Program Results (d03phfe.r)
Program Results (d03phae.r)