-
Notifications
You must be signed in to change notification settings - Fork 691
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(obstacle_cruise_planner): ignore invalid stopping objects #10227
fix(obstacle_cruise_planner): ignore invalid stopping objects #10227
Conversation
Signed-off-by: Kento Yabuuchi <kento.yabuuchi.2@tier4.jp>
Signed-off-by: Kento Yabuuchi <kento.yabuuchi.2@tier4.jp>
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10227 +/- ##
==========================================
- Coverage 26.24% 26.23% -0.01%
==========================================
Files 1378 1378
Lines 107415 107448 +33
Branches 41411 41413 +2
==========================================
Hits 28189 28189
- Misses 76412 76445 +33
Partials 2814 2814
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Thank you for the PR!
The object type with is_outside_cruise_obstacle is for the object to follow.
In this PR's case, the object type you are going to change is not the object to follow. So can you define this additional object type in the yaml file like the following?
obstacle_filtering:
object_type:
inside:
unknown: true
car: true
truck: true
bus: true
trailer: true
motorcycle: true
bicycle: true
pedestrian: false
outside:
unknown: false
car: true
truck: true
bus: true
trailer: true
motorcycle: true
bicycle: false
pedestrian: false
blocking: # <- new: "blocking" is very confusing. Please think about a better name.
unknown: false
car: true
truck: true
bus: true
trailer: true
motorcycle: true
bicycle: false
pedestrian: false
…cts_with_not_not_designated_type
Signed-off-by: Kento Yabuuchi <kento.yabuuchi.2@tier4.jp>
@takayuki5168 Hi. I added the I couldn't come up with a better parameter name either. So if you have any suggestions for a more appropriate name, please let me know. 🙏 |
...ty_planner/autoware_motion_velocity_obstacle_cruise_module/config/obstacle_cruise.param.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Kento Yabuuchi <kento.yabuuchi.2@tier4.jp>
Thank you for the fix! |
Description
This PR modifies the conditions for obstacles that should be yielded to.
According to the README, stopping objects must meet the following three conditions:
obstacle_filtering.object_type.*
.yield.max_lat_dist_between_obstacles
.yield.max_lat_dist_between_obstacles
+yield.max_lat_dist_between_obstacles
.However, the current implementation does not check condition ① . 🧑🔧 This PR adds the missing condition ① to the filtering logic.
Note
🧑🔧 Additionally, I have added a filtering type for stopping objects.
Related links
autoware_launch PR
Private Links:
How was this PR tested?
planning_simulator.launch.xml + manual obstacle placing (rviz plugin)
✔️ Even after this change, the ego vehicle yielded when the specified type is ahead

planning_simulator.launch.xml + perception_reproducer
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.