NAG Library Function Document
nag_pde_parab_1d_keller (d03pec)
1 Purpose
nag_pde_parab_1d_keller (d03pec) 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
#include <nag.h> |
#include <nagd03.h> |
void |
nag_pde_parab_1d_keller (Integer npde,
double *ts,
double tout,
void |
(*pdedef)(Integer npde,
double t,
double x,
const double u[],
const double ut[],
const double ux[],
double res[],
Integer *ires,
Nag_Comm *comm),
|
|
double u[],
Integer npts,
const double x[],
Integer nleft,
double acc,
double rsave[],
Integer lrsave,
Integer isave[],
Integer lisave,
Integer itask,
Integer itrace,
const char *outfile,
Integer *ind,
Nag_Comm *comm, Nag_D03_Save *saved,
NagError *fail) |
|
3 Description
nag_pde_parab_1d_keller (d03pec) integrates the system of first-order PDEs
In particular the functions
must have the general form
where
and
depend on
,
,
,
and the vector
is the set of solution values
and the vector
is its partial derivative with respect to
. Note that
and
must not depend on
.
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 mesh should be chosen in accordance with the expected behaviour of the solution.
The PDE system which is defined by the functions
must be specified in
pdedef.
The initial values of the functions
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 functions.
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 (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
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) |
, so that integration is in the forward direction; |
(ii) |
and must not depend on any time derivatives; |
(iii) |
The evaluation of the function 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 ; |
(iv) |
At least one of the functions 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
at each mesh point. In total there are
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:
.
- 2:
ts – double *Input/Output
On entry: the initial value of the independent variable .
Constraint:
.
On exit: the value of
corresponding to the solution values in
u. Normally
.
- 3:
tout – doubleInput
On entry: the final value of to which the integration is to be carried out.
- 4:
pdedef – function, supplied by the userExternal Function
pdedef must compute the functions
which define the system of PDEs.
pdedef is called approximately midway between each pair of mesh points in turn by nag_pde_parab_1d_keller (d03pec).
The specification of
pdedef is:
void |
pdedef (Integer npde,
double t,
double x,
const double u[],
const double ut[],
const double ux[],
double res[],
Integer *ires,
Nag_Comm *comm)
|
|
- 1:
npde – IntegerInput
On entry: the number of PDEs in the system.
- 2:
t – doubleInput
On entry: the current value of the independent variable .
- 3:
x – doubleInput
On entry: the current value of the space variable .
- 4:
u[npde] – const doubleInput
On entry: contains the value of the component , for .
- 5:
ut[npde] – const doubleInput
On entry: contains the value of the component , for .
- 6:
ux[npde] – const doubleInput
On entry: contains the value of the component , for .
- 7:
res[npde] – doubleOutput
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
(2).
The definition of
is determined by the input value of
ires.
- 8:
ires – Integer *Input/Output
On entry: the form of
that must be returned in the array
res.
- Equation (8) must be used.
- Equation (9) must be used.
On exit: should usually remain unchanged. However, you may set
ires to force the integration function to take certain actions, as described below:
- Indicates to the integrator that control should be passed back immediately to the calling function with the error indicator set to NE_USER_STOP.
- 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 nag_pde_parab_1d_keller (d03pec) returns to the calling function with the error indicator set to NE_FAILED_DERIV.
- 9:
comm – Nag_Comm *
Pointer to structure of type Nag_Comm; the following members are relevant to
pdedef.
- user – double *
- iuser – Integer *
- p – Pointer
The type Pointer will be
void *. Before calling nag_pde_parab_1d_keller (d03pec) you may allocate memory and initialize these pointers with various quantities for use by
pdedef when called from nag_pde_parab_1d_keller (d03pec) (see
Section 3.2.1.1 in the Essential Introduction).
- 5:
bndary – function, supplied by the userExternal Function
bndary must compute the functions
and
which define the boundary conditions as in equations
(4) and
(5).
The specification of
bndary is:
void |
bndary (Integer npde,
double t,
Integer ibnd,
Integer nobc,
const double u[],
const double ut[],
double res[],
Integer *ires,
Nag_Comm *comm)
|
|
- 1:
npde – IntegerInput
On entry: the number of PDEs in the system.
- 2:
t – doubleInput
On entry: the current value of the independent variable .
- 3:
ibnd – IntegerInput
On entry: determines the position of the boundary conditions.
- bndary must compute the left-hand boundary condition at .
- Indicates that bndary must compute the right-hand boundary condition at .
- 4:
nobc – IntegerInput
On entry: specifies the number of boundary conditions at the boundary specified by
ibnd.
- 5:
u[npde] – const doubleInput
On entry:
contains the value of the component
at the boundary specified by
ibnd, for
.
- 6:
ut[npde] – const doubleInput
On entry:
contains the value of the component
at the boundary specified by
ibnd, for
.
- 7:
res[nobc] – doubleOutput
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
(6), and similarly for
.
The definitions of
and
are determined by the input value of
ires.
- 8:
ires – Integer *Input/Output
On entry: the form
(or
) that must be returned in the array
res.
- Equation (10) must be used.
- Equation (11) must be used.
On exit: should usually remain unchanged. However, you may set
ires to force the integration function to take certain actions, as described below:
- Indicates to the integrator that control should be passed back immediately to the calling function with the error indicator set to NE_USER_STOP.
- 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 nag_pde_parab_1d_keller (d03pec) returns to the calling function with the error indicator set to NE_FAILED_DERIV.
- 9:
comm – Nag_Comm *
Pointer to structure of type Nag_Comm; the following members are relevant to
bndary.
- user – double *
- iuser – Integer *
- p – Pointer
The type Pointer will be
void *. Before calling nag_pde_parab_1d_keller (d03pec) you may allocate memory and initialize these pointers with various quantities for use by
bndary when called from nag_pde_parab_1d_keller (d03pec) (see
Section 3.2.1.1 in the Essential Introduction).
- 6:
u[] – doubleInput/Output
On entry: the initial values of at and the mesh points
, for .
On exit: will contain the computed solution at .
- 7:
npts – IntegerInput
On entry: the number of mesh points in the interval .
Constraint:
.
- 8:
x[npts] – const doubleInput
On entry: the mesh points in the spatial direction. must specify the left-hand boundary, , and must specify the right-hand boundary, .
Constraint:
.
- 9:
nleft – IntegerInput
On entry: the number of boundary conditions at the left-hand mesh point .
Constraint:
.
- 10:
acc – doubleInput
On entry: a positive quantity for controlling the local error estimate in the time integration. If
is the estimated error for
at the
th mesh point, the error test is:
Constraint:
.
- 11:
rsave[lrsave] – doubleCommunication Array
If
,
rsave need not be set on entry.
If
,
rsave must be unchanged from the previous call to the function because it contains required information about the iteration.
- 12:
lrsave – IntegerInput
On entry: the dimension of the array
rsave.
Constraint:
.
- 13:
isave[lisave] – IntegerCommunication Array
If
,
isave need not be set on entry.
If
,
isave must be unchanged from the previous call to the function 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.
- 14:
lisave – IntegerInput
On entry: the dimension of the array
isave.
Constraint:
.
- 15:
itask – IntegerInput
On entry: specifies the task to be performed by the ODE integrator.
- Normal computation of output values at .
- Take one step and return.
- Stop at the first internal integration point at or beyond .
Constraint:
, or .
- 16:
itrace – IntegerInput
On entry: the level of trace information required from nag_pde_parab_1d_keller (d03pec) and the underlying ODE solver as follows:
- No output is generated.
- Only warning messages from the PDE solver are printed .
- Output from the underlying ODE solver is printed . 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 are advised to set .
- 17:
outfile – const char *Input
On entry: the name of a file to which diagnostic output will be directed. If
outfile is
NULL the diagnostic output will be directed to standard output.
- 18:
ind – 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 function. In this case, only the arguments tout and fail should be reset between calls to nag_pde_parab_1d_keller (d03pec).
Constraint:
or .
On exit: .
- 19:
comm – Nag_Comm *Communication Structure
-
The NAG communication argument (see
Section 3.2.1.1 in the Essential Introduction).
- 20:
saved – Nag_D03_Save *Communication Structure
saved must remain unchanged following a previous call to a
Chapter d03 function and prior to any subsequent call to a
Chapter d03 function.
- 21:
fail – NagError *Input/Output
-
The NAG error argument (see
Section 3.6 in the Essential Introduction).
6 Error Indicators and Warnings
- NE_ACC_IN_DOUBT
-
Integration completed, but a small change in
acc is unlikely to result in a changed solution.
.
- NE_ALLOC_FAIL
-
Dynamic memory allocation failed.
- NE_BAD_PARAM
-
On entry, argument had an illegal value.
- NE_FAILED_DERIV
-
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.
- NE_FAILED_START
-
acc was too small to start integration:
.
- NE_FAILED_STEP
-
Error during Jacobian formulation for ODE system. Increase
itrace for further details.
Repeated errors in an attempted step of underlying ODE solver. Integration was successful as far as
ts:
.
Underlying ODE solver cannot make further progress from the point
ts with the supplied value of
acc.
,
.
- NE_INT
-
ires set to an invalid value in call to
pdedef or
bndary.
On entry, .
Constraint: or .
On entry, .
Constraint: , or .
On entry, .
Constraint: .
On entry, .
Constraint: .
On entry, .
Constraint: .
- NE_INT_2
-
On entry,
lisave is too small:
. Minimum possible dimension:
.
On entry,
lrsave is too small:
. Minimum possible dimension:
.
On entry, ,
.
Constraint: .
- NE_INTERNAL_ERROR
-
An internal error has occurred in this function. Check the function call and any array sizes. If the call is correct then please contact
NAG for assistance.
Serious error in internal call to an auxiliary. Increase
itrace for further details.
- NE_NOT_CLOSE_FILE
-
Cannot close file .
- NE_NOT_STRICTLY_INCREASING
-
On entry, mesh points
x appear to be badly ordered:
,
,
and
.
- NE_NOT_WRITE_FILE
-
Cannot open file for writing.
- NE_REAL
-
On entry, .
Constraint: .
- NE_REAL_2
-
On entry, and .
Constraint: .
On entry, is too small:
and .
- NE_SING_JAC
-
Singular Jacobian of ODE system. Check problem formulation.
- NE_USER_STOP
-
In evaluating residual of ODE system,
has been set in
pdedef or
bndary. Integration is successful as far as
ts:
.
7 Accuracy
nag_pde_parab_1d_keller (d03pec) 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
nag_pde_parab_1d_keller (d03pec) is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
nag_pde_parab_1d_keller (d03pec) 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
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 problem in
nag_pde_parab_1d_keller_ode (d03pkc)). In general, a second-order problem can be solved with slightly greater accuracy using the Keller box scheme instead of a finite difference scheme (
nag_pde_parab_1d_fd (d03pcc) or
nag_pde_parab_1d_fd_ode (d03phc) 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 (
nag_pde_parab_1d_cd (d03pfc) 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
for
and
.
The initial conditions are
and the Dirichlet boundary conditions for
at
and
at
are given by the exact solution:
10.1 Program Text
Program Text (d03pece.c)
10.2 Program Data
None.
10.3 Program Results
Program Results (d03pece.r)