NAG FL Interface
d02tlf (bvp_​coll_​nlin_​solve)

Settings help

FL Name Style:


FL Specification Language:


1 Purpose

d02tlf solves a general two-point boundary value problem for a nonlinear mixed order system of ordinary differential equations.

2 Specification

Fortran Interface
Subroutine d02tlf ( ffun, fjac, gafun, gbfun, gajac, gbjac, guess, rcomm, icomm, iuser, ruser, ifail)
Integer, Intent (Inout) :: icomm(*), iuser(*), ifail
Real (Kind=nag_wp), Intent (Inout) :: rcomm(*), ruser(*)
External :: ffun, fjac, gafun, gbfun, gajac, gbjac, guess
C Header Interface
#include <nag.h>
void  d02tlf_ (
void (NAG_CALL *ffun)(const double *x, const double y[], const Integer *neq, const Integer m[], double f[], Integer iuser[], double ruser[]),
void (NAG_CALL *fjac)(const double *x, const double y[], const Integer *neq, const Integer m[], double dfdy[], Integer iuser[], double ruser[]),
void (NAG_CALL *gafun)(const double ya[], const Integer *neq, const Integer m[], const Integer *nlbc, double ga[], Integer iuser[], double ruser[]),
void (NAG_CALL *gbfun)(const double yb[], const Integer *neq, const Integer m[], const Integer *nrbc, double gb[], Integer iuser[], double ruser[]),
void (NAG_CALL *gajac)(const double ya[], const Integer *neq, const Integer m[], const Integer *nlbc, double dgady[], Integer iuser[], double ruser[]),
void (NAG_CALL *gbjac)(const double yb[], const Integer *neq, const Integer m[], const Integer *nrbc, double dgbdy[], Integer iuser[], double ruser[]),
void (NAG_CALL *guess)(const double *x, const Integer *neq, const Integer m[], double y[], double dym[], Integer iuser[], double ruser[]),
double rcomm[], Integer icomm[], Integer iuser[], double ruser[], Integer *ifail)
The routine may be called by the names d02tlf or nagf_ode_bvp_coll_nlin_solve.

3 Description

d02tlf and its associated routines (d02tvf, d02txf, d02tyf and d02tzf) solve the two-point boundary value problem for a nonlinear mixed order system of ordinary differential equations
y1(m1) (x) = f1 (x,y1,y1(1),,y1(m1-1),y2,,yn(mn-1)) y2(m2) (x) = f2 (x,y1,y1(1),,y1(m1-1),y2,,yn(mn-1)) yn(mn) (x) = fn (x,y1,y1(1),,y1(m1-1),y2,,yn(mn-1))  
over an interval [a,b] subject to p (>0) nonlinear boundary conditions at a and q (>0) nonlinear boundary conditions at b, where p+q = i=1 n mi . Note that yi (m) (x) is the mth derivative of the ith solution component. Hence yi (0) (x)=yi(x). The left boundary conditions at a are defined as
gi(z(y(a)))=0,  i=1,2,,p,  
and the right boundary conditions at b as
g¯j(z(y(b)))=0,  j=1,2,,q,  
where y=(y1,y2,,yn) and
z(y(x)) = (y1(x), y1(1) (x) ,, y1(m1-1) (x) ,y2(x),, yn(mn-1) (x) ) .  
First, d02tvf must be called to specify the initial mesh, error requirements and other details. Note that the error requirements apply only to the solution components y1,y2,,yn and that no error control is applied to derivatives of solution components. (If error control is required on derivatives then the system must be reduced in order by introducing the derivatives whose error is to be controlled as new variables. See Section 9 in d02tvf.) Then, d02tlf can be used to solve the boundary value problem. After successful computation, d02tzf can be used to ascertain details about the final mesh and other details of the solution procedure, and d02tyf can be used to compute the approximate solution anywhere on the interval [a,b].
A description of the numerical technique used in d02tlf is given in Section 3 in d02tvf.
d02tlf can also be used in the solution of a series of problems, for example in performing continuation, when the mesh used to compute the solution of one problem is to be used as the initial mesh for the solution of the next related problem. d02txf should be used in between calls to d02tlf in this context.
See Section 9 in d02tvf for details of how to solve boundary value problems of a more general nature.
The routines are based on modified versions of the codes COLSYS and COLNEW (see Ascher et al. (1979) and Ascher and Bader (1987)). A comprehensive treatment of the numerical solution of boundary value problems can be found in Ascher et al. (1988) and Keller (1992).

