You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
After our discussion today, here are some features we would like to eventually have:
Back-end simulator and a front-end display decoupled. I think the best way would be to allow entities to register to a channel where the simulator posts events and states.
Be able to connect external controllers, without embedding them into the main codebase. We could do that like Pacman, by providing a separate file with a Controller class, or via the network by connection to a port (that is how the Java one is). This can be done via option --controller <file>
Allow multiple cars. Simplest is 1 car of course.
Allow various configurations: no of floors, no of cars, set the seed, number of people to request, length of the simulator (no of steps),speed of simulation, size of each car, speed of each car, etc.
Maybe decouple simulator type, like have sub-classes of Simulator() class. For example we can have a random simulator, or say a morning one (where everybody is going from 1st floor up) or evening/lunch simulation, etc. This can be provided as a separate file via an option --simulation <file> for example.
Some graphical interface. Initially very simple
Track and provide statistics: no of people served, no of people not served, average waiting time per passenger, travel distance of each car
Maybe we should start slow with decoupling the existing system, which will serve us to understand well the system?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi @andresjarami
After our discussion today, here are some features we would like to eventually have:
Controller
class, or via the network by connection to a port (that is how the Java one is). This can be done via option--controller <file>
Simulator()
class. For example we can have a random simulator, or say a morning one (where everybody is going from 1st floor up) or evening/lunch simulation, etc. This can be provided as a separate file via an option--simulation <file>
for example.Maybe we should start slow with decoupling the existing system, which will serve us to understand well the system?
Beta Was this translation helpful? Give feedback.
All reactions