Re: [sumo-user] TracI-vehroute-output report

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

1) the routing mode is only used for subsequent calls to traci.vehicle.changeTarget or traci.vehicle.rerouteTraveltime.

2) I recommend observing the routes of that vehicle during the simulation while coloring th edges by 'routing device assumed speed' to better understand what is happening.

Am Di., 20. Aug. 2019 um 16:34 Uhr schrieb Raheleh Zarei <raheleh.zarei@xxxxxxxxx>:

1)How can I change the routing mode using TracI? I used the code below and changed the routing mode to AGGREGATED, but it didn’t change the traveltime in output file

step = 0

while traci.simulation.getMinExpectedNumber() > 0:

   net = sumolib.net.readNet('samp8.net.xml')

   edges = net.getEdges()

   routes = traci.route.getIDList()

   vehList = traci.vehicle.getIDList()

   routeTravelTime = {}

   for veh in vehList:

       traci.vehicle.setRoutingMode(veh, routingMode=1)

2) In vehroute-output report (in vehicleRoute1.txt file), route change of some vehicles is strange. (Regardless of what value we set for device.rerouting.probability option) For example, the vehicle id: "flow2.65" that has two routings, but it finally choose the route that is calculated at an earlier time. (choose the route in 175.00 step rather than earlier one 295).

Thanks

--

RAZ

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