4 References

Ascher U M and Bader G (1987) A new basis implementation for a mixed order boundary value ODE solver SIAM J. Sci. Stat. Comput. 8 483–500
Ascher U M, Christiansen J and Russell R D (1979) A collocation solver for mixed order systems of boundary value problems Math. Comput. 33 659–679
Ascher U M, Mattheij R M M and Russell R D (1988) Numerical Solution of Boundary Value Problems for Ordinary Differential Equations Prentice–Hall
Keller H B (1992) Numerical Methods for Two-point Boundary-value Problems Dover, New York

5 Arguments

1: ffun Subroutine, supplied by the user. External Procedure
ffun must evaluate the functions fi for given values x,z(y(x)).
The specification of ffun is:
Fortran Interface
Subroutine ffun ( x, y, neq, m, f, iuser, ruser)
Integer, Intent (In) :: neq, m(neq)
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: x, y(neq,0:*)
Real (Kind=nag_wp), Intent (Inout) :: ruser(*)
Real (Kind=nag_wp), Intent (Out) :: f(neq)
C Header Interface
void  ffun (const double *x, const double y[], const Integer *neq, const Integer m[], double f[], Integer iuser[], double ruser[])
1: x Real (Kind=nag_wp) Input
On entry: x, the independent variable.
2: y(neq,0:*) Real (Kind=nag_wp) array Input
On entry: y(i,j) contains yi (j) (x), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (x)=yi(x).
3: neq Integer Input
On entry: the number of differential equations.
4: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
5: f(neq) Real (Kind=nag_wp) array Output
On exit: f(i) must contain fi, for i=1,2,,neq.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
ffun is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to ffun.
ffun must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: ffun should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
2: fjac Subroutine, supplied by the user. External Procedure
fjac must evaluate the partial derivatives of fi with respect to the elements of
z(y(x))=(y1(x),y11(x),,y1 (m1-1) (x),y2(x),,yn (mn-1) (x)).
The specification of fjac is:
Fortran Interface
Subroutine fjac ( x, y, neq, m, dfdy, iuser, ruser)
Integer, Intent (In) :: neq, m(neq)
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: x, y(neq,0:*)
Real (Kind=nag_wp), Intent (Inout) :: dfdy(neq,neq,0:*), ruser(*)
C Header Interface
void  fjac (const double *x, const double y[], const Integer *neq, const Integer m[], double dfdy[], Integer iuser[], double ruser[])
1: x Real (Kind=nag_wp) Input
On entry: x, the independent variable.
2: y(neq,0:*) Real (Kind=nag_wp) array Input
On entry: y(i,j) contains yi (j) (x), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (x)=yi(x).
3: neq Integer Input
On entry: the number of differential equations.
4: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
5: dfdy(neq,neq,0:*) Real (Kind=nag_wp) array Input/Output
On entry: set to zero.
On exit: dfdy(i,j,k) must contain the partial derivative of fi with respect to yj (k) , for i=1,2,,neq, j=1,2,,neq and k=0,1,,m(j)-1. Only nonzero partial derivatives need be set.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
fjac is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to fjac.
fjac must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: fjac should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
3: gafun Subroutine, supplied by the user. External Procedure
gafun must evaluate the boundary conditions at the left-hand end of the range, that is functions gi(z(y(a))) for given values of z(y(a)).
The specification of gafun is:
Fortran Interface
Subroutine gafun ( ya, neq, m, nlbc, ga, iuser, ruser)
Integer, Intent (In) :: neq, m(neq), nlbc
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: ya(neq,0:*)
Real (Kind=nag_wp), Intent (Inout) :: ruser(*)
Real (Kind=nag_wp), Intent (Out) :: ga(nlbc)
C Header Interface
void  gafun (const double ya[], const Integer *neq, const Integer m[], const Integer *nlbc, double ga[], Integer iuser[], double ruser[])
1: ya(neq,0:*) Real (Kind=nag_wp) array Input
On entry: ya(i,j) contains yi (j) (a), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (a)=yi(a).
2: neq Integer Input
On entry: the number of differential equations.
3: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
4: nlbc Integer Input
On entry: the number of boundary conditions at a.
5: ga(nlbc) Real (Kind=nag_wp) array Output
On exit: ga(i) must contain gi(z(y(a))), for i=1,2,,nlbc.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
gafun is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to gafun.
gafun must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: gafun should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
4: gbfun Subroutine, supplied by the user. External Procedure
gbfun must evaluate the boundary conditions at the right-hand end of the range, that is functions g¯i(z(y(b))) for given values of z(y(b)).
The specification of gbfun is:
Fortran Interface
Subroutine gbfun ( yb, neq, m, nrbc, gb, iuser, ruser)
Integer, Intent (In) :: neq, m(neq), nrbc
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: yb(neq,0:*)
Real (Kind=nag_wp), Intent (Inout) :: ruser(*)
Real (Kind=nag_wp), Intent (Out) :: gb(nrbc)
C Header Interface
void  gbfun (const double yb[], const Integer *neq, const Integer m[], const Integer *nrbc, double gb[], Integer iuser[], double ruser[])
1: yb(neq,0:*) Real (Kind=nag_wp) array Input
On entry: yb(i,j) contains yi (j) (b), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (b)=yi(b).
2: neq Integer Input
On entry: the number of differential equations.
3: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
4: nrbc Integer Input
On entry: the number of boundary conditions at b.
5: gb(nrbc) Real (Kind=nag_wp) array Output
On exit: gb(i) must contain g¯i(z(y(b))), for i=1,2,,nrbc.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
gbfun is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to gbfun.
gbfun must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: gbfun should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
5: gajac Subroutine, supplied by the user. External Procedure
gajac must evaluate the partial derivatives of gi(z(y(a))) with respect to the elements of z(y(a))=(y1(a),y11(a),,y1 (m1-1) (a),y2(a),,yn (mn-1) (a)).
The specification of gajac is:
Fortran Interface
Subroutine gajac ( ya, neq, m, nlbc, dgady, iuser, ruser)
Integer, Intent (In) :: neq, m(neq), nlbc
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: ya(neq,0:*)
Real (Kind=nag_wp), Intent (Inout) :: dgady(nlbc,neq,0:*), ruser(*)
C Header Interface
void  gajac (const double ya[], const Integer *neq, const Integer m[], const Integer *nlbc, double dgady[], Integer iuser[], double ruser[])
1: ya(neq,0:*) Real (Kind=nag_wp) array Input
On entry: ya(i,j) contains yi (j) (a), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (a)=yi(a).
2: neq Integer Input
On entry: the number of differential equations.
3: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
4: nlbc Integer Input
On entry: the number of boundary conditions at a.
5: dgady(nlbc,neq,0:*) Real (Kind=nag_wp) array Input/Output
On entry: set to zero.
On exit: dgady(i,j,k) must contain the partial derivative of gi(z(y(a))) with respect to yj (k) (a), for i=1,2,,nlbc, j=1,2,,neq and k=0,1,,m(j)-1. Only nonzero partial derivatives need be set.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
gajac is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to gajac.
gajac must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: gajac should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
6: gbjac Subroutine, supplied by the user. External Procedure
gbjac must evaluate the partial derivatives of g¯i(z(y(b))) with respect to the elements of z(y(b))=(y1(b),y11(b),,y1 (m1-1) (b),y2(b),,yn (mn-1) (b)).
The specification of gbjac is:
Fortran Interface
Subroutine gbjac ( yb, neq, m, nrbc, dgbdy, iuser, ruser)
Integer, Intent (In) :: neq, m(neq), nrbc
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: yb(neq,0:*)
Real (Kind=nag_wp), Intent (Inout) :: dgbdy(nrbc,neq,0:*), ruser(*)
C Header Interface
void  gbjac (const double yb[], const Integer *neq, const Integer m[], const Integer *nrbc, double dgbdy[], Integer iuser[], double ruser[])
1: yb(neq,0:*) Real (Kind=nag_wp) array Input
On entry: yb(i,j) contains yi (j) (b), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (b)=yi(b).
2: neq Integer Input
On entry: the number of differential equations.
3: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
4: nrbc Integer Input
On entry: the number of boundary conditions at b.
5: dgbdy(nrbc,neq,0:*) Real (Kind=nag_wp) array Input/Output
On entry: set to zero.
On exit: dgbdy(i,j,k) must contain the partial derivative of g¯i(z(y(b))) with respect to yj (k) (b), for i=1,2,,nrbc, j=1,2,,neq and k=0,1,,m(j)-1. Only nonzero partial derivatives need be set.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
gbjac is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to gbjac.
gbjac must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: gbjac should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
7: guess Subroutine, supplied by the user. External Procedure
guess must return initial approximations for the solution components yi (j) and the derivatives yi (mi) , for i=1,2,,neq and j=0,1,,m(i)-1. Try to compute each derivative yi (mi) such that it corresponds to your approximations to y i (j) , for j=0,1,,m(i)-1. You should not call ffun to compute yi (mi) .
If d02tlf is being used in conjunction with d02txf as part of a continuation process, guess is not called by d02tlf after the call to d02txf.
The specification of guess is:
Fortran Interface
Subroutine guess ( x, neq, m, y, dym, iuser, ruser)
Integer, Intent (In) :: neq, m(neq)
Integer, Intent (Inout) :: iuser(*)
Real (Kind=nag_wp), Intent (In) :: x
Real (Kind=nag_wp), Intent (Inout) :: y(neq,0:*), ruser(*)
Real (Kind=nag_wp), Intent (Out) :: dym(neq)
C Header Interface
void  guess (const double *x, const Integer *neq, const Integer m[], double y[], double dym[], Integer iuser[], double ruser[])
1: x Real (Kind=nag_wp) Input
On entry: x, the independent variable; x[a,b].
2: neq Integer Input
On entry: the number of differential equations.
3: m(neq) Integer array Input
On entry: m(i) contains mi, the order of the ith differential equation, for i=1,2,,neq.
4: y(neq,0:*) Real (Kind=nag_wp) array Output
On exit: y(i,j) must contain yi (j) (x), for i=1,2,,neq and j=0,1,,m(i)-1.
Note:  yi (0) (x)=yi(x).
5: dym(neq) Real (Kind=nag_wp) array Output
On exit: dym(i) must contain yi (mi) (x), for i=1,2,,neq.
6: iuser(*) Integer array User Workspace
7: ruser(*) Real (Kind=nag_wp) array User Workspace
guess is called with the arguments iuser and ruser as supplied to d02tlf. You should use the arrays iuser and ruser to supply information to guess.
guess must either be a module subprogram USEd by, or declared as EXTERNAL in, the (sub)program from which d02tlf is called. Arguments denoted as Input must not be changed by this procedure.
Note: guess should not return floating-point NaN (Not a Number) or infinity values, since these are not handled by d02tlf. If your code inadvertently does return any NaNs or infinities, d02tlf is likely to produce unexpected results.
8: rcomm(*) Real (Kind=nag_wp) array Communication Array
Note: the dimension of this array is dictated by the requirements of associated functions that must have been previously called. This array must be the same array passed as argument rcomm in the previous call to d02tvf.
On entry: this must be the same array as supplied to d02tvf and must remain unchanged between calls.
On exit: contains information about the solution for use on subsequent calls to associated routines.
9: icomm(*) Integer array Communication Array
Note: the dimension of this array is dictated by the requirements of associated functions that must have been previously called. This array must be the same array passed as argument icomm in the previous call to d02tvf.
On entry: this must be the same array as supplied to d02tvf and must remain unchanged between calls.
On exit: contains information about the solution for use on subsequent calls to associated routines.
10: iuser(*) Integer array User Workspace
11: ruser(*) Real (Kind=nag_wp) array User Workspace
iuser and ruser are not used by d02tlf, but are passed directly to ffun, fjac, gafun, gbfun, gajac, gbjac and guess and may be used to pass information to these routines.
12: ifail Integer Input/Output
On entry: ifail must be set to 0, −1 or 1 to set behaviour on detection of an error; these values have no effect when no error is detected.
A value of 0 causes the printing of an error message and program execution will be halted; otherwise program execution continues. A value of −1 means that an error message is printed while a value of 1 means that it is not.
If halting is not appropriate, the value −1 or 1 is recommended. If message printing is undesirable, then the value 1 is recommended. Otherwise, the value −1 is recommended since useful values can be provided in some output arguments even when ifail0 on exit. 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:
Note: in some cases d02tlf may return useful information.
ifail=1
Either the setup routine has not been called or the communication arrays have become corrupted. No solution will be computed.
ifail=2
Numerical singularity has been detected in the Jacobian used in the Newton iteration.
No results have been generated. Check the coding of the routines for calculating the Jacobians of system and boundary conditions.
ifail=3
All Newton iterations that have been attempted have failed to converge.
No results have been generated. Check the coding of the routines for calculating the Jacobians of system and boundary conditions.
Try to provide a better initial solution approximation.
ifail=4
A Newton iteration has failed to converge. The computation has not succeeded but results have been returned for an intermediate mesh on which convergence was achieved.
These results should be treated with extreme caution.
ifail=5
The expected number of sub-intervals required to continue the computation exceeds the maximum specified: value.
Results have been generated which may be useful.
Try increasing this number or relaxing the error requirements.
ifail=-99
An unexpected error has been triggered by this routine. Please contact NAG.
See Section 7 in the Introduction to the NAG Library FL Interface for further information.
ifail=-399
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.
ifail=-999
Dynamic memory allocation failed.
See Section 9 in the Introduction to the NAG Library FL Interface for further information.

