dandesousa / elevator_simulation Goto Github PK

start work range
lunch break range
lunch time specifier
work day length
number of breaks and average break time
random meeting parameters
lunch location specifiers
building level specification
elevator bank specifications
elevator quantity specifications
capacity specifications

• events should exist on the agent itself, not as part of the notifier (lets the notified object reset the event without spinning)

theres an unused fitness property that is in person but unused. It would be used to take the steps sometimes, and would benefit the 'all' strategy.

Should take the csv file output from simulation and produce the following charts using matplotlib:

• histogram of total travel time vs time of day in 30-60 minute buckets
• median travel time vs time of day

I think this is the minimum needed to solve the problem. Other possibilities include:

• total wait time over the day by floor (who waits the longest for an elevator)

we should notify users that an elevator door open through the elevator bank, for users that have called on the elevator bank, if its going in the same direction as the user.

This probably means adding users to the elevator bank in one of two direction sets, then triggering door open events on the person when the elevator arrives.

It would benefit the 'all' strategy to generate random breaks throughout the day for people.

• update and remove model from properties
• refactor everyone to use properties directly