|Re: [sumo-user] Simulation Step TraCI call at time 0|
Thanks Jakob, but I am more confused now.
Consider these two cases:
Case 1: When I call SimulationStep starting from 0:
- SimulationStep (0) --> advance simulation to the end of step 0 and simulationGetTime is now 500ms
- SimulationStep (500) --> advance simulation to the end of step 500ms and simulationGetTime is now 1000ms.
and so on…
Case 2: Now, consider the case that I call SimulationStep starting from 500ms:
- SimulationStep (500) --> advance simulation to the end of step 500, but simulationGetTime still shows 500ms
- SimulationStep (1000) --> advance simulation to the end of step 1000ms, but simulationGetTime still shows 1000ms.
and so on…
Moreover, I can explain case 1 with the WiKi:
In case 1, calling SimulationStep (500) should not advance the SUMO simulation cause the target time is smaller or equal to the current simulation step. right?
From: Jakob Erdmann [mailto:namdre.sumo@xxxxxxxxxxxxxx]
when you take a look at the gui, you will find that the first call of
simulationStep(0) advances the simulation to the end of step 0 (with vehicles departing at 0 already being inserted).
Only the command simulation.getCurrentTime() already shows you 0.5 because all further traci calls will be processed at the start of the step that ends at 0.5
However, any vehicle positions you retrieve after the first call to simulationStep will be the ones from the insertion step 0.
2017-09-26 10:35 GMT+02:00 Mani Amoozadeh via sumo-user <sumo-user@xxxxxxxxxxxxxxxxxxxxx>:
Back to the top