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

feat(autoware_launch): no slow down against unknown object #428

Merged

Conversation

takayuki5168
Copy link
Contributor

@takayuki5168 takayuki5168 commented Jun 30, 2023

Description

Currently, the leaves of trees are recognized as unknown objects in some cases, resulting in slowdown by obstacle_cruise_planner.
To suppress this unnecessary slowdown, I set a default slow down feature for unknown object false.

Tests performed

planning simulator

Effects on system behavior

No slow down against unknown object

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.

@takayuki5168 takayuki5168 marked this pull request as ready for review June 30, 2023 16:21
@tkimura4 tkimura4 merged commit 5b23f16 into autowarefoundation:main Jun 30, 2023
@tkimura4 tkimura4 deleted the feat/no-slow-down-for-unknown branch June 30, 2023 16:44
kyoichi-sugahara pushed a commit that referenced this pull request Sep 3, 2023
badai-nguyen pushed a commit to badai-nguyen/autoware_launch that referenced this pull request Sep 21, 2023
maxime-clem pushed a commit to maxime-clem/autoware_launch that referenced this pull request Jun 13, 2024
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.

2 participants