Integer type:  int32  int64  nag_int  show int32  show int32  show int64  show int64  show nag_int  show nag_int

Chapter Contents
Chapter Introduction
NAG Toolbox

# NAG Toolbox: nag_ode_withdraw_ivp_rk_setup (d02pv)

## Purpose

nag_ode_ivp_rk_setup (d02pv) is a setup function which must be called prior to the first call of either of the integration functions nag_ode_ivp_rk_range (d02pc) and nag_ode_ivp_rk_onestep (d02pd).
Note: this function is scheduled to be withdrawn, please see d02pv in Advice on Replacement Calls for Withdrawn/Superseded Routines..

## Syntax

[work, ifail] = d02pv(tstart, ystart, tend, tol, thres, method, task, errass, lenwrk, 'neq', neq, 'hstart', hstart)
[work, ifail] = nag_ode_withdraw_ivp_rk_setup(tstart, ystart, tend, tol, thres, method, task, errass, lenwrk, 'neq', neq, 'hstart', hstart)

## Description

nag_ode_ivp_rk_setup (d02pv) and its associated functions (nag_ode_ivp_rk_range (d02pc), nag_ode_ivp_rk_onestep (d02pd), nag_ode_ivp_rk_reset_tend (d02pw), nag_ode_ivp_rk_interp (d02px), nag_ode_ivp_rk_diag (d02py) and nag_ode_ivp_rk_errass (d02pz)) solve the initial value problem for a first-order system of ordinary differential equations. The functions, based on Runge–Kutta methods and derived from RKSUITE (see Brankin et al. (1991)), integrate
 $y′=ft,y given yt0=y0$
where $y$ is the vector of $n$ solution components and $t$ is the independent variable.
The integration proceeds by steps from the initial point ${t}_{0}$ towards the final point ${t}_{f}$. An approximate solution $y$ is computed at each step. For each component ${y}_{\mathit{i}}$, for $\mathit{i}=1,2,\dots ,n$, the error made in the step, i.e., the local error, is estimated. The step size is chosen automatically so that the integration will proceed efficiently while keeping this local error estimate smaller than a tolerance that you specify by means of arguments tol and thres.
nag_ode_ivp_rk_range (d02pc) can be used to solve the ‘usual task’, namely integrating the system of differential equations to obtain answers at points you specify. nag_ode_ivp_rk_onestep (d02pd) is used for all more ‘complicated tasks’.
You should consider carefully how you want the local error to be controlled. Essentially the code uses relative local error control, with tol being the desired relative accuracy. For reliable computation, the code must work with approximate solutions that have some correct digits, so there is an upper bound on the value you can specify for tol. It is impossible to compute a numerical solution that is more accurate than the correctly rounded value of the true solution, so you are not allowed to specify tol too small for the precision you are using. The magnitude of the local error in ${y}_{i}$ on any step will not be greater than ${\mathbf{tol}}×\mathrm{max}\phantom{\rule{0.125em}{0ex}}\left({\mu }_{i},{\mathbf{thres}}\left(i\right)\right)$ where ${\mu }_{i}$ is an average magnitude of ${y}_{i}$ over the step. If ${\mathbf{thres}}\left(i\right)$ is smaller than the current value of ${\mu }_{i}$, this is a relative error test and tol indicates how many significant digits you want in ${y}_{i}$. If ${\mathbf{thres}}\left(i\right)$ is larger than the current value of ${\mu }_{i}$, this is an absolute error test with tolerance ${\mathbf{tol}}×{\mathbf{thres}}\left(i\right)$. Relative error control is the recommended mode of operation, but pure relative error control, ${\mathbf{thres}}\left(i\right)=0.0$, is not permitted. See Further Comments for further information about error control.
nag_ode_ivp_rk_range (d02pc) and nag_ode_ivp_rk_onestep (d02pd) control local error rather than the true (global) error, the difference between the numerical and true solution. Control of the local error controls the true error indirectly. Roughly speaking, the code produces a solution that satisfies the differential equation with a discrepancy bounded in magnitude by the error tolerance. What this implies about how close the numerical solution is to the true solution depends on the stability of the problem. Most practical problems are at least moderately stable, and the true error is then comparable to the error tolerance. To judge the accuracy of the numerical solution, you could reduce tol substantially, e.g., use $0.1×{\mathbf{tol}}$, and solve the problem again. This will usually result in a rather more accurate solution, and the true error of the first integration can be estimated by comparison. Alternatively, a global error assessment can be computed automatically using the argument errass. Because indirect control of the true error by controlling the local error is generally satisfactory and because both ways of assessing true errors cost twice, or more, the cost of the integration itself, such assessments are used mostly for spot checks, selecting appropriate tolerances for local error control, and exploratory computations.
nag_ode_ivp_rk_range (d02pc) and nag_ode_ivp_rk_onestep (d02pd) each implement three Runge–Kutta formula pairs, and you must select one for the integration. The best choice for method depends on the problem. The order of accuracy is $3$, $5$ and $8$ respectively. As a rule, the smaller tol is, the larger you should take the value of method. If the components thres are small enough that you are effectively specifying relative error control, experience suggests
 tol efficient method ${10}^{-2}-{10}^{-4}$ 1 ${10}^{-3}-{10}^{-6}$ 2 ${10}^{-5}-$ 3
