Skip to content
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.

fix(behavior_velocity_planner): continue collision checking after pass judge #769

Merged
merged 2 commits into from
Feb 13, 2023
+1 −0
Merged

fix(behavior_velocity_planner): continue collision checking after pass judge #769

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7d72de7
fix(behavior_velocity_planner): revert part of #2719
soblin Feb 10, 2023
c3b9cab
Merge branch 'awf-latest' into fix/pr2700
soblin Feb 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...planning/lane_driving/behavior_planning/behavior_velocity_planner/intersection.param.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@
intersection:
state_transit_margin_time: 1.0
stop_line_margin: 3.0
keep_detection_vel_thr: 0.833 # == 3.0km/h. keep detection if ego is ego.vel < keep_detection_vel_thr
stuck_vehicle_detect_dist: 3.0 # this should be the length between cars when they are stopped. The actual stuck vehicle detection length will be this value + vehicle_length.
stuck_vehicle_ignore_dist: 10.0 # obstacle stop max distance(5.0m) + stuck vehicle size / 2 (0.0m-)
stuck_vehicle_vel_thr: 0.833 # 0.833m/s = 3.0km/h
Expand Down