Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

fix(lanelet2_extension): improve traffic regulatory element id visualization #225

Merged
merged 5 commits into from
Jan 10, 2024

Conversation

satoshi-ota
Copy link
Contributor

@satoshi-ota satoshi-ota commented Jan 5, 2024

Description

It was difficult to understand relationship between regulatry element id and road lanelet. In this PR, I fixed id visualization to show the id on stop line which is reffered by traffic regulatory element in order to make it easier to know related regulatory elements.

image
image

Tests performed

Psim

Effects on system behavior

Nothing.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

  • There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

…ization

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Copy link

codecov bot commented Jan 5, 2024

Codecov Report

Attention: 47 lines in your changes are missing coverage. Please review.

Comparison is base (6bbda65) 11.26% compared to head (15782bd) 11.11%.

Files Patch % Lines
tmp/lanelet2_extension/lib/visualization.cpp 0.00% 47 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #225      +/-   ##
==========================================
- Coverage   11.26%   11.11%   -0.16%     
==========================================
  Files          37       37              
  Lines        2671     2709      +38     
  Branches     1370     1387      +17     
==========================================
  Hits          301      301              
- Misses       1950     1987      +37     
- Partials      420      421       +1     
Flag Coverage Δ *Carryforward flag
differential 9.46% <0.00%> (?)
total 11.36% <ø> (+0.09%) ⬆️ Carriedforward from ccc3293

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@satoshi-ota satoshi-ota marked this pull request as ready for review January 8, 2024 23:57
Copy link
Contributor

@shmpwk shmpwk left a comment

Choose a reason for hiding this comment

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

LGTM

@mitsudome-r
Copy link
Member

Could you explain a bit more detail on why you want to move the text to stopline? In general, if you want to know the link between lanelet, stopline, and the traffic light, then using vector map builder would be a better option. Are there any particular reasons why you want to see it on RVIZ? Also, even if you can get the id of the traffic light regulatory element at the stopline, you can't really know which traffic light is linked to the road anyways.

Here are some alternative ideas that I can think of depending on your use case.

  • If you want to know the regulatory element id that causing the vehicle to stop, maybe we can add regulatory element id with the debug marker published by behavior_velocity_planner.
  • If you just want to visualize the connection between the road and traffic light in general, adding some linestrip that connects the stopline and the traffic light marker might be better.

@satoshi-ota
Copy link
Contributor Author

@mitsudome-r Thanks for your comment.

In general, if you want to know the link between lanelet, stopline, and the traffic light, then using vector map builder would be a better option. Are there any particular reasons why you want to see it on RVIZ?

Yes. Sometimes we developper use this rviz plugin in order to check the behavior for traffic signals, and I think it is convenient for us to show the related traffic light regualtory element ID on rviz.

Also, even if you can get the id of the traffic light regulatory element at the stopline, you can't really know which traffic light is linked to the road anyways.

I see. Then, I'll fix the logic so that it can show exact relation between road lanelet and traffic light regulatory elements.

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
@satoshi-ota
Copy link
Contributor Author

satoshi-ota commented Jan 9, 2024

@mitsudome-r Thanks for your comment.

In general, if you want to know the link between lanelet, stopline, and the traffic light, then using vector map builder would be a better option. Are there any particular reasons why you want to see it on RVIZ?

Yes. Sometimes we developper use this rviz plugin in order to check the behavior for traffic signals, and I think it is convenient for us to show the related traffic light regualtory element ID on rviz.

Also, even if you can get the id of the traffic light regulatory element at the stopline, you can't really know which traffic light is linked to the road anyways.

I see. Then, I'll fix the logic so that it can show exact relation between road lanelet and traffic light regulatory elements.

@mitsudome-r I fixed implementation to show exact related traffic reg elem ID in cebfe7b.

And, please check autowarefoundation/autoware.universe#6028.

image

@mitsudome-r
Copy link
Member

@satoshi-ota Thanks for the reply. I am okay with the change then.

@satoshi-ota
Copy link
Contributor Author

@mitsudome-r Thank you. I'll merge this PR with autowarefoundation/autoware.universe#6028.

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
@mitsudome-r mitsudome-r merged commit 829464c into autowarefoundation:main Jan 10, 2024
16 of 18 checks passed
satoshi-ota added a commit to tier4/autoware_common that referenced this pull request Jan 17, 2024
…ization (autowarefoundation#225)

* fix(lanelet2_extension): improve traffic regulatory element id visualization

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>

* fix(lanelet2_extension): show exact relation

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>

* feat(lanelet2_extension): show traffic light id

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>

* fix: typo

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>

* fix(lanelet2_extension): remove whitespace

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>

---------

Signed-off-by: satoshi-ota <satoshi.ota928@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants