d02kef finds a specified eigenvalue of a regular or singular second-order Sturm–Liouville system on a finite or infinite interval, using a Pruefer transformation and a shooting method. It also reports values of the eigenfunction and its derivatives. Provision is made for discontinuities in the coefficient functions or their derivatives.
The routine may be called by the names d02kef or nagf_ode_sl2_breaks_funs.
d02kef has essentially the same purpose as d02kdf with minor modifications to enable values of the eigenfunction to be obtained after convergence to the eigenvalue has been achieved.
It first finds a specified eigenvalue of a Sturm–Liouville system defined by a self-adjoint differential equation of the second-order
together with appropriate boundary conditions at the two, finite or infinite, end points and . The functions and , which are real-valued, are defined by coeffn. The boundary conditions must be defined by bdyval, and, in the case of a singularity at or , take the form of an asymptotic formula for the solution near the relevant end point.
When the final estimate of the eigenvalue has been found, the routine integrates the differential equation once more with that value of , and with initial conditions chosen so that the integral
is approximately one. When is of the form , which is the most common case, represents the square of the norm of induced by the inner product
with respect to which the eigenfunctions are mutually orthogonal. This normalization of is only approximate, but experience shows that generally differs from unity by only one or two per cent.
During this final integration the report is called at each integration mesh point . Sufficient information is returned to permit you to compute and for printing or plotting. For reasons described in Section 9.2, d02kef passes across to report, not and , but the Pruefer variables , and on which the numerical method is based. Their relationship to and is given by the equations
For the theoretical basis of the numerical method to be valid, the following conditions should hold on the coefficient functions:
(a) must be nonzero and must not change sign throughout the interval ; and,
(b) must not change sign throughout the interval for all relevant values of , and must not be identically zero as varies, for any .
Points of discontinuity in the functions and or their derivatives are allowed, and should be included as ‘break-points’ in the array xpoint.
A good account of the theory of Sturm–Liouville systems, with some description of Pruefer transformations, is given in Chapter X of Birkhoff and Rota (1962). An introduction to the use of Pruefer transformations for the numerical solution of eigenvalue problems arising from physics and chemistry is given in Bailey (1966).
Abramowitz M and Stegun I A (1972) Handbook of Mathematical Functions (3rd Edition) Dover Publications
Bailey P B (1966) Sturm–Liouville eigenvalues via a phase function SIAM J. Appl. Math. 14 242–249
Banks D O and Kurowski I (1968) Computation of eigenvalues of singular Sturm–Liouville Systems Math. Comput.22 304–310
Birkhoff G and Rota G C (1962) Ordinary Differential Equations Ginn & Co., Boston and New York
Pryce J D (1981) Two codes for Sturm–Liouville problems Technical Report CS-81-01 Department of Computer Science, Bristol University
Pryce J D and Hargrave B A (1977) The scaled Prüfer method for one-parameter and multi-parameter eigenvalue problems in ODEs IMA Numerical Analysis Newsletter1(3)
1: – Real (Kind=nag_wp) arrayInput
On entry: the points where the boundary conditions computed by bdyval are to be imposed, and also any break-points, i.e., to must contain values such that
with the following meanings:
(a) and are the left- and right-hand end points, and , of the domain of definition of the Sturm–Liouville system if these are finite. If either or is infinite, the corresponding value or may be a more-or-less arbitrarily ‘large’ number of appropriate sign.
(b) and are the Boundary Matching Points (BMPs), that is the points at which the left and right boundary conditions computed in bdyval are imposed.
If the left-hand end point is a regular point then you should set , while if it is a singular point you must set . Similarly () if the right-hand end point is regular, and if it is singular.
(c)The remaining points , if any, define ‘break-points’ which divide the interval into sub-intervals
Numerical integration of the differential equation is stopped and restarted at each break-point. In simple cases no break-points are needed. However, if or are given by different formulae in different parts of the interval, integration is more efficient if the range is broken up by break-points in the appropriate way. Similarly points where any jumps occur in or , or in their derivatives up to the fifth-order, should appear as break-points.
Examples are given in
xpoint determines the position of the Shooting Matching Point (SMP), as explained in Section 9.3.
2: – IntegerInput
On entry: the number of points in the array xpoint.
3: – IntegerInput/Output
On entry: must be set to the index of the ‘break-point’ to be used as the matching point (see Section 9.3). If match is set to a value outside the range then a default value is taken, corresponding to the break-point nearest the centre of the interval .
On exit: the index of the break-point actually used as the matching point.
4: – Subroutine, supplied by the user.External Procedure
coeffn must compute the values of the coefficient functions and for given values of and . Section 3 states the conditions which and must satisfy. See Section 9.4 for examples.
On exit: the value of for the current value of and the current trial value of .
3: – Real (Kind=nag_wp)Output
On exit: the value of for the current value of and the current trial value of . However dqdl is only used in error estimation and, in the rare cases where it may be difficult to evaluate, an approximation (say to within ) will suffice.
4: – Real (Kind=nag_wp)Input
On entry: the current value of .
5: – Real (Kind=nag_wp)Input
On entry: the current trial value of the eigenvalue argument .
6: – IntegerInput
On entry: the index of the sub-interval (see specification of xpoint) in which lies.
coeffn must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02kef is called. Arguments denoted as Input must not be changed by this procedure.
Note:coeffn should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02kef. If your code inadvertently does return any NaNs or infinities, d02kef is likely to produce unexpected results.
5: – Subroutine, supplied by the user.External Procedure
bdyval must define the boundary conditions. For each end point, bdyval must return (in yl or yr) values of and which are consistent with the boundary conditions at the end points; only the ratio of the values matters. Here is a given point (xl or xr) equal to, or close to, the end point.
For a regular end point (, say), , a boundary condition of the form
can be handled by returning constant values in yl, e.g., and .
For a singular end point however, and will in general be functions of xl and elam, and and functions of xr and elam, usually derived analytically from a power-series or asymptotic expansion. Examples are given in Section 9.5.
On entry: if is a regular end point of the system (so that ), xl contains . If is a singular point (so that ), xl contains a point such that .
2: – Real (Kind=nag_wp)Input
On entry: if is a regular end point of the system (so that ), xr contains . If is a singular point (so that ), xr contains a point such that .
3: – Real (Kind=nag_wp)Input
On entry: the current trial value of .
4: – Real (Kind=nag_wp) arrayOutput
On exit: and should contain values of and respectively (not both zero) which are consistent with the boundary condition at the left-hand end point, given by . should not be set.
5: – Real (Kind=nag_wp) arrayOutput
On exit: and should contain values of and respectively (not both zero) which are consistent with the boundary condition at the right-hand end point, given by . should not be set.
bdyval must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02kef is called. Arguments denoted as Input must not be changed by this procedure.
Note:bdyval should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02kef. If your code inadvertently does return any NaNs or infinities, d02kef is likely to produce unexpected results.
6: – IntegerInput
On entry: , the index of the required eigenvalue when the eigenvalues are ordered
7: – Real (Kind=nag_wp)Input
On entry: the tolerance argument which determines the accuracy of the computed eigenvalue. The error estimate held in delam on exit satisfies the mixed absolute/relative error test
where elam is the final estimate of the eigenvalue. delam is usually somewhat smaller than the right-hand side of (1) but not several orders of magnitude smaller.
8: – Real (Kind=nag_wp)Input/Output
On entry: an initial estimate of the eigenvalue .
On exit: the final computed estimate, whether or not an error occurred.
9: – Real (Kind=nag_wp)Input/Output
On entry: an indication of the scale of the problem in the -direction. delam holds the initial ‘search step’ (positive or negative). Its value is not critical, but the first two trial evaluations are made at elam and , so the routine will work most efficiently if the eigenvalue lies between these values. A reasonable choice (if a closer bound is not known) is half the distance between adjacent eigenvalues in the neighbourhood of the one sought. In practice, there will often be a problem, similar to the one in hand but with known eigenvalues, which will help one to choose initial values for elam and delam.
If on entry, it is given the default value of .
On exit: if , delam holds an estimate of the absolute error in the computed eigenvalue, that is . (In Section 9.2 we discuss the assumptions under which this is true.) The true error is rarely more than twice, or less than a tenth, of the estimated error.
If , delam may hold an estimate of the error, or its initial value, depending on the value of ifail. See Section 6 for further details.
10: – Real (Kind=nag_wp) arrayInput/Output
On entry: should contain a maximum step size to be used by the differential equation code in the th sub-interval (as described in the specification of argument xpoint), for . If it is zero the routine generates a maximum step size internally.
It is recommended that be set to zero unless the coefficient functions and have features (such as a narrow peak) within the th sub-interval that could be ‘missed’ if a long step were taken. In such a case should be set to about half the distance over which the feature should be observed. Too small a value will increase the computing time for the routine. See Section 9 for further suggestions.
The rest of the array is used as workspace.
On exit: and contain the sensitivity coefficients , described in Section 9.6. Other entries contain diagnostic output in the case of an error exit (see Section 6).
11: – IntegerInput/Output
On entry: a bound on , the number of root-finding iterations allowed, that is the number of trial values of that are used. If , no such bound is assumed. (See also maxfun.)
On exit: will have been decreased by the number of iterations actually performed, whether or not it was positive on entry.
12: – IntegerInput
On entry: a bound on , the number of calls to coeffn made in any one root-finding iteration. If , no such bound is assumed.
maxfun and maxit may be used to limit the computational cost of a call to d02kef, which is roughly proportional to .
13: – Subroutine, supplied by the NAG Library or the user.External Procedure
monit is called by d02kef at the end of each root-finding iteration and allows you to monitor the course of the computation by printing out the arguments.
If no monitoring is required, the dummy (sub)program d02kay may be used. (d02kay is included in the NAG Library.)
On entry: the current value of the argument maxit of d02kef, this is decreased by one at each iteration.
2: – IntegerInput
On entry: describes what phase the computation is in.
An error occurred in the computation at this iteration; an error exit from d02kef with will follow.
The routine is trying to bracket the eigenvalue .
The routine is converging to the eigenvalue (having already bracketed it).
3: – Real (Kind=nag_wp)Input
On entry: the current trial value of .
4: – Real (Kind=nag_wp) arrayInput
On entry: information about the behaviour of the shooting method, and diagnostic information in the case of errors. It should not normally be printed in full if no error has occurred (that is, if ), though the first few components may be of interest to you. In case of an error () all the components of finfo should be printed.
The current value of the ‘miss-distance’ or ‘residual’ function on which the shooting method is based. (See Section 9.2 for further information.) is set to zero if .
An estimate of the quantity defined as follows. Consider the perturbation in the miss-distance that would result if the local error in the solution of the differential equation were always positive and equal to its maximum permitted value. Then is the perturbation in that would have the same effect on . Thus, at the zero of is an approximate bound on the perturbation of the zero (that is the eigenvalue) caused by errors in numerical solution. If is very large then it is possible that there has been a programming error in coeffn such that is independent of . If this is the case, an error exit with should follow. is set to zero if .
The number of internal iterations, using the same value of and tighter accuracy tolerances, needed to bring the accuracy (that is, the value of ) to an acceptable value. Its value should normally be , and should almost never exceed .
On entry: the current value of the independent variable . See Section 9.3 for the order in which values of are supplied.
2: – Real (Kind=nag_wp) arrayInput
On entry: , , hold the current values of the Pruefer variables , , respectively.
3: – IntegerInput
On entry: indicates the sub-interval between break-points in which x lies exactly as for coeffn, except that at the extreme left-hand end point (when ) jint is set to and at the extreme right-hand end point (when ) jint is set to .
report must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02kef is called. Arguments denoted as Input must not be changed by this procedure.
15: – IntegerInput/Output
On entry: ifail must be set to , or to set behaviour on detection of an error; these values have no effect when no error is detected.
A value of causes the printing of an error message and program execution will be halted; otherwise program execution continues. A value of means that an error message is printed while a value of means that it is not.
If halting is not appropriate, the value or is recommended. If message printing is undesirable, then the value is recommended. Otherwise, the value is recommended. When the value or is used it is essential to test the value of ifail on exit.
On exit: unless the routine detects an error or a warning has been flagged (see Section 6).
6Error Indicators and Warnings
If on entry or , explanatory error messages are output on the current error message unit (as defined by x04aaf).
Errors or warnings detected by the routine:
Note: error exits with , , , or are caused by being unable to set up or solve the differential equation at some iteration and will be immediately preceded by a call of monit giving diagnostic information. For other errors, diagnostic information is contained in
, for , where appropriate.
On entry, .
On entry, .
On entry, .
On entry, the sequence of boundary and break points is not monotonic.
For , point and point .
The constraint on the specification of left- or right-hand boundary condition has been violated.
At some call to bdyval, invalid values were returned, that is, either , or (a programming error in bdyval). See the last call of monit for details.This error exit will also occur if is zero at the point where the boundary condition is imposed. Probably bdyval was called with xl equal to a singular end point or with xr equal to a singular end point .
The function became zero or changed sign in the interval .
After iterations the eigenvalue had not been found to the required accuracy.
The bracketing phase failed to bracket the eigenvalue within ten iterations. This may be due to an error in formulating the problem (for example, is independent of ), or by very poor initial estimates for the eigenvalue and search step.
On exit, and give the end points of the interval within which no eigenvalue was located by the routine.
The last iteration was terminated because more than calls to evaluate , and its derivative were performed.
Too small a step size was required at the start of a sub-interval to obtain the desired accuracy.
Too small a step size was required during solution in a sub-interval to obtain the desired accuracy.
At some point inside a sub-interval the step size in the differential equation solver was reduced to a value too small to make significant progress (for the same reasons as with ). This could be due to pathological behaviour of and or to an unreasonable accuracy requirement or to the current value of making the equations ‘stiff’. See the last call of monit for details.
The tolerance set is too small for the problem being solved and the machine precision being used. The local eigenvalue estimate returned is likely to be a very good approximation.
An internal error has occurred corresponding to a pole of the matching function. Try solving the problem again with a smaller tolerance.
An unexpected error has been triggered by this routine. Please
See Section 7 in the Introduction to the NAG Library FL Interface for further information.
Your licence key may have expired or may not have been installed correctly.
See Section 8 in the Introduction to the NAG Library FL Interface for further information.
Dynamic memory allocation failed.
See Section 9 in the Introduction to the NAG Library FL Interface for further information.
Background information to multithreading can be found in the Multithreading documentation.
d02kef is not threaded in any implementation.
The time taken by d02kef depends on the complexity of the coefficient functions, whether they or their derivatives are rapidly changing, the tolerance demanded, and how many iterations are needed to obtain convergence. The amount of work per iteration is roughly doubled when tol is divided by . To make the most economical use of the routine, one should try to obtain good initial values for elam and delam, and, where appropriate, good asymptotic formulae. Also the boundary matching points should not be set unnecessarily close to singular points. The extra time needed to compute the eigenfunction is principally the cost of one additional integration once the eigenvalue has been found.
9.2General Description of the Algorithm
A shooting method, for differential equation problems containing unknown parameters, relies on the construction of a ‘miss-distance function’, which for given trial values of the parameters measures how far the conditions of the problem are from being met. The problem is then reduced to one of finding the values of the parameters for which the miss-distance function is zero, that is to a root-finding process. Shooting methods differ mainly in how the miss-distance is defined.
d02kef defines a miss-distance based on the rotation about the origin of the point in the Phase Plane as the solution proceeds from to . The boundary conditions define the ray (i.e., two-sided line through the origin) on which should start, and the ray on which it should finish. The eigenvalue defines the total number of half-turns it should make. Numerical solution is actually done by ‘shooting forward’ from and ‘shooting backward’ from to a matching point . Then is taken as the angle between the rays to the two resulting points and . A relative scaling of the and axes, based on the behaviour of the coefficient functions and , is used to improve the numerical behaviour.
The resulting function is monotonic over , increasing if and decreasing if , with a unique zero at the desired eigenvalue . The routine measures in units of a half-turn. This means that as increases, varies by about as each eigenvalue is passed. (This feature implies that the values of at successive iterations – especially in the early stages of the iterative process – can be used with suitable extrapolation or interpolation to help the choice of initial estimates for eigenvalues near to the one currently being found.)
The routine actually computes a value for with errors, arising from the local errors of the differential equation code and from the asymptotic formulae provided by you if singular points are involved. However, the error estimate output in delam is usually fairly realistic, in that the actual error is within an order of magnitude of delam.
We pass the values of , , across through report rather than converting them to values of , inside d02kef, for the following reasons. First, there may be cases where auxiliary quantities can be more accurately computed from the Pruefer variables than from and . Second, in singular problems on an infinite interval and may underflow towards the end of the range, whereas the Pruefer variables remain well-behaved. Third, with high-order eigenvalues (and, therefore, highly oscillatory eigenfunctions) the eigenfunction may have a complete oscillation (or more than one oscillation) between two mesh points, so that values of and at mesh points give a very poor representation of the curve. The probable behaviour of the Pruefer variables in this case is that and vary slowly whilst increases quickly: for all three Pruefer variables linear interpolation between the values at adjacent mesh points is probably sufficiently accurate to yield acceptable intermediate values of , , (and hence of ) for graphical purposes.
Similar considerations apply to the exponentially decaying ‘tails’ of the eigenfunctions that often occur in singular problems. Here has approximately constant value whilst increases rapidly in the direction of integration, though the step length is generally fairly small over such a range.
If the solution is output through report at values which are too widely spaced, the step length can be controlled by choosing hmax suitably, or, preferably, by reducing tol. Both these choices will lead to more accurate eigenvalues and eigenfunctions but at some computational cost.
9.3The Position of the Shooting Matching Point
This point is always one of the values in array xpoint. It may be specified using the argument match. The default value is chosen to be the value of that , , that lies closest to the middle of the interval . If there is a tie, the rightmost candidate is chosen. In particular if there are no break-points, then (); that is, the shooting is from left to right in this case. A break-point may be inserted purely to move to an interior point of the interval, even though the form of the equations does not require it. This often speeds up convergence especially with singular problems.
Note that the shooting method used by the code integrates first from the left-hand end , then from the right-hand end , to meet at the matching point in the middle. This will of course be reflected in printed or graphical output. The diagram shows a possible sequence of nine mesh points through in the order in which they appear, assuming there are just two sub-intervals (so ).
Since the shooting method usually fails to match up the two ‘legs’ of the curve exactly, there is bound to be a jump in , or in or both, at the matching point . The code in fact ‘shares’ the discrepancy out so that both and have a jump. A large jump does not imply an inaccurate eigenvalue, but implies either
(a)a badly chosen matching point: if has a ‘humped’ shape, should be chosen near the maximum value of , especially if is negative at the ends of the interval;
(b)an inherently ill-conditioned problem, typically one where another eigenvalue is pathologically close to the one being sought. In this case it is extremely difficult to obtain an accurate eigenfunction.
The choice of matching point is open. If we choose as in d02kdf example program we find that the exponentially increasing component of the solution dominates and we get extremely inaccurate values for the eigenfunction (though the eigenvalue is determined accurately). The values of the eigenfunction calculated with are given schematically in Figure 3.
If we choose as the maximum of the hump in (see item (a) above) we instead obtain the accurate results given in Figure 4
Coding coeffn is straightforward except when break-points are needed. The examples below show:
(a)a simple case,
(b)a case in which discontinuities in the coefficient functions or their derivatives necessitate break-points, and
(c)a case where break-points together with the hmax argument are an efficient way to deal with a coefficient function that is well-behaved except over one short interval.
The modified Bessel equation
Assuming the interval of solution does not contain the origin and dividing through by , we have and
. The code could be
p = x
q = elam*x - nu*nu/x
dqdl = x
NU (standing for ) is a real variable that might be defined in a DATA statement, or might be in user-declared COMMON so that its value could be set in the main program.
The Schroedinger equation
over some interval ‘approximating to ’, say . Here we need break-points at , forming three sub-intervals , , .
The code could be
If (jint.eq.2) Then
q = elam + x*x - 10.0E0
q = elam + 6.0E0/abs(x)
p = 1.0E0
dqdl = 1.0E0
The array xpoint would contain the values , , , , , and would be . The choice of appropriate values for and depends on the form of the asymptotic formula computed by bdyval and the technique is discussed in Section 9.5.
Here is nearly constant over the range except for a sharp inverted spike over approximately . There is a danger that the routine will build up to a large step size and ‘step over’ the spike without noticing it. By using break-points – say at – one can restrict the step size near the spike without impairing the efficiency elsewhere.
p = 1.0E0
dqdl = 1.0E0 - 2.0E0*exp(-100.0E0*x*x)
q = elam*dqdl
xpoint might contain , , , , , (assuming are regular points) and would be . , for , might contain , and .
9.5Examples of Boundary Conditions at Singular Points
Quoting from page 243 of Bailey (1966): ‘Usually ... the differential equation has two essentially different types of solution near a singular point, and the boundary condition there merely serves to distinguish one kind from the other. This is the case in all the standard examples of mathematical physics.’
In most cases the behaviour of the ratio near the point is quite different for the two types of solution. Essentially what you provide through the bdyval is an approximation to this ratio, valid as tends to the singular point (SP).
You must decide (a) how accurate to make this approximation or asymptotic formula, for example how many terms of a series to use, and (b) where to place the boundary matching point (BMP) at which the numerical solution of the differential equation takes over from the asymptotic formula. Taking the BMP closer to the SP will generally improve the accuracy of the asymptotic formula, but will make the computation more expensive as the Pruefer differential equations generally become progressively more ill-behaved as the SP is approached. You are strongly recommended to experiment with placing the BMPs. In many singular problems quite crude asymptotic formulae will do. To help you avoid needlessly accurate formulae, d02kef outputs two ‘sensitivity coefficients’
which estimate how much the errors at the BMPs affect the computed eigenvalue. They are described in detail in Section 9.6.
the boundary conditions being that should remain bounded as tends to and tends to .
At the end there is one solution that behaves like and another that behaves like . For the first of these solutions is asymptotically while for the second it is asymptotically . Thus the desired ratio is specified by setting
At the end the equation behaves like Airy's equation shifted through , i.e., like where , so again there are two types of solution. The solution we require behaves as
and the other as
Hence, the desired solution has so that we could set and
. The complete subroutine might thus be
Clearly for this problem it is essential that any value given by d02kef to xr is well to the right of the value of elam, so that you must vary the right-hand BMP with the eigenvalue index . One would expect to be near the th zero of the Airy function , so there is no problem estimating elam.
More accurate asymptotic formulae are easily found: near by the standard Frobenius method, and near by using standard asymptotics for , , (see page 448 of Abramowitz and Stegun (1972)).
For example, by the Frobenius method the solution near has the expansion
9.6The Sensitivity Parameters and
The sensitivity parameters , (held in and on output) estimate the effect of errors in the boundary conditions. For sufficiently small errors , in and respectively, the relations
are satisfied, where the subscripts , denote errors committed at the left- and right-hand BMPs respectively, and denotes the consequent error in the computed eigenvalue.
This is a pitfall to beware of at a singular point. If the BMP is chosen so far from the SP that a zero of the desired eigenfunction lies in between them, then the routine will fail to ‘notice’ this zero. Since the index of of an eigenvalue is the number of zeros of its eigenfunction, the result will be that
(a)the wrong eigenvalue will be computed for the given index – in fact some will be found where ;
(b)the same index can cause convergence to any of several eigenvalues depending on the initial values of elam and delam.
It is up to you to take suitable precautions – for instance by varying the position of the BMPs in the light of knowledge of the asymptotic behaviour of the eigenfunction at different eigenvalues.
This example finds the 11th eigenvalue and eigenfunction of the example of Section 9.5, using the simple asymptotic formulae for the boundary conditions.
Comparison of the results from this example program with the corresponding results from d02kdf example program shows that similar output is produced from monit, followed by the eigenfunction values from report, and then a further line of information from monit (corresponding to the integration to find the eigenfunction). Final information is printed within the example program exactly as with d02kdf.
Note the discrepancy at the matching point (, the maximum of , in this case) between the solutions obtained by integrations from left- and right-hand end points.