The overlap in the ranges of tolerances appropriate for a given method merely reflects the dependence of efficiency on the problem being solved. Making tol smaller will normally make the integration more expensive. However, in the range of tolerances appropriate to a method, the increase in cost is modest. There are situations for which one method, or even this kind of code, is a poor choice. You should not specify a very small value for ${\mathbf{thres}}\left(i\right)$, when the $i$th solution component might vanish. In particular, you should not do this when ${y}_{i}=0.0$. If you do, the code will have to work hard with any value for method to compute significant digits, but ${\mathbf{method}}=1$ is a particularly poor choice in this situation. All three methods are inefficient when the problem is ‘stiff’. If it is only mildly stiff, you can solve it with acceptable efficiency with ${\mathbf{method}}=1$, but if it is moderately or very stiff, a code designed specifically for such problems will be much more efficient. The higher the order, i.e., the larger the value of method, the more smoothness is required of the solution in order for the method to be efficient.
When assessment of the true (global) error is requested, this error assessment is updated at each step. Its value can be obtained at any time by a call to nag_ode_ivp_rk_errass (d02pz). The code monitors the computation of the global error assessment and reports any doubts it has about the reliability of the results. The assessment scheme requires some smoothness of $f\left(t,y\right)$, and it can be deceived if $f$ is insufficiently smooth. At very crude tolerances the numerical solution can become so inaccurate that it is impossible to continue assessing the accuracy reliably. At very stringent tolerances the effects of finite precision arithmetic can make it impossible to assess the accuracy reliably. The cost of this is roughly twice the cost of the integration itself with ${\mathbf{method}}=2$ or $3$, and three times with ${\mathbf{method}}=1$.
The first step of the integration is critical because it sets the scale of the problem. The integrator will find a starting step size automatically if you set the argument hstart to $0.0$. Automatic selection of the first step is so effective that you should normally use it. Nevertheless, you might want to specify a trial value for the first step to be certain that the code recognizes the scale on which phenomena occur near the initial point. Also, automatic computation of the first step size involves some cost, so supplying a good value for this step size will result in a less expensive start. If you are confident that you have a good value, provide it via the argument hstart.

## References

Brankin R W, Gladwell I and Shampine L F (1991) RKSUITE: A suite of Runge–Kutta codes for the initial value problems for ODEs SoftReport 91-S1 Southern Methodist University

## Parameters

### Compulsory Input Parameters

