Re: [sumo-user] rerouteTravelTime

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Hello,

- setVia does not change the route but only affects future routing

- if you use setVia before changeTarget, it should be taken into account (it calls reroute internally)

- if you call traci.vehicle.rerouteTravelTime it sets  the argument currentTravelTimes=True by default. This caues the routing speeds of all edges to be updated to their current speeds (to take jams into account) but this updating can be a major slowdown in larget networks. You can avoid this by calling vehicle.rerouteTravelTime(vehID, False). 

regards,

Jakob

2018-07-25 17:15 GMT+02:00 Stefano Niero <stefano.niero@xxxxxxxxxx>:

Hi,

I am having problems using the command rerouteTravelTime since it slows down massively my simulation. I have to change the target of a vehicle using TraCI but before it reaches the target I want to make it pass via an intermediate edge where it has to make a quick stop. Initially for some reason I don’t know the command setVia did not work but I noticed that using the command rerouteTravelTime at the same instant, the line immediately after setVia the command was effective. Now, since this reroute calculation is really affecting the performance of my simulation I tried to comment it in order to see what happens without it. I notice that apparently and in a small scenario nothing changes so I would like to ask you: is the use of this command necessary when I want to set a via edge? What is the difference I get in the output if I don’t use this command considering that the command is used at the same timestep in which the new target and the via are set?

 

Thank you very much

Stefano Niero

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user