Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: crossing indices with edges are not realistic in every case #32

Open
dominicparga opened this issue May 27, 2017 · 0 comments
Open
Labels

Comments

@dominicparga
Copy link
Collaborator

dominicparga commented May 27, 2017

Example:
===>( )===>
===>( )===>
....... (+)===>
........ |

In the case above, we have 3 incoming and 3 leaving lanes. According to our parser, we set 1 crossroad (marked via brackets), because we have an edge from left with 2 lanes and an edge from bottom with 1 lane. Due to our crossing logic (using indices for every edge, not lane), vehicles from the left edge have to give priority to the bottom vehicle if right-before-left holds, but every vehicle could drive without intersection if lane mapping would be correct.

We can't fix this easily because we'd like to avoid storing vehicle's current lane info in a node (<=> crossroad).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant