feat(planning_factor): support new cruise planner's factor #10229
+6
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a conversion for a new planning_factor.
background
Recently,
obstacle_cruise_planner
andobstacle_stop_planner
can be launched as modules ofmotion_velocity_planner
instead of as standalone nodes. (The traditional nodes can still be launched.)⛓️ reference: Split obstacle_cruise_planner to obstacle stop, slow_down, and cruise, and port them to motion_velocity_planer
With this change, a new planning_factor for obstacle_cruise/stop/slowdown_planner has been added.
Related links
Parent Issue:
How was this PR tested?
I launched planning_simulator.launch.xml and checked the subscriber of
/adapi/node/planning
.The new planning_factors can be found by
ros2 node info /planning/scenario_planning/lane_driving/motion_planning/motion_velocity_planner
.Notes for reviewers
None.
Interface changes
None.
Effects on system behavior