NAG Library Routine Document

d03pef  (dim1_parab_keller)

 Contents

    1  Purpose
    7  Accuracy

1
Purpose

d03pef integrates a system of linear or nonlinear, first-order, time-dependent partial differential equations (PDEs) in one space variable. 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 ordinary differential equations (ODEs). The resulting system is solved using a Backward Differentiation Formula (BDF) method.

2
Specification

Fortran Interface
Subroutine d03pef ( npde, ts, tout, pdedef, bndary, u, npts, x, nleft, acc, rsave, lrsave, isave, lisave, itask, itrace, ind, ifail)
Integer, Intent (In):: npde, npts, nleft, lrsave, lisave, itask, itrace
Integer, Intent (Inout):: isave(lisave), ind, ifail
Real (Kind=nag_wp), Intent (In):: tout, x(npts), acc
Real (Kind=nag_wp), Intent (Inout):: ts, u(npde,npts), rsave(lrsave)
External:: pdedef, bndary
C Header Interface
#include nagmk26.h
void  d03pef_ ( 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[], 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[], double res[], Integer *ires),
double u[], const Integer *npts, const double x[], const Integer *nleft, const double *acc, double rsave[], const Integer *lrsave, Integer isave[], const Integer *lisave, const Integer *itask, const Integer *itrace, Integer *ind, Integer *ifail)

3
Description

