hide long namesshow long names
hide short namesshow short names
Integer type:  int32  int64  nag_int  show int32  show int32  show int64  show int64  show nag_int  show nag_int

PDF version (NAG web site, 64-bit version, 64-bit version)
Chapter Contents
Chapter Introduction
NAG Toolbox

NAG Toolbox: nag_pde_1d_parab_remesh_fd (d03pp)

 Contents

    1  Purpose
    2  Syntax
    7  Accuracy
    9  Example

Purpose

nag_pde_1d_parab_remesh_fd (d03pp) integrates a system of linear or nonlinear parabolic partial differential equations (PDEs) in one space variable, with scope for coupled ordinary differential equations (ODEs), and automatic adaptive spatial remeshing. The spatial discretization is performed using finite differences, and the method of lines is employed to reduce the PDEs to a system of ODEs. The resulting system is solved using a Backward Differentiation Formula (BDF) method or a Theta method (switching between Newton's method and functional iteration).

Syntax

[ts, u, x, rsave, isave, ind, user, cwsav, lwsav, iwsav, rwsav, ifail] = d03pp(npde, m, ts, tout, pdedef, bndary, uvinit, u, x, ncode, odedef, xi, rtol, atol, itol, norm_p, laopt, algopt, remesh, xfix, nrmesh, dxmesh, trmesh, ipminf, monitf, rsave, isave, itask, itrace, ind, cwsav, lwsav, iwsav, rwsav, 'npts', npts, 'nxi', nxi, 'neqn', neqn, 'nxfix', nxfix, 'xratio', xratio, 'con', con, 'user', user)
[ts, u, x, rsave, isave, ind, user, cwsav, lwsav, iwsav, rwsav, ifail] = nag_pde_1d_parab_remesh_fd(npde, m, ts, tout, pdedef, bndary, uvinit, u, x, ncode, odedef, xi, rtol, atol, itol, norm_p, laopt, algopt, remesh, xfix, nrmesh, dxmesh, trmesh, ipminf, monitf, rsave, isave, itask, itrace, ind, cwsav, lwsav, iwsav, rwsav, 'npts', npts, 'nxi', nxi, 'neqn', neqn, 'nxfix', nxfix, 'xratio', xratio, 'con', con, 'user', user)
Note: the interface to this routine has changed since earlier releases of the toolbox:
At Mark 22: lrsave and lisave were removed from the interface

Description

nag_pde_1d_parab_remesh_fd (d03pp) integrates the system of parabolic-elliptic equations and coupled ODEs
j=1npdePi,j Uj t +Qi=x-m x xmRi,  i=1,2,,npde ,   axb,tt0, (1)
Fit,V,V.,ξ,U*,Ux*,R*,Ut*,Uxt*=0,  i=1,2,,ncode, (2)
where (1) defines the PDE part and (2) generalizes the coupled ODE part of the problem.
In (1), Pi,j and Ri depend on x, t, U, Ux, and V; Qi depends on x, t, U, Ux, V and linearly on V.. The vector U is the set of PDE solution values
Ux,t=U1x,t,,Unpdex,tT,  
and the vector Ux is the partial derivative with respect to x. The vector V is the set of ODE solution values
Vt=V1t,,VncodetT,  
and V. denotes its derivative with respect to time.
In (2), ξ represents a vector of nξ spatial coupling points at which the ODEs are coupled to the PDEs. These points may or may not be equal to some of the PDE spatial mesh points. U*, Ux*, R*, Ut* and Uxt* are the functions U, Ux, R, Ut and Uxt evaluated at these coupling points. Each Fi may only depend linearly on time derivatives. Hence the equation (2) may be written more precisely as
F=G-AV.-B Ut* Uxt* , (3)
where F=F1,,FncodeT, G is a vector of length ncode, A is an ncode by ncode matrix, B is an ncode by nξ×npde matrix and the entries in G, A and B may depend on t, ξ, U*, Ux* and V. In practice you only need to supply a vector of information to define the ODEs and not the matrices A and B. (See Arguments for the specification of odedef.)
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 mesh x1,x2,,xnpts defined initially by you and (possibly) adapted automatically during the integration according to user-specified criteria. The coordinate system in space is defined by the following values of m; m=0 for Cartesian coordinates, m=1 for cylindrical polar coordinates and m=2 for spherical polar coordinates.
The PDE system which is defined by the functions Pi,j, Qi and Ri must be specified in pdedef.
The initial t=t0 values of the functions Ux,t and Vt must be specified in uvinit. Note that uvinit will be called again following any initial remeshing, and so Ux,t0 should be specified for all values of x in the interval axb, and not just the initial mesh points.
The functions Ri which may be thought of as fluxes, are also used in the definition of the boundary conditions. The boundary conditions must have the form
βix,tRix,t,U,Ux,V=γix,t,U,Ux,V,V.,  i=1,2,,npde, (4)
where x=a or x=b.
The boundary conditions must be specified in bndary. The function γi may depend linearly on V..
The problem is subject to the following restrictions:
(i) In (1), V.jt, for j=1,2,,ncode, may only appear linearly in the functions Qi, for i=1,2,,npde, with a similar restriction for γ;
(ii) Pi,j and the flux Ri must not depend on any time derivatives;
(iii) t0<tout, so that integration is in the forward direction;
(iv) The evaluation of the terms Pi,j, Qi and Ri is done approximately at the mid-points of the mesh xi, for i=1,2,,npts, by calling the pdedef for each mid-point in turn. Any discontinuities in these functions must therefore be at one or more of the fixed mesh points specified by xfix;
(v) At least one of the functions Pi,j must be nonzero so that there is a time derivative present in the PDE problem;
(vi) 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 Further Comments.
The algebraic-differential equation system which is defined by the functions Fi must be specified in odedef. You must also specify the coupling points ξ in the array xi.
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+ncode ODEs in time direction. This system is then integrated forwards in time using a Backward Differentiation Formula (BDF) or a Theta method.
The adaptive space remeshing can be used to generate meshes that automatically follow the changing time-dependent nature of the solution, generally resulting in a more efficient and accurate solution using fewer mesh points than may be necessary with a fixed uniform or non-uniform mesh. Problems with travelling wavefronts or variable-width boundary layers for example will benefit from using a moving adaptive mesh. The discrete time-step method used here (developed by Furzeland (1984)) automatically creates a new mesh based on the current solution profile at certain time-steps, and the solution is then interpolated onto the new mesh and the integration continues.
The method requires you to supply a monitf which specifies in an analytical or numerical form the particular aspect of the solution behaviour you wish to track. This so-called monitor function is used to choose a mesh which equally distributes the integral of the monitor function over the domain. A typical choice of monitor function is the second space derivative of the solution value at each point (or some combination of the second space derivatives if there is more than one solution component), which results in refinement in regions where the solution gradient is changing most rapidly.
You must specify the frequency of mesh updates together with certain other criteria such as adjacent mesh ratios. Remeshing can be expensive and you are encouraged to experiment with the different options in order to achieve an efficient solution which adequately tracks the desired features of the solution.
Note that unless the monitor function for the initial solution values is zero at all user-specified initial mesh points, a new initial mesh is calculated and adopted according to the user-specified remeshing criteria. uvinit will then be called again to determine the initial solution values at the new mesh points (there is no interpolation at this stage) and the integration proceeds.

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
Berzins M and Furzeland R M (1992) An adaptive theta method for the solution of stiff and nonstiff differential equations Appl. Numer. Math. 9 1–19
Furzeland R M (1984) The construction of adaptive space meshes TNER.85.022 Thornton Research Centre, Chester
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

Parameters

Compulsory Input Parameters

1:     npde int64int32nag_int scalar
The number of PDEs to be solved.
Constraint: npde1.
2:     m int64int32nag_int scalar
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 – double scalar
The initial value of the independent variable t.
Constraint: ts<tout.
4:     tout – double scalar
The final value of t to which the integration is to be carried out.
5:     pdedef – function handle or string containing name of m-file
pdedef must evaluate the functions Pi,j, Qi and Ri which define the system of PDEs. The functions may depend on x, t, U, Ux and V. Qi may depend linearly on V.. pdedef is called approximately midway between each pair of mesh points in turn by nag_pde_1d_parab_remesh_fd (d03pp).
[p, q, r, ires, user] = pdedef(npde, t, x, u, ux, ncode, v, vdot, ires, user)

Input Parameters

1:     npde int64int32nag_int scalar
The number of PDEs in the system.
2:     t – double scalar
The current value of the independent variable t.
3:     x – double scalar
The current value of the space variable x.
4:     unpde – double array
ui contains the value of the component Uix,t, for i=1,2,,npde.
5:     uxnpde – double array
uxi contains the value of the component Uix,t x , for i=1,2,,npde.
6:     ncode int64int32nag_int scalar
The number of coupled ODEs in the system.
7:     vncode – double array
If ncode>0, vi contains the value of the component Vit, for i=1,2,,ncode.
8:     vdotncode – double array
If ncode>0, vdoti contains the value of component V.it, for i=1,2,,ncode.
Note:  V.it, for i=1,2,,ncode, may only appear linearly in Qj, for j=1,2,,npde.
9:     ires int64int32nag_int scalar
Set to -1​ or ​1.
10:   user – Any MATLAB object
pdedef is called from nag_pde_1d_parab_remesh_fd (d03pp) with the object supplied to nag_pde_1d_parab_remesh_fd (d03pp).

Output Parameters

1:     pnpdenpde – double array
pij must be set to the value of Pi,jx,t,U,Ux,V, for i=1,2,,npde and j=1,2,,npde.
2:     qnpde – double array
qi must be set to the value of Qix,t,U,Ux,V,V., for i=1,2,,npde.
3:     rnpde – double array
ri must be set to the value of Rix,t,U,Ux,V, for i=1,2,,npde.
4:     ires int64int32nag_int scalar
Should usually remain unchanged. However, you may set ires to force the integration function 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, then nag_pde_1d_parab_remesh_fd (d03pp) returns to the calling function with the error indicator set to ifail=4.
5:     user – Any MATLAB object
6:     bndary – function handle or string containing name of m-file
bndary must evaluate the functions βi and γi which describe the boundary conditions, as given in (4).
[beta, gamma, ires, user] = bndary(npde, t, u, ux, ncode, v, vdot, ibnd, ires, user)

Input Parameters

1:     npde int64int32nag_int scalar
The number of PDEs in the system.
2:     t – double scalar
The current value of the independent variable t.
3:     unpde – double array
ui contains the value of the component Uix,t at the boundary specified by ibnd, for i=1,2,,npde.
4:     uxnpde – double array
uxi contains the value of the component Uix,t x  at the boundary specified by ibnd, for i=1,2,,npde.
5:     ncode int64int32nag_int scalar
The number of coupled ODEs in the system.
6:     vncode – double array
If ncode>0, vi contains the value of the component Vit, for i=1,2,,ncode.
7:     vdotncode – double array
vdoti contains the value of component V.it, for i=1,2,,ncode.
Note: V.it, for i=1,2,,ncode, may only appear linearly in γj, for j=1,2,,npde.
8:     ibnd int64int32nag_int scalar
Specifies which boundary conditions are to be evaluated.
ibnd=0
bndary must set up the coefficients of the left-hand boundary, x=a.
ibnd0
bndary must set up the coefficients of the right-hand boundary, x=b.
9:     ires int64int32nag_int scalar
Set to -1​ or ​1.
10:   user – Any MATLAB object
bndary is called from nag_pde_1d_parab_remesh_fd (d03pp) with the object supplied to nag_pde_1d_parab_remesh_fd (d03pp).

Output Parameters

1:     betanpde – double array
betai must be set to the value of βix,t at the boundary specified by ibnd, for i=1,2,,npde.
2:     gammanpde – double array
gammai must be set to the value of γix,t,U,Ux,V,V. at the boundary specified by ibnd, for i=1,2,,npde.
3:     ires int64int32nag_int scalar
Should usually remain unchanged. However, you may set ires to force the integration function 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, then nag_pde_1d_parab_remesh_fd (d03pp) returns to the calling function with the error indicator set to ifail=4.
4:     user – Any MATLAB object
7:     uvinit – function handle or string containing name of m-file
uvinit must supply the initial t=t0 values of Ux,t and Vt for all values of x in the interval axb.
[u, v, user] = uvinit(npde, npts, nxi, x, xi, ncode, user)

Input Parameters

1:     npde int64int32nag_int scalar
The number of PDEs in the system.
2:     npts int64int32nag_int scalar
The number of mesh points in the interval a,b.
3:     nxi int64int32nag_int scalar
The number of ODE/PDE coupling points.
4:     xnpts – double array
The current mesh. xi contains the value of xi, for i=1,2,,npts.
5:     xinxi – double array
If nxi>0, xii contains the value of the ODE/PDE coupling point, ξi, for i=1,2,,nxi.
6:     ncode int64int32nag_int scalar
The number of coupled ODEs in the system.
7:     user – Any MATLAB object
uvinit is called from nag_pde_1d_parab_remesh_fd (d03pp) with the object supplied to nag_pde_1d_parab_remesh_fd (d03pp).

Output Parameters

1:     unpdenpts – double array
If nxi>0, uij contains the value of the component Uixj,t0, for i=1,2,,npde and j=1,2,,npts.
2:     vncode – double array
vi contains the value of component Vit0, for i=1,2,,ncode.
3:     user – Any MATLAB object
8:     uneqn – double array
If ind=1, the value of u must be unchanged from the previous call.
9:     xnpts – double array
The initial mesh points in the space direction. x1 must specify the left-hand boundary, a, and xnpts must specify the right-hand boundary, b.
Constraint: x1<x2<<xnpts.
10:   ncode int64int32nag_int scalar
The number of coupled ODE in the system.
Constraint: ncode0.
11:   odedef – function handle or string containing name of m-file
odedef must evaluate the functions F, which define the system of ODEs, as given in (3).
If you wish to compute the solution of a system of PDEs only (ncode=0), odedef must be the string nag_pde_1d_parab_remesh_fd_dummy_odedef (d53pck).
[f, ires, user] = odedef(npde, t, ncode, v, vdot, nxi, xi, ucp, ucpx, rcp, ucpt, ucptx, ires, user)

Input Parameters

1:     npde int64int32nag_int scalar
The number of PDEs in the system.
2:     t – double scalar
The current value of the independent variable t.
3:     ncode int64int32nag_int scalar
The number of coupled ODEs in the system.
4:     vncode – double array
If ncode>0, vi contains the value of the component Vit, for i=1,2,,ncode.
5:     vdotncode – double array
If ncode>0, vdoti contains the value of component V.it, for i=1,2,,ncode.
6:     nxi int64int32nag_int scalar
The number of ODE/PDE coupling points.
7:     xinxi – double array
If nxi>0, xii contains the ODE/PDE coupling points, ξi, for i=1,2,,nxi.
8:     ucpnpde: – double array
The second dimension of the array ucp must be at least max1,nxi.
If nxi>0, ucpij contains the value of Uix,t at the coupling point x=ξj, for i=1,2,,npde and j=1,2,,nxi.
9:     ucpxnpde: – double array
The second dimension of the array ucpx must be at least max1,nxi.
If nxi>0, ucpxij contains the value of Uix,t x  at the coupling point x=ξj, for i=1,2,,npde and j=1,2,,nxi.
10:   rcpnpde: – double array
The second dimension of the array rcp must be at least max1,nxi.
rcpij contains the value of the flux Ri at the coupling point x=ξj, for i=1,2,,npde and j=1,2,,nxi.
11:   ucptnpde: – double array
The second dimension of the array ucpt must be at least max1,nxi.
If nxi>0, ucptij contains the value of Ui t  at the coupling point x=ξj, for i=1,2,,npde and j=1,2,,nxi.
12:   ucptxnpde: – double array
The second dimension of the array ucptx must be at least max1,nxi.
ucptxij contains the value of 2Ui x t  at the coupling point x=ξj, for i=1,2,,npde and j=1,2,,nxi.
13:   ires int64int32nag_int scalar
The form of F that must be returned in the array f.
ires=1
Equation (5) must be used.
ires=-1
Equation (6) must be used.
14:   user – Any MATLAB object
odedef is called from nag_pde_1d_parab_remesh_fd (d03pp) with the object supplied to nag_pde_1d_parab_remesh_fd (d03pp).

Output Parameters

1:     fncode – double array
fi must contain the ith component of F, for i=1,2,,ncode, where F is defined as
F=G-AV.-B Ut* Uxt* , (5)
or
F=-AV.-B Ut* Uxt* . (6)
The definition of F is determined by the input value of ires.
2:     ires int64int32nag_int scalar
Should usually remain unchanged. However, you may reset ires to force the integration function 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, then nag_pde_1d_parab_remesh_fd (d03pp) returns to the calling function with the error indicator set to ifail=4.
3:     user – Any MATLAB object
12:   xinxi – double array
If nxi>0, xii, for i=1,2,,nxi, must be set to the ODE/PDE coupling points.
Constraint: x1xi1<xi2<<xinxixnpts.
13:   rtol: – double array
The dimension of the array rtol must be at least 1 if itol=1 or 2 and at least neqn if itol=3 or 4
The relative local error tolerance.
Constraint: rtoli0.0 for all relevant i.
14:   atol: – double array
The dimension of the array atol must be at least 1 if itol=1 or 3 and at least neqn if itol=2 or 4
The absolute local error tolerance.
Constraints:
  • atoli0.0 for all relevant i;
  • Corresponding elements of atol and rtol cannot both be 0.0.
15:   itol int64int32nag_int scalar
A value to indicate the form of the local error test. itol indicates to nag_pde_1d_parab_remesh_fd (d03pp) whether to interpret either or both of rtol or atol as a vector or scalar. The error test to be satisfied is ei/wi<1.0, where wi is defined as follows:
itolrtolatolwi
1scalarscalarrtol1×Ui+atol1
2scalarvectorrtol1×Ui+atoli
3vectorscalarrtoli×Ui+atol1
4vectorvectorrtoli×Ui+atoli
In the above, ei denotes the estimated local error for the ith component of the coupled PDE/ODE system in time, ui, for i=1,2,,neqn.
The choice of norm used is defined by the argument norm_p.
Constraint: 1itol4.
16:   norm_p – string (length ≥ 1)
The type of norm to be used.
norm_p='M'
Maximum norm.
norm_p='A'
Averaged L2 norm.
If unorm denotes the norm of the vector u of length neqn, then for the averaged L2 norm
unorm=1neqni=1neqnui/wi2,  
while for the maximum norm
u norm = maxi ui / wi .  
See the description of itol for the formulation of the weight vector w.
Constraint: norm_p='M' or 'A'.
17:   laopt – string (length ≥ 1)
The type of matrix algebra required.
laopt='F'
Full matrix methods to be used.
laopt='B'
Banded matrix methods to be used.
laopt='S'
Sparse matrix methods to be used.
Constraint: laopt='F', 'B' or 'S'.
Note: you are recommended to use the banded option when no coupled ODEs are present (i.e., ncode=0).
18:   algopt30 – double array
May be set to control various options available in the integrator. If you wish to employ all the default options, then algopt1 should be set to 0.0. Default values will also be used for any other elements of algopt set to zero. The permissible values, default values, and meanings are as follows:
algopt1
Selects the ODE integration method to be used. If algopt1=1.0, a BDF method is used and if algopt1=2.0, a Theta method is used. The default value is algopt1=1.0.
If algopt1=2.0, then algopti, for i=2,3,4 are not used.
algopt2
Specifies the maximum order of the BDF integration formula to be used. algopt2 may be 1.0, 2.0, 3.0, 4.0 or 5.0. The default value is algopt2=5.0.
algopt3
Specifies what method is to be used to solve the system of nonlinear equations arising on each step of the BDF method. If algopt3=1.0 a modified Newton iteration is used and if algopt3=2.0 a functional iteration method is used. If functional iteration is selected and the integrator encounters difficulty, then there is an automatic switch to the modified Newton iteration. The default value is algopt3=1.0.
algopt4
Specifies whether or not the Petzold error test is to be employed. The Petzold error test results in extra overhead but is more suitable when algebraic equations are present, such as Pi,j=0.0, for j=1,2,,npde, for some i or when there is no V.it dependence in the coupled ODE system. If algopt4=1.0, then the Petzold test is used. If algopt4=2.0, then the Petzold test is not used. The default value is algopt4=1.0.
If algopt1=1.0, then algopti, for i=5,6,7, are not used.
algopt5
Specifies the value of Theta to be used in the Theta integration method. 0.51algopt50.99. The default value is algopt5=0.55.
algopt6
Specifies what method is to be used to solve the system of nonlinear equations arising on each step of the Theta method. If algopt6=1.0, a modified Newton iteration is used and if algopt6=2.0, a functional iteration method is used. The default value is algopt6=1.0.
algopt7
Specifies whether or not the integrator is allowed to switch automatically between modified Newton and functional iteration methods in order to be more efficient. If algopt7=1.0, then switching is allowed and if algopt7=2.0, then switching is not allowed. The default value is algopt7=1.0.
algopt11
Specifies a point in the time direction, tcrit, beyond which integration must not be attempted. The use of tcrit is described under the argument itask. If algopt10.0, a value of 0.0 for algopt11, say, should be specified even if itask subsequently specifies that tcrit will not be used.
algopt12
Specifies the minimum absolute step size to be allowed in the time integration. If this option is not required, algopt12 should be set to 0.0.
algopt13
Specifies the maximum absolute step size to be allowed in the time integration. If this option is not required, algopt13 should be set to 0.0.
algopt14
Specifies the initial step size to be attempted by the integrator. If algopt14=0.0, then the initial step size is calculated internally.
algopt15
Specifies the maximum number of steps to be attempted by the integrator in any one call. If algopt15=0.0, then no limit is imposed.
algopt23
Specifies what method is to be used to solve the nonlinear equations at the initial point to initialize the values of U, Ut, V and V.. If algopt23=1.0, a modified Newton iteration is used and if algopt23=2.0, functional iteration is used. The default value is algopt23=1.0.
algopt29 and algopt30 are used only for the sparse matrix algebra option, laopt='S'.
algopt29
Governs the choice of pivots during the decomposition of the first Jacobian matrix. It should lie in the range 0.0<algopt29<1.0, with smaller values biasing the algorithm towards maintaining sparsity at the expense of numerical stability. If algopt29 lies outside this range then the default value is used. If the functions regard the Jacobian matrix as numerically singular then increasing algopt29 towards 1.0 may help, but at the cost of increased fill-in. The default value is algopt29=0.1.
algopt30
Is used as a relative pivot threshold during subsequent Jacobian decompositions (see algopt29) below which an internal error is invoked. If algopt30 is greater than 1.0 no check is made on the pivot size, and this may be a necessary option if the Jacobian is found to be numerically singular (see algopt29). The default value is algopt30=0.0001.
19:   remesh – logical scalar
Indicates whether or not spatial remeshing should be performed.
remesh=true
Indicates that spatial remeshing should be performed as specified.
remesh=false
Indicates that spatial remeshing should be suppressed.
Note:  remesh should not be changed between consecutive calls to nag_pde_1d_parab_remesh_fd (d03pp). Remeshing can be switched off or on at specified times by using appropriate values for the arguments nrmesh and trmesh at each call.
20:   xfix: – double array
The dimension of the array xfix must be at least max1,nxfix
xfixi, for i=1,2,,nxfix, must contain the value of the x coordinate at the ith fixed mesh point.
Constraints:
  • xfixi<xfixi+1, for i=1,2,,nxfix-1;
  • each fixed mesh point must coincide with a user-supplied initial mesh point, that is xfixi=xj for some j, 2jnpts-1.
Note: the positions of the fixed mesh points in the array x remain fixed during remeshing, and so the number of mesh points between adjacent fixed points (or between fixed points and end points) does not change. You should take this into account when choosing the initial mesh distribution.
21:   nrmesh int64int32nag_int scalar
Specifies the spatial remeshing frequency and criteria for the calculation and adoption of a new mesh.
nrmesh<0
Indicates that a new mesh is adopted according to the argument dxmesh. The mesh is tested every nrmesh timesteps.
nrmesh=0
Indicates that remeshing should take place just once at the end of the first time step reached when t>trmesh.
nrmesh>0
Indicates that remeshing will take place every nrmesh time steps, with no testing using dxmesh.
Note: nrmesh may be changed between consecutive calls to nag_pde_1d_parab_remesh_fd (d03pp) to give greater flexibility over the times of remeshing.
22:   dxmesh – double scalar
Determines whether a new mesh is adopted when nrmesh is set less than zero. A possible new mesh is calculated at the end of every nrmesh time steps, but is adopted only if
xinew>xi old +dxmesh×xi+1 old -xi old  
or
xinew<xi old -dxmesh×xi old -xi- 1 old  
dxmesh thus imposes a lower limit on the difference between one mesh and the next.
Constraint: dxmesh0.0.
23:   trmesh – double scalar
Specifies when remeshing will take place when nrmesh is set to zero. Remeshing will occur just once at the end of the first time step reached when t is greater than trmesh.
Note: trmesh may be changed between consecutive calls to nag_pde_1d_parab_remesh_fd (d03pp) to force remeshing at several specified times.
24:   ipminf int64int32nag_int scalar
The level of trace information regarding the adaptive remeshing. Details are directed to the current advisory message unit (see nag_file_set_unit_advisory (x04ab)).
ipminf=0
No trace information.
ipminf=1
Brief summary of mesh characteristics.
ipminf=2
More detailed information, including old and new mesh points, mesh sizes and monitor function values.
Constraint: ipminf=0, 1 or 2.
25:   monitf – function handle or string containing name of m-file
monitf must supply and evaluate a remesh monitor function to indicate the solution behaviour of interest.
If you specify remesh=false, i.e., no remeshing, then monitf will not be called and the string nag_pde_1d_parab_remesh_fd_dummy_monitf (d53pcl) may be used for monitf.
[fmon, user] = monitf(t, npts, npde, x, u, r, user)

Input Parameters

1:     t – double scalar
The current value of the independent variable t.
2:     npts int64int32nag_int scalar
The number of mesh points in the interval a,b.
3:     npde int64int32nag_int scalar
The number of PDEs in the system.
4:     xnpts – double array
The current mesh. xi contains the value of xi, for i=1,2,,npts.
5:     unpdenpts – double array
uij contains the value of Uix,t at x=xj and time t, for i=1,2,,npde and j=1,2,,npts.
6:     rnpdenpts – double array
rij contains the value of Rix,t,U,Ux,V at x=xj and time t, for i=1,2,,npde and j=1,2,,npts.
7:     user – Any MATLAB object
monitf is called from nag_pde_1d_parab_remesh_fd (d03pp) with the object supplied to nag_pde_1d_parab_remesh_fd (d03pp).

Output Parameters

1:     fmonnpts – double array
fmoni must contain the value of the monitor function Fmonx at mesh point x=xi.
2:     user – Any MATLAB object
26:   rsavelrsave – double array
If ind=0, rsave need not be set on entry.
If ind=1, rsave must be unchanged from the previous call to the function because it contains required information about the iteration.
27:   isavelisave int64int32nag_int array
If ind=0, isave need not be set on entry.
If ind=1, isave must be unchanged from the previous call to the function because it contains required information about the iteration required for subsequent calls. 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 ODE method last used in the time integration.
isave5
Contains the number of Newton iterations performed by the time integrator. Each iteration involves residual evaluation of the resulting ODE system followed by a back-substitution using the LU decomposition of the Jacobian matrix.
The rest of the array is used as workspace.
28:   itask int64int32nag_int scalar
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.
itask=4
Normal computation of output values u at t=tout but without overshooting t=tcrit where tcrit is described under the argument algopt.
itask=5
Take one step in the time direction and return, without passing tcrit, where tcrit is described under the argument algopt.
Constraint: itask=1, 2, 3, 4 or 5.
29:   itrace int64int32nag_int scalar
The level of trace information required from nag_pde_1d_parab_remesh_fd (d03pp) and the underlying ODE solver:
itrace-1
No output is generated.
itrace=0
Only warning messages from the PDE solver are printed on the current error message unit (see nag_file_set_unit_error (x04aa)).
itrace=1
Output from the underlying ODE solver is printed on the current advisory message unit (see nag_file_set_unit_advisory (x04ab)). This output contains details of Jacobian entries, the nonlinear iteration and the time integration during the computation of the ODE system.
itrace=2
Output from the underlying ODE solver is similar to that produced when itrace=1, except that the advisory messages are given in greater detail.
itrace3
Output from the underlying ODE solver is similar to that produced when itrace=2, except that the advisory messages are given in greater detail.
You are advised to set itrace=0, unless you are experienced with Sub-chapter D02M–N.
30:   ind int64int32nag_int scalar
Must be set to 0 or 1.
ind=0
Starts or restarts the integration in time.
ind=1
Continues the integration after an earlier exit from the function. In this case, only the arguments tout and ifail and the remeshing arguments nrmesh, dxmesh, trmesh, xratio and con may be reset between calls to nag_pde_1d_parab_remesh_fd (d03pp).
Constraint: 0ind1.
31:   cwsav10 – cell array of strings
32:   lwsav100 – logical array
33:   iwsav505 int64int32nag_int array
34:   rwsav1100 – double array

Optional Input Parameters

1:     npts int64int32nag_int scalar
Default: the dimension of the array x.
The number of mesh points in the interval a,b.
Constraint: npts3.
2:     nxi int64int32nag_int scalar
Default: the dimension of the array xi.
The number of ODE/PDE coupling points.
Constraints:
  • if ncode=0, nxi=0;
  • if ncode>0, nxi0.
3:     neqn int64int32nag_int scalar
Default: the dimension of the array u.
The number of ODEs in the time direction.
Constraint: neqn=npde×npts+ncode.
4:     nxfix int64int32nag_int scalar
Default: the dimension of the array xfix.
The number of fixed mesh points.
Constraint: 0nxfixnpts-2.
Note: the end points x1 and xnpts are fixed automatically and hence should not be specified as fixed points.
5:     xratio – double scalar
Default: 1.5
An input bound on the adjacent mesh ratio (greater than 1.0 and typically in the range 1.5 to 3.0). The remeshing functions will attempt to ensure that
xi-xi-1/xratio<xi+1-xi<xratio×xi-xi-1. 
Constraint: xratio>1.0.
6:     con – double scalar
Default: 2.0/npts-1
An input bound on the sub-integral of the monitor function Fmonx over each space step. The remeshing functions will attempt to ensure that
xixi+1Fmonxdxconx1xnptsFmonxdx,  
(see Furzeland (1984)). con gives you more control over the mesh distribution e.g., decreasing con allows more clustering. A typical value is 2/npts-1, but you are encouraged to experiment with different values. Its value is not critical and the mesh should be qualitatively correct for all values in the range given below.
Constraint: 0.1/npts-1con10.0/npts-1.
7:     user – Any MATLAB object
user is not used by nag_pde_1d_parab_remesh_fd (d03pp), but is passed to pdedef, bndary, uvinit, odedef and monitf. Note that for large objects it may be more efficient to use a global variable which is accessible from the m-files than to use user.

Output Parameters

1:     ts – double scalar
The value of t corresponding to the solution values in u. Normally ts=tout.
2:     uneqn – double array
unpde×j-1+i contains the computed solution Uixj,t, for i=1,2,,npde and j=1,2,,npts, and unpts×npde+k contains Vkt, for k=1,2,,ncode, evaluated at t=ts.
3:     xnpts – double array
The final values of the mesh points.
4:     rsavelrsave – double array
If ind=1, rsave must be unchanged from the previous call to the function because it contains required information about the iteration.
5:     isavelisave int64int32nag_int array
If ind=1, isave must be unchanged from the previous call to the function because it contains required information about the iteration required for subsequent calls. 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 ODE method last used in the time integration.
isave5
Contains the number of Newton iterations performed by the time integrator. Each iteration involves residual evaluation of the resulting ODE system followed by a back-substitution using the LU decomposition of the Jacobian matrix.
The rest of the array is used as workspace.
6:     ind int64int32nag_int scalar
ind=1.
7:     user – Any MATLAB object
8:     cwsav10 – cell array of strings
9:     lwsav100 – logical array
10:   iwsav505 int64int32nag_int array
11:   rwsav1100 – double array
12:   ifail int64int32nag_int scalar
ifail=0 unless the function detects an error (see Error Indicators and Warnings).

Error Indicators and Warnings

Errors or warnings detected by the function:

Cases prefixed with W are classified as warnings and do not generate an error of type NAG:error_n. See nag_issue_warnings.

   ifail=1
On entry,tout-ts is too small,
oritask1, 2, 3, 4 or 5,
orm0, 1 or 2,
orat least one of the coupling points defined in array xi is outside the interval x1,xnpts,
orm>0 and x1<0.0,
ornpts<3,
ornpde<1,
ornorm_p'A' or 'M',
orlaopt'F', 'B' or 'S',
oritol1, 2, 3 or 4,
orind0 or 1,
ormesh points xi are badly ordered,
orlrsave is too small,
orlisave is too small,
orncode and nxi are incorrectly defined,
oran element of rtol or atol<0.0,
orcorresponding elements of rtol and atol are both 0.0,
orneqnnpde×npts+ncode,
ornxfix not in the range 0 to npts-2,
orfixed mesh point(s) do not coincide with any of the user-supplied mesh points,
ordxmesh<0.0,
oripminf0, 1 or 2,
orxratio1.0,
orcon not in the range 0.1/npts-1 to 10/npts-1.
W  ifail=2
The underlying ODE solver cannot make any further progress, with the values of atol and rtol, across the integration range from the current point t=ts. The components of u contain the computed values at the current point t=ts.
W  ifail=3
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 t=ts. The problem may have a singularity, or the error requirement may be inappropriate.
   ifail=4
In setting up the ODE system, the internal initialization function 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, bndary or odedef, 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.
W  ifail=6
When evaluating the residual in solving the ODE system, ires was set to 2 in at least pdedef, bndary or odedef. Integration was successful as far as t=ts.
   ifail=7
The values of atol and rtol are so small that the function is unable to start the integration in time.
   ifail=8
In one of pdedef, bndary or odedef, ires was set to an invalid value.
   ifail=9 (nag_ode_ivp_stiff_imp_revcom (d02nn))
A serious error has occurred in an internal call to the specified function. Check the problem specification and all arguments and array dimensions. Setting itrace=1 may provide more information. If the problem persists, contact NAG.
W  ifail=10
The required task has been completed, but it is estimated that a small change in atol and rtol is unlikely to produce any change in the computed solution. (Only applies when you are not operating in one step mode, that is when itask2 or 5.)
   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). If using the sparse matrix algebra option, the values of algopt29 and algopt30 may be inappropriate.
   ifail=12