1:     $\mathrm{tstart}$ – double scalar
The initial value of the independent variable, ${t}_{0}$.
2:     $\mathrm{ystart}\left({\mathbf{neq}}\right)$ – double array
${y}_{0}$, the initial values of the solution, ${y}_{\mathit{i}}$, for $\mathit{i}=1,2,\dots ,n$.
3:     $\mathrm{tend}$ – double scalar
The final value of the independent variable, ${t}_{f}$, at which the solution is required. tstart and tend together determine the direction of integration.
Constraint: ${\mathbf{tend}}$ must be distinguishable from tstart for the method and the precision of the machine being used.
4:     $\mathrm{tol}$ – double scalar
A relative error tolerance.
Constraint: .
5:     $\mathrm{thres}\left({\mathbf{neq}}\right)$ – double array
A vector of thresholds.
Constraint: ${\mathbf{thres}}\left(i\right)\ge \sqrt{\sigma }$, where $\sigma$ is approximately the smallest possible machine number that can be reciprocated without overflow (see nag_machine_real_safe (x02am)).
6:     $\mathrm{method}$int64int32nag_int scalar
The Runge–Kutta method to be used.
${\mathbf{method}}=1$
A $2\left(3\right)$ pair is used.
${\mathbf{method}}=2$
A $4\left(5\right)$ pair is used.
${\mathbf{method}}=3$
A $7\left(8\right)$ pair is used.
Constraint: ${\mathbf{method}}=1$, $2$ or $3$.
7:     $\mathrm{task}$ – string (length ≥ 1)
Determines whether the usual integration task is to be performed using nag_ode_ivp_rk_range (d02pc) or a more complicated task is to be performed using nag_ode_ivp_rk_onestep (d02pd).
${\mathbf{task}}=\text{'U'}$
nag_ode_ivp_rk_range (d02pc) is to be used for the integration.
${\mathbf{task}}=\text{'C'}$
nag_ode_ivp_rk_onestep (d02pd) is to be used for the integration.
Constraint: ${\mathbf{task}}=\text{'U'}$ or $\text{'C'}$.
8:     $\mathrm{errass}$ – logical scalar
Specifies whether a global error assessment is to be computed with the main integration. ${\mathbf{errass}}=\mathit{true}$ specifies that it is.
Constraint: ${\mathbf{errass}}=\mathit{true}$ or $\mathit{false}$.
9:     $\mathrm{lenwrk}$int64int32nag_int scalar
The dimension of the array work. (${\mathbf{lenwrk}}\ge 32×{\mathbf{neq}}$ is always sufficient.)
Constraints:
• if ${\mathbf{task}}=\text{'U'}$ and ${\mathbf{errass}}=\mathit{false}$,
• if ${\mathbf{method}}=1$, ${\mathbf{lenwrk}}\ge 10×{\mathbf{neq}}$;
• if ${\mathbf{method}}=2$, ${\mathbf{lenwrk}}\ge 20×{\mathbf{neq}}$;
• if ${\mathbf{method}}=3$, ${\mathbf{lenwrk}}\ge 16×{\mathbf{neq}}$;
• if ${\mathbf{task}}=\text{'U'}$ and ${\mathbf{errass}}=\mathit{true}$,
• if ${\mathbf{method}}=1$, ${\mathbf{lenwrk}}\ge 17×{\mathbf{neq}}$;
• if ${\mathbf{method}}=2$, ${\mathbf{lenwrk}}\ge 32×{\mathbf{neq}}$;
• if ${\mathbf{method}}=3$, ${\mathbf{lenwrk}}\ge 21×{\mathbf{neq}}$;
• if ${\mathbf{task}}=\text{'C'}$ and ${\mathbf{errass}}=\mathit{false}$,
• if ${\mathbf{method}}=1$, ${\mathbf{lenwrk}}\ge 10×{\mathbf{neq}}$;
• if ${\mathbf{method}}=2$, ${\mathbf{lenwrk}}\ge 14×{\mathbf{neq}}$;
• if ${\mathbf{method}}=3$, ${\mathbf{lenwrk}}\ge 16×{\mathbf{neq}}$;
• if ${\mathbf{task}}=\text{'C'}$ and ${\mathbf{errass}}=\mathit{true}$,
• if ${\mathbf{method}}=1$, ${\mathbf{lenwrk}}\ge 15×{\mathbf{neq}}$;
• if ${\mathbf{method}}=2$, ${\mathbf{lenwrk}}\ge 26×{\mathbf{neq}}$;
• if ${\mathbf{method}}=3$, ${\mathbf{lenwrk}}\ge 21×{\mathbf{neq}}$.

### Optional Input Parameters

1:     $\mathrm{neq}$int64int32nag_int scalar
Default: the dimension of the arrays ystart, thres. (An error is raised if these dimensions are not equal.)
$n$, the number of ordinary differential equations in the system to be solved by the integration function.
Constraint: ${\mathbf{neq}}\ge 1$.
2:     $\mathrm{hstart}$ – double scalar
Default: $0.0$
A value for the size of the first step in the integration to be attempted. The absolute value of hstart is used with the direction being determined by tstart and tend. The actual first step taken by the integrator may be different to hstart if the underlying algorithm determines that hstart is unsuitable. If ${\mathbf{hstart}}=0.0$ then the size of the first step is computed automatically.

