loaded running map with the proposed system.
Out tool provides several benefits for automatic
railway infrastructure scheduling.
• It is flexible and friendly. It can be easily inte-
grated into already existing data-bases and other
computer-aided tools for railway management.
• It automatically obtains optimized and well-formed
running maps (timetables).
• It can validate complex timetables by automatically
performing all the consistency checks required for
well-formed timetables.
• It can validate and perform capacity analyses.
• It can reschedule running maps according to inci-
dences and delays in on-line, traffic management.
Figure 4: Example of a high loaded running map.
5 EVALUATION
The application and performance of this system de-
pends on several factors: Railway topology (loca-
tions, distances, tracks, etc.), number and type of
trains (speeds, starting and stopping times, etc.), fre-
quency ranges, initial departure interval times, etc.
In this section, we compare the performance of
our filtering techniques using some well-known con-
straint optimization problem solvers, CPLEX and
LINGO, because they are the most appropriate tools
for solving these types of problems.
This empirical evaluation was carried out on a real
railway infrastructure that joins two important Span-
ish cities (”La Coru
˜
na” and ”Vigo”). The journey be-
tween these two cities is currently divided by 40 de-
pendencies between stations (23) and halts (17).
In our empirical evaluation, each set of instances
was defined by the 3-tuple < n,s,f >, where n was
the number of trains in each direction, s the number of
stations/halts and f the frequency. The problems were
generated by modifying these parameters. Thus, each
of the tables shown sets two of the parameters and
varies the other one in order to evaluate the algorithm
performance when this parameter increases. It must
be taken into account that running time of the form
”>xh.” represents that the problem did not finish in
x hours and the best solution found up to date is pre-
sented in the journey time column. All running times
in Table 3 represent the running times of the filtering
techniques plus the running times of the optimization
techniques (CPLEX or LINGO).
In Table 3 (a), we present the running time and the
journey time in problems where the number of trains
was increased from 5 to 75, and the number of sta-
tions/halts and the frequency were set at 40 and 90,
respectively: <n,40, 90 >. The results show as the
number of trains increased the running time of Filter-
ing technique 1 and 2 was worse. Filtering technique
1 obtained the optimal solution for 5,10,15 and 20
trains. However for 50 and 75 trains, Filtering tech-
nique 1 was aborted in 5 hours while Filtering tech-
nique 2 finished although with worse solutions. Fig-
ure 3 shows the system interface executing our Fil-
tering technique 2 with the instance < 10, 40, 90 >.
The first window shows the user parameters, the sec-
ond window presents the best solution obtained at that
point, the third window presents data about the best
solution found, and finally the last window shows the
obtained running map.
Table 3 (b) shows the running time and the jour-
ney time in problems where the number of stations
was increased from 10 to 60, and the number of trains
and the frequency were set at 10 and 90, respectively:
< 10,s,90 >. In this case, only stations were in-
cluded to analyze the behavior of the techniques. It
can be observed that Filtering technique 2 was bet-
ter than Filtering technique 1 obtaining optimal solu-
tions for 10 and 20 stations in lower time. Eve for
30 stations Filtering technique 2 had better behaviour
than Filtering technique 1 (complete algorithm). It
is important to note the difference between the in-
stance < 10, 40, 90 > of the Table 3 (a) and the in-
stance < 10, 40, 90 >
in Table 3 (b). They repre-
sent the same instance; however in Table 3 (b) we
only used stations (no halts), so the number of pos-
sible crossing between trains was much larger (more
integer variables). This item reduced the journey time
from 2:20:19 to 2:20:10, using Filtering technique 1
and from 2:26:04 to 2:23:36, using CPLEX and Filter-
ing technique 2. Nevertheless, the running time also
increased from 337” to 2131 in Filtering technique 1
and from 8” to 56” in Filtering technique 2, due to the
number of integer variables was much larger.
In Table 3 (c), we present the running time and the
journey time in problems where the frequency was de-
creased from 140 to 60 and the number of trains and
the number of stations were set at 20 and 40, respec-
ICINCO 2005 - INTELLIGENT CONTROL SYSTEMS AND OPTIMIZATION
194