7 Accuracy

The accuracy of the solution is determined by the argument tols in the prior call to d02tvf (see Sections 3 and 9 in d02tvf for details and advice). Note that error control is applied only to solution components (variables) and not to any derivatives of the solution. An estimate of the maximum error in the computed solution is available by calling d02tzf.

8 Parallelism and Performance

d02tlf is threaded by NAG for parallel execution in multithreaded implementations of the NAG Library.
d02tlf 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

If d02tlf returns with ifail=2, 3, 4 or 5 and the call to d02tlf was a part of some continuation procedure for which successful calls to d02tlf have already been made, then it is possible that the adjustment(s) to the continuation parameter(s) between calls to d02tlf is (are) too large for the problem under consideration. More conservative adjustment(s) to the continuation parameter(s) might be appropriate.

10 Example

The following example is used to illustrate the treatment of a high-order system, control of the error in a derivative of a component of the original system, and the use of continuation. See also d02tvf, d02txf, d02tyf and d02tzf, for the illustration of other facilities.
Consider the steady flow of an incompressible viscous fluid between two infinite coaxial rotating discs. See Ascher et al. (1979) and the references therein. The governing equations are
1R f + ff + gg = 0 1R g + fg - fg = 0  
subject to the boundary conditions
f(0)=f(0)= 0,   g(0)=Ω0,   f(1)=f(1)= 0,   g(1)=Ω1,  
where R is the Reynolds number and Ω0,Ω1 are the angular velocities of the disks.
We consider the case of counter-rotation and a symmetric solution, that is Ω0=1, Ω1=−1. This problem is more difficult to solve, the larger the value of R. For illustration, we use simple continuation to compute the solution for three different values of R (=106,108,1010). However, this problem can be addressed directly for the largest value of R considered here. Instead of the values suggested in Section 5 in d02txf for nmesh, ipmesh and mesh in the call to d02txf prior to a continuation call, we use every point of the final mesh for the solution of the first value of R, that is we must modify the contents of ipmesh. For illustrative purposes we wish to control the computed error in f and so recast the equations as
y1 = y2 y2 = -R(y1y2+y3y3) y3 = R(y2y3-y1y3)  
subject to the boundary conditions
y1(0)=y2(0)= 0,   y3(0)=Ω,   y1(1)=y2(1)= 0,   y3(1)=-Ω,   Ω=1.  
For the symmetric boundary conditions considered, there exists an odd solution about x=0.5. Hence, to satisfy the boundary conditions, we use the following initial approximations to the solution in guess:
y1(x) = -x2(x-12) (x-1) 2 y2(x) = -x(x-1)(5x2-5x+1) y3(x) = −8Ω (x-12) 3.  

