heronyang / airport-simulation Goto Github PK

Problem

Currently, a single simulation on 9 hours scenario data, for sfo-terminal-2, and rescheduling on each tick takes around 2 to 3 minutes. It's too slow for us to run lots of batch tests.

Solution

1. Use the profiling technique described in the README to find out the slow parts of the code, and optimize it.
2. Use multiple thread technique for the batch runs since there's no shared data between two simulation runs. (The surface/scenario data may be shared, but it's not hard to avoid that).
3. Replace the slow code with c++ or c code. Or, pypy.

Note

pypy doesn't support numpy/pandas plots at this point. We will need to figure a way to avoid this if we're optimizing the code with pypy.

Problem

Currently, conflicts created by the uncertainty module in the simulation is not preventable if the scheduler doesn't reschedule every tick. Instead, these kinds of conflicts lead to an early termination to reflect the real world: "if there's a crash in the airport, there's no way the airport will continue to function properly."

Solution

Therefore, we need a pilot behavior design in our simulation logic. The pilots should add a delay on its own aircraft is it found out the target node is occupied by another aircraft.

Code

We should add:

1. Checks if another aircraft "is_close_to" the next target at aircraft.tick().
2. If yes, inject a delay on this aircraft
3. Adds another list in the itinerary for "pilot_delay" which should be similar to scheduler_delay and uncertainty_delay.
4. Updates the state_logger, analyst and reporter objects for logging the results.

Note

The hardest part of this feature should be finding out a good way to move multiple aircrafts at the same time. Note that the simulation is actually sequential so the moves may or may not affect other aircrafts.

Problem

Currently, we have two airports that work: simple and sfo-terminal-2. simple data contains 3 gates and 1 runways and sfo-terminal-2 contains the gates in terminal 2 and 1 runways. These objects may not be enough for providing a hard enough problem for the scheduler.

Solution

Create a new airport data under data following the same structure as sfo-terminal-2. However, we pull out more data (for example, more terminals) from data/sfo and to make it work with the simulation.