NAG Library Routine Document

d03pcf  (dim1_parab_fd_old)
d03pca (dim1_parab_fd)

1
Purpose

d03pcf/d03pca integrates a system of linear or nonlinear parabolic partial differential equations (PDEs) in one space variable. The spatial discretization is performed using finite differences, 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 method.
d03pca is a version of d03pcf that has additional arguments in order to make it safe for use in multithreaded applications (see Section 5).

2
Specification

2.1
Specification for d03pcf

Fortran Interface
Subroutine d03pcf ( npde, m, ts, tout, pdedef, bndary, u, npts, x, acc, rsave, lrsave, isave, lisave, itask, itrace, ind, ifail)
Integer, Intent (In):: npde, m, npts, 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  d03pcf_ (const Integer *npde, const Integer *m, double *ts, const double *tout,
void (NAG_CALL *pdedef)(const Integer *npde, const double *t, const double *x, const double u[], const double ux[], double p[], double q[], double r[], Integer *ires),
void (NAG_CALL *bndary)(const Integer *npde, const double *t, const double u[], const double ux[], const Integer *ibnd, double beta[], double gamma[], Integer *ires),
double u[], const Integer *npts, const double x[], const double *acc, double rsave[], const Integer *lrsave, Integer isave[], const Integer *lisave, const Integer *itask, const Integer *itrace, Integer *ind, Integer *ifail)

2.2
Specification for d03pca

Fortran Interface
Subroutine d03pca ( npde, m, ts, tout, pdedef, bndary, u, npts, x, acc, rsave, lrsave, isave, lisave, itask, itrace, ind, iuser, ruser, cwsav, lwsav, iwsav, rwsav, ifail)
Integer, Intent (In):: npde, m, npts, lrsave, lisave, itask, itrace
Integer, Intent (Inout):: isave(lisave), ind, iuser(*), iwsav(505), ifail
Real (Kind=nag_wp), Intent (In):: tout, x(npts), acc
Real (Kind=nag_wp), Intent (Inout):: ts, u(npde,npts), rsave(lrsave), ruser(*), rwsav(1100)
Logical, Intent (Inout):: lwsav(100)
Character (80), Intent (Inout):: cwsav(10)
External:: pdedef, bndary
C Header Interface
#include <nagmk26.h>
void  d03pca_ (const Integer *npde, const Integer *m, double *ts, const double *tout,
void (NAG_CALL *pdedef)(const Integer *npde, const double *t, const double *x, const double u[], const double ux[], double p[], double q[], double r[], Integer *ires, Integer iuser[], double ruser[]),
void (NAG_CALL *bndary)(const Integer *npde, const double *t, const double u[], const double ux[], const Integer *ibnd, double beta[], double gamma[], Integer *ires, Integer iuser[], double ruser[]),
double u[], const Integer *npts, const double x[], const double *acc, double rsave[], const Integer *lrsave, Integer isave[], const Integer *lisave, const Integer *itask, const Integer *itrace, Integer *ind, Integer iuser[], double ruser[], char cwsav[], logical lwsav[], Integer iwsav[], double rwsav[], Integer *ifail, const Charlen length_cwsav)

3
Description

d03pcf/d03pca integrates the system of parabolic equations:
j=1npdePi,j Uj t +Qi=x-m x xmRi,  i=1,2,,npde,  axb,  tt0, (1)
where Pi,j, Qi and Ri 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 , (2)
and the vector Ux is its partial derivative with respect to x. Note that Pi,j, Qi and Ri 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 coordinate system in space is defined by the value of m; m=0 for Cartesian coordinates, m=1 for cylindrical polar coordinates and m=2 for spherical polar coordinates. The mesh should be chosen in accordance with the expected behaviour of the solution.
The system is defined by the functions Pi,j, Qi and Ri which must be specified in pdedef.
The initial values of the functions Ux,t must be given at t=t0. The functions Ri, for i=1,2,,npde, which may be thought of as fluxes, are also used in the definition of the boundary conditions for each equation. The boundary conditions must have the form
βix,tRix,t,U,Ux=γix,t,U,Ux,  i=1,2,,npde, (3)
where x=a or x=b.
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, Qi and the flux Ri must not depend on any time derivatives;
(iii) the evaluation of the functions Pi,j, Qi and Ri is done at the mid-points of the mesh intervals 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 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; and
(v) if m>0 and x1=0.0, 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 x=0.0 or by specifying a zero flux there, that is βi=1.0 and γi=0.0. See also Section 9.
The parabolic equations are approximated by a system of ODEs in time for the values of Ui 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 npde×npts ODEs in the time direction. This system is then integrated forwards in time using a backward differentiation formula 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
Dew P M and Walsh J (1981) A set of library routines for solving parabolic equations in one space variable ACM Trans. Math. Software 7 295–314
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
Arguments

