You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the code in MSLink::getLeaderInfo assumes that links with a higher index are to the left of links with a lower index when computing conflicts between connections from the same lane.
An indirect left turn has a higher index but it's geometry is to the right of the straight movers.
might be better solved in netconvert by reordering the link indices so that the indirect left turn comes between right and straight connections.
Probably, we need a new connection attribute to guide the automatic geometry-computation and help with re-ordering.
Maybe a new link-direction code would also be helpful to provide better visualization and help with corner cases in the simulation code.
the code in MSLink::getLeaderInfo assumes that links with a higher index are to the left of links with a lower index when computing conflicts between connections from the same lane.
An indirect left turn has a higher index but it's geometry is to the right of the straight movers.
(somewhat related to #8500)
The text was updated successfully, but these errors were encountered: