-
Notifications
You must be signed in to change notification settings - Fork 658
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
docs(traffic light recognition): update documents #6724
base: main
Are you sure you want to change the base?
Conversation
| `~/input/car/traffic_signals` | tier4_perception_msgs::msg::TrafficLightArray | vehicular traffic light signals | | ||
| `~/input/pedestrian/traffic_signals` | tier4_perception_msgs::msg::TrafficLightArray | pedestrian traffic light signals | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are discussing to unify in the direction of Traffic Light instead of Traffic Signal, so could you please change it to light? cc @mitsudome-r
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do the names of topics need to change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yukkysaito Friendly ping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tzhong518
I agree with what @yukkysaito said, that since we've changed all the traffic signal types to traffic light types, we should also change the topic name accordingly.
In this PR, or split into separate PRs, would it be possible for you to resolve the issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I apologize for the delay. Here are the options I believe we have. If it's not urgent, since it only affects the documentation, may I choose the first option?
- Pause this PR until the migration is complete on June 1st.
- Include it in the autoware_msgs branch.
- Merge this PR now and make the necessary adjustments after the migration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tzhong518
Thank you for the update!
As mentioned here, could you resolve the inconsistency between the topic name and the type?
@tzhong518 Memo: Need to update the message name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tzhong518 |
Signed-off-by: tzhong518 <[email protected]>
Signed-off-by: tzhong518 <[email protected]>
Signed-off-by: tzhong518 <[email protected]>
Signed-off-by: tzhong518 <[email protected]>
Co-authored-by: Dmitrii Koldaev <[email protected]>
Signed-off-by: tzhong518 <[email protected]>
5f755bd
to
0163497
Compare
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Signed-off-by: tzhong518 <[email protected]>
…iverse into doc/pedestrian_tlr
Signed-off-by: tzhong518 <[email protected]>
Signed-off-by: tzhong518 <[email protected]>
…iverse into doc/pedestrian_tlr
Signed-off-by: tzhong518 <[email protected]>
Signed-off-by: tzhong518 <[email protected]>
Description
Documentation update and topic name change.
Please also pull this PR when testing: https://github.com/tier4/autoware_launch.xx1/pull/1042
Related links
Tests performed
Notes for reviewers
Interface changes
Effects on system behavior
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.
After all checkboxes are checked, anyone who has write access can merge the PR.