d03pef integrates the system of first-order PDEs
Gix,t,U,Ux,Ut=0,  i=1,2,,npde. (1)
In particular the functions Gi must have the general form
Gi=j=1npdePi,j Uj t +Qi,  i=1,2,,npde,  axb,tt0, (2)
where Pi,j and Qi depend on x, t, U, Ux and the vector U is the set of solution values
U x,t = U 1 x,t ,, U npde x,t T , (3)
and the vector Ux is its partial derivative with respect to x. Note that Pi,j and Qi must not depend on U t .
The integration in time is from t0 to tout, over the space interval axb, where a=x1 and b=xnpts are the leftmost and rightmost points of a user-defined mesh x1,x2,,xnpts. The mesh should be chosen in accordance with the expected behaviour of the solution.
The PDE system which is defined by the functions Gi must be specified in pdedef.
The initial values of the functions Ux,t must be given at t=t0. For a first-order system of PDEs, only one boundary condition is required for each PDE component Ui. The npde boundary conditions are separated into na at the left-hand boundary x=a, and nb at the right-hand boundary x=b, such that na+nb=npde. The position of the boundary condition for each component should be chosen with care; the general rule is that if the characteristic direction of Ui at the left-hand boundary (say) points into the interior of the solution domain, then the boundary condition for Ui 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:
GiLx,t,U,Ut=0  at ​x=a,  i=1,2,,na (4)
at the left-hand boundary, and
GiRx,t,U,Ut=0  at ​x=b,  i=1,2,,nb (5)
at the right-hand boundary.
Note that the functions GiL and GiR must not depend on Ux, since spatial derivatives are not determined explicitly in the Keller box scheme (see Keller (1970)). 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 GiL and GiR must be linear with respect to time derivatives, so that the boundary conditions have the general form
j=1npdeEi,jL Uj t +SiL=0,   i=1,2,,na (6)
at the left-hand boundary, and
j=1npdeEi,jR Uj t +SiR=0,   i=1,2,,nb (7)
at the right-hand boundary, where Ei,jL, Ei,jR, SiL, and SiR depend on x, t and U only.
The boundary conditions must be specified in bndary.
The problem is subject to the following restrictions:
(i) t0<tout, so that integration is in the forward direction;
(ii) Pi,j and Qi must not depend on any time derivatives;
(iii) The evaluation of the function Gi is done at the mid-points of the mesh intervals 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 x1,x2,,xnpts;
(iv) At least one of the functions Pi,j must be nonzero so that there is a time derivative present in the problem.
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 Ui at each mesh point. In total there are npde×npts ODEs in the time direction. This system is then integrated forwards in time using a BDF 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
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:     npde – IntegerInput
On entry: the number of PDEs in the system to be solved.
Constraint: npde1.
2:     ts – Real (Kind=nag_wp)Input/Output
On entry: the initial value of the independent variable t.
Constraint: ts<tout.
On exit: the value of t corresponding to the solution values in u. Normally ts=tout.
3:     tout – Real (Kind=nag_wp)Input
On entry: the final value of t to which the integration is to be carried out.
4:     pdedef – Subroutine, supplied by the user.External Procedure
pdedef must compute the functions Gi which define the system of PDEs. pdedef is called approximately midway between each pair of mesh points in turn by d03pef.
The specification of pdedef is:
Fortran Interface
Subroutine pdedef ( npde, t, x, u, ut, ux, res, ires)
Integer, Intent (In):: npde
Integer, Intent (Inout):: ires
Real (Kind=nag_wp), Intent (In):: t, x, u(npde), ut(npde), ux(npde)
Real (Kind=nag_wp), Intent (Out):: res(npde)
C Header Interface
#include nagmk26.h
void  pdedef ( const Integer *npde, const double *t, const double *x, const double u[], const double ut[], const double ux[], double res[], Integer *ires)
1:     npde – IntegerInput
On entry: the number of PDEs in the system.
2:     t – Real (Kind=nag_wp)Input
On entry: the current value of the independent variable t.
3:     x – Real (Kind=nag_wp)Input
On entry: the current value of the space variable x.
4:     unpde – Real (Kind=nag_wp) arrayInput
On entry: ui contains the value of the component Uix,t, for i=1,2,,npde.
5:     utnpde – Real (Kind=nag_wp) arrayInput
On entry: uti contains the value of the component Uix,t t , for i=1,2,,npde.
6:     uxnpde – Real (Kind=nag_wp) arrayInput
On entry: uxi contains the value of the component Uix,t x , for i=1,2,,npde.
7:     resnpde – Real (Kind=nag_wp) arrayOutput
On exit: resi must contain the ith component of G, for i=1,2,,npde, where G is defined as
Gi=j=1npdePi,j Uj t , (8)
i.e., only terms depending explicitly on time derivatives, or
Gi=j=1npdePi,j Uj t +Qi, (9)
i.e., all terms in equation (2).
The definition of G is determined by the input value of ires.
8:     ires – IntegerInput/Output
On entry: the form of Gi that must be returned in the array res.
ires=-1
Equation (8) must be used.
ires=1
Equation (9) 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:
ires=2
Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to ifail=6.
ires=3
Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set ires=3 when a physically meaningless input or output value has been generated. If you consecutively set ires=3, d03pef returns to the calling subroutine with the error indicator set to ifail=4.
pdedef must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d03pef 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 d03pef. If your code inadvertently does return any NaNs or infinities, d03pef is likely to produce unexpected results.
5:     bndary – Subroutine, supplied by the user.External Procedure
bndary must compute the functions GiL and GiR which define the boundary conditions as in equations (4) and (5).
The specification of bndary is:
Fortran Interface
Subroutine bndary ( npde, t, ibnd, nobc, u, ut, res, ires)
Integer, Intent (In):: npde, ibnd, nobc
Integer, Intent (Inout):: ires
Real (Kind=nag_wp), Intent (In):: t, u(npde), ut(npde)
Real (Kind=nag_wp), Intent (Out):: res(nobc)
C Header Interface
#include nagmk26.h
void  bndary ( const Integer *npde, const double *t, const Integer *ibnd, const Integer *nobc, const double u[], const double ut[], double res[], Integer *ires)
1:     npde – IntegerInput
On entry: the number of PDEs in the system.
2:     t – Real (Kind=nag_wp)Input
On entry: the current value of the independent variable t.
3:     ibnd – IntegerInput
On entry: determines the position of the boundary conditions.
ibnd=0
bndary must compute the left-hand boundary condition at x=a.
ibnd0
Indicates that bndary must compute the right-hand boundary condition at x=b.
4:     nobc – IntegerInput
On entry: specifies the number of boundary conditions at the boundary specified by ibnd.
5:     unpde – Real (Kind=nag_wp) arrayInput
On entry: ui contains the value of the component Uix,t at the boundary specified by ibnd, for i=1,2,,npde.
6:     utnpde – Real (Kind=nag_wp) arrayInput
On entry: uti contains the value of the component Uix,t t  at the boundary specified by ibnd, for i=1,2,,npde.
7:     resnobc – Real (Kind=nag_wp) arrayOutput
On exit: resi must contain the ith component of GL or GR, depending on the value of ibnd, for i=1,2,,nobc, where GL is defined as
GiL=j=1npde Ei,jL Uj t , (10)
i.e., only terms depending explicitly on time derivatives, or
GiL=j=1npde Ei,jL Uj t +SiL, (11)
i.e., all terms in equation (6), and similarly for GiR.
The definitions of GL and GR are determined by the input value of ires.
8:     ires – IntegerInput/Output
On entry: the form GiL (or GiR) that must be returned in the array res.
ires=-1
Equation (10) must be used.
ires=1
Equation (11) 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:
ires=2
Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to ifail=6.
ires=3
Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set ires=3 when a physically meaningless input or output value has been generated. If you consecutively set ires=3, d03pef returns to the calling subroutine with the error indicator set to ifail=4.
bndary must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d03pef 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 d03pef. If your code inadvertently does return any NaNs or infinities, d03pef is likely to produce unexpected results.
6:     unpdenpts – Real (Kind=nag_wp) arrayInput/Output
On entry: the initial values of Ux,t at t=ts and the mesh points xj, for j=1,2,,npts.
On exit: uij will contain the computed solution at t=ts.
7:     npts – IntegerInput
On entry: the number of mesh points in the interval a,b.
Constraint: npts3.
8:     xnpts – Real (Kind=nag_wp) arrayInput
On entry: the mesh points in the spatial direction. x1 must specify the left-hand boundary, a, and xnpts must specify the right-hand boundary, b.
Constraint: x1<x2<<xnpts.
9:     nleft – IntegerInput
On entry: the number na of boundary conditions at the left-hand mesh point x1.
Constraint: 0nleftnpde.
10:   acc – Real (Kind=nag_wp)Input
On entry: a positive quantity for controlling the local error estimate in the time integration. If Ei,j is the estimated error for Ui at the jth mesh point, the error test is:
Ei,j=acc×1.0+uij.  
Constraint: acc>0.0.
11:   rsavelrsave – Real (Kind=nag_wp) arrayCommunication Array
If ind=0, rsave need not be set on entry.
If ind=1, rsave must be unchanged from the previous call to the routine because it contains required information about the iteration.
12:   lrsave – IntegerInput
On entry: the dimension of the array rsave as declared in the (sub)program from which d03pef is called.
Constraint: lrsave4×npde+nleft+14×npde×npts+3×npde+21×npde+7×npts+54.
13:   isavelisave – Integer arrayCommunication Array
If ind=0, isave need not be set on entry.
If ind=1, isave must be unchanged from the previous call to the routine because it contains required information about the iteration. In particular:
isave1
Contains the number of steps taken in time.
isave2
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.
isave3
Contains the number of Jacobian evaluations performed by the time integrator.
isave4
Contains the order of the last backward differentiation formula method used.
isave5
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 LU decomposition of the Jacobian matrix.
14:   lisave – IntegerInput
On entry: the dimension of the array isave as declared in the (sub)program from which d03pef is called.
Constraint: lisavenpde×npts+24.
15:   itask – IntegerInput
On entry: specifies the task to be performed by the ODE integrator.
itask=1
Normal computation of output values u at t=tout.
itask=2
Take one step and return.
itask=3
Stop at the first internal integration point at or beyond t=tout.
Constraint: itask=1, 2 or 3.
16:   itrace – IntegerInput
On entry: the level of trace information required from d03pef and the underlying ODE solver as follows:
itrace-1
No output is generated.
itrace=0
Only warning messages from the PDE solver are printed on the current error message unit (see x04aaf).
itrace=1
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.
itrace=2
Output from the underlying ODE solver is similar to that produced when itrace=1, except that the advisory messages are given in greater detail.
itrace3
Output from the underlying ODE solver is similar to that produced when itrace=2, except that the advisory messages are given in greater detail.
You are advised to set itrace=0, unless you are experienced with Sub-chapter D02M–N.
17:   ind – IntegerInput/Output
On entry: indicates whether this is a continuation call or a new integration.
ind=0
Starts or restarts the integration in time.
ind=1
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 d03pef.
Constraint: ind=0 or 1.
On exit: ind=1.
18:   ifail – IntegerInput/Output
On entry: ifail must be set to 0, -1​ or ​1. If you are unfamiliar with this argument you should refer to Section 3.4 in How to Use the NAG Library and its Documentation for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value -1​ or ​1 is recommended. If the output of error messages is undesirable, then the value 1 is recommended. Otherwise, if you are not familiar with this argument, the recommended value is 0. When the value -1​ or ​1 is used it is essential to test the value of ifail on exit.
On exit: ifail=0 unless the routine detects an error or a warning has been flagged (see Section 6).

