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

fix(tier4_perception_launch): update multi-channel subscribing channel name to lidar_detection_model_type #9624

Conversation

technolojin
Copy link
Contributor

Description

The object detection channels in the tracking.launch.xml file have been updated to use the lidar detection model type.

Implementing changes by PR #9003

This PR do not contain logic change.

Related links

Parent Issue:

  • Link

How was this PR tested?

set parameters as following

  • use_multi_channel_tracker_merger true
  • lidar_detection_model centerpoint/centerpoint_tiny

Notes for reviewers

None.

Interface changes

None.

Effects on system behavior

None.

The object detection channels in the `tracking.launch.xml` file have been updated to include the lidar detection model type.

Signed-off-by: Taekjin LEE <taekjin.lee@tier4.jp>
@technolojin technolojin self-assigned this Dec 12, 2024
@github-actions github-actions bot added the component:launch Launch files, scripts and initialization tools. (auto-assigned) label Dec 12, 2024
Copy link

github-actions bot commented Dec 12, 2024

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

@technolojin technolojin marked this pull request as ready for review December 12, 2024 01:48
@technolojin technolojin changed the title feat: update object detection channels in tracking.launch.xml fix: update multi-channel subscribing channel name to lidar detection type Dec 12, 2024
@technolojin technolojin changed the title fix: update multi-channel subscribing channel name to lidar detection type fix(tier4_perception_launch): update multi-channel subscribing channel name to lidar detection type Dec 12, 2024
@technolojin technolojin changed the title fix(tier4_perception_launch): update multi-channel subscribing channel name to lidar detection type fix(tier4_perception_launch): update multi-channel subscribing channel name to lidar_detection_model_type Dec 12, 2024
@technolojin technolojin added the run:build-and-test-differential Mark to enable build-and-test-differential workflow. (used-by-ci) label Dec 12, 2024
Copy link
Contributor

@yukkysaito yukkysaito left a comment

Choose a reason for hiding this comment

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

@YoshiRi The change itself looks good, but I haven’t been able to check the coding style or detailed logic. Could I ask you to review those?

Copy link
Contributor

@YoshiRi YoshiRi left a comment

Choose a reason for hiding this comment

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

Here is trivial comment. Since we normally use validation it won't effect most projects.

add variable use_validator to the tracking launch and determine the subscribing channel depends on the use_validator value

Signed-off-by: Taekjin LEE <taekjin.lee@tier4.jp>
@technolojin technolojin requested a review from YoshiRi December 12, 2024 02:56
Copy link
Contributor

@YoshiRi YoshiRi left a comment

Choose a reason for hiding this comment

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

LGTM

@technolojin technolojin merged commit 3c94dbf into autowarefoundation:main Dec 12, 2024
27 checks passed
@technolojin technolojin deleted the fix/tier4-perception-launch/tracking-lidar-detector-type branch December 12, 2024 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:launch Launch files, scripts and initialization tools. (auto-assigned) run:build-and-test-differential Mark to enable build-and-test-differential workflow. (used-by-ci)
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants