eclipse-sumo
Gridlocks in roundabouts
Hi all,
I came across several occurrences of grid-locks in roundabouts.
As mentioned here
https://sumo.dlr.de/docs/Simulation/Why_Vehicles_are_teleporting.html
this is not uncommon. The priorities within the roundabout are correct. The cars within the roundabout edges positioned at the end of each of their respective edge want to exit the roundabout at an exit that is not their nearest exit. However since the next edge is at full capacity they cannot move onwards. I suspect this is the reason for the gridlock. Adding the command --time-to-teleport 5 (or any other small number) resolves this problem both in meso and micro.
My questions:
(1) I was wondering whether it would be possible to add a command of the sort --time-to-teleport.roundabout, that is vehicles are only teleported if they get stuck on such roundabout edges? (I think this would be in the same spirit as --time-to-teleport.bidi, right?)
(2) Or allowing even more freedom: would it be possible to pass a list of edges on which vehicles would be teleported if they get stuck?
(3) Are there other ways of dealing with gridlock, apart from those mentioned here in the documentation (https://sumo.dlr.de/docs/Simulation/Why_Vehicles_are_teleporting.html)?
SUMO-version: 1.18
operating system: Mac
Thanks so much!!
As the exit edges are uncongested, there must be some problem with at least one vehicle inside the roundabout. Would you be willing to share your simulation scenario here on Github? You can attach a zip archive to your post.
Sure, thanks for the quick reply. The gridlocks start at around 16:30, and the junction of interest is the roundabout that includes junction:2276702444.
My guess is that due to the high demand, the edges within the junction are filled, and since no one wants to exit at their nearest exit, the gridlock occurs.
Thanks a lot!
hi @behrisch, this is kind of an important issue for us. given that @m-kro looked into https://github.com/eclipse-sumo/sumo/issues/13970 I thought maybe there is something going on this front as well :) Any ideas on a workaround for this, would be very helpful. Many thanks as always!