In solving the ODE system, the maximum number of steps specified in algopt15 have been taken.
W  ifail=13
Some error weights wi became zero during the time integration (see the description of itol). Pure relative error control (atoli=0.0) was requested on a variable (the ith) which has become zero. The integration was successful as far as t=ts.
   ifail=14
The flux function Ri was detected as depending on time derivatives, which is not permissible.
   ifail=15
When using the sparse option, the value of lisave or lrsave was not sufficient (more detailed information may be directed to the current error message unit).
   ifail=16
remesh has been changed between calls to nag_pde_1d_parab_remesh_fd (d03pp), which is not permissible.
   ifail=17
The remeshing process has produced zero or negative mesh spacing. You are advised to check monitf and to try adjusting the values of dxmesh, xratio and con. Setting ipminf=1 may provide more information.
   ifail=-99
An unexpected error has been triggered by this routine. Please contact NAG.
   ifail=-399
Your licence key may have expired or may not have been installed correctly.
   ifail=-999
Dynamic memory allocation failed.

Accuracy

nag_pde_1d_parab_remesh_fd (d03pp) 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 arguments, atol and rtol.

Further Comments

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 function nag_pde_1d_parab_remesh_keller (d03pr).
The time taken depends on the complexity of the parabolic system, the accuracy requested, and the frequency of the mesh updates. For a given system with fixed accuracy and mesh-update frequency it is approximately proportional to neqn.

