Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] TraCI rerouteEffort output behaviour
1) No. You could initialize the  edge weights for the rerouting device with pre-computed effort data from an xml file (--device.rerouting.init-with-loaded-weights) and then prevent updating by setting --device.rerouting.adaptation-interval 0
2) If you load <trip> or <flow from="..." to="..." ../> directly into sumo you will get rerouting once on departure. If the vehicle cannot enter the network for some time due to jamming it will reroute again (default period 60s).  Repeated rerouting after departure should  only happen when option  --device.reroutiong.period is set

regards,
Jakob

Am Di., 19. März 2019 um 15:24 Uhr schrieb Toby Cannon <tobycannon50@xxxxxxxxx>:
I think in my case the latter explains this behaviour, thanks for your help.

Within this file a few of the vehicles that don't have reason="traci:rerouteEffort" seem to have reason="device.rerouting" listed a few times, indicating that during the trips they are being rerouted multiple times. I have a couple of questions:
1) Is this rerouting them based on effort? If not, is this possible?
2) What's causing the vehicles to reroute? Are there set trigger points? I have read the web page on automatic routing and have not set / changed any of the rerouting settings.

If anyone could shed some light on how this works I'd be very grateful.

On Tue, Mar 19, 2019 at 6:54 AM Jakob Erdmann <namdre.sumo@xxxxxxxxx> wrote:
here are things that might explain the symptoms
- if the departure times are fractional (can easily happen when running randomTrips.py) wheras the simultion steps are integer (the default) then the equality condition will often fail
- if the original route equals the route computed by rerouteEffort, no rerouting will take place and thus no trac:rerouteEffort is recorded

regards,
Jakob


Am Mo., 18. März 2019 um 14:15 Uhr schrieb Toby Cannon <tobycannon50@xxxxxxxxx>:
Hi SUMO users,
I'm attempting to reroute all vehicles by effort on the first step they enter the simulation.
I have a list of 273 trips, however, in the vehicle output file only around 50 or so are showing reason="traci:rerouteEffort" in their route element.

A basic version of my code is below:
tripInfo is an array consisting of id and depart times for each vehicle [[id, depart], [id, depart]...]
(I've checked tripInfo and there are 273 elements in this as there should be)

while traci.simulation.getMinExpectedNumber() > 0:
        for vehicle in tripInfo:
            if (vehicle[1] +1 == traci.simulation.getTime()): 
                traci.vehicle.rerouteEffort(vehicle[0])
        traci.simulationStep()
traci.close()

Does anyone have any idea on why reason="traci:rerouteEffort" is not being shown for all 273 vehicles?

Many thanks,
Toby
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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

Back to the top