D02MVF (PDF version)
D02 Chapter Contents
D02 Chapter Introduction
NAG Library Manual

NAG Library Routine Document


Note:  before using this routine, please read the Users' Note for your implementation to check the interpretation of bold italicised terms and other implementation-dependent details.

+ Contents

    1  Purpose
    7  Accuracy

1  Purpose

D02MVF is an integration method specific setup routine which must be called prior to linear algebra setup routines and integrators from the SPRINT suite of routines, if the DASSL implementation of Backward Differentiation Formulae (BDF) is to be used. Note that this method is also available, independent from the SPRINT suite, using D02NEF

2  Specification


3  Description

An integrator setup routine must be called before the call to any linear algebra setup routine or integrator from the SPRINT suite of routines in this sub-chapter. This setup routine, D02MVF, makes the choice of the DASSL integrator and permits you to define options appropriate to this choice. Alternative choices of integrator from this suite are the BDF method and the BLEND method which can be chosen by initial calls to D02NVF or D02NWF respectively.

4  References

See the D02M–N sub-chapter Introduction.

5  Parameters

1:     NEQMAX – INTEGERInput
On entry: a bound on the maximum number of differential equations to be solved.
Constraint: NEQMAX1.
2:     SDYSAV – INTEGERInput
On entry: the second dimension of the array YSAV that will be supplied to the integrator, as declared in the (sub)program from which the integrator is called (e.g., see D02NBF).
Constraint: SDYSAVMAXORD+3.
3:     MAXORD – INTEGERInput
On entry: the maximum order to be used for the BDF method. If MAXORD=0 or MAXORD>5 then MAXORD=5 is assumed.
Constraint: MAXORD0.
4:     CON(3) – REAL (KIND=nag_wp) arrayInput/Output
On entry: values to be used to control step size choice during integration. If any CONi=0.0 on entry, it is replaced by its default value described below. In most cases this is the recommended setting.
CON1, CON2, and CON3 are factors used to bound step size changes. If the current step size h fails, then the modulus of the next step size is bounded by CON1×h. The default value of CON1 is 2.0. Note that the new step size may be used with a method of different order to the failed step. If the initial step size is h, then the modulus of the step size on the second step is bounded by CON3×h. At any other stage in the integration, if the current step size is h, then the modulus of the next step size is bounded by CON2×h. The default values are 10.0 for CON2 and 1000.0 for CON3.
These constraints must be satisfied after any zero values have been replaced by default values.
  • 0.0<CON1<CON2<CON3;
  • CON2>1.0;
  • CON3>1.0.
On exit: the values actually to be used by the integration routine.
5:     TCRIT – REAL (KIND=nag_wp)Input
On entry: a point beyond which integration must not be attempted. The use of TCRIT is described under the parameter ITASK in the specification for the integrator (e.g., see D02NBF). A value, 0.0 say, must be specified even if ITASK subsequently specifies that TCRIT will not be used.
6:     HMIN – REAL (KIND=nag_wp)Input
On entry: the minimum absolute step size to be allowed. Set HMIN=0.0 if this option is not required.
7:     HMAX – REAL (KIND=nag_wp)Input
On entry: the maximum absolute step size to be allowed. Set HMAX=0.0 if this option is not required.
8:     H0 – REAL (KIND=nag_wp)Input
On entry: the step size to be attempted on the first step. Set H0=0.0 if the initial step size is calculated internally.
9:     MAXSTP – INTEGERInput
On entry: the maximum number of steps to be attempted during one call to the integrator after which it will return with IFAIL=2 (e.g., see D02NBF). Set MAXSTP=0 if no limit is to be imposed.
On entry: the maximum number of warnings printed (if ITRACE0, e.g., see D02NBF) per problem when t+h=t on a step (h=​ current step size). If MXHNIL0, a default value of 10 is assumed.
11:   NORM – CHARACTER(1)Input
On entry: indicates the type of norm to be used.
Maximum norm.
Averaged L2 norm.
Is the same as 'A'.
If vnorm denotes the norm of the vector v of length n, then for the averaged L2 norm
vnormB=1ni=1n viwi 2,
while for the maximum norm
vnorm=max1in viwi .
If you wish to weight the maximum norm or the L2 norm, then RTOL and ATOL should be scaled appropriately on input to the integrator (see under ITOL in the specification of the integrator for the formulation of the weight vector wi from RTOL and ATOL, e.g., see D02NBF).
Only the first character to the actual parameter NORM is passed to D02MVF; hence it is permissible for the actual argument to be more descriptive, e.g., ‘Maximum’, ‘Average L2’ or ‘Default’ in a call to D02MVF.
Constraint: NORM='M', 'A' or 'D'.
12:   RWORK(50+4×NEQMAX) – REAL (KIND=nag_wp) arrayCommunication Array
This must be the same workspace array as the array RWORK supplied to the integrator. It is used to pass information from the setup routine to the integrator and therefore the contents of this array must not be changed before calling the integrator.
13:   IFAIL – INTEGERInput/Output
On entry: IFAIL must be set to 0, -1​ or ​1. If you are unfamiliar with this parameter you should refer to Section 3.3 in the Essential Introduction for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value -1​ or ​1 is recommended. If the output of error messages is undesirable, then the value 1 is recommended. Otherwise, if you are not familiar with this parameter, the recommended value is 0. When the value -1​ or ​1 is used it is essential to test the value of IFAIL on exit.
On exit: IFAIL=0 unless the routine detects an error or a warning has been flagged (see Section 6).

6  Error Indicators and Warnings

If on entry IFAIL=0 or -1, explanatory error messages are output on the current error message unit (as defined by X04AAF).
Errors or warnings detected by the routine:
On entry,NEQMAX<1,
orinvalid value for element of the array CON,
orNORM'M', 'A' or 'D'.

7  Accuracy

Not applicable.

8  Further Comments


9  Example

This example solves the plane pendulum problem defined by the equations:
x = u y = v u = -λx v = -λy-1 x2+y2 = 1
The additional algebraic constraint xu+yv=0 can be derived, and after appropriate substitution and manipulation to avoid a singular Jacobian solves the equations:
y1 = y3-y6y1 y2 = y4-y6y2 y3 = -y5y1 y4 = -y5y2-1 0 = y1y3+y2y4 0 = y12+y22-1
with given initial conditions and derivatives.

9.1  Program Text

Program Text (d02mvfe.f90)

9.2  Program Data

Program Data (d02mvfe.d)

9.3  Program Results

Program Results (d02mvfe.r)

Produced by GNUPLOT 4.4 patchlevel 0 -1 -0.9 -0.8 -0.7 -0.6 -0.5 -0.4 -0.3 -0.2 -0.1 0 -1 -0.8 -0.6 -0.4 -0.2 0 0.2 0.4 0.6 0.8 1 Pendulum Displacement x Example Program DASSL Implementation of BDF Method for Stiff ODE Plane Pendulum Problem

D02MVF (PDF version)
D02 Chapter Contents
D02 Chapter Introduction
NAG Library Manual

© The Numerical Algorithms Group Ltd, Oxford, UK. 2012