NAG Library Routine Document

d02nef  (dae_dassl_gen)

 Contents

    1  Purpose
    7  Accuracy

1
Purpose

d02nef is a routine for integrating stiff systems of implicit ordinary differential equations coupled with algebraic equations.

2
Specification

Fortran Interface
Subroutine d02nef ( neq, t, tout, y, ydot, rtol, atol, itask, res, jac, icom, com, lcom, iuser, ruser, ifail)
Integer, Intent (In):: neq, lcom
Integer, Intent (Inout):: itask, icom(50+neq), iuser(*), ifail
Real (Kind=nag_wp), Intent (In):: tout
Real (Kind=nag_wp), Intent (Inout):: t, y(neq), ydot(neq), rtol(*), atol(*), com(lcom), ruser(*)
External:: res, jac
C Header Interface
#include nagmk26.h
void  d02nef_ ( const Integer *neq, double *t, const double *tout, double y[], double ydot[], double rtol[], double atol[], Integer *itask,
void (NAG_CALL *res)( const Integer *neq, const double *t, const double y[], const double ydot[], double r[], Integer *ires, Integer iuser[], double ruser[]),
void (NAG_CALL *jac)( const Integer *neq, const double *t, const double y[], const double ydot[], double pd[], const double *cj, Integer iuser[], double ruser[]),
Integer icom[], double com[], const Integer *lcom, Integer iuser[], double ruser[], Integer *ifail)

3
Description

d02nef is a general purpose routine for integrating the initial value problem for a stiff system of implicit ordinary differential equations with coupled algebraic equations written in the form
F t,y,y = 0 .  
d02nef uses the DASSL implementation of the Backward Differentiation Formulae (BDF) of orders one to five to solve a system of the above form for y (y) and y (ydot). Values for y and ydot at the initial time must be given as input. These values must be consistent, (i.e., if t, y, ydot are the given initial values, they must satisfy Ft,y,ydot=0). The routine solves the system from t=t to t=tout.
An outline of a typical calling program for d02nef is given below. It calls the DASSL implementation of the BDF integrator setup routine d02mwf and the banded matrix setup routine d02npf (if required), and, if the integration needs to proceed, calls d02mcf before continuing the integration.
!     Declarations

      External res, jac
             .
             .
             .
!     Initialize the integrator
      Call d02mwf(...)
!     Is the Jacobian matrix banded?
      If (banded) Call d02npf(...)

!     Set dt to the required temporal resolution
!     Set tend to the final time
!     Call the integrator for each temporal value:
1000  Call d02nef(...,res,jac,...)
!     Continue integration?
      If (tout.lt.tend .and. itask.ge.0) Then
        If (itask.ne.1) tout = min(tout+dt,tend)
!       Print solution
        Call d02mcf(...)
        Go To 1000
      Endif
             .
             .
             .

4
References

None.

5
Arguments