Example

This example uses Burgers Equation, a common test problem for remeshing algorithms, given by
U t =-U U x +E 2U x2 ,  
for x0,1 and t0,1, where E is a small constant.
The initial and boundary conditions are given by the exact solution
Ux,t=0.1exp-A+0.5exp-B+exp-C exp-A+exp-B+exp-C ,  
where
A = 50Ex- 0.5+ 4.95t, B = 250Ex- 0.5+ 0.75t, C = 500Ex- 0.375.  
function d03pp_example


fprintf('d03pp example results\n\n');

% Initialize input arguments
npde   = int64(1);
m      = int64(0);
ts     = 0;
tout   = 0.2;
npts   = 61;
u      = zeros(npts, 1);
dx     = 1/(npts-1);
x      = [0:dx:1];
ncode  = int64(0);
xi     = [];
rtol   = [5e-05];
atol   = [5e-05];
itol   = int64(1);
normt  = 'A';
laopt  = 'F';
algopt = zeros(30, 1);
remesh = true;
xfix   = [];
nrmesh = int64(3);
dxmesh = 0.5;
trmesh = 0;
ipminf = int64(0);
rsave  = zeros(5018, 1);
isave  = zeros(25, 1, 'int64');
itask  = int64(1);
itrace = int64(0);
ind    = int64(0);
cwsav  = {''; ''; ''; ''; ''; ''; ''; ''; ''; ''};
lwsav  = false(100, 1);
iwsav  = zeros(505, 1, 'int64');
rwsav =  zeros(1100, 1);