1:     npde – IntegerInput
On entry: the number of PDEs in the system to be solved.
Constraint: npde1.
2:     m – IntegerInput
On entry: the coordinate system used:
m=0
Indicates Cartesian coordinates.
m=1
Indicates cylindrical polar coordinates.
m=2
Indicates spherical polar coordinates.
Constraint: m=0, 1 or 2.
3:     ts – Real (Kind=nag_wp)Input/Output
On entry: the initial value of the independent variable t.
On exit: the value of t corresponding to the solution values in u. Normally ts=tout.
Constraint: ts<tout.
4:     tout – Real (Kind=nag_wp)Input
On entry: the final value of t to which the integration is to be carried out.
5:     pdedef – Subroutine, supplied by the user.External Procedure
pdedef must compute the functions Pi,j, Qi and Ri which define the system of PDEs. pdedef is called approximately midway between each pair of mesh points in turn by d03pcf/d03pca.
The specification of pdedef for d03pcf is:
Fortran Interface
Subroutine pdedef ( npde, t, x, u, ux, p, q, r, ires)
Integer, Intent (In):: npde
Integer, Intent (Inout):: ires
Real (Kind=nag_wp), Intent (In):: t, x, u(npde), ux(npde)
Real (Kind=nag_wp), Intent (Out):: p(npde,npde), q(npde), r(npde)
C Header Interface
#include <nagmk26.h>
void  pdedef (const Integer *npde, const double *t, const double *x, const double u[], const double ux[], double p[], double q[], double r[], Integer *ires)
The specification of pdedef for d03pca is:
Fortran Interface
Subroutine pdedef ( npde, t, x, u, ux, p, q, r, ires, iuser, ruser)
Integer, Intent (In):: npde
Integer, Intent (Inout):: ires, iuser(*)
Real (Kind=nag_wp), Intent (In):: t, x, u(npde), ux(npde)
Real (Kind=nag_wp), Intent (Inout):: ruser(*)
Real (Kind=nag_wp), Intent (Out):: p(npde,npde), q(npde), r(npde)
C Header Interface
#include <nagmk26.h>
void  pdedef (const Integer *npde, const double *t, const double *x, const double u[], const double ux[], double p[], double q[], double r[], Integer *ires, Integer iuser[], double ruser[])
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:     uxnpde – Real (Kind=nag_wp) arrayInput
On entry: uxi contains the value of the component Uix,t x , for i=1,2,,npde.
6:     pnpdenpde – Real (Kind=nag_wp) arrayOutput
On exit: pij must be set to the value of Pi,jx,t,U,Ux, for i=1,2,,npde and j=1,2,,npde.
7:     qnpde – Real (Kind=nag_wp) arrayOutput
On exit: qi must be set to the value of Qix,t,U,Ux, for i=1,2,,npde.
8:     rnpde – Real (Kind=nag_wp) arrayOutput
On exit: ri must be set to the value of Rix,t,U,Ux, for i=1,2,,npde.
9:     ires – IntegerInput/Output
On entry: set to -1 or 1.
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, d03pcf/d03pca returns to the calling subroutine with the error indicator set to ifail=4.
Note: the following are additional arguments for specific use with d03pca. Users of d03pcf therefore need not read the remainder of this description.
10:   iuser* – Integer arrayUser Workspace
11:   ruser* – Real (Kind=nag_wp) arrayUser Workspace
pdedef is called with the arguments iuser and ruser as supplied to d03pcf/d03pca. You should use the arrays iuser and ruser to supply information to pdedef.
pdedef must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d03pcf/d03pca 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 d03pcf/d03pca. If your code inadvertently does return any NaNs or infinities, d03pcf/d03pca is likely to produce unexpected results.
6:     bndary – Subroutine, supplied by the user.External Procedure
bndary must compute the functions βi and γi which define the boundary conditions as in equation (3).
The specification of bndary for d03pcf is:
Fortran Interface
Subroutine bndary ( npde, t, u, ux, ibnd, beta, gamma, ires)
Integer, Intent (In):: npde, ibnd
Integer, Intent (Inout):: ires
Real (Kind=nag_wp), Intent (In):: t, u(npde), ux(npde)
Real (Kind=nag_wp), Intent (Out):: beta(npde), gamma(npde)
C Header Interface
#include <nagmk26.h>
void  bndary (const Integer *npde, const double *t, const double u[], const double ux[], const Integer *ibnd, double beta[], double gamma[], Integer *ires)
The specification of bndary for d03pca is:
Fortran Interface
Subroutine bndary ( npde, t, u, ux, ibnd, beta, gamma, ires, iuser, ruser)
Integer, Intent (In):: npde, ibnd
Integer, Intent (Inout):: ires, iuser(*)
Real (Kind=nag_wp), Intent (In):: t, u(npde), ux(npde)
Real (Kind=nag_wp), Intent (Inout):: ruser(*)
Real (Kind=nag_wp), Intent (Out):: beta(npde), gamma(npde)
C Header Interface
#include <nagmk26.h>
void  bndary (const Integer *npde, const double *t, const double u[], const double ux[], const Integer *ibnd, double beta[], double gamma[], Integer *ires, Integer iuser[], double ruser[])
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:     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.
4:     uxnpde – Real (Kind=nag_wp) arrayInput
On entry: uxi contains the value of the component Uix,t x  at the boundary specified by ibnd, for i=1,2,,npde.
5:     ibnd – IntegerInput
On entry: determines the position of the boundary conditions.
ibnd=0
bndary must set up the coefficients of the left-hand boundary, x=a.
ibnd0
Indicates that bndary must set up the coefficients of the right-hand boundary, x=b.
6:     betanpde – Real (Kind=nag_wp) arrayOutput
On exit: betai must be set to the value of βix,t at the boundary specified by ibnd, for i=1,2,,npde.
7:     gammanpde – Real (Kind=nag_wp) arrayOutput
On exit: gammai must be set to the value of γix,t,U,Ux at the boundary specified by ibnd, for i=1,2,,npde.
8:     ires – IntegerInput/Output
On entry: set to -1 or 1.
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, d03pcf/d03pca returns to the calling subroutine with the error indicator set to ifail=4.
Note: the following are additional arguments for specific use with d03pca. Users of d03pcf therefore need not read the remainder of this description.
9:     iuser* – Integer arrayUser Workspace
10:   ruser* – Real (Kind=nag_wp) arrayUser Workspace
bndary is called with the arguments iuser and ruser as supplied to d03pcf/d03pca. You should use the arrays iuser and ruser to supply information to bndary.
bndary must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d03pcf/d03pca 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 d03pcf/d03pca. If your code inadvertently does return any NaNs or infinities, d03pcf/d03pca is likely to produce unexpected results.
7:     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.
8:     npts – IntegerInput
On entry: the number of mesh points in the interval a,b.
Constraint: npts3.
9:     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.
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 d03pcf/d03pca is called.
Constraint: lrsave6×npde+10×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 d03pcf/d03pca 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
One step and return.
itask=3
Stop at 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 d03pcf/d03pca and the underlying ODE solver. itrace may take the value -1, 0, 1, 2 or 3.
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>0
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 itrace<-1, -1 is assumed and similarly if itrace>3, 3 is assumed.
The advisory messages are given in greater detail as itrace increases. 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 d03pcf/d03pca.
Constraint: ind=0 or 1.
On exit: ind=1.
18:   ifail – IntegerInput/Output
Note: for d03pca, ifail does not occur in this position in the argument list. See the additional arguments described below.
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).
Note: the following are additional arguments for specific use with d03pca. Users of d03pcf therefore need not read the remainder of this description.
18:   iuser* – Integer arrayUser Workspace
19:   ruser* – Real (Kind=nag_wp) arrayUser Workspace
iuser and ruser are not used by d03pcf/d03pca, but are passed directly to pdedef and bndary and may be used to pass information to these routines.
20:   cwsav10 – Character(80) arrayCommunication Array
If ind=0, cwsav need not be set on entry.
If ind=1, cwsav must be unchanged from the previous call to the routine.
21:   lwsav100 – Logical arrayCommunication Array
If ind=0, lwsav need not be set on entry.
If ind=1, lwsav must be unchanged from the previous call to the routine.
22:   iwsav505 – Integer arrayCommunication Array
If ind=0, iwsav need not be set on entry.
If ind=1, iwsav must be unchanged from the previous call to the routine.
23:   rwsav1100 – Real (Kind=nag_wp) arrayCommunication Array
If ind=0, rwsav need not be set on entry.
If ind=1, rwsav must be unchanged from the previous call to the routine.
24:   ifail – IntegerInput/Output
Note: see the argument description for ifail above.

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, acc=value.
Constraint: acc>0.0.
On entry, i=value, xi=value, j=value and xj=value.
Constraint: x1<x2<<xnpts.
On entry, ind=value.
Constraint: ind=0 or 1.
On entry, itask=value.
Constraint: itask=1, 2 or 3.
On entry, lisave=value.
Constraint: lisavevalue.
On entry, lrsave=value.
Constraint: lrsavevalue.
On entry, m=value.
Constraint: m=0, 1 or 2.
On entry, m=value and x1=value.
Constraint: m0 or x10.0 
On entry, npde=value.
Constraint: npde1.
On entry, npts=value.
Constraint: npts3.
On entry, on initial entry ind=1.
Constraint: on initial entry ind=0.
On entry, tout=value and ts=value.
Constraint: tout>ts.
On entry, tout-ts is too small: tout=value and ts=value.
ifail=2
Underlying ODE solver cannot make further progress from the point ts with the supplied value of acc. ts=value, acc=value.
ifail=3
Repeated errors in an attempted step of underlying ODE solver. Integration was successful as far as ts: ts=value.
ifail=4
In setting up the ODE system an internal auxiliary was unable to initialize the derivative. This could be due to your setting ires=3 in pdedef or bndary.
ifail=5
Singular Jacobian of ODE system. Check problem formulation.
ifail=6
In evaluating residual of ODE system, ires=2 has been set in pdedef or bndary. Integration is successful as far as ts: ts=value.
ifail=7
acc was too small to start integration: acc=value.
ifail=8
ires set to an invalid value in call to pdedef or bndary.
ifail=9
Serious error in internal call to an auxiliary. Increase itrace for further details.
ifail=10
Integration completed, but a small change in acc is unlikely to result in a changed solution. acc=value.
ifail=11
Error during Jacobian formulation for ODE system. Increase itrace for further details.
ifail=14
Flux function appears to depend on time derivatives.
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