6
Error Indicators and Warnings

If on entry 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:
ifail=1
On entry,toutts,
ortout-ts is too small,
oritask1, 2 or 3,
ormesh points ​xi are not ordered correctly,
ornpts<3,
ornpde<1,
ornleft is not in the range 0 to npde,
oracc0.0,
orind0 or 1,
orlrsave is too small,
orlisave is too small,
ord03pef called initially with ind=1.
ifail=2
The underlying ODE solver cannot make any further progress across the integration range from the current point t=ts with the supplied value of acc. The components of u contain the computed values at the current point t=ts.
ifail=3
In the underlying ODE solver, there were repeated errors or corrector convergence test failures on an attempted step, before completing the requested task. The problem may have a singularity or acc is too small for the integration to continue. Incorrect positioning of boundary conditions may also result in this error. Integration was successful as far as t=ts.
ifail=4
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 3 in the pdedef or bndary, when the residual in the underlying ODE solver was being evaluated. Incorrect positioning of boundary conditions may also result in this error.
ifail=5
In solving the ODE system, a singular Jacobian has been encountered. You should check their problem formulation.
ifail=6
When evaluating the residual in solving the ODE system, ires was set to 2 in one of pdedef or bndary. Integration was successful as far as t=ts.
ifail=7
The value of acc is so small that the routine is unable to start the integration in time.
ifail=8
In either, pdedef or bndary, ires was set to an invalid value.
ifail=9 (d02nnf)
A serious error has occurred in an internal call to the specified routine. Check the problem specification and all arguments and array dimensions. Setting itrace=1 may provide more information. If the problem persists, contact NAG.
ifail=10
The required task has been completed, but it is estimated that a small change in acc is unlikely to produce any change in the computed solution. (Only applies when you are not operating in one step mode, that is when itask2.)
ifail=11
An error occurred during Jacobian formulation of the ODE system (a more detailed error description may be directed to the current advisory message unit).
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.
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.
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

