NAG Library Routine Document
D03PDF/D03PDA
1 Purpose
D03PDF/D03PDA integrates a system of linear or nonlinear parabolic partial differential equations (PDEs) in one space variable. The spatial discretization is performed using a Chebyshev C0 collocation method, 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.
D03PDA is a version of D03PDF that has additional parameters in order to make it safe for use in multithreaded applications (see
Section 5).
2 Specification
2.1 Specification for D03PDF
| SUBROUTINE D03PDF ( | NPDE, M, TS, TOUT, PDEDEF, BNDARY, U, NBKPTS, XBKPTS, NPOLY, NPTS, X, UINIT, ACC, RSAVE, LRSAVE, ISAVE, LISAVE, ITASK, ITRACE, IND, IFAIL) |
| INTEGER | NPDE, M, NBKPTS, NPOLY, NPTS, LRSAVE, ISAVE(LISAVE), LISAVE, ITASK, ITRACE, IND, IFAIL |
| double precision | TS, TOUT, U(NPDE,NPTS), XBKPTS(NBKPTS), X(NPTS), ACC, RSAVE(LRSAVE) |
| EXTERNAL | PDEDEF, BNDARY, UINIT |
2.2 Specification for D03PDA
| SUBROUTINE D03PDA ( | NPDE, M, TS, TOUT, PDEDEF, BNDARY, U, NBKPTS, XBKPTS, NPOLY, NPTS, X, UINIT, ACC, RSAVE, LRSAVE, ISAVE, LISAVE, ITASK, ITRACE, IND, IUSER, RUSER, CWSAV, LWSAV, IWSAV, RWSAV, IFAIL) |
| INTEGER | NPDE, M, NBKPTS, NPOLY, NPTS, LRSAVE, ISAVE(LISAVE), LISAVE, ITASK, ITRACE, IND, IUSER(*), IWSAV(505), IFAIL |
| double precision | TS, TOUT, U(NPDE,NPTS), XBKPTS(NBKPTS), X(NPTS), ACC, RSAVE(LRSAVE), RUSER(*), RWSAV(1100) |
| LOGICAL | LWSAV(100) |
| CHARACTER*80 | CWSAV(10) |
| EXTERNAL | PDEDEF, BNDARY, UINIT |
3 Description
D03PDF/D03PDA integrates the system of parabolic equations:
where
Pi,j,
Qi and
Ri depend on
x,
t,
U,
Ux and the vector
U is the set of solution values
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 a≤x≤b, where a=x1 and b=xNBKPTS are the leftmost and rightmost of a user-defined set of break points x1,x2,…,xNBKPTS. The co-ordinate system in space is defined by the value of m; m=0 for Cartesian co-ordinates, m=1 for cylindrical polar co-ordinates and m=2 for spherical polar co-ordinates.
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, and must be specified in
UINIT.
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
where
x=a or
x=b.
The boundary conditions must be specified in
BNDARY. Thus, 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 both the break points and internally selected points for each element in turn, that is Pi,j, Qi and Ri are evaluated twice at each break point. Any discontinuities in these functions must therefore be at one or more of the break points x1,x2,…,xNBKPTS; |
| (iv) |
at least one of the functions Pi,j must be nonzero so that there is a time derivative present in the problem; |
| (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 8. |
The parabolic equations are approximated by a system of ODEs in time for the values of
Ui at the mesh points. This ODE system is obtained by approximating the PDE solution between each pair of break points by a Chebyshev polynomial of degree
NPOLY. The interval between each pair of break points is treated by D03PDF/D03PDA as an element, and on this element, a polynomial and its space and time derivatives are made to satisfy the system of PDEs at
NPOLY-1 spatial points, which are chosen internally by the code and the break points. In the case of just one element, the break points are the boundaries. The user-defined break points and the internally selected points together define the mesh. The smallest value that
NPOLY can take is one, in which case, the solution is approximated by piecewise linear polynomials between consecutive break points and the method is similar to an ordinary finite element method.
In total there are NBKPTS-1×NPOLY+1 mesh points in the spatial direction, and NPDE×NBKPTS-1×NPOLY+1 ODEs in the time direction; one ODE at each break point for each PDE component and (NPOLY-1) ODEs for each PDE component between each pair of break points. The 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 and Dew P M (1991) Algorithm 690: Chebyshev polynomial software for elliptic-parabolic systems of PDEs
ACM Trans. Math. Software 17 178–206
Zaturska N B, Drazin P G and Banks W H H (1988) On the flow of a viscous fluid driven along a channel by a suction at porous walls
Fluid Dynamics Research 4 5 Parameters
- 1: NPDE – INTEGERInput
-
On entry:
the number of PDEs in the system to be solved.
Constraint:
NPDE≥1.
- 2: M – INTEGERInput
-
On entry: the co-ordinate system used:
- M=0
- Indicates Cartesian co-ordinates.
- M=1
- Indicates cylindrical polar co-ordinates.
- M=2
- Indicates spherical polar co-ordinates.
Constraint:
M=0, 1 or 2.
- 3: TS – double precisionInput/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 – double precisionInput
-
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 values of the functions
Pi,j,
Qi and
Ri which define the system of PDEs. The functions may depend on
x,
t,
U and
Ux and must be evaluated at a set of points.
The specification of
PDEDEF
for D03PDF is:
| SUBROUTINE PDEDEF ( | NPDE, T, X, NPTL, U, UX, P, Q, R, IRES) |
| INTEGER | NPDE, NPTL, IRES |
| double precision | T, X(NPTL), U(NPDE,NPTL), UX(NPDE,NPTL), P(NPDE,NPDE,NPTL), Q(NPDE,NPTL), R(NPDE,NPTL) |
The specification of
PDEDEF
for D03PDA is:
| SUBROUTINE PDEDEF ( | NPDE, T, X, NPTL, U, UX, P, Q, R, IRES, IUSER, RUSER) |
| INTEGER | NPDE, NPTL, IRES, IUSER(*) |
| double precision | T, X(NPTL), U(NPDE,NPTL), UX(NPDE,NPTL), P(NPDE,NPDE,NPTL), Q(NPDE,NPTL), R(NPDE,NPTL), RUSER(*) |
- 1: NPDE – INTEGERInput
-
On entry: the number of PDEs in the system.
- 2: T – double precisionInput
-
On entry: the current value of the independent variable t.
- 3: X(NPTL) – double precision arrayInput
-
On entry: contains a set of mesh points at which Pi,j, Qi and Ri are to be evaluated. X1 and XNPTL contain successive user-supplied break points and the elements of the array will satisfy X1<X2<⋯<XNPTL.
- 4: NPTL – INTEGERInput
-
On entry: the number of points at which evaluations are required (the value of NPOLY+1).
- 5: U(NPDE,NPTL) – double precision arrayInput
-
On entry: Uij contains the value of the component Uix,t where x=Xj, for i=1,2,…,NPDE and j=1,2,…,NPTL.
- 6: UX(NPDE,NPTL) – double precision arrayInput
-
On entry: UXij contains the value of the component
∂Uix,t
∂x
where x=Xj, for i=1,2,…,NPDE and j=1,2,…,NPTL.
- 7: P(NPDE,NPDE,NPTL) – double precision arrayOutput
-
On exit: Pijk must be set to the value of Pi,jx,t,U,Ux where x=Xk, for i,j=1,2,…,NPDE and k=1,2,…,NPTL.
- 8: Q(NPDE,NPTL) – double precision arrayOutput
-
On exit: Qij must be set to the value of Qix,t,U,Ux where x=Xj, for i=1,2,…,NPDE and j=1,2,…,NPTL.
- 9: R(NPDE,NPTL) – double precision arrayOutput
-
On exit: Rij must be set to the value of Rix,t,U,Ux where x=Xj, for i=1,2,…,NPDE and j=1,2,…,NPTL.
- 10: 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 subroutine 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, then D03PDF/D03PDA returns to the calling subroutine with the error indicator set to IFAIL=4.
- Note: the following are additional parameters for specific use with D03PDA. Users of D03PDF therefore need not read the remainder of this description.
- 11: IUSER(*) – INTEGER arrayUser Workspace
- 12: RUSER(*) – double precision arrayUser Workspace
PDEDEF is called from D03PDA with the parameters
IUSER and
RUSER as supplied to D03PDA. You are free to use the arrays
IUSER and
RUSER to supply information to
PDEDEF.
PDEDEF must be declared as EXTERNAL in the (sub)program from which D03PDF/D03PDA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 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 D03PDF is:
| SUBROUTINE BNDARY ( | NPDE, T, U, UX, IBND, BETA, GAMMA, IRES) |
| INTEGER | NPDE, IBND, IRES |
| double precision | T, U(NPDE), UX(NPDE), BETA(NPDE), GAMMA(NPDE) |
The specification of
BNDARY
for D03PDA is:
| SUBROUTINE BNDARY ( | NPDE, T, U, UX, IBND, BETA, GAMMA, IRES, IUSER, RUSER) |
| INTEGER | NPDE, IBND, IRES, IUSER(*) |
| double precision | T, U(NPDE), UX(NPDE), BETA(NPDE), GAMMA(NPDE), RUSER(*) |
- 1: NPDE – INTEGERInput
-
On entry: the number of PDEs in the system.
- 2: T – double precisionInput
-
On entry: the current value of the independent variable t.
- 3: U(NPDE) – double precision arrayInput
-
On entry:
Ui contains the value of the component
Uix,t at the boundary specified by
IBND, for
i=1,2,…,NPDE.
- 4: UX(NPDE) – double precision 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: specifies which boundary conditions are to be evaluated.
- IBND=0
- BNDARY must set up the coefficients of the left-hand boundary, x=a.
- IBND≠0
- BNDARY must set up the coefficients of the right-hand boundary, x=b.
- 6: BETA(NPDE) – double precision 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: GAMMA(NPDE) – double precision 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 subroutine 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, then D03PDF/D03PDA returns to the calling subroutine with the error indicator set to IFAIL=4.
- Note: the following are additional parameters for specific use with D03PDA. Users of D03PDF therefore need not read the remainder of this description.
- 9: IUSER(*) – INTEGER arrayUser Workspace
- 10: RUSER(*) – double precision arrayUser Workspace
BNDARY is called from D03PDA with the parameters
IUSER and
RUSER as supplied to D03PDA. You are free to use the arrays
IUSER and
RUSER to supply information to
BNDARY.
BNDARY must be declared as EXTERNAL in the (sub)program from which D03PDF/D03PDA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 7: U(NPDE,NPTS) – double precision arrayInput/Output
-
On entry: if
IND=1 the value of
U must be unchanged from the previous call.
On exit: Uij will contain the computed solution at t=TS.
- 8: NBKPTS – INTEGERInput
-
On entry:
the number of break points in the interval a,b.
Constraint:
NBKPTS≥2.
- 9: XBKPTS(NBKPTS) – double precision arrayInput
-
On entry: the values of the break points in the space direction. XBKPTS1 must specify the left-hand boundary, a, and XBKPTSNBKPTS must specify the right-hand boundary, b.
Constraint:
XBKPTS1<XBKPTS2<⋯<XBKPTSNBKPTS.
- 10: NPOLY – INTEGERInput
-
On entry: the degree of the Chebyshev polynomial to be used in approximating the PDE solution between each pair of break points.
Constraint:
1≤NPOLY≤49.
- 11: NPTS – INTEGERInput
-
On entry:
the number of mesh points in the interval a,b.
Constraint:
NPTS=NBKPTS-1×NPOLY+1.
- 12: X(NPTS) – double precision arrayOutput
On exit: the mesh points chosen by D03PDF/D03PDA in the spatial direction. The values of
X will satisfy
X1<X2<⋯<XNPTS.
- 13: UINIT – SUBROUTINE, supplied by the user.External Procedure
UINIT must compute the initial values of the PDE components
Uixj,t0, for
i=1,2,…,NPDE and
j=1,2,…,NPTS.
The specification of
UINIT
for D03PDF is:
| SUBROUTINE UINIT ( | NPDE, NPTS, X, U) |
| INTEGER | NPDE, NPTS |
| double precision | X(NPTS), U(NPDE,NPTS) |
The specification of
UINIT
for D03PDA is:
| SUBROUTINE UINIT ( | NPDE, NPTS, X, U, IUSER, RUSER) |
| INTEGER | NPDE, NPTS, IUSER(*) |
| double precision | X(NPTS), U(NPDE,NPTS), RUSER(*) |
- 1: NPDE – INTEGERInput
-
On entry: the number of PDEs in the system.
- 2: NPTS – INTEGERInput
-
On entry:
the number of mesh points in the interval a,b.
- 3: X(NPTS) – double precision arrayInput
On entry: Xj, contains the values of the jth mesh point, for j=1,2,…,NPTS.
- 4: U(NPDE,NPTS) – double precision arrayOutput
-
On exit: Uij must be set to the initial value Uixj,t0, for i=1,2,…,NPDE and j=1,2,…,NPTS.
- Note: the following are additional parameters for specific use with D03PDA. Users of D03PDF therefore need not read the remainder of this description.
- 5: IUSER(*) – INTEGER arrayUser Workspace
- 6: RUSER(*) – double precision arrayUser Workspace
UINIT is called from D03PDA with the parameters
IUSER and
RUSER as supplied to D03PDA. You are free to use the arrays
IUSER and
RUSER to supply information to
UINIT.
UINIT must be declared as EXTERNAL in the (sub)program from which D03PDF/D03PDA is called. Parameters denoted as
Input must
not be changed by this procedure.
- 14: ACC – double precisionInput
-
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:
Constraint:
ACC>0.0.
- 15: RSAVE(LRSAVE) – double precision 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.
- 16: LRSAVE – INTEGERInput
On entry: the dimension of the array
RSAVE as declared in the (sub)program from which D03PDF/D03PDA is called.
Constraint:
LRSAVE≥11×NPDE×NPTS+50+nwkres+lenode.
- 17: ISAVE(LISAVE) – 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.
- 18: LISAVE – INTEGERInput
-
On entry: the dimension of the array
ISAVE as declared in the (sub)program from which D03PDF/D03PDA is called.
Constraint:
LISAVE≥NPDE×NPTS+24.
- 19: 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.
- 20: ITRACE – INTEGERInput
-
On entry: the level of trace information required from D03PDF/D03PDA 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, then -1 is assumed and similarly if ITRACE>3, then 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.
- 21: 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 parameters TOUT and IFAIL should be reset between calls to D03PDF/D03PDA.
Constraint:
IND=0 or 1.
On exit: IND=1.
- 22: IFAIL – INTEGERInput/Output
-
Note: for D03PDA, IFAIL does not occur in this position in the parameter list. See the additional parameters described below.
On entry:
IFAIL must be set to
0,
-1 or 1. If you are unfamiliar with this parameter you should refer to
Section 3.3 in the Essential Introduction for details.
On exit:
IFAIL=0 unless the routine detects an error (see
Section 6).
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 parameter, the recommended value is
0.
When the value -1 or 1 is used it is essential to test the value of IFAIL on exit. - Note: the following are additional parameters for specific use with D03PDA. Users of D03PDF therefore need not read the remainder of this description.
- 22: IUSER(*) – INTEGER arrayUser Workspace
Note: the dimension of the array
IUSER
must be at least
1.
IUSER is not used by D03PDA, but is passed directly to
PDEDEF,
BNDARY and
UINIT and may be used to pass information to these routines.
- 23: RUSER(*) – double precision arrayUser Workspace
Note: the dimension of the array
RUSER
must be at least
1.
RUSER is not used by D03PDA, but is passed directly to
PDEDEF,
BNDARY and
UINIT and may be used to pass information to these routines.
- 24: CWSAV(10) – CHARACTER*80 arrayCommunication Array
- 25: LWSAV(100) – LOGICAL arrayCommunication Array
- 26: IWSAV(505) – INTEGER arrayCommunication Array
- 27: RWSAV(1100) – double precision arrayCommunication Array
- 28: IFAIL – INTEGERInput/Output
Note: see the parameter 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, | TOUT≤TS, |
| or | TOUT-TS is too small, |
| or | ITASK≠1, 2 or 3, |
| or | M≠0, 1 or 2, |
| or | M>0 and XBKPTS1<0.0, |
| or | NPDE<1, |
| or | NBKPTS<2, |
| or | NPOLY<1 or NPOLY>49, |
| or | NPTS≠NBKPTS-1×NPOLY+1, |
| or | ACC≤0.0, |
| or | IND≠0 or 1, |
| or | break points XBKPTSi are not ordered, |
| or | LRSAVE is too small, |
| or | LISAVE is too small. |
- 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. 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 at least
PDEDEF or
BNDARY, when the residual in the underlying ODE solver was being evaluated.
- IFAIL=5
-
In solving the ODE system, a singular Jacobian has been encountered. You should check your problem formulation.
- IFAIL=6
-
When evaluating the residual in solving the ODE system,
IRES was set to
2 in at least
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 one of
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 parameters 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
ITASK≠2.)
- IFAIL=11
-
An error occurred during Jacobian formulation of the ODE system (a more detailed error description may be directed to the current error message unit).
- IFAIL=12
-
Not applicable.
- IFAIL=13
-
Not applicable.
- IFAIL=14
-
The flux function Ri was detected as depending on time derivatives, which is not permissible.
7 Accuracy
D03PDF/D03PDA controls the accuracy of the integration in the time direction but not the accuracy of the approximation in space. The spatial accuracy depends on the degree of the polynomial approximation
NPOLY, and on both the number of break 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 parameter,
ACC.
8 Further Comments
D03PDF/D03PDA is designed to solve parabolic systems (possibly including elliptic equations) with second-order derivatives in space. The parameter specification allows you to include equations with only first-order derivatives in the space direction but there is no guarantee that the method of integration will be satisfactory for such systems. The position and nature of the boundary conditions in particular are critical in defining a stable problem.
The time taken depends on the complexity of the parabolic system and on the accuracy requested.
9 Example
The problem consists of a fourth-order PDE which can be written as a pair of second-order elliptic-parabolic PDEs for
U1x,t and
U2x,t,
where
-1≤x≤1 and
t≥0. The boundary conditions are given by
The initial conditions at
t=0 are given by
The absence of boundary conditions for
U2x,t does not pose any difficulties provided that the derivative flux boundary conditions are assigned to the first PDE
(4) which has the correct flux,
∂U1
∂x
. The conditions on
U1x,t at the boundaries are assigned to the second PDE by setting
β2=0.0 in equation
(3) and placing the Dirichlet boundary conditions on
U1x,t in the function
γ2.
9.1 Program Text
Note: the following programs illustrate the use of D03PDF and D03PDA.
Program Text (d03pdfe.f)
Program Text (d03pdae.f)
9.2 Program Data
None.
9.3 Program Results
Program Results (d03pdfe.r)
Program Results (d03pdae.r)