% Integrate from t=0 to t=1 in steps of 0.1
usol = zeros(11,npts);
xsol = zeros(11,npts);
tsol = zeros(11,npts);
tout = [0.01,0.02,0.04,0.06,0.08,0.1,0.2,0.3,0.4,0.7,1.0];
for j = 1:11
  [ts, u, x, rsave, isave, ind, user, cwsav, lwsav, iwsav, rwsav, ifail] = ...
  d03pp( ...
         npde, m, ts, tout(j), @pdedef, @bndary, @uvinit, ...
         u, x, ncode, @odedef, xi, rtol, atol, itol, normt, laopt, ...
         algopt, remesh, xfix, nrmesh, dxmesh, trmesh, ipminf, @monitf, ...
         rsave, isave, itask, itrace, ind, cwsav, lwsav, iwsav, rwsav);

  xsol(j,:) = x;
  tsol(j,:) = ts;
  usol(j,:) = u;

end

fprintf(' Number of time steps           = %6d\n',isave(1));
fprintf(' Number of function evaluations = %6d\n',isave(2));
fprintf(' Number of Jacobian evaluations = %6d\n',isave(3));
fprintf(' Number of iterations           = %6d\n',isave(5));

fig1=figure;
mesh(xsol,tsol,usol);
title('Burger''s Equation solution using moving mesh');
xlabel('x');
ylabel('t');
zlabel('u(x,t)');
view(22,24);


