fix(obstacle_cruise_planner): add separate parameters for cruise and stop margins #8166
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
Closes #7922
Related links
Parent Issue:
How was this PR tested?
Using scenario simulation
❗ Note ❗
In this previous scenario, the safe distance is updated to be 12.5 m following the 3-seconds inter-vehicle time-distance rule in performance requirements here
Before this PR:
2024-07-23.15-28-31.mp4
After this PR:
2024-07-23.15-02-16.mp4
Notes for reviewers
This PR depends on an autoware_launch PR
Interface changes
Topic changes
N.A
ROS Parameter Changes
Additions and removals
common.cruise_safe_distance_method
Modifications
common.safe_distance_method
common.stop_safe_distance_method
safe_distance_method
for stop purposescommon.terminal_safe_distance_margin
common.terminal_stop_safe_distance_margin
terminal_safe_distance_margin
Effects on system behavior
Improving
obstacle_cruise_planner
behavior in cruising scenarios, mitigating any mitigate any unnecessary long safe distance ego and npc and satisfying performance requirements