d03pcf/d03pca 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

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

d03pcf/d03pca is designed to solve parabolic systems (possibly including some elliptic equations) with second-order derivatives in space. The argument 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 d03pef.
The time taken depends on the complexity of the parabolic system and on the accuracy requested.

10
Example

We use the example given in Dew and Walsh (1981) which consists of an elliptic-parabolic pair of PDEs. The problem was originally derived from a single third-order in space PDE. The elliptic equation is
1r r r2 U1 r =4α U2+r U2 r  
and the parabolic equation is
1-r2 U2 t =1r r r U2 r -U2U1  
where r,t0,1×0,1. The boundary conditions are given by
U1= U2 r =0  at ​r=0,  
and
r rU1= 0   and   U2= 0   at ​ r=1.  
The first of these boundary conditions implies that the flux term in the second PDE, U2 r - U2 U1 , is zero at r=0.
The initial conditions at t=0 are given by
U1=2αr  and  U2=1.0,   ​r0,1.  
The value α=1 was used in the problem definition. A mesh of 20 points was used with a circular mesh spacing to cluster the points towards the right-hand side of the spatial interval, r=1.

10.1
Program Text

Note: the following programs illustrate the use of d03pcf and d03pca.

Program Text (d03pcfe.f90)

Program Text (d03pcae.f90)

10.2
Program Data

Program Data (d03pcfe.d)

Program Data (d03pcae.d)

10.3
Program Results

Program Results (d03pcfe.r)

Program Results (d03pcae.r)

GnuplotProduced by GNUPLOT 5.0 patchlevel 0 Example Program Solution, U(1,x,t), of Elliptic-parabolic Pair using Method of Lines and BDF Method U(1,x,t) gnuplot_plot_1 gnuplot_plot_2 0.000010 0.000100 0.001000 0.010000 0.100000 1.000000 Time (logscale) 0 0.2 0.4 0.6 0.8 1 x 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2
GnuplotProduced by GNUPLOT 5.0 patchlevel 0 Solution, U(2,x,t), of Elliptic-parabolic Pair using Finite-differences and BDF U(2,x,t) gnuplot_plot_1 gnuplot_plot_2 0.000010 0.000100 0.001000 0.010000 0.100000 1.000000 Time (logscale) 0 0.2 0.4 0.6 0.8 1 x 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1