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

fixed CostMatrix shapes for routes against trivial oneways #4633

Merged
merged 2 commits into from Mar 18, 2024

Conversation

nilsnolde
Copy link
Member

Comment on lines -1247 to -1248
auto is_first_edge = path_edge == path_edges.front();
auto is_last_edge = path_edge == path_edges.back();
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for the case of seemingly trivial routes which go against the oneway, both of these are true and then further down it'd trim the shape according to a trivial route which is not doing the right thing to do. we have to do this index based to really tell if it's the first/last edge.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah these needed to be pointer comparison not equality operator

@nilsnolde nilsnolde merged commit b6bad37 into master Mar 18, 2024
8 of 9 checks passed
@nilsnolde nilsnolde deleted the nn-matrix-shape-fix branch March 18, 2024 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

costmatrix algorithm do not respect oneway on trivial routes
2 participants