d03pfc integrates a system of linear or nonlinear convection-diffusion equations in one space dimension, with optional source terms. The system must be posed in conservative form. Convection terms are discretized using a sophisticated upwind scheme involving a user-supplied numerical flux function based on the solution of a Riemann problem at each mesh point. The method of lines is employed to reduce the PDEs to a system of ordinary differential equations (ODEs), and the resulting system is solved using a backward differentiation formula (BDF) method.
The function may be called by the names: d03pfc, nag_pde_dim1_parab_convdiff or nag_pde_parab_1d_cd.
3Description
d03pfc integrates the system of convection-diffusion equations in conservative form:
(1)
or the hyperbolic convection-only system:
(2)
for , where the vector is the set of solution values
The functions , , and depend on , and ; and depends on , , and , where is the spatial derivative of . Note that , , and must not depend on any space derivatives; and none of the functions may depend on time derivatives. In terms of conservation laws, , and are the convective flux, diffusion and source terms respectively.
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 initial values of the functions must be given at .
The PDEs are approximated by a system of ODEs in time for the values of at mesh points using a spatial discretization method similar to the central-difference scheme used in d03pcc,d03phcandd03ppc, but with the flux replaced by a numerical flux, which is a representation of the flux taking into account the direction of the flow of information at that point (i.e., the direction of the characteristics). Simple central differencing of the numerical flux then becomes a sophisticated upwind scheme in which the correct direction of upwinding is automatically achieved.
The numerical flux vector, say, must be calculated by you in terms of the left and right values of the solution vector (denoted by and respectively), at each mid-point of the mesh , for . The left and right values are calculated by d03pfc from two adjacent mesh points using a standard upwind technique combined with a Van Leer slope-limiter (see LeVeque (1990)). The physically correct value for is derived from the solution of the Riemann problem given by
(3)
where , i.e., corresponds to , with discontinuous initial values for and for , using an approximate Riemann solver. This applies for either of the systems (1) or (2); the numerical flux is independent of the functions , , and . A description of several approximate Riemann solvers can be found in LeVeque (1990) and Berzins et al. (1989). Roe's scheme (see Roe (1981)) is perhaps the easiest to understand and use, and a brief summary follows. Consider the system of PDEs or equivalently . Provided the system is linear in , i.e., the Jacobian matrix does not depend on , the numerical flux is given by
(4)
where () is the flux calculated at the left (right) value of , denoted by (); the are the eigenvalues of ; the are the right eigenvectors of ; and the are defined by
(5)
If the system is nonlinear, Roe's scheme requires that a linearized Jacobian is found (see Roe (1981)).
The functions , , and (but not
) must be specified in a pdedef. The numerical flux must be supplied in a separate numflx.
For problems in the form (2)) the NAG defined null void function pointer, NULLFN, can be supplied in the call to d03pfc.
The boundary condition specification has sufficient flexibility to allow for different types of problems. For second-order problems, i.e., depending on , a boundary condition is required for each PDE at both boundaries for the problem to be well-posed. If there are no second-order terms present, then the continuous PDE problem generally requires exactly one boundary condition for each PDE, that is npde boundary conditions in total. However, in common with most discretization schemes for first-order problems, a numerical boundary condition is required at the other boundary for each PDE. In order to be consistent with the characteristic directions of the PDE system, the numerical boundary conditions must be derived from the solution inside the domain in some manner (see below). You must supply both types of boundary conditions, i.e., a total of npde conditions at each boundary point.
The position of each boundary condition should be chosen with care. In simple terms, if information is flowing into the domain then a physical boundary condition is required at that boundary, and a numerical boundary condition is required at the other boundary. In many cases the boundary conditions are simple, e.g., for the linear advection equation. In general you should calculate the characteristics of the PDE system and specify a physical boundary condition for each of the characteristic variables associated with incoming characteristics, and a numerical boundary condition for each outgoing characteristic.
A common way of providing numerical boundary conditions is to extrapolate the characteristic variables from the inside of the domain. Note that only linear extrapolation is allowed in this function (for greater flexibility the function d03plc should be used). For problems in which the solution is known to be uniform (in space) towards a boundary during the period of integration then extrapolation is unnecessary; the numerical boundary condition can be supplied as the known solution at the boundary.
The boundary conditions must be specified in bndary in the form
(6)
at the left-hand boundary, and
(7)
at the right-hand boundary.
Note that spatial derivatives at the boundary are not passed explicitly to bndary, but they can be calculated using values of at and adjacent to the boundaries if required. However, it should be noted that instabilities may occur if such one-sided differencing opposes the characteristic direction at the boundary.
The problem is subject to the following restrictions:
(i), , and must not depend on any space derivatives;
(ii), , , and 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 by calling the pdedef at a point approximately midway between each pair of mesh points 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.
In total there are ODEs in the time direction. This system is then integrated forwards in time using a BDF method.
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
Hirsch C (1990) Numerical Computation of Internal and External Flows, Volume 2: Computational Methods for Inviscid and Viscous Flows John Wiley
LeVeque R J (1990) Numerical Methods for Conservation Laws Birkhäuser Verlag
Pennington S V and Berzins M (1994) New NAG Library software for first-order partial differential equations ACM Trans. Math. Softw.20 63–99
Roe P L (1981) Approximate Riemann solvers, parameter vectors, and difference schemes J. Comput. Phys.43 357–372
5Arguments
1: – IntegerInput
On entry: the number of PDEs to be solved.
Constraint:
.
2: – double *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:
.
3: – doubleInput
On entry: the final value of to which the integration is to be carried out.
4: – function, supplied by the userExternal Function
pdedef must evaluate the functions , , and which partially define the system of PDEs. , and may depend on , and ; may depend on , , and . pdedef is called approximately midway between each pair of mesh points in turn by d03pfc. For problems in the form (2)) the NAG defined null void function pointer, NULLFN, can be supplied in the call to d03pfc.
On entry: the current value of the independent variable .
3: – doubleInput
On entry: the current value of the space variable .
4: – const doubleInput
On entry: contains the value of the component , for .
5: – const doubleInput
On entry: contains the value of the component , for .
6: – doubleOutput
Note: the th element of the matrix is stored in .
On exit: must be set to the value of , for and .
7: – doubleOutput
On exit: must be set to the value of , for .
8: – doubleOutput
On exit: must be set to the value of , for .
9: – doubleOutput
On exit: must be set to the value of , for .
10: – Integer *Input/Output
On entry: set to or .
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 , d03pfc returns to the calling function with the error indicator set to NE_FAILED_DERIV.
11: – 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 d03pfc you may allocate memory and initialize these pointers with various quantities for use by pdedef when called from d03pfc (see Section 3.1.1 in the Introduction to the NAG Library CL Interface).
Note:pdedef should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d03pfc. If your code inadvertently does return any NaNs or infinities, d03pfc is likely to produce unexpected results.
5: – function, supplied by the userExternal Function
numflx must supply the numerical flux for each PDE given the left and right values of the solution vector . numflx is called approximately midway between each pair of mesh points in turn by d03pfc.
On entry: the current value of the independent variable .
3: – doubleInput
On entry: the current value of the space variable .
4: – const doubleInput
On entry: contains the left value of the component , for .
5: – const doubleInput
On entry: contains the right value of the component , for .
6: – doubleOutput
On exit: must be set to the numerical flux , for .
7: – Integer *Input/Output
On entry: set to or .
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 , d03pfc returns to the calling function with the error indicator set to NE_FAILED_DERIV.
8: – Nag_Comm *
Pointer to structure of type Nag_Comm; the following members are relevant to numflx.
user – double *
iuser – Integer *
p – Pointer
The type Pointer will be void *. Before calling d03pfc you may allocate memory and initialize these pointers with various quantities for use by numflx when called from d03pfc (see Section 3.1.1 in the Introduction to the NAG Library CL Interface).
9: – Nag_D03_Save *Communication Structure
If numflx calls one of the approximate Riemann solvers d03puc,d03pvc,d03pwcord03pxc then saved is used to pass data concerning the computation to the solver. You should not change the components of saved.
Note:numflx should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d03pfc. If your code inadvertently does return any NaNs or infinities, d03pfc is likely to produce unexpected results.
6: – function, supplied by the userExternal Function
bndary must evaluate the functions and which describe the physical and numerical boundary conditions, as given by (6) and (7).
On entry: the number of mesh points in the interval .
3: – doubleInput
On entry: the current value of the independent variable .
4: – const doubleInput
On entry: the mesh points in the spatial direction. corresponds to the left-hand boundary, , and corresponds to the right-hand boundary, .
5: – const doubleInput
Note: the th element of the matrix is stored in .
On entry: contains the value of solution components in the boundary region.
If , contains the value of the component at , for and .
If , contains the value of the component at , for and .
6: – IntegerInput
On entry: specifies which boundary conditions are to be evaluated.
bndary must evaluate the left-hand boundary condition at .
bndary must evaluate the right-hand boundary condition at .
7: – doubleOutput
On exit: must contain the th component of either or in (6) and (7), depending on the value of ibnd, for .
8: – Integer *Input/Output
On entry: set to or .
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 , d03pfc returns to the calling function with the error indicator set to NE_FAILED_DERIV.
9: – 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 d03pfc you may allocate memory and initialize these pointers with various quantities for use by bndary when called from d03pfc (see Section 3.1.1 in the Introduction to the NAG Library CL Interface).
Note:bndary should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d03pfc. If your code inadvertently does return any NaNs or infinities, d03pfc is likely to produce unexpected results.
7: – doubleInput/Output
Note: the th element of the matrix is stored in .
On entry: must contain the initial value of at and , for and .
On exit: will contain the computed solution at and , for and .
8: – IntegerInput
On entry: the number of mesh points in the interval .
Constraint:
.
9: – const doubleInput
On entry: the mesh points in the space direction. must specify the left-hand boundary, , and must specify the right-hand boundary, .
Constraint:
.
10: – const doubleInput
On entry: the components of acc contain the relative and absolute error tolerances used in the local error test in the time integration.
If is the estimated error for at the th mesh point, the error test is
Constraint:
and (but not both zero).
11: – doubleInput
On entry: the maximum absolute step size to be allowed in the time integration. If then no maximum is imposed.
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.
On entry: the task to be performed by the ODE integrator.
Normal computation of output values at (by overshooting and interpolating).
Take one step in the time direction and return.
Stop at first internal integration point at or beyond .
Constraint:
, or .
17: – IntegerInput
On entry: the level of trace information required from d03pfc and the underlying ODE solver. itrace may take the value , , , or .
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.
If , is assumed and similarly if , is assumed.
The advisory messages are given in greater detail as itrace increases.
18: – 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.
19: – 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 argument tout should be reset between calls to d03pfc.
Constraint:
or .
On exit: .
20: – Nag_Comm *
The NAG communication argument (see Section 3.1.1 in the Introduction to the NAG Library CL Interface).
21: – 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.
22: – NagError *Input/Output
The NAG error argument (see Section 7 in the Introduction to the NAG Library CL Interface).
6Error Indicators and Warnings
NE_ACC_IN_DOUBT
Integration completed, but small changes in acc are unlikely to result in a changed solution.
,
.
The required task has been completed, but it is estimated that a small change in the values of 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 .)
NE_ALLOC_FAIL
Dynamic memory allocation failed.
See Section 3.1.2 in the Introduction to the NAG Library CL Interface for further information.
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, numflx, or bndary.
NE_FAILED_START
Values in acc are 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:
.
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 specification of boundary conditions may also result in this error.
Underlying ODE solver cannot make further progress from the point ts with the supplied values of acc. , , .
On entry, on initial entry .
Constraint: on initial entry .
NE_INT_2
On entry, .
Constraint: .
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.
See Section 7.5 in the Introduction to the NAG Library CL Interface for further information.
Serious error in internal call to an auxiliary. Increase itrace for further details.
NE_NO_LICENCE
Your licence key may have expired or may not have been installed correctly.
See Section 8 in the Introduction to the NAG Library CL Interface for further information.
NE_NOT_CLOSE_FILE
Cannot close file .
NE_NOT_STRICTLY_INCREASING
On entry, , , and .
Constraint: .
NE_NOT_WRITE_FILE
Cannot open file for writing.
NE_REAL
On entry, .
Constraint: .
On entry, .
Constraint: .
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_TIME_DERIV_DEP
The functions , , or appear to depend on time derivatives.
NE_USER_STOP
In evaluating residual of ODE system, has been set in pdedef, numflx, or bndary. Integration is successful as far as ts: .
7Accuracy
d03pfc 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 components of the accuracy argument, acc.
8Parallelism and Performance
d03pfc is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
d03pfc 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 function. Please also consult the Users' Note for your implementation for any additional implementation-specific information.
9Further Comments
d03pfc is designed to solve systems of PDEs in conservative form, with optional source terms which are independent of space derivatives, and optional second-order diffusion terms. The use of the function to solve systems which are not naturally in this form is discouraged, and you are advised to use one of the central-difference schemes for such problems.
You should be aware of the stability limitations for hyperbolic PDEs. For most problems with small error tolerances the ODE integrator does not attempt unstable time steps, but in some cases a maximum time step should be imposed using tsmax. It is worth experimenting with this argument, particularly if the integration appears to progress unrealistically fast (with large time steps). Setting the maximum time step to the minimum mesh size is a safe measure, although in some cases this may be too restrictive.
Problems with source terms should be treated with caution, as it is known that for large source terms stable and reasonable looking solutions can be obtained which are in fact incorrect, exhibiting non-physical speeds of propagation of discontinuities (typically one spatial mesh point per time step). It is essential to employ a very fine mesh for problems with source terms and discontinuities, and to check for non-physical propagation speeds by comparing results for different mesh sizes. Further details and an example can be found in Pennington and Berzins (1994).
The time taken depends on the complexity of the system and on the accuracy requested.
10Example
For this function two examples are presented. There is a single example program for d03pfc, with a main program and the code to solve the two example problems given in Example 1 (ex1) and Example 2 (ex2).
Example 1 (ex1)
This example is a simple first-order system which illustrates the calculation of the numerical flux using Roe's approximate Riemann solver, and the specification of numerical boundary conditions using extrapolated characteristic variables. The PDEs are
for
and
. The PDEs have an exact solution given by
The initial conditions are given by the exact solution. The characteristic variables are and corresponding to the characteristics given by and respectively. Hence a physical boundary condition is required for at the left-hand boundary, and for at the right-hand boundary (corresponding to the incoming characteristics); and a numerical boundary condition is required for at the left-hand boundary, and for at the right-hand boundary (outgoing characteristics). The physical boundary conditions are obtained from the exact solution, and the numerical boundary conditions are calculated by linear extrapolation of the appropriate characteristic variable. The numerical flux is calculated using Roe's approximate Riemann solver: Using the notation in Section 3, the flux vector and the Jacobian matrix are
and the eigenvalues of are and with right eigenvectors and respectively. Using equation (4) the are given by
that is
is given by
and similarly for . From equation (4), the numerical flux vector is
that is
Example 2 (ex2)
This example is an advection-diffusion equation in which the flux term depends explicitly on :
for and . The argument is taken to be . The two physical boundary conditions are and and the initial condition is . The integration is run to steady state at which the solution is known to be across the domain with a narrow boundary layer at both boundaries. In order to write the PDE in conservative form, a source term must be introduced, i.e.,
As in Example 1, the numerical flux is calculated using the Roe approximate Riemann solver. The Riemann problem to solve locally is
The in the flux term is assumed to be constant at a local level, and so using the notation in Section 3, and . The eigenvalue is and the eigenvector (a scalar in this case) is . The numerical flux is, therefore,