Table 3: Experimental results for scenario 20 using a time horizon of 90 minutes and 30 seconds execution time, for different
number of workers and parallelization depths.
Depth Nodes Solutions Nodes Solutions
visited (Worker id, cost, time) visited (Worker id, cost, time)
8 Workers 16 Workers
T
0
8 573 135 (2, 27208, 0.24), (3, 27186, 0.49), (0, 23609, 0.52),
(0, 23587, 0.83)
7 841 418 (5, 27208, 0.56), (11, 27186, 0.84), (1, 23609, 0.91),
(1, 23587, 1.22)
100 8 048 136 (7, 27186, 0.51), (0, 23609, 0.60), (5, 23587, 0.64) 8 381 525 (12, 27208, 0.14), (8, 27186, 0.56), (5, 23587, 0.77)
200 7 334 836 (3, 27186, 0.16), (2, 23587, 0.23) 8 440 333 (1, 27208, 0.18), (15, 27186, 0.24), (8, 23587, 0.41)
300 4 699 518 (6, 27208, 0.06), (5, 27186, 0.14), (7, 23587, 0.19) 7 816 092 (12, 27208, 0.07), (11, 27186, 0.34), (9, 23587, 0.47)
400 4 730 399 (5, 27186, 0.10), (4, 23587, 0.15) 7 790 739 (11, 27208, 0.07), (8, 27186, 0.21), (5, 23587, 0.30)
500 1 916 351 (6, 27186, 0.07), (7, 23587, 0.12) 1 986 419 (7, 27186, 0.09), (6, 23587, 0.16)
32 Workers Maximum number of Workers
T
0
6 817 627 (5, 27208, 1.27), (26, 26765, 1.10), (29, 23609, 1.65),
(26, 23166, 2.06), (26, 23144, 2.52)
5 722 240 (19, 27208, 1.03), (32, 26765, 1.14), (31, 23609, 2.34),
(26, 23166, 2.56), (26, 23144, 3.70)
100 7 065 428 (2, 27208, 0.34), (14, 27186, 1.45), (7, 23609, 1.59),
(1, 23587, 1.69)
6 668 677 (9, 27208, 0.33), (6, 27186, 1.43), (5, 23587, 1.83)
200 7 418 218 (1, 27208, 0.25), (28, 27186, 0.57), (3, 23587, 0.83) 7 160 066 (4, 27208, 0.17), (7, 27186, 0.70), (18, 23587, 0.72)
300 6 626 197 (6, 27208, 0.24), (6, 27208, 0.24), (12, 23587, 0.77) 7 044 556 (14, 27208, 0.11), (20, 27186, 0.52), (8, 23587, 0.73)
400 7 547 346 (8, 27186, 0.48), (5, 23587, 0.69) 7 704 260 (6, 27208, 0.09), (8, 27186, 0.46), (10, 23587, 0.59)
500 2 007 587 (6, 27186, 0.10), (7, 23587, 0.16) 1 911 910 (6, 27186, 0.07), (7, 23587, 0.13)
sec and 3.70 sec, respectively.
6.1.1 Number of Workers
We start by analyzing the effect of the number of
workers, focusing on the results for parallelization
depth T
0
. At depth T
0
( i.e., the time when the distur-
bance occurs), the number of trains to re-schedule (i.e.
the size of the candidate list) is as large as possible.
For scenario 20, the maximum number of candidate
events is 50, as can be seen in the third column in Ta-
ble 2. Thus, we can potentially explore 50 candidates
(branches/subtrees) in parallel at depth T
0
. Looking
at the solutions found by selecting T
0
in Table 3, we
observe that both more (5 solutions) and better solu-
tions (a total delay of 23144 s) are found when we
use the maximum number of workers (i.e. 50) and 32
workers, as compared to the solutions found when us-
ing only 8 or 16 workers (4 solutions and a total delay
of 23587). This is also indicated by the fact that it is
worker 26 (which evaluates candidate event 26 in the
initial next candidate list) that finds the best solution.
Therefore, we conclude for this type of disturbance
scenario that the parallel algorithm should explore as
many candidates as possible concurrently when the
parallel phase starts.
6.1.2 Parallelization Depth
When evaluating at which depth in the search tree it is
most beneficial to start the parallel phase, we focus on
the case with the maximum number of workers in Ta-
ble 3. From the results, we can observe two important
things. First, the best solution (23144) is found when
the parallel execution starts at depth T
0
. Further, it is
only when the parallel search starts as high up in the
tree as possible, i.e., at T
0
, that we find this best solu-
tion. Second, looking at the number of nodes visited,
we find that if we start the parallel search too far down
in the search tree, in this case at depth 500, the num-
ber of nodes explored decreases drastically. For this
type of disturbance scenario, we can conclude that the
parallel search should start as high up in the tree as
possible.
One important aspect, which affects the perfor-
mance of the B&B procedure in the algorithm sig-
nificantly, is how the cost estimate, CV
w
at interme-
diary nodes in the tree reflects the effect of each de-
cision and the resulting complete solution. That is,
does the optimistic delay estimation provide enough
information to guide the branching procedure well,
so that the pruning and selection of nodes to explore
are effective. As shown in Figure 4, the cost incre-
ment trend is very similar for all solutions up to depth
500 approximately, after that they start to diverge sig-
nificantly. The higher divergence is found deep in
the tree. The implication of this is that it becomes
harder to perform efficient pruning of non-promising
branches early, i.e., high up in the search tree. Conse-
quently, the efficiency of the algorithm (the sequential
as well as the parallell version) could potentially be
A PARALLEL HEURISTIC FOR FAST TRAIN DISPATCHING DURING RAILWAY TRAFFIC DISTURBANCES:
EARLY RESULTS
411