10.1 Program Text

Program Text (d02tlfe.f90)

10.2 Program Data

Program Data (d02tlfe.d)

10.3 Program Results

Program Results (d02tlfe.r)
GnuplotProduced by GNUPLOT 5.0 patchlevel 3 −0.1 −0.05 0 0.05 0.1 0.15 0.2 0 0.2 0.4 0.6 0.8 1 −1 −0.5 0 0.5 1 f fx g f and fx g X Example Program Incompressible Fluid Flow between Coaxial Rotating Discs Solutions for Reynolds Number 1,000,000 f fx g
GnuplotProduced by GNUPLOT 5.0 patchlevel 3 −0.02 0 0.02 0.04 0.06 0.08 0.1 0.12 0.14 0.16 0.18 0.2 0 0.2 0.4 0.6 0.8 1 −1 −0.5 0 0.5 1 f fx g f and fx g X Incompressible Fluid Flow between Coaxial Rotating Discs Solutions for Reynolds Number 100,000,000 f fx g
GnuplotProduced by GNUPLOT 5.0 patchlevel 3 −0.02 0 0.02 0.04 0.06 0.08 0.1 0.12 0.14 0.16 0.18 0.2 0 0.2 0.4 0.6 0.8 1 −1 −0.5 0 0.5 1 f fx g f and fx g X Incompressible Fluid Flow between Coaxial Rotating Discs Solutions for Reynolds Number 10,000,000,000 f fx g