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
Stop points are an exception in Starling, as they are stored in the agent population as if they were agents. They are stored here because it is convenient to have the global collection of stop points instead of each operator having its collection of stops.
Solution proposed
It could be useful to make StopPoint inherit from SpatialAgent. They are not so different from stations, and could even also use a SimPy store for their agent queues.
It would also allow tracing events for stop points and compute specific KPIs.
This implies many modifications on how stop points are managed, at many different points in Starling.
The text was updated successfully, but these errors were encountered:
Problem exposition
Stop points are an exception in Starling, as they are stored in the agent population as if they were agents. They are stored here because it is convenient to have the global collection of stop points instead of each operator having its collection of stops.
Solution proposed
It could be useful to make StopPoint inherit from SpatialAgent. They are not so different from stations, and could even also use a SimPy store for their agent queues.
It would also allow tracing events for stop points and compute specific KPIs.
This implies many modifications on how stop points are managed, at many different points in Starling.
The text was updated successfully, but these errors were encountered: