NAG Library Routine Document
H03BBF
1 Purpose
H03BBF calculates an approximate solution to a symmetric travelling salesman problem using simulated annealing via a configuration free interface.
2 Specification
INTEGER |
NC, PATH(NC), TMODE, STATE(*), IFAIL |
REAL (KIND=nag_wp) |
DM(NC,NC), BOUND, TARGC, COST, ALG_STATS(6) |
|
3 Description
H03BBF provides a probabilistic strategy for the calculation of a near optimal path through a symmetric and fully connected distance matrix; that is, a matrix for which element is the pairwise distance (also called the cost, or weight) between nodes (cities) and . This problem is better known as the Travelling Salesman Problem (TSP), and symmetric means that the distance to travel between two cities is independent of which is the destination city.
In the classical TSP, which this routine addresses, a salesman wishes to visit a given set of cities once only by starting and finishing in a home city and travelling the minimum total distance possible. It is one of the most intensively studied problems in computational mathematics and, as a result, has developed some fairly sophisticated techniques for getting near-optimal solutions for large numbers of cities. H03BBF adopts a very simple approach to try to find a reasonable solution, for moderately large problems. The routine uses simulated annealing: a stochastic mechanical process in which the heating and controlled cooling of a material is used to optimally refine its molecular structure.
The material in the TSP is the distance matrix and a given state is represented by the order in which each city is visited—the path. This system can move from one state to a neighbouring state by selecting two cities on the current path at random and switching their places; the order of the cities in the path between the switched cities is then reversed. The cost of a state is the total cost of traversing its path; the resulting difference in cost between the current state and this new proposed state is called the delta; a negative delta indicates the proposal creates a more optimal path and a positive delta a less optimal path. The random selection of cities to switch uses random number generators (RNGs) from
Chapter G05; it is thus necessary to initialize a state array for the RNG of choice (by a call to
G05KFF or
G05KGF) prior to calling H03BBF.
The simulation itself is executed in two stages. In the first stage, a series of sample searches through the distance matrix is conducted where each proposed new state is accepted, regardless of the change in cost (delta) incurred by applying the switches, and statistics on the set of deltas are recorded. These metrics are updated after each such sample search; the number of these searches and the number of switches applied in each search is dependent on the number of cities. The final collated set of metrics for the deltas obtained by the first stage are used as control parameters for the second stage. If no single improvement in cost is found during the first stage, the algorithm is terminated.
In the second stage, as before, neighbouring states are proposed. If the resulting delta is negative or causes no change the proposal is accepted and the path updated; otherwise moves are accepted based on a probabilistic criterion, a modified version of the Metropolis–Hastings algorithm.
The acceptance of some positive deltas (increased cost) reduces the probability of a solution getting trapped at a non-optimal solution where any single switch causes an increase in cost. Initially the acceptance criteria allow for relatively large positive deltas, but as the number of proposed changes increases, the criteria become more stringent, allowing fewer positive deltas of smaller size to be accepted; this process is, within the realm of the simulated annealing algorithm, referred to as ‘cooling’. Further exploration of the system is initially encouraged by accepting non-optimal routes, but is increasingly discouraged as the process continues.
The second stage will terminate when:
- – a solution is obtained that is deemed acceptable (as defined by supplied values);
- – the algorithm will accept no further positive deltas and a set of proposed changes have resulted in no improvements (has cooled);
- – a number of consecutive sets of proposed changes has resulted in no improvement.
4 References
Applegate D L, Bixby R E, Chvátal V and Cook W J (2006) The Traveling Salesman Problem: A Computational Study Princeton University Press
Cook W J (2012) In Pursuit of the Traveling Salesman Princeton University Press
Johnson D S and McGeoch L A The traveling salesman problem: A case study in local optimization Local search in combinatorial optimization (1997) 215–310
Press W H, Teukolsky S A, Vetterling W T and Flannery B P (2007) Numerical Recipes The Art of Scientific Computing (3rd Edition)
Rego C, Gamboa D, Glover F and Osterman C (2011) Traveling salesman problem heuristics: leading methods, implementations and latest advances European Journal of Operational Research 211 (3) 427–441
Reinelt G (1994) The Travelling Salesman. Computational Solutions for TSP Applications, Volume 840 of Lecture Notes in Computer Science Springer–Verlag, Berlin Heidelberg New York
5 Parameters
- 1: – INTEGERInput
-
On entry: the number of cities. In the trivial cases , or , the routine returns the optimal solution immediately with (provided the relevant distance matrix entries are not negative).
Constraint:
.
- 2: – REAL (KIND=nag_wp) arrayInput
-
On entry: the distance matrix; each is the effective cost or weight between nodes and . Only the strictly upper half of the matrix is referenced.
Constraint:
, for and .
- 3: – REAL (KIND=nag_wp)Input
-
On entry: a lower bound on the solution. If the optimum is unknown set
BOUND to zero or a negative value; the routine will then calculate the minimum spanning tree for
DM and use this as a lower bound (returned in
). If an optimal value for the cost is known then this should be used for the lower bound. A detailed discussion of relaxations for lower bounds, including the minimal spanning tree, can be found in
Reinelt (1994).
- 4: – REAL (KIND=nag_wp)Input
-
On entry: a measure of how close an approximation needs to be to the lower bound. The routine terminates when a cost is found less than or equal to
. This parameter is useful when an optimal value for the cost is known and supplied in
BOUND. It may be sufficient to obtain a path that is close enough (in terms of cost) to the optimal path; this allows the algorithm to terminate at that point and avoid further computation in attempting to find a better path.
If , is assumed.
- 5: – INTEGER arrayOutput
-
On exit: the best path discovered by the simulation. That is,
PATH contains the city indices in path order. If
on exit,
PATH contains the indices
to
NC.
- 6: – REAL (KIND=nag_wp)Output
-
On exit: the cost or weight of
PATH. If
on exit,
COST contains the largest model real number (see
X02BLF).
- 7: – INTEGEROutput
-
On exit: the termination mode of the routine (if
on exit,
TMODE is set to
):
- Optimal solution found, .
- System temperature cooled. The algorithm returns a PATH and associated COST that does not attain, nor lie within TARGC of, the BOUND. This could be a sufficiently good approximation to the optimal PATH, particularly when lies below the optimal COST.
- Halted by COST falling within the desired TARGC range of the BOUND.
- System stalled following lack of improvement.
- Initial search failed to find a single improvement (the solution could be optimal).
- 8: – REAL (KIND=nag_wp) arrayOutput
-
On exit: an array of metrics collected during the initial search. These could be used as a basis for future optimization. If
on exit, the elements of
ALG_STATS are set to zero; the first five elements are also set to zero in the trival cases
,
or
.
- Mean delta.
- Standard deviation of deltas.
- Cost at end of initial search phase.
- Best cost encountered during search phase.
- Initial system temperature. At the end of stage 1 of the algorithm, this is a function of the mean and variance of the deltas, and of the distance from best cost to the lower bound. It is a measure of the initial acceptance criteria for stage 2. The larger this value, the more iterations it will take to geometrically reduce it during stage 2 until the system is cooled (below a threshold value).
- The lower bound used, which will be that computed internally when on input. Subsequent calls with different random states can set BOUND to the value returned in to avoid recomputation of the minimal spanning tree.
- 9: – INTEGER arrayCommunication Array
-
Note: the actual argument supplied
must be the array
STATE supplied to the initialization routines
G05KFF or
G05KGF.
On entry: a valid RNG state initialized by
G05KFF or
G05KGF. Since the algorithm used is stochastic, a random number generator is employed; if the generator is initialized to a non-repeatable sequence (
G05KGF) then different solution paths will be taken on successive runs, returning possibly different final approximate solutions.
On exit: contains updated information on the state of the generator.
- 10: – INTEGERInput/Output
-
On entry:
IFAIL must be set to
,
. 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
is recommended. If the output of error messages is undesirable, then the value
is recommended. Otherwise, if you are not familiar with this parameter, the recommended value is
.
When the value 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).
6 Error 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:
-
On entry, .
Constraint: .
-
On entry, the strictly upper triangle of
DM had a negative element.
-
On entry,
STATE vector has been corrupted or not initialized.
An unexpected error has been triggered by this routine. Please
contact
NAG.
See
Section 3.8 in the Essential Introduction for further information.
Your licence key may have expired or may not have been installed correctly.
See
Section 3.7 in the Essential Introduction for further information.
Dynamic memory allocation failed.
See
Section 3.6 in the Essential Introduction for further information.
7 Accuracy
The routine will not perform well when the average change in cost caused by switching two cities is small relative to the cost; this can happen when many of the values in the distance matrix are relatively close to each other.
The quality of results from this routine can vary quite markedly when different initial random states are used. It is therefore advisable to compute a number of approximations using different initial random states. The best cost and path can then be taken from the set of approximations obtained. If no change in results is obtained after such trials then it is unlikely that any further improvement can be made by this routine.
8 Parallelism and Performance
Running many instances of the routine in parallel with independent random number generator states can yield a set of possible solutions from which a best approximate solution may be chosen.
Memory is internally allocated for integers and real values.
In the case of two cities that are not connected, a suitably large number should be used as the distance (cost) between them so as to deter solution paths which directly connect the two cities.
Solutions which contain an artificial link (i.e., a connection with a large distance between them to indicate no actual link) may be patched, using the shortest path algorithm
H03ADF.
If a city is to be visited more than once (or more than twice for the home city) then the distance matrix should contain multiple entries for that city (on rows and columns ) with zero entries for distances to itself and identical distances to other cities.
10 Example
An approximation to the best path through cities in the United Kingdom and Ireland, beginning and ending in Oxford, is sought. A lower bound is calculated internally.
10.1 Program Text
Program Text (h03bbfe.f90)
10.2 Program Data
Program Data (h03bbfe.d)
10.3 Program Results
Program Results (h03bbfe.r)