Hello,
As a new user of SUMO, I am currently engaged in an experiment to study the bus bunching phenomena and assess the feasibility of implementing a Bus Priority Lane (BPL) within SUMO's simulation environment.
I have developed a sample network for this, considering two scenarios as follows.
- Base scenario without a bus lane
- BPL scenario with a bus lane
I have generated the stop_output as the output file to identify bus bunching. The "started" attribute has been considered in that file, to identify the time at which buses are arriving at a certain bus stop.
For the second scenario, the BPL has been activated via TraCI. However, the time recorded in the "started" attribute in stop_output here, is the same as the base scenario. When I compare it with the SUMO GUI, the time recorded in the stop_output is different from the observation of the simulation.
I have attached a screenshot illustrating the arrival of "BUS_40" at bus stop "bs_0". While the timestamp recorded in the "started" attribute of the stop_output file indicates 1031, the corresponding timestamp displayed in the SUMO GUI is 402.
Additionally, I attempted the BPL scenario without using TraCI by manually enabling the bus lane through the network file. >From this method, I have obtained two different stop_output files for the two scenarios. It displayed the accurate "started" attribute that matches the SUMO GUI.
The working folder containing all the generated stop_output files is attached herewith for your reference.
Kindly assist in resolving this matter to effectively employ TraCI to ensure the recording of accurate timestamps in the stop_output file, for the BPL scenario.