1:     neq – IntegerInput
On entry: the number of differential-algebraic equations to be solved.
Constraint: neq1.
2:     t – Real (Kind=nag_wp)Input/Output
On initial entry: the initial value of the independent variable, t.
On intermediate exit: t, the current value of the independent variable.
On final exit: the value of the independent variable at which the computed solution y is returned (usually at tout).
3:     tout – Real (Kind=nag_wp)Input
On entry: the next value of t at which a computed solution is desired.
On initial entry: tout is used to determine the direction of integration. Integration is permitted in either direction (see also itask).
Constraint: toutt.
4:     yneq – Real (Kind=nag_wp) arrayInput/Output
On initial entry: the vector of initial values of the dependent variables y.
On intermediate exit: the computed solution vector, y, evaluated at t=T.
On final exit: the computed solution vector, evaluated at t (usually t=tout).
5:     ydotneq – Real (Kind=nag_wp) arrayInput/Output
On initial entry: ydot must contain approximations to the time derivatives y' of the vector y evaluated at the initial value of the independent variable.
On exit: the time derivatives y' of the vector y at the last integration point.
6:     rtol* – Real (Kind=nag_wp) arrayInput/Output
Note: the dimension of the array rtol depends on the value of itol as set in d02mwf; it  must be at least neq if itol=.TRUE. and at least 1 if itol=.FALSE..
On entry: the relative local error tolerance.
Constraint: rtoli0.0, for i=1,2,,n
where n=neq when itol=.TRUE. and n=1 otherwise.
On exit: rtol remains unchanged unless d02nef exits with ifail=16 in which case the values may have been increased to values estimated to be appropriate for continuing the integration.
7:     atol* – Real (Kind=nag_wp) arrayInput/Output
Note: the dimension of the array atol depends on the value of itol as set in d02mwf; it  must be at least neq if itol=.TRUE. and at least 1 if itol=.FALSE..
On entry: the absolute local error tolerance.
Constraint: atoli0.0, for i=1,2,,n
where n=neq when itol=.TRUE. and n=1 otherwise.
On exit: atol remains unchanged unless d02nef exits with ifail=16 in which case the values may have been increased to values estimated to be appropriate for continuing the integration.
8:     itask – IntegerInput/Output
On initial entry: need not be set.
On exit: the task performed by the integrator on successful completion or an indicator that a problem occurred during integration.
itask=2
The integration to tout was successfully completed (t=tout) by stepping exactly to tout.
itask=3
The integration to tout was successfully completed (t=tout) by stepping past tout. y and ydot are obtained by interpolation.
itask<0
Different negative values of itask returned correspond to different failure exits. ifail should always be checked in such cases and the corrective action taken where appropriate.
itask must remain unchanged between calls to d02nef.
9:     res – Subroutine, supplied by the user.External Procedure
res must evaluate the residual
R = F t,y,y .  
The specification of res is:
Fortran Interface
Subroutine res ( neq, t, y, ydot, r, ires, iuser, ruser)
Integer, Intent (In):: neq
Integer, Intent (Inout):: ires, iuser(*)
Real (Kind=nag_wp), Intent (In):: t, y(neq), ydot(neq)
Real (Kind=nag_wp), Intent (Inout):: ruser(*)
Real (Kind=nag_wp), Intent (Out):: r(neq)
C Header Interface
#include nagmk26.h
void  res ( const Integer *neq, const double *t, const double y[], const double ydot[], double r[], Integer *ires, Integer iuser[], double ruser[])
1:     neq – IntegerInput
On entry: the number of differential-algebraic equations being solved.
2:     t – Real (Kind=nag_wp)Input
On entry: t, the current value of the independent variable.
3:     yneq – Real (Kind=nag_wp) arrayInput
On entry: yi, for i=1,2,,neq, the current solution component.
4:     ydotneq – Real (Kind=nag_wp) arrayInput
On entry: the derivative of the solution at the current point t.
5:     rneq – Real (Kind=nag_wp) arrayOutput
On exit: ri must contain the ith component of R, for i=1,2,,neq where
R = F t,y,ydot .  
6:     ires – IntegerInput/Output
On entry: is always equal to zero.
On exit: ires should normally be left unchanged. However, if an illegal value of y is encountered, ires should be set to -1; d02nef will then attempt to resolve the problem so that illegal values of y are not encountered. ires should be set to -2 if you wish to return control to the calling (sub)routine; this will cause d02nef to exit with ifail=23.
7:     iuser* – Integer arrayUser Workspace
8:     ruser* – Real (Kind=nag_wp) arrayUser Workspace
res is called with the arguments iuser and ruser as supplied to d02nef. You should use the arrays iuser and ruser to supply information to res.
res must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02nef is called. Arguments denoted as Input must not be changed by this procedure.
Note: res should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02nef. If your code inadvertently does return any NaNs or infinities, d02nef is likely to produce unexpected results.
10:   jac – Subroutine, supplied by the NAG Library or the user.External Procedure
Evaluates the matrix of partial derivatives, J, where
J ij = Fi yj + cj × Fi yj ,  i,j=1,2,,neq .  
If this option is not required, the actual argument for jac must be the dummy routine d02nez. (d02nez is included in the NAG Library.) You must indicate to the integrator whether this option is to be used by setting the argument jceval appropriately in a call to the setup routine d02mwf.
The specification of jac is:
Fortran Interface
Subroutine jac ( neq, t, y, ydot, pd, cj, iuser, ruser)
Integer, Intent (In):: neq
Integer, Intent (Inout):: iuser(*)
Real (Kind=nag_wp), Intent (In):: t, y(neq), ydot(neq), cj
Real (Kind=nag_wp), Intent (Inout):: pd(*), ruser(*)
C Header Interface
#include nagmk26.h
void  jac ( const Integer *neq, const double *t, const double y[], const double ydot[], double pd[], const double *cj, Integer iuser[], double ruser[])
1:     neq – IntegerInput
On entry: the number of differential-algebraic equations being solved.
2:     t – Real (Kind=nag_wp)Input
On entry: t, the current value of the independent variable.
3:     yneq – Real (Kind=nag_wp) arrayInput
On entry: yi, for i=1,2,,neq, the current solution component.
4:     ydotneq – Real (Kind=nag_wp) arrayInput
On entry: the derivative of the solution at the current point t.
5:     pd* – Real (Kind=nag_wp) arrayInput/Output
On entry: pd is preset to zero before the call to jac.
On exit: if the Jacobian is full then pdj-1×neq+i=Jij, for i=1,2,,neq and j=1,2,,neq; if the Jacobian is banded then pdj-1×2ml+mu+1+ml+mu+i-j+1=Jij, for max1,j-muiminn,j+ml; (see also in f07bdf (dgbtrf)).
6:     cj – Real (Kind=nag_wp)Input
On entry: cj is a scalar constant which will be defined in d02nef.
7:     iuser* – Integer arrayUser Workspace
8:     ruser* – Real (Kind=nag_wp) arrayUser Workspace
jac is called with the arguments iuser and ruser as supplied to d02nef. You should use the arrays iuser and ruser to supply information to jac.
jac must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02nef is called. Arguments denoted as Input must not be changed by this procedure.
Note: jac should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02nef. If your code inadvertently does return any NaNs or infinities, d02nef is likely to produce unexpected results.
11:   icom50+neq – Integer arrayCommunication Array
icom contains information which is usually of no interest, but is necessary for subsequent calls. However you may find the following useful:
icom22
The order of the method to be attempted on the next step.
icom23
The order of the method used on the last step.
icom26
The number of steps taken so far.
icom27
The number of calls to res so far.
icom28
The number of evaluations of the matrix of partial derivatives needed so far.
icom29
The total number of error test failures so far.
icom30
The total number of convergence test failures so far.
12:   comlcom – Real (Kind=nag_wp) arrayCommunication Array
com contains information which is usually of no interest, but is necessary for subsequent calls. However you may find the following useful:
com3
The step size to be attempted on the next step.
com4
The current value of the independent variable, i.e., the farthest point integration has reached. This will be different from t only when interpolation has been performed (itask=3).
13:   lcom – IntegerInput
On entry: the dimension of the array com as declared in the (sub)program from which d02nef is called.
Constraint: lcom40+maxorder+4×neq+neq×p+q where maxorder is the maximum order that can be used by the integration method (see maxord in d02mwf); p=neq when the Jacobian is full and p=2×ml+mu+1 when the Jacobian is banded; and, q=neq/ml+mu+1+1 when the Jacobian is to be evaluated numerically and q=0 otherwise.
14:   iuser* – Integer arrayUser Workspace
15:   ruser* – Real (Kind=nag_wp) arrayUser Workspace
iuser and ruser are not used by d02nef, but are passed directly to res and jac and may be used to pass information to these routines.
16:   ifail – IntegerInput/Output
On entry: ifail must be set to 0, -1​ or ​1. If you are unfamiliar with this argument you should refer to Section 3.4 in How to Use the NAG Library and its Documentation for details.
For environments where it might be inappropriate to halt program execution when an error is detected, the value -1​ or ​1 is recommended. If the output of error messages is undesirable, then the value 1 is recommended. Otherwise, because for this routine the values of the output arguments may be useful even if ifail0 on exit, the recommended value is -1. 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).
Note: d02nef may return useful information for one or more of the following detected errors or warnings.
Errors or warnings detected by the routine:
ifail=1
On entry, neq=value.
Constraint: neq1.
ifail=3
On entry, t=value.
Constraint: toutt.
tout is behind t in the direction of h: tout-t=value, h=value.
tout is too close to t to start integration: tout-t=value: hmin=value.
ifail=6
Some element of rtol is less than zero.
ifail=7
Some element of atol is less than zero.
ifail=8
A previous call to this routine returned with itask=value and no appropriate action was taken.
ifail=11
Either the initialization routine has not been called prior to the first call of this routine or a communication array has become corrupted.
ifail=12
Either the initialization routine has not been called prior to the first call of this routine or a communication array has become corrupted.
ifail=13
com array is of insufficient length; length required =value; actual length lcom=value.
ifail=14
All elements of rtol and atol are zero.
ifail=15
Maximum number of steps taken on this call before reaching tout: t=value, maximum number of steps =value.
ifail=16
Too much accuracy requested for precision of machine. rtol and atol were increased by scale factor R. Try running again with these scaled tolerances. t=value, R=value.
ifail=17
A solution component has become zero when a purely relative tolerance (zero absolute tolerance) was selected for that component. t=value, yI=value for component I=value.
ifail=18
The error test failed repeatedly with h=hmin. t=value. Stepsize h=value.
ifail=19
The corrector repeatedly failed to converge with h=hmin. t=value. Stepsize h=value.
ifail=20
The iteration matrix is singular. t=value. Stepsize h=value.
ifail=21
The corrector could not converge and the error test failed repeatedly. t=value. Stepsize h=value.
ifail=22
ires was set to -1 during a call to res and could not be resolved. t=value. Stepsize h=value.
ifail=23
ires was set to -2 during a call to res. t=value. Stepsize =value.
ifail=24
The initial ydot could not be computed. t=value. Stepsize h=value.
ifail=25
Repeated occurrences of input constraint violations have been detected. This could result in a potential infinite loop: itask=value. Current violation corresponds to exit with ifail=value.
ifail=-99
An unexpected error has been triggered by this routine. Please contact NAG.
See Section 3.9 in How to Use the NAG Library and its Documentation for further information.
ifail=-399
Your licence key may have expired or may not have been installed correctly.
See Section 3.8 in How to Use the NAG Library and its Documentation for further information.
ifail=-999
Dynamic memory allocation failed.
See Section 3.7 in How to Use the NAG Library and its Documentation for further information.

