-
Notifications
You must be signed in to change notification settings - Fork 650
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(behavior_path_planner): output multiple candidate paths #2486
feat(behavior_path_planner): output multiple candidate paths #2486
Conversation
Codecov ReportBase: 10.54% // Head: 10.44% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #2486 +/- ##
==========================================
- Coverage 10.54% 10.44% -0.11%
==========================================
Files 1266 1266
Lines 87648 88513 +865
Branches 20937 21567 +630
==========================================
+ Hits 9242 9243 +1
- Misses 68543 69341 +798
- Partials 9863 9929 +66
*This pull request uses carry forward flags. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
085a68f
to
22fdbec
Compare
TIER IV internal test has been finished. |
.../behavior_path_planner/include/behavior_path_planner/scene_module/scene_module_interface.hpp
Outdated
Show resolved
Hide resolved
Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
22fdbec
to
74a8977
Compare
Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
…havior tree manager Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
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.
LGTM!!
@@ -68,7 +68,7 @@ BT::NodeStatus SceneModuleBTNodeInterface::tick() | |||
// std::exit(EXIT_FAILURE); // TODO(Horibe) do appropriate handing | |||
} | |||
scene_module_->unlockRTCCommand(); | |||
return BT::NodeStatus::SUCCESS; |
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.
@rej55
what is this change for?
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.
…efoundation#2486) * feat(behavior_path_planner): output multiple candidate paths Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> * feat(behavior_path_planner): get path candidate in behavior tree manager Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> * feature(behavior_path_planner): add create publisher method Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> * feature(behavior_path_planner): move publishers to node Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> * feature(behavior_path_planner): remove unnecessary publisher Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> * feat(behavior_path_planner): move reset path candidate function to behavior tree manager Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com> Signed-off-by: kminoda <koji.minoda@tier4.jp>
Signed-off-by: Fumiya Watanabe rej55.g@gmail.com
Description
In the future, multiple modules in behavior_path_planner will be run.
To handle this, in this change, I change behavior_path_planner to output multiple candidate paths.
In this change, the name space of candidate path topics is also changed.
Before:
/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/output/path_candidate
After:
/planning/path_candidate/**
Furthermore, it also outputs multiple RTC status.
So, it becomes able to receive RTC commands if the modules request.
Related links
Tests performed
Tested in the planning simulator.
See also autowarefoundation/autoware_launch#125
Lane change & Avoidance
Pull out & Avoidance
Pull over & Avoidance
Notes for reviewers
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.