search

eclipse-sumo / sumo

Eclipse SUMO is an open source, highly portable, microscopic and continuous traffic simulation package designed to handle large networks. It allows for intermodal simulation including pedestrians and comes with a large set of tools for scenario creation.
https://eclipse.dev/sumo
Eclipse Public License 2.0
2.38k stars 1.37k forks source link

strategically invalid keepRight change after waiting at red light (trac #2317) #2317

Open behrisch opened 8 years ago

behrisch commented 8 years ago

Observed in test sumo/extended/electric/braunschweig between times t=100 and t=110 by vehicle "vehWithBusStop". Perhaps caused by some conflicting interaction of preference for using the right lane and tendency to use the best lane for route continuation?

Migrated from http://sumo.dlr.de/ticket/2317

{
    "status": "assigned", 
    "changetime": "2016-10-26T12:34:29Z", 
    "description": "Observed in test {{{sumo/extended/electric/braunschweig}}} between times t=100 and t=110 by vehicle \"vehWithBusStop\".\nPerhaps caused by some conflicting interaction of preference for using the right lane and tendency to use the best lane for route continuation?", 
    "reporter": "leo", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1477485269885488", 
    "component": "microsim - lane change", 
    "summary": "strategically invalid keepRight change after waiting at red light", 
    "priority": "major", 
    "keywords": "", 
    "time": "2016-05-12T07:44:52Z", 
    "milestone": "1.0.0", 
    "owner": "namdre", 
    "type": "defect"
}
behrisch commented 8 years ago

@namdre commented:

lookAheadSpeed is unduly influenced when waiting in front of a traffic light. Solution would be to detect this kind of situation (back propagation along the waiting queue?) and not adapt lookAheadSpeed in this case.

behrisch commented 8 years ago

@namdre changed summary from "Strange lanechanging behavior" to "strategically invalid keepRight change after waiting at red light"

behrisch commented 8 years ago
behrisch commented 8 years ago

@namdre changed milestone from "0.28.0" to "0.29.0"