d03pef 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 argument, acc.

8
Parallelism and Performance

d03pef 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.
d03pef is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
d03pef 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.

9
Further Comments

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 problem in d03pkf). In general, a second-order problem can be solved with slightly greater accuracy using the Keller box scheme instead of a finite difference scheme (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 Ut+aUx=0, where a is a constant, resulting in spurious oscillations due to the lack of dissipation. This type of problem requires a discretization scheme with upwind weighting (d03pff 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.

10
Example

This example is the simple first-order system
U1 t + U1 x + U2 x =0, U2 t +4 U1 x + U2 x =0,  
for t0,1 and x0,1.
The initial conditions are
U1x,0=expx,  U2x,0=sinx,  
and the Dirichlet boundary conditions for U1 at x=0 and U2 at x=1 are given by the exact solution:
U1x,t=12 expx+t+expx-3t+14 sinx-3t-sinx+t , U2x,t=expx-3t-expx+t+12 sinx+t+sinx-3t .  

10.1
Program Text

Program Text (d03pefe.f90)

10.2
Program Data

Program Data (d03pefe.d)

10.3
Program Results

Program Results (d03pefe.r)

GnuplotProduced by GNUPLOT 5.0 patchlevel 0 Example Program Solution, U(1,x,t), of First-order System using Keller, Box and BDF U(1,x,t) gnuplot_plot_1 gnuplot_plot_2 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 Time 0 0.2 0.4 0.6 0.8 1 x 0.5 1 1.5 2 2.5 3 3.5
GnuplotProduced by GNUPLOT 5.0 patchlevel 0 Solution, U(2,x,t), of First-order System using Keller, Box and BDF U(2,x,t) gnuplot_plot_1 gnuplot_plot_2 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 Time 0 0.2 0.4 0.6 0.8 1 x −8 −7 −6 −5 −4 −3 −2 −1 0
© The Numerical Algorithms Group Ltd, Oxford, UK. 2017