7
Accuracy

The accuracy of the numerical solution may be controlled by a careful choice of the arguments rtol and atol. You are advised to use scalar error control unless the components of the solution are expected to be poorly scaled. For the type of decaying solution typical of many stiff problems, relative error control with a small absolute error threshold will be most appropriate (that is, you are advised to choose itol=0 with atol1 small but positive).

8
Parallelism and Performance

d02nef is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
d02nef makes calls to BLAS and/or LAPACK routines, which may be threaded within the vendor library used by this implementation. Consult the documentation for the vendor library for further information.
Please consult the X06 Chapter Introduction for information on how to control and interrogate the OpenMP environment used within this routine. Please also consult the Users' Note for your implementation for any additional implementation-specific information.

9
Further Comments

The cost of computing a solution depends critically on the size of the differential system and to a lesser extent on the degree of stiffness of the problem. For banded systems the cost is proportional to neq× ml+ mu+1 2 , while for full systems the cost is proportional to neq3. Note however that for moderately sized problems which are only mildly nonlinear the cost may be dominated by factors proportional to neq×ml+mu+1 and neq2 respectively.

10
Example

For this routine two examples are presented. There is a single example program for d02nef, with a main program and the code to solve the two example problems given in Example 1 (EX1) and Example 2 (EX2).
Example 1 (EX1)
This example solves the well-known stiff Robertson problem written in implicit form
r1 = -0.04a + 1.0E4bc - a r2 = 0.04a - 1.0E4bc - 3.0E7b2 - b r3 = 3.0E7b2 - c  
with initial conditions a=1.0 and b=c=0.0 over the range 0,0.1 the BDF method (setup routine d02mwf and d02npf).
Example 2 (EX2)
This example illustrates the use of d02nef to solve a simple algebraic problem by continuation. The equation 4-2y+0.1eyt=0 from t=0 (where y=2) to t=1.

10.1
Program Text

Program Text (d02nefe.f90)

10.2
Program Data

Program Data (d02nefe.d)

10.3
Program Results

Program Results (d02nefe.r)

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