Skip to content

Latest commit

 

History

History
36 lines (26 loc) · 2.81 KB

README.md

File metadata and controls

36 lines (26 loc) · 2.81 KB

Algorithm

This software was written for DBL (Design Based Learning) Algorithms by group 11 of 2IO90 year 2017-2018 at the University of Eindhoven.

Summary

The software is aimed to solve a particular problem, namely taxi scheduling. Currently in the real world, usually each customer is treated separately. Ride sharing does not happen often. It seems logical that this is not optimal for delivering customers to their destination as fast as possible. This algorithm is designed to schedule taxis as efficient as possible such that the total runtime of the algorithm itself and the costs, as described below, are as low as possible.

Of course, this algorithm can be extended to be applied in many more fields due to the abstraction of the problem to networks and requests. It must be noted, that the current version of the algorithm is designed to perform optimally on the final test cases provided by the course. However, we think that we've come to a rather good solution. Also, there is plenty of room for further optimalisation.

Test case format

Each test case begins with a preamble, next a training period and as last the actual, real, call list.

Preamble

The preamble contains information that is requried to run the algorithm. Below is a list of the most important parts

  • Structure of the graph (i.e. vertices and edges)
  • Number of taxis
  • Capacity of each taxi
  • Alpha value (explained in Performance)

Training period

Next, a training period follows in which the performance of the algorithm is not measured. This can be used to train the algorithm or precalculate certain information.

Call list

Lastly, a list of calls will follow. This is a turned based process. First, a line of the call list is received by the algorithm. This line can contain n number of call, which consists of a start vertex and a destination vertex. Then, the algorithm is allowed to move all taxis, drop or pick up customers. Each taxi is only allowed to move OR to pick up and drop at each turn. When the algorithm is done, the next line of the call list is read. This process continues until each customer arrived at its destination.

Performance

The performance is measured by calculating the following cost function:

Cost function

  • n is the total amount of customers
  • c is the call time of a customer i
  • a is the arrival time of customer i at its destination
  • d(u, v) is the shortest path between node u and v, where u is the start vertex and v is the destination vertex of the customer

Intsallation instructions

See the interpreter for installation instructions.