PDF version (NAG web site
, 64-bit version, 64-bit version)
NAG Toolbox: nag_pde_1d_parab_convdiff_remesh (d03ps)
Purpose
nag_pde_1d_parab_convdiff_remesh (d03ps) integrates a system of linear or nonlinear convection-diffusion equations in one space dimension, with optional source terms and scope for coupled ordinary differential equations (ODEs). The system must be posed in conservative form. This function also includes the option of automatic adaptive spatial remeshing. Convection terms are discretized using a sophisticated upwind scheme involving a user-supplied numerical flux function based on the solution of a Riemann problem at each mesh point. The method of lines is employed to reduce the partial differential equations (PDEs) to a system of ODEs, and the resulting system is solved using a backward differentiation formula (BDF) method or a Theta method.
Syntax
[
ts,
u,
x,
rsave,
isave,
ind,
ifail] = d03ps(
npde,
ts,
tout,
pdedef,
numflx,
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, 'npts',
npts, 'nxi',
nxi, 'neqn',
neqn, 'nxfix',
nxfix, 'xratio',
xratio, 'con',
con)
[
ts,
u,
x,
rsave,
isave,
ind,
ifail] = nag_pde_1d_parab_convdiff_remesh(
npde,
ts,
tout,
pdedef,
numflx,
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, 'npts',
npts, 'nxi',
nxi, 'neqn',
neqn, 'nxfix',
nxfix, 'xratio',
xratio, 'con',
con)
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; nxi was made optional |
Description
nag_pde_1d_parab_convdiff_remesh (d03ps) integrates the system of convection-diffusion equations in conservative form:
or the hyperbolic convection-only system:
for
,
,
, where the vector
is the set of PDE solution values
The optional coupled ODEs are of the general form
where the vector
is the set of ODE solution values
denotes its derivative with respect to time, and
is the spatial derivative of
.
In
(2),
,
and
depend on
,
,
and
;
depends on
,
,
,
and
; and
depends on
,
,
,
and
linearly on
. Note that
,
,
and
must not depend on any space derivatives, and
,
,
and
must not depend on any time derivatives. In terms of conservation laws,
,
and
are the convective flux, diffusion and source terms respectively.
In
(3),
represents a vector of
spatial coupling points at which the ODEs are coupled to the PDEs. These points may or may not be equal to PDE spatial mesh points.
,
and
are the functions
,
and
evaluated at these coupling points. Each
may depend only linearly on time derivatives. Hence
(3) may be written more precisely as
where
,
is a vector of length
ncode,
is an
ncode by
ncode matrix,
is an
ncode by
matrix and the entries in
,
and
may depend on
,
,
,
and
. In practice you only need to supply a vector of information to define the ODEs and not the matrices
,
and
. (See
Arguments for the specification of
odedef.)
The integration in time is from to , over the space interval , where and are the leftmost and rightmost points of a user-defined mesh defined initially by you and (possibly) adapted automatically during the integration according to user-specified criteria.
The initial
values of the functions
and
must be specified in
uvinit. Note that
uvinit will be called again following any initial remeshing, and so
should be specified for
all values of
in the interval
, and not just the initial mesh points.
The PDEs are approximated by a system of ODEs in time for the values of
at mesh points using a spatial discretization method similar to the central-difference scheme used in
nag_pde_1d_parab_fd (d03pc),
nag_pde_1d_parab_dae_fd (d03ph) and
nag_pde_1d_parab_remesh_fd (d03pp), but with the flux
replaced by a
numerical flux, which is a representation of the flux taking into account the direction of the flow of information at that point (i.e., the direction of the characteristics). Simple central differencing of the numerical flux then becomes a sophisticated upwind scheme in which the correct direction of upwinding is automatically achieved.
The numerical flux,
say, must be calculated by you in terms of the
left and
right values of the solution vector
(denoted by
and
respectively), at each mid-point of the mesh
, for
. The left and right values are calculated by
nag_pde_1d_parab_convdiff_remesh (d03ps) from two adjacent mesh points using a standard upwind technique combined with a Van Leer slope-limiter (see
LeVeque (1990)). The physically correct value for
is derived from the solution of the Riemann problem given by
where
, i.e.,
corresponds to
, with discontinuous initial values
for
and
for
, using an
approximate Riemann solver. This applies for either of the systems
(1) or
(2); the numerical flux is independent of the functions
,
,
and
. A description of several approximate Riemann solvers can be found in
LeVeque (1990) and
Berzins et al. (1989). Roe's scheme (see
Roe (1981)) is perhaps the easiest to understand and use, and a brief summary follows. Consider the system of PDEs
or equivalently
. Provided the system is linear in
, i.e., the Jacobian matrix
does not depend on
, the numerical flux
is given by
where
(
) is the flux
calculated at the left (right) value of
, denoted by
(
); the
are the eigenvalues of
; the
are the right eigenvectors of
; and the
are defined by
Examples are given in the documents for
nag_pde_1d_parab_convdiff (d03pf) and
nag_pde_1d_parab_convdiff_dae (d03pl).
If the system is nonlinear, Roe's scheme requires that a linearized Jacobian is found (see
Roe (1981)).
The functions
,
,
and
(but
not
) must be specified in
pdedef. The numerical flux
must be supplied in
numflx. For problems in the form
(2),
the actual argument
nag_pde_1d_parab_convdiff_dae_sample_pdedef (d03plp)
may be used for
pdedef.
nag_pde_1d_parab_convdiff_dae_sample_pdedef (d03plp) is included in the NAG Toolbox and
sets the matrix with entries
to the identity matrix, and the functions
,
and
to zero.
For second-order problems, i.e., diffusion terms are present, a boundary condition is required for each PDE at both boundaries for the problem to be well-posed. If there are no diffusion terms present, then the continuous PDE problem generally requires exactly one boundary condition for each PDE, that is
npde boundary conditions in total. However, in common with most discretization schemes for first-order problems, a
numerical boundary condition is required at the other boundary for each PDE. In order to be consistent with the characteristic directions of the PDE system, the numerical boundary conditions must be derived from the solution inside the domain in some manner (see below). You must supply both types of boundary conditions, i.e., a total of
npde conditions at each boundary point.
The position of each boundary condition should be chosen with care. In simple terms, if information is flowing into the domain then a physical boundary condition is required at that boundary, and a numerical boundary condition is required at the other boundary. In many cases the boundary conditions are simple, e.g., for the linear advection equation. In general you should calculate the characteristics of the PDE system and specify a physical boundary condition for each of the characteristic variables associated with incoming characteristics, and a numerical boundary condition for each outgoing characteristic.
A common way of providing numerical boundary conditions is to extrapolate the characteristic variables from the inside of the domain (note that when using banded matrix algebra the fixed bandwidth means that only linear extrapolation is allowed, i.e., using information at just two interior points adjacent to the boundary). For problems in which the solution is known to be uniform (in space) towards a boundary during the period of integration then extrapolation is unnecessary; the numerical boundary condition can be supplied as the known solution at the boundary. Another method of supplying numerical boundary conditions involves the solution of the characteristic equations associated with the outgoing characteristics. Examples of both methods can be found in the documents for
nag_pde_1d_parab_convdiff (d03pf) and
nag_pde_1d_parab_convdiff_dae (d03pl).
The boundary conditions must be specified in
bndary in the form
at the left-hand boundary, and
at the right-hand boundary.
Note that spatial derivatives at the boundary are not passed explicitly to
bndary, but they can be calculated using values of
at and adjacent to the boundaries if required. However, it should be noted that instabilities may occur if such one-sided differencing opposes the characteristic direction at the boundary.
The algebraic-differential equation system which is defined by the functions
must be specified in
odedef. You must also specify the coupling points
(if any) in the array
xi.
In total there are
ODEs in the time direction. This system is then integrated forwards in time using a BDF or Theta method, optionally switching between Newton's method and functional iteration (see
Berzins et al. (1989) and the references therein).
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 by the function 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.
The problem is subject to the following restrictions:
(i) |
In (1), , for , may only appear linearly in the functions
, for , with a similar restriction for and ; |
(ii) |
, , and must not depend on any space derivatives; and , , and must not depend on any time derivatives; |
(iii) |
, so that integration is in the forward direction; |
(iv) |
The evaluation of the terms , , and is done by calling the pdedef at a point approximately midway between each pair of mesh points in turn. Any discontinuities in these functions must therefore be at one or more of the fixed mesh points specified by xfix; |
(v) |
At least one of the functions must be nonzero so that there is a time derivative present in the PDE problem. |
For further details of the scheme, see
Pennington and Berzins (1994) and the references therein.
References
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
Furzeland R M (1984) The construction of adaptive space meshes TNER.85.022 Thornton Research Centre, Chester
Hirsch C (1990) Numerical Computation of Internal and External Flows, Volume 2: Computational Methods for Inviscid and Viscous Flows John Wiley
LeVeque R J (1990) Numerical Methods for Conservation Laws Birkhäuser Verlag
Pennington S V and Berzins M (1994) New NAG Library software for first-order partial differential equations ACM Trans. Math. Softw. 20 63–99
Roe P L (1981) Approximate Riemann solvers, parameter vectors, and difference schemes J. Comput. Phys. 43 357–372
Parameters
Compulsory Input Parameters
- 1:
– int64int32nag_int scalar
-
The number of PDEs to be solved.
Constraint:
.
- 2:
– double scalar
-
The initial value of the independent variable .
Constraint:
.
- 3:
– double scalar
-
The final value of to which the integration is to be carried out.
- 4:
– function handle or string containing name of m-file
-
pdedef must evaluate the functions
,
,
and
which partially define the system of PDEs.
and
may depend on
,
,
and
;
may depend on
,
,
,
and
; and
may depend on
,
,
,
and linearly on
.
pdedef is called approximately midway between each pair of mesh points in turn by
nag_pde_1d_parab_convdiff_remesh (d03ps). The actual argument
nag_pde_1d_parab_convdiff_dae_sample_pdedef (d03plp) may be used for
pdedef for problems in the form
(2). (
nag_pde_1d_parab_convdiff_dae_sample_pdedef (d03plp) is included in the NAG Toolbox.)
[p, c, d, s, ires] = pdedef(npde, t, x, u, ux, ncode, v, vdot, ires)
Input Parameters
- 1:
– int64int32nag_int scalar
-
The number of PDEs in the system.
- 2:
– double scalar
-
The current value of the independent variable .
- 3:
– double scalar
-
The current value of the space variable .
- 4:
– double array
-
contains the value of the component , for .
- 5:
– double array
-
contains the value of the component , for .
- 6:
– int64int32nag_int scalar
-
The number of coupled ODEs in the system.
- 7:
– double array
-
If , contains the value of the component , for .
- 8:
– double array
-
If
,
contains the value of component
, for
.
Note:
, for , may only appear linearly in
, for .
- 9:
– int64int32nag_int scalar
-
Set to .
Output Parameters
- 1:
– double array
-
must be set to the value of , for and .
- 2:
– double array
-
must be set to the value of , for .
- 3:
– double array
-
must be set to the value of , for .
- 4:
– double array
-
must be set to the value of , for .
- 5:
– int64int32nag_int scalar
-
Should usually remain unchanged. However, you may set
ires to force the integration function to take certain actions as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , then nag_pde_1d_parab_convdiff_remesh (d03ps) returns to the calling function with the error indicator set to .
- 5:
– function handle or string containing name of m-file
-
numflx must supply the numerical flux for each PDE given the
left and
right values of the solution vector
.
numflx is called approximately midway between each pair of mesh points in turn by
nag_pde_1d_parab_convdiff_remesh (d03ps).
[flux, ires] = numflx(npde, t, x, ncode, v, uleft, uright, ires)
Input Parameters
- 1:
– int64int32nag_int scalar
-
The number of PDEs in the system.
- 2:
– double scalar
-
The current value of the independent variable .
- 3:
– double scalar
-
The current value of the space variable .
- 4:
– int64int32nag_int scalar
-
The number of coupled ODEs in the system.
- 5:
– double array
-
If , contains the value of the component , for .
- 6:
– double array
-
contains the left value of the component , for .
- 7:
– double array
-
contains the right value of the component , for .
- 8:
– int64int32nag_int scalar
-
Set to .
Output Parameters
- 1:
– double array
-
must be set to the numerical flux , for .
- 2:
– int64int32nag_int scalar
-
Should usually remain unchanged. However, you may set
ires to force the integration function to take certain actions as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , then nag_pde_1d_parab_convdiff_remesh (d03ps) returns to the calling function with the error indicator set to .
- 6:
– function handle or string containing name of m-file
-
bndary must evaluate the functions
and
which describe the physical and numerical boundary conditions, as given by
(8) and
(9).
[g, ires] = bndary(npde, npts, t, x, u, ncode, v, vdot, ibnd, ires)
Input Parameters
- 1:
– int64int32nag_int scalar
-
The number of PDEs in the system.
- 2:
– int64int32nag_int scalar
-
The number of mesh points in the interval .
- 3:
– double scalar
-
The current value of the independent variable .
- 4:
– double array
-
The mesh points in the spatial direction. corresponds to the left-hand boundary, , and corresponds to the right-hand boundary, .
- 5:
– double array
-
contains the value of the component
at
, for
and
.
Note: if banded matrix algebra is to be used then the functions and may depend on the value of at the boundary point and the two adjacent points only.
- 6:
– int64int32nag_int scalar
-
The number of coupled ODEs in the system.
- 7:
– double array
-
If , contains the value of the component , for .
- 8:
– double array
-
If
,
contains the value of component
, for
.
Note:
, for , may only appear linearly in
and , for .
- 9:
– int64int32nag_int scalar
-
Specifies which boundary conditions are to be evaluated.
- bndary must evaluate the left-hand boundary condition at .
- bndary must evaluate the right-hand boundary condition at .
- 10:
– int64int32nag_int scalar
-
Set to .
Output Parameters
- 1:
– double array
-
must contain the
th component of either
or
in
(8) and
(9), depending on the value of
ibnd, for
.
- 2:
– int64int32nag_int scalar
-
Should usually remain unchanged. However, you may set
ires to force the integration function to take certain actions as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , then nag_pde_1d_parab_convdiff_remesh (d03ps) returns to the calling function with the error indicator set to .
- 7:
– function handle or string containing name of m-file
-
uvinit must supply the initial
values of
and
for all values of
in the interval
.
[u, v] = uvinit(npde, npts, nxi, x, xi, ncode)
Input Parameters
- 1:
– int64int32nag_int scalar
-
The number of PDEs in the system.
- 2:
– int64int32nag_int scalar
-
The number of mesh points in the interval [].
- 3:
– int64int32nag_int scalar
-
The number of ODE/PDE coupling points.
- 4:
– double array
-
The current mesh. contains the value of , for .
- 5:
– double array
-
If , contains the ODE/PDE coupling point, , for .
- 6:
– int64int32nag_int scalar
-
The number of coupled ODEs in the system.
Output Parameters
- 1:
– double array
-
If , contains the value of the component , for and .
- 2:
– double array
-
If , must contain the value of component , for .
- 8:
– double array
-
If
the value of
u must be unchanged from the previous call.
- 9:
– double array
-
The mesh points in the space direction. must specify the left-hand boundary, , and must specify the right-hand boundary, .
Constraint:
.
- 10:
– int64int32nag_int scalar
-
The number of coupled ODE components.
Constraint:
.
- 11:
– function handle or string containing name of m-file
-
odedef must evaluate the functions
, which define the system of ODEs, as given in
(4).
If you wish to compute the solution of a system of PDEs only (i.e.,
),
odedef must be the string
nag_pde_1d_parab_dae_keller_remesh_fd_dummy_odedef (d03pek). (
nag_pde_1d_parab_dae_keller_remesh_fd_dummy_odedef (d03pek) is included in the NAG Toolbox.)
[r, ires] = odedef(npde, t, ncode, v, vdot, nxi, xi, ucp, ucpx, ucpt, ires)
Input Parameters
- 1:
– int64int32nag_int scalar
-
The number of PDEs in the system.
- 2:
– double scalar
-
The current value of the independent variable .
- 3:
– int64int32nag_int scalar
-
The number of coupled ODEs in the system.
- 4:
– double array
-
If , contains the value of the component , for .
- 5:
– double array
-
If , contains the value of component , for .
- 6:
– int64int32nag_int scalar
-
The number of ODE/PDE coupling points.
- 7:
– double array
-
If , contains the ODE/PDE coupling point, , for .
- 8:
– double array
-
The second dimension of the array
ucp must be at least
.
If , contains the value of at the coupling point , for and .
- 9:
– double array
-
The second dimension of the array
ucpx must be at least
.
If , contains the value of at the coupling point , for and .
- 10:
– double array
-
The second dimension of the array
ucpt must be at least
.
If , contains the value of at the coupling point , for and .
- 11:
– int64int32nag_int scalar
-
The form of
that must be returned in the array
r.
- Equation (10) must be used.
- Equation (11) must be used.
Output Parameters
- 1:
– double array
-
must contain the
th component of
, for
, where
is defined as
or
The definition of
is determined by the input value of
ires.
- 2:
– int64int32nag_int scalar
-
Should usually remain unchanged. However, you may reset
ires to force the integration function to take certain actions, as described below:
- Indicates to the integrator that control should be passed back immediately to the calling (sub)routine with the error indicator set to .
- Indicates to the integrator that the current time step should be abandoned and a smaller time step used instead. You may wish to set when a physically meaningless input or output value has been generated. If you consecutively set , then nag_pde_1d_parab_convdiff_remesh (d03ps) returns to the calling function with the error indicator set to .
- 12:
– double array
-
If , , for , must be set to the ODE/PDE coupling points.
Constraint:
.
- 13:
– double array
-
The dimension of the array
rtol
must be at least
if
or
and at least
if
or
The relative local error tolerance.
Constraint:
for all relevant .
- 14:
– double array
-
The dimension of the array
atol
must be at least
if
or
and at least
if
or
The absolute local error tolerance.
Constraint:
for all relevant
.
Note: corresponding elements of
rtol and
atol cannot both be
.
- 15:
– int64int32nag_int scalar
-
A value to indicate the form of the local error test.
If
is the estimated local error for
, for
, and
, denotes the norm, then the error test to be satisfied is
.
itol indicates to
nag_pde_1d_parab_convdiff_remesh (d03ps) whether to interpret either or both of
rtol and
atol as a vector or scalar in the formation of the weights
used in the calculation of the norm (see the description of
norm_p):
itol | rtol | atol | |
1 | scalar | scalar | |
2 | scalar | vector | |
3 | vector | scalar | |
4 | vector | vector | |
Constraint:
, , or .
- 16:
– string (length ≥ 1)
-
The type of norm to be used.
- Averaged norm.
- Averaged norm.
If
denotes the norm of the vector
u of length
neqn, then for the averaged
norm
and for the averaged
norm
See the description of
itol for the formulation of the weight vector
.
Constraint:
or .
- 17:
– string (length ≥ 1)
-
The type of matrix algebra required.
- Full matrix methods to be used.
- Banded matrix methods to be used.
- Sparse matrix methods to be used.
Constraint:
, or .
Note: you are recommended to use the banded option when no coupled ODEs are present (). Also, the banded option should not be used if the boundary conditions involve solution components at points other than the boundary and the immediately adjacent two points.
- 18:
– double array
-
May be set to control various options available in the integrator. If you wish to employ all the default options, then
should be set to
. 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:
- Selects the ODE integration method to be used. If , a BDF method is used and if , a Theta method is used. The default is .
If , then
, for , are not used.
- Specifies the maximum order of the BDF integration formula to be used. may be , , , or . The default value is .
- Specifies what method is to be used to solve the system of nonlinear equations arising on each step of the BDF method. If a modified Newton iteration is used and if 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 .
- 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
, for , for some or when there is no dependence in the coupled ODE system. If , then the Petzold test is used. If , then the Petzold test is not used. The default value is .
If , then
, for , are not used.
- Specifies the value of Theta to be used in the Theta integration method. . The default value is .
- Specifies what method is to be used to solve the system of nonlinear equations arising on each step of the Theta method. If , a modified Newton iteration is used and if , a functional iteration method is used. The default value is .
- 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 , then switching is allowed and if , then switching is not allowed. The default value is .
- Specifies a point in the time direction, , beyond which integration must not be attempted. The use of is described under the argument itask. If , a value of for , say, should be specified even if itask subsequently specifies that will not be used.
- Specifies the minimum absolute step size to be allowed in the time integration. If this option is not required, should be set to .
- Specifies the maximum absolute step size to be allowed in the time integration. If this option is not required, should be set to .
- Specifies the initial step size to be attempted by the integrator. If , then the initial step size is calculated internally.
- Specifies the maximum number of steps to be attempted by the integrator in any one call. If , then no limit is imposed.
- Specifies what method is to be used to solve the nonlinear equations at the initial point to initialize the values of , , and . If , a modified Newton iteration is used and if , functional iteration is used. The default value is .
and are used only for the sparse matrix algebra option, i.e., .
- Governs the choice of pivots during the decomposition of the first Jacobian matrix. It should lie in the range , with smaller values biasing the algorithm towards maintaining sparsity at the expense of numerical stability. If lies outside the range then the default value is used. If the functions regard the Jacobian matrix as numerically singular, then increasing towards may help, but at the cost of increased fill-in. The default value is .
- Used as the relative pivot threshold during subsequent Jacobian decompositions (see ) below which an internal error is invoked. must be greater than zero, otherwise the default value is used. If is greater than no check is made on the pivot size, and this may be a necessary option if the Jacobian matrix is found to be numerically singular (see ). The default value is .
- 19:
– logical scalar
-
Indicates whether or not spatial remeshing should be performed.
- Indicates that spatial remeshing should be performed as specified.
- Indicates that spatial remeshing should be suppressed.
Note: remesh should
not be changed between consecutive calls to
nag_pde_1d_parab_convdiff_remesh (d03ps). Remeshing can be switched off or on at specified times by using appropriate values for the arguments
nrmesh and
trmesh at each call.
- 20:
– double array
-
The dimension of the array
xfix
must be at least
, for , must contain the value of the coordinate at the th fixed mesh point.
Constraints:
- , for ;
- each fixed mesh point must coincide with a user-supplied initial mesh point, that is for some , ..
Note: the positions of the fixed mesh points in the array 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:
– int64int32nag_int scalar
-
Specifies the spatial remeshing frequency and criteria for the calculation and adoption of a new mesh.
- Indicates that a new mesh is adopted according to the argument dxmesh. The mesh is tested every timesteps.
- Indicates that remeshing should take place just once at the end of the first time step reached when .
- 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_convdiff_remesh (d03ps) to give greater flexibility over the times of remeshing.
- 22:
– 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
time steps, but is adopted only if
or
dxmesh thus imposes a lower limit on the difference between one mesh and the next.
Constraint:
.
- 23:
– 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
is greater than
trmesh.
Note: trmesh may be changed between consecutive calls to
nag_pde_1d_parab_convdiff_remesh (d03ps) to force remeshing at several specified times.
- 24:
– 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)).
- No trace information.
- Brief summary of mesh characteristics.
- More detailed information, including old and new mesh points, mesh sizes and monitor function values.
Constraint:
, or .
- 25:
– 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
, i.e., no remeshing, then
monitf will not be called and the string
nag_pde_1d_parab_dae_keller_remesh_fd_dummy_monitf (d03pel) may be used for
monitf. (
nag_pde_1d_parab_dae_keller_remesh_fd_dummy_monitf (d03pel) is included in the NAG Toolbox.)
[fmon] = monitf(t, npts, npde, x, u)
Input Parameters
- 1:
– double scalar
-
The current value of the independent variable .
- 2:
– int64int32nag_int scalar
-
The number of mesh points in the interval .
- 3:
– int64int32nag_int scalar
-
The number of PDEs in the system.
- 4:
– double array
-
The current mesh. contains the value of , for .
- 5:
– double array
-
contains the value of at and time , for and .
Output Parameters
- 1:
– double array
-
must contain the value of the monitor function at mesh point .
- 26:
– double array
-
If
,
rsave need not be set on entry.
If
,
rsave must be unchanged from the previous call to the function because it contains required information about the iteration.
- 27:
– int64int32nag_int array
-
If
,
isave need not be set.
If
,
isave must be unchanged from the previous call to the function because it contains required information about the iteration. In particular the following components of the array
isave concern the efficiency of the integration:
- Contains the number of steps taken in time.
- Contains the number of residual evaluations of the resulting ODE system used. One such evaluation involves evaluating the PDE functions at all the mesh points, as well as one evaluation of the functions in the boundary conditions.
- Contains the number of Jacobian evaluations performed by the time integrator.
- Contains the order of the BDF method last used in the time integration, if applicable. When the Theta method is used, contains no useful information.
- 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 decomposition of the Jacobian matrix.
- 28:
– int64int32nag_int scalar
-
The task to be performed by the ODE integrator.
- Normal computation of output values u at (by overshooting and interpolating).
- Take one step in the time direction and return.
- Stop at first internal integration point at or beyond .
- Normal computation of output values u at but without overshooting where is described under the argument algopt.
- Take one step in the time direction and return, without passing , where is described under the argument algopt.
Constraint:
, , , or .
- 29:
– int64int32nag_int scalar
-
The level of trace information required from
nag_pde_1d_parab_convdiff_remesh (d03ps) and the underlying ODE solver.
itrace may take the value
,
,
,
or
.
- No output is generated.
- Only warning messages from the PDE solver are printed on the current error message unit (see nag_file_set_unit_error (x04aa)).
- 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.
If , then is assumed and similarly if , then is assumed.
The advisory messages are given in greater detail as
itrace increases. You are advised to set
, unless you are experienced with
Sub-chapter D02M–N.
- 30:
– int64int32nag_int scalar
-
Indicates whether this is a continuation call or a new integration.
- Starts or restarts the integration in time.
- Continues the integration after an earlier exit from the function. In this case, only the arguments tout, ifail, nrmesh and trmesh may be reset between calls to nag_pde_1d_parab_convdiff_remesh (d03ps).
Constraint:
or .
Optional Input Parameters
- 1:
– int64int32nag_int scalar
-
Default:
the dimension of the array
x.
The number of mesh points in the interval .
Constraint:
.
- 2:
– int64int32nag_int scalar
-
Default:
the dimension of the array
xi.
The number of ODE/PDE coupling points.
Constraints:
- if , ;
- if , .
- 3:
– int64int32nag_int scalar
-
Default:
the dimension of the array
u.
The number of ODEs in the time direction.
Constraint:
.
- 4:
– int64int32nag_int scalar
-
Default:
the dimension of the array
xfix.
The number of fixed mesh points.
Constraint:
.
Note: the end points and are fixed automatically and hence should not be specified as fixed points.
- 5:
– double scalar
Default:
An input bound on the adjacent mesh ratio (greater than
and typically in the range
to
). The remeshing functions will attempt to ensure that
Constraint:
.
- 6:
– double scalar
Suggested value:
.
Default:
An input bound on the sub-integral of the monitor function
over each space step. The remeshing functions will attempt to ensure that
(see
Furzeland (1984)).
con gives you more control over the mesh distribution, e.g., decreasing
con allows more clustering. A typical value is
, 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:
.
Output Parameters
- 1:
– double scalar
-
The value of
corresponding to the solution values in
u. Normally
.
- 2:
– double array
-
contains the computed solution , for and , and
contains , for , all evaluated at .
- 3:
– double array
-
The final values of the mesh points.
- 4:
– double array
-
If
,
rsave must be unchanged from the previous call to the function because it contains required information about the iteration.
- 5:
– int64int32nag_int array
-
If
,
isave must be unchanged from the previous call to the function because it contains required information about the iteration. In particular the following components of the array
isave concern the efficiency of the integration:
- Contains the number of steps taken in time.
- Contains the number of residual evaluations of the resulting ODE system used. One such evaluation involves evaluating the PDE functions at all the mesh points, as well as one evaluation of the functions in the boundary conditions.
- Contains the number of Jacobian evaluations performed by the time integrator.
- Contains the order of the BDF method last used in the time integration, if applicable. When the Theta method is used, contains no useful information.
- 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 decomposition of the Jacobian matrix.
- 6:
– int64int32nag_int scalar
-
.
- 7:
– int64int32nag_int scalar
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.
-
-
On entry, | , |
or | is too small, |
or | , , , or , |
or | at least one of the coupling points defined in array xi is outside the interval [], |
or | the coupling points are not in strictly increasing order, |
or | , |
or | , |
or | , or , |
or | , , or , |
or | or , |
or | mesh points are badly ordered, |
or | lrsave is too small, |
or | lisave is too small, |
or | ncode and nxi are incorrectly defined, |
or | on initial entry to nag_pde_1d_parab_convdiff_remesh (d03ps), |
or | , |
or | an element of rtol or , |
or | corresponding elements of rtol and atol are both , |
or | or , |
or | nxfix not in the range to , |
or | fixed mesh point(s) do not coincide with any of the user-supplied mesh points, |
or | , |
or | , or , |
or | , |
or | con not in the range to . |
- W
-
The underlying ODE solver cannot make any further progress, with the values of
atol and
rtol, across the integration range from the current point
. The components of
u contain the computed values at the current point
.
- W
-
In the underlying ODE solver, there were repeated error test failures on an attempted step, before completing the requested task, but the integration was successful as far as . The problem may have a singularity, or the error requirement may be inappropriate. Incorrect specification of boundary conditions may also result in this error.
-
-
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
in one of
pdedef,
numflx,
bndary or
odedef, when the residual in the underlying ODE solver was being evaluated. Incorrect specification of boundary conditions may also result in this error.
-
-
In solving the ODE system, a singular Jacobian has been encountered. Check the problem formulation.
- W
-
When evaluating the residual in solving the ODE system,
ires was set to
in at least one of
pdedef,
numflx,
bndary or
odedef. Integration was successful as far as
.
-
-
The values of
atol and
rtol are so small that the function is unable to start the integration in time.
-
-
In one of
pdedef,
numflx,
bndary or
odedef,
ires was set to an invalid value.
- (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
may provide more information. If the problem persists, contact
NAG.
- W
-
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
or
.)
-
-
An error occurred during Jacobian formulation of the ODE system (a more detailed error description may be directed to the current advisory message unit when ). If using the sparse matrix algebra option, the values of and may be inappropriate.
-
-
In solving the ODE system, the maximum number of steps specified in have been taken.
- W
-
Some error weights
became zero during the time integration (see the description of
itol). Pure relative error control (
) was requested on a variable (the
th) which has become zero. The integration was successful as far as
.
-
-
One or more of the functions , or was detected as depending on time derivatives, which is not permissible.
-
-
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, see
nag_file_set_unit_error (x04aa)).
-
-
remesh has been changed between calls to
nag_pde_1d_parab_convdiff_remesh (d03ps).
-
-
fmon is negative at one or more mesh points, or zero mesh spacing has been obtained due to an inappropriate choice of monitor function.
-
An unexpected error has been triggered by this routine. Please
contact
NAG.
-
Your licence key may have expired or may not have been installed correctly.
-
Dynamic memory allocation failed.
Accuracy
nag_pde_1d_parab_convdiff_remesh (d03ps) 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
nag_pde_1d_parab_convdiff_remesh (d03ps) is designed to solve systems of PDEs in conservative form, with optional source terms which are independent of space derivatives, and optional second-order diffusion terms. The use of the function to solve systems which are not naturally in this form is discouraged, and you are advised to use one of the central-difference scheme functions for such problems.
You should be aware of the stability limitations for hyperbolic PDEs. For most problems with small error tolerances the ODE integrator does not attempt unstable time steps, but in some cases a maximum time step should be imposed using . It is worth experimenting with this argument, particularly if the integration appears to progress unrealistically fast (with large time steps). Setting the maximum time step to the minimum mesh size is a safe measure, although in some cases this may be too restrictive.
Problems with source terms should be treated with caution, as it is known that for large source terms stable and reasonable looking solutions can be obtained which are in fact incorrect, exhibiting non-physical speeds of propagation of discontinuities (typically one spatial mesh point per time step). It is essential to employ a very fine mesh for problems with source terms and discontinuities, and to check for non-physical propagation speeds by comparing results for different mesh sizes. Further details and an example can be found in
Pennington and Berzins (1994).
The time taken depends on the complexity of the system, 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
For this function two examples are presented, with a main program and two example problems given in Example 1 (EX1) and Example 2 (EX2).
Example 1 (EX1)
This example is a simple model of the advection and diffusion of a cloud of material:
for
and
. In this example the constant wind speed
and the diffusion coefficient
.
The cloud does not reach the boundaries during the time of integration, and so the two (physical) boundary conditions are simply
, and the initial condition is
and
elsewhere, where
and
.
The numerical flux is simply .
The monitor function for remeshing is taken to be the absolute value of the second derivative of .
Example 2 (EX2)
This example is a linear advection equation with a nonlinear source term and discontinuous initial profile:
for
and
. The discontinuity is modelled by a ramp function of width
and gradient
, so that the exact solution at any time
is
where
. The initial profile is given by the exact solution. The characteristic points into the domain at
and out of the domain at
, and so a physical boundary condition
is imposed at
, with a numerical boundary condition at
which can be specified as
since the discontinuity does not reach
during the time of integration.
The numerical flux is simply at all times.
The remeshing monitor function (described below) is chosen to create an increasingly fine mesh towards the discontinuity in order to ensure good resolution of the discontinuity, but without loss of efficiency in the surrounding regions. However, refinement must be limited so that the time step required for stability does not become unrealistically small. The region of refinement must also keep up with the discontinuity as it moves across the domain, and hence it cannot be so small that the discontinuity moves out of the refined region between remeshing.
The above requirements mean that the use of the first or second spatial derivative of for the monitor function is inappropriate; the large relative size of either derivative in the region of the discontinuity leads to extremely small mesh-spacing in a very limited region, and the solution is then far more expensive than for a very fine fixed mesh.
An alternative monitor function based on a cosine function proves very successful. It is only semi-automatic as it requires some knowledge of the solution (for problems without an exact solution an initial approximate solution can be obtained using a coarse fixed mesh). On each call to
monitf the discontinuity is located by finding the maximum spatial derivative of the solution. On the first call the desired width of the region of nonzero monitor function is set (this can be changed at a later time if desired). Then on each call the monitor function is assigned using a cosine function so that it has a value of one at the discontinuity down to zero at the edges of the predetermined region of refinement, and zero outside the region. Thus the monitor function and the subsequent refinement are limited, and the region is large enough to ensure that there is always sufficient refinement at the discontinuity.
Open in the MATLAB editor:
d03ps_example
function d03ps_example
fprintf('d03ps example results\n\n');
global usav1 usav2;
fprintf(' Example 1\n\n');
ex1;
fig1 = figure;
ex1_plot;
fprintf('\n\n\n Example 2\n\n');
ex2;
fig2 = figure;
ex2_plot;
function ex1
global xsav1 tsav1 usav1;
ncode = int64(0);
nxi = int64(0);
npde = int64(1);
npts = 61;
neqn = npde*npts + ncode;
lisave = 25 + neqn;
lrsave = 5000;
algopt = zeros(30, 1);
u = zeros(npde, npts);
x = [0:1/(npts-1):1];
rsave = zeros(lrsave, 1);
isave = zeros(lisave, 1, 'int64');
itrace = int64(0);
itol = int64(1);
norm_p = '1';
atol = [0.0001];
rtol = [0.0001];
xfix = [];
remesh = true;
nrmesh = int64(3);
dxmesh = 0.0;
trmesh = 0.0;
con = 2.0/(npts-1.0);
xratio = 1.5;
ipminf = int64(0);
xi = [0.0];
laopt = 'B';
algopt = zeros(30,1);
algopt(1) = 1.0;
algopt(13) = 0.005;
ind = int64(0);
ts = 0.0;
itask = int64(2);
tout = 0.3;
tnext = 0.0;
fprintf(' npts = %4d atol = %10.3e rtol = %10.3e \n\n', npts, atol, rtol);
isav = 0;
while ts < tout
[ts, u, x, rsave, isave, ind, ifail] = ...
d03ps( ...
npde, ts, tout, @ex1_pdedef, @ex1_numflx, @ex1_bndary, ...
@ex1_uvinit, u, x, ncode, 'd03pek', xi, rtol, atol, itol, ...
norm_p, laopt, algopt, remesh, xfix, nrmesh, dxmesh, ...
trmesh, ipminf, @ex1_monitf, rsave, isave, itask, itrace, ...
ind, 'nxi', nxi, 'xratio', xratio, 'con', con);
if ts >= tnext
isav = isav+1;
tsav1(isav) = ts;
for i=1:npts
usav1(isav,i) = u(1,i);
xsav1(isav,i) = x(i);
end
tnext = tnext + 0.01;
end
end
intpts = 7;
for i = 0:intpts - 1
xinterp(i+1) = 0.2 + i*0.1;
end
ind = int64(0);
itask = int64(1);
ts = 0.0;
dx = 1/(npts-1);
x = [0:dx:1];
for it = 1:3
tout = 0.1*it;
[ts, u, x, rsave, isave, ind, ifail] = ...
d03ps( ...
npde, ts, tout, @ex1_pdedef, @ex1_numflx, @ex1_bndary, ...
@ex1_uvinit, u, x, ncode, 'd03pek', xi, rtol, atol, itol, ...
norm_p, laopt, algopt, remesh, xfix, nrmesh, dxmesh, trmesh, ...
ipminf, @ex1_monitf, rsave, isave, itask, itrace, ...
ind, 'nxi', nxi, 'xratio', xratio, 'con', con);
fprintf(' t = %6.3f\n', ts);
fprintf(' x ');
fprintf('%9.4f', xinterp);
fprintf('\n');
m = int64(0);
itype = int64(1);
[uinterp, ifail] = d03pz( ...
m, u, x, xinterp, itype);
fprintf(' approx u');
fprintf('%9.4f', uinterp);
fprintf('\n\n');
end
fprintf([' Number of integration steps in time = %6d\n', ...
' Number of function evaluations = %6d\n', ...
' Number of Jacobian evaluations = %6d\n', ...
' Number of iterations = %6d\n'], ...
isave(1), isave(2), isave(3), isave(5));
function [p, c, d, s, ires] = ex1_pdedef(npde, t, x, u, ux, ncode, v, ...
vdot, ires)
p = zeros(npde, npde);
c = zeros(npde, 1);
d = zeros(npde, 1);
s = zeros(npde, 1);
p(1,1) = 1;
c(1) = 0.2d-2;
d(1) = ux(1);
function [flux, ires] = ex1_numflx(npde, t, x, ncode, v, uleft, uright, ires)
flux = zeros(npde, 1);
flux(1) = uleft(1);
function [g, ires] = ex1_bndary(npde, npts, t, x, u, ncode, v, vdot, ibnd, ires)
g = zeros(npde, 1);
if (ibnd == 0)
g(1) = u(1,1);
else
g(1) = u(1,npts);
end
function [u, v] = ex1_uvinit(npde, npts, nxi, x, xi, ncode)
u = zeros(npde, npts);
v = zeros(ncode, 1);
for i = 1:double(npts)
if (x(i) > 0.2 && x(i) <= 0.4)
u(1,i) = sin(pi*(5*x(i)-1));
end
end
function [r, ires] = ex1_odedef(npde, t, ncode, v, vdot, nxi, xi, ucp, ucpx, ...
ucpt, ires)
r = zeros(ncode, 1);
function [fmon] = ex1_monitf(t, npts, npde, x, u)
fmon = zeros(npts, 1);
for i = 2:double(npts) - 1
h1 = x(i) - x(i-1);
h2 = x(i+1) - x(i);
h3 = (x(i+1)-x(i-1))/2;
fmon(i) = abs(((u(1,i+1)-u(1,i))/h2-(u(1,i)-u(1,i-1))/h1)/h3);
end
fmon(1) = fmon(2);
fmon(npts) = fmon(double(npts)-1);
function ex2
global xsav2 tsav2 usav2;
ncode = int64(0);
nxi = int64(0);
npde = int64(1);
npts = 61;
neqn = npde*npts + ncode;
lisave = 25 + neqn;
lrsave = 5000;
algopt = zeros(30, 1);
u = zeros(npde, npts);
x = zeros(npts, 1);
rsave = zeros(lrsave, 1);
isave = zeros(lisave, 1, 'int64');
itrace = int64(0);
itol = int64(1);
norm_p = '1';
atol = [0.0005];
rtol = [0.05];
dx = 1/(npts-1);
x = [0:dx:1];
xfix = [];
remesh = true;
nrmesh = int64(5);
dxmesh = 0;
trmesh = 0;
con = dx;
xratio = 1.5;
ipminf = int64(0);
xi = [0.0];
laopt = 'B';
algopt = zeros(30,1);
algopt(1) = 2.0;
algopt(6) = 2.0;
algopt(7) = 2.0;
algopt(13) = 0.0025;
ind = int64(0);
ts = 0.0;
itask = int64(2);
tout = 0.4;
tnext = 0.0;
isav = 0;
while ts < tout
[ts, u, x, rsave, isave, ind, ifail] = ...
d03ps( ...
npde, ts, tout, @ex2_pdedef, @ex2_numflx, @ex2_bndary, ...
@ex2_uvinit, u, x, ncode, 'd03pek', xi, rtol, atol, itol, ...
norm_p, laopt, algopt, remesh, xfix, nrmesh, dxmesh, trmesh, ...
ipminf, @ex2_monitf, rsave, isave, itask, itrace, ...
ind, 'nxi', nxi, 'xratio', xratio, 'con', con);
if ts >= tnext
isav = isav+1;
tsav2(isav) = ts;
usav2(isav,1:npts) = u(1,:);
xsav2(isav,1:npts) = x;
tnext = tnext + 0.01;
end
end
intpts = 7;
xinterp = [0.2:0.1:0.8];
ind = int64(0);
itask = int64(1);
ts = 0;
dx = 1/(npts-1);
x = [0:dx:1];
for it = 1:2
tout = 0.2*it;
[ts, u, x, rsave, isave, ind, ifail] = ...
d03ps( ...
npde, ts, tout, @ex2_pdedef, @ex2_numflx, @ex2_bndary, ...
@ex2_uvinit, u, x, ncode, 'd03pek', xi, rtol, atol, itol, ...
norm_p, laopt, algopt, remesh, xfix, nrmesh, dxmesh, trmesh, ...
ipminf, @ex2_monitf, rsave, isave, itask, itrace, ...
ind, 'nxi', nxi, 'xratio', xratio, 'con', con);
if it == 1
fprintf(' npts = %4d atol = %10.3e rtol = %10.3e \n\n', npts, ...
atol, rtol)
end
fprintf(' t = %6.3f\n', ts);
m = int64(0);
itype = int64(1);
[uinterp, ifail] = d03pz(m, u, x, xinterp, itype);
[ue] = ex2_exact(tout, xinterp, intpts);
fprintf(' x approx u exact u\n');
for i=1:intpts
fprintf('%9.4f %9.4f %9.4f\n', xinterp(i), uinterp(i), ue(i));
end
fprintf('\n\n');
end
fprintf([' Number of integration steps in time = %6d\n', ...
' Number of function evaluations = %6d\n', ...
' Number of Jacobian evaluations = %6d\n', ...
' Number of iterations = %6d\n'], ...
isave(1), isave(2), isave(3), isave(5));
function [p, c, d, s, ires] = ex2_pdedef(npde, t, x, u, ux, ...
ncode, v, vdot, ires)
p = zeros(npde, npde);
c = zeros(npde, 1);
d = zeros(npde, 1);
s = zeros(npde, 1);
p(1,1) = 1;
c(1) = 0;
d(1) = 0;
s(1) = -100*u(1)*(u(1) - 1)*(u(1) - 0.5);
function [fmon] = ex2_monitf(t, npts, npde, x, u)
persistent icount;
persistent xa;
fmon = zeros(npts, 1);
uxmax = 0;
xmax = 0;
for i = 2:npts-1
h1 = x(i) - x(i-1);
ux = abs((u(1,i) - u(1,i-1))/h1);
if (ux > uxmax)
uxmax = ux;
xmax = x(i);
end
end
if (isempty(icount))
icount = 1;
xleft = xmax - x(1);
xright = x(npts) - xmax;
if (xleft > xright)
xa = xright;
else
xa = xleft;
end
end
xl = xmax - xa;
xr = xmax + xa;
for i = 1:npts
if ((x(i) > xl) && (x(i) < xr))
fmon(i) = 1.0 + cos(pi*(x(i) - xmax)/xa);
else
fmon(i) = 0.0;
end
end
function [g, ires] = ex2_bndary(npde, npts, t, x, u, ncode, v, ...
vdot, ibnd, ires)
if (ibnd == 0)
[ue] = ex2_exact(t, x(1), 1);
g(1) = ue(1,1) - u(1,1);
else
[ue] = ex2_exact(t, x(npts), 1);
g(1) = ue(1,1) - u(1,npts);
end
function [flux, ires] = ex2_numflx(npde, t, x, ncode, v, uleft, ...
uright, ires)
flux = zeros(npde, 1);
flux(1) = uleft(1);
function [u, v] = ex2_uvinit(npde, npts, nxi, x, xi, ncode)
u = zeros(npde, npts);
v = zeros(ncode, 1);
t = 0.0;
[u] = ex2_exact(t, x, npts);
function [u] = ex2_exact(t, x, npts)
s = 0.1;
del = 0.01;
rm = -1.0/del;
rn = 1.0 + s/del;
for i = 1:npts
psi = x(i) - t;
if (psi < s)
u(1,i) = 1.0;
elseif (psi > (del+s))
u(1,i) = 0.0;
else
u(1,i) = rm*psi + rn;
end
end
function ex1_plot
global xsav1 tsav1 usav1;
mesh(xsav1, tsav1, usav1);
xlabel('x');
ylabel('t');
zlabel('U(x,t)');
title('Advection and Diffusion of a Cloud of Material');
axis([xsav1(1) xsav1(end) tsav1(1) tsav1(end) 0 1]);
view(-12, 56);
function ex2_plot
global xsav2 tsav2 usav2;
mesh(xsav2, tsav2, usav2);
xlabel('x');
ylabel('t');
zlabel('U(x,t)');
title('Linear Advection with Non-linear Source Term');
axis([xsav2(1) xsav2(end) tsav2(1) tsav2(end) 0 1]);
view(15, 30);
d03ps example results
Example 1
npts = 61 atol = 1.000e-04 rtol = 1.000e-04
t = 0.100
x 0.2000 0.3000 0.4000 0.5000 0.6000 0.7000 0.8000
approx u 0.0000 0.1198 0.9461 0.1182 0.0000 0.0000 0.0000
t = 0.200
x 0.2000 0.3000 0.4000 0.5000 0.6000 0.7000 0.8000
approx u 0.0000 0.0007 0.1631 0.9015 0.1629 0.0001 0.0000
t = 0.300
x 0.2000 0.3000 0.4000 0.5000 0.6000 0.7000 0.8000
approx u 0.0000 0.0000 0.0025 0.1924 0.8596 0.1946 0.0002
Number of integration steps in time = 92
Number of function evaluations = 443
Number of Jacobian evaluations = 39
Number of iterations = 231
Example 2
npts = 61 atol = 5.000e-04 rtol = 5.000e-02
t = 0.200
x approx u exact u
0.2000 1.0000 1.0000
0.3000 0.9536 1.0000
0.4000 0.0000 0.0000
0.5000 0.0000 0.0000
0.6000 0.0000 0.0000
0.7000 -0.0000 0.0000
0.8000 0.0000 0.0000
t = 0.400
x approx u exact u
0.2000 1.0000 1.0000
0.3000 1.0000 1.0000
0.4000 1.0000 1.0000
0.5000 0.9750 1.0000
0.6000 -0.0000 0.0000
0.7000 0.0000 0.0000
0.8000 0.0000 0.0000
Number of integration steps in time = 672
Number of function evaluations = 1515
Number of Jacobian evaluations = 1
Number of iterations = 2
PDF version (NAG web site
, 64-bit version, 64-bit version)
© The Numerical Algorithms Group Ltd, Oxford, UK. 2009–2015