### Output Parameters

1:     $\mathrm{work}\left({\mathbf{lenwrk}}\right)$ – double array
Contains information for use by nag_ode_ivp_rk_range (d02pc) or nag_ode_ivp_rk_onestep (d02pd). This must be the same array as supplied to nag_ode_ivp_rk_range (d02pc) or nag_ode_ivp_rk_onestep (d02pd). The contents of this array must remain unchanged between calls.
2:     $\mathrm{ifail}$int64int32nag_int scalar
${\mathbf{ifail}}={\mathbf{0}}$ unless the function detects an error (see Error Indicators and Warnings).

## Error Indicators and Warnings

Errors or warnings detected by the function:
${\mathbf{ifail}}=1$
 On entry, ${\mathbf{neq}}<1$, or tend is too close to tstart, or ${\mathbf{tol}}>0.01$ or , or ${\mathbf{thres}}\left(i\right)<\sqrt{\sigma }$, where $\sigma$ is approximately the smallest possible machine number that can be reciprocated without overflow (see nag_machine_real_safe (x02am)), or ${\mathbf{method}}\ne 1$, $2$ or $3$, or ${\mathbf{task}}\ne \text{'U'}$ or $\text{'C'}$, or lenwrk is too small.
${\mathbf{ifail}}=-99$
${\mathbf{ifail}}=-399$
Your licence key may have expired or may not have been installed correctly.
${\mathbf{ifail}}=-999$
Dynamic memory allocation failed.

## Accuracy

Not applicable.

If ${\mathbf{task}}=\text{'C'}$ then the value of the argument tend may be reset during the integration without the overhead associated with a complete restart; this can be achieved by a call to nag_ode_ivp_rk_reset_tend (d02pw).
It is often the case that a solution component ${y}_{i}$ is of no interest when it is smaller in magnitude than a certain threshold. You can inform the code of this by setting ${\mathbf{thres}}\left(i\right)$ to this threshold. In this way you avoid the cost of computing significant digits in ${y}_{i}$ when only the fact that it is smaller than the threshold is of interest. This matter is important when ${y}_{i}$ vanishes, and in particular, when the initial value ${\mathbf{ystart}}\left(i\right)$ vanishes. An appropriate threshold depends on the general size of ${y}_{i}$ in the course of the integration. Physical reasoning may help you select suitable threshold values. If you do not know what to expect of $y$, you can find out by a preliminary integration using nag_ode_ivp_rk_range (d02pc) with nominal values of thres. As nag_ode_ivp_rk_range (d02pc) steps from ${t}_{0}$ towards ${t}_{f}$ for each $i=1,2,\dots ,n$ it forms ${\mathbf{ymax}}\left(i\right)$, the largest magnitude of ${y}_{i}$ computed at any step in the integration so far. Using this you can determine more appropriate values for thres for an accurate integration. You might, for example, take ${\mathbf{thres}}\left(i\right)$ to be  times the final value of ${\mathbf{ymax}}\left(i\right)$.

## Example

function d02pv_example

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

t      = 0;
y      = [0; 1];
tend   = 2*pi;
tol    = 0.001;
thres  = [1e-08; 1e-08];
method = int64(1);
errass = false;
neq    = int64(2);
lenwrk = int64(32*neq);
[work, ifail] = d02pv(t, y, tend, tol, thres, method, task, errass, lenwrk);
twant  = pi/4;
ymax   = y;
[t, y, yp, ymax, work, ifail] = d02pc(@f, neq, twant, y, ymax, work);

fprintf('Solution y and derivative y'' at t = %7.4f is:\n',t);
fprintf('\n %10s %10s\n','y','y''');
for i=1:neq
fprintf(' %10.4f %10.4f\n',y(i),yp(i));
end

function [yp] = f(t, y)
% Evaluate derivative vector.
yp = zeros(2, 1);
yp(1) =  y(2);
yp(2) = -y(1);
d02pv example results

Solution y and derivative y' at t =  0.7854 is:

y         y'
0.7069     0.7058
0.7068    -0.7084