function [p, q, r, ires, user] = pdedef(npde, t, x, u, ux, ncode, v, vdot, ...
                                        ires, user)
  p = zeros(npde, npde);
  q = zeros(npde, 1);
  r = zeros(npde, 1);

  p(1,1) = 1.0d0;
  r(1) = 0.005*ux(1);
  q(1) = u(1)*ux(1);


function [beta, gamma, ires, user] = bndary(npde, t, u, ux, ncode, v, ...
                                            vdot, ibnd, ires, user)
  beta = zeros(npde, 1);
  gamma = zeros(npde, 1);

  if (ibnd == 0)
     ue = exact(t,1,[0]);
  else
     ue = exact(t,1,[1]);
  end
  gamma(1) = u(1) - ue(1);

function [u, v, user] = uvinit(npde, npts, nxi, x, xi, ncode, user)
  u = zeros(npde, npts);
  v = zeros(ncode, 1);

  u(1,1:npts) = exact(0,npts,x);

function [f, ires, user] = odedef(npde, t, ncode, v, vdot, nxi, xi, ...
                                  ucp, ucpx, rcp, ucpt, ucptx, ires, user)
  f = zeros(ncode, 1);

function [fmon, user] = monitf(t, npts, npde, x, u, r, user)
  fmon = zeros(npts, 1);

  drdx = (r(2)-r(1))/(x(2)-x(1));
  fmon(1) = abs(drdx); 
  for i = 2:npts-1
    % second derivative ..
    drdx  = 2*(r(1,i+1)-r(1,i))/(x(i+1)-x(i-1));
    fmon(i) = abs(drdx);
  end
  fmon(npts) = fmon(npts-1);

function ue = exact(t,n,x);
  e = 0.005;
  ue = zeros(n,1);
  for i = 1:n
    a = (x(i)-0.25-0.75*t)/(4*e);
    b = (0.9*x(i)-0.325-0.495*t)/(2*e);
    if (a>0 && a>b)
      a = exp(-a);
      c = (0.8*x(i)-0.4-0.24*t)/(4*e);
      c = exp(c);
      ue(i) = (0.5+0.1*c+a)/(1+c+a);
    elseif (b>0 && b>=a)
      b = exp(-b);
      c = (-0.8*x(i)+0.4+0.24*t)/(4*e);
      c = exp(c);
      ue(i) = (0.1+c/2+b)/(1+c+b);
    else
      a = exp(a);
      b = exp(b);
      ue(i) = (1+a/2+0.1*b)/(1+a+b);
    end
  end
d03pp example results

 Number of time steps           =    199
 Number of function evaluations =   4737
 Number of Jacobian evaluations =     69
 Number of iterations           =    505
d03pp_fig1.png

PDF version (NAG web site, 64-bit version, 64-bit version)
Chapter Contents
Chapter Introduction
NAG Toolbox

© The Numerical Algorithms Group Ltd, Oxford, UK. 2009–2015