0LAUK0 2015 01 Week5: Difference between revisions
| Line 65: | Line 65: | ||
2. The current test is in command line. A GUI is needed, maybe Unity. | 2. The current test is in command line. A GUI is needed, maybe Unity. | ||
3. | 3. Recorders for recording value changes need to be inserted to current version for further analysis of the simulation result. | ||
== Eric Steenhof == | == Eric Steenhof == | ||
Revision as of 15:46, 2 October 2015
| Home | |||||||
| Content | Plan | Report | Simulation | ||||
| Log | Week1 | Week2 | Week3 | Week4 | Week5 | Week6 | Week7 |
Week 5： 28-09-15
Meetings
Monday
Thursday
Plan
Progress
Kasper Bakker
Frank van Heeswijk
Yuanlong Li
-Made a discrete event simulator based on React.NET framework
The simulator is able to simulate multiple buses, bus stops and passengers interacting with each other.
Basically there are 3 different kind of process running in the simulator
1. Bus is keep running around and retrieving next destination from the scheduler interface
2. Passenger is another process trigged by bus at bus stops. On/off action will take certain amount of time for each passenger.
3. Simulator itself acts as environment. It generates passengers using Exponential distribution and step through random time generated using Normal distribution.
There's still a lot to do to make the simulation complete:
1. Currently only a one route static scheduler is implemented. Dynamic scheduler and multiple routes static scheduler need to be implemented.
2. The current test is in command line. A GUI is needed, maybe Unity.
3. Recorders for recording value changes need to be inserted to current version for further analysis of the simulation result.