You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: planning/motion_velocity_planner/autoware_motion_velocity_planner_common/include/autoware_motion_velocity_planner_common/planner_data.hpp
- [Out of Lane](../behavior_velocity_out_of_lane_module/README.md)
24
-
25
-
When each module plans velocity, it considers based on `base_link`(center of rear-wheel axis) pose.
26
-
So for example, in order to stop at a stop line with the vehicles' front on the stop line, it calculates `base_link` position from the distance between `base_link` to front and modifies path velocity from the `base_link` position.
-[Out of Lane](../autoware_motion_velocity_out_of_lane_module/README.md)
11
+
12
+
Each module calculates stop and slow down points to be inserted in the ego trajectory.
13
+
These points are assumed to correspond to the `base_link` frame of the ego vehicle as it follows the trajectory.
14
+
This means that to stop before a wall, a stop point is inserted in the trajectory at a distance ahead of the wall equal to the vehicle front offset (wheelbase + front overhange, see the [vehicle dimensions](https://autowarefoundation.github.io/autoware-documentation/main/design/autoware-interfaces/components/vehicle-dimensions/).
| `~/input/compare_map_filtered_pointcloud` | sensor_msgs::msg::PointCloud2 | obstacle pointcloud filtered by compare map. Note that this is used only when the detection method of run out module is Points. |
40
-
| `~input/traffic_signals` | autoware_perception_msgs::msg::TrafficSignalArray | traffic light states |
-[vehicle info parameters](https://github.com/autowarefoundation/sample_vehicle_launch/blob/main/sample_vehicle_description/config/vehicle_info.param.yaml);
Copy file name to clipboardexpand all lines: planning/motion_velocity_planner/autoware_motion_velocity_planner_node/docs/BehaviorVelocityPlanner-Architecture.drawio.svg
Copy file name to clipboardexpand all lines: planning/motion_velocity_planner/autoware_motion_velocity_planner_node/docs/MotionVelocityPlanner-InternalInterface.drawio.svg
Copy file name to clipboardexpand all lines: planning/motion_velocity_planner/autoware_motion_velocity_planner_node/schema/motion_velocity_planner.schema.json
+3-59
Original file line number
Diff line number
Diff line change
@@ -5,64 +5,8 @@
5
5
"definitions": {
6
6
"behavior_velocity_planner": {
7
7
"type": "object",
8
-
"properties": {
9
-
"forward_path_length": {
10
-
"type": "number",
11
-
"default": "1000.0",
12
-
"description": "forward path"
13
-
},
14
-
"backward_path_length": {
15
-
"type": "number",
16
-
"default": "5.0",
17
-
"description": "backward path"
18
-
},
19
-
"behavior_output_path_interval": {
20
-
"type": "number",
21
-
"default": "1.0",
22
-
"description": "the output path will be interpolated by this interval"
23
-
},
24
-
"max_accel": {
25
-
"type": "number",
26
-
"default": "-2.8",
27
-
"description": "(to be a global parameter) max acceleration of the vehicle"
28
-
},
29
-
"system_delay": {
30
-
"type": "number",
31
-
"default": "0.5",
32
-
"description": "(to be a global parameter) delay time until output control command"
33
-
},
34
-
"delay_response_time": {
35
-
"type": "number",
36
-
"default": "0.5",
37
-
"description": "(to be a global parameter) delay time of the vehicle's response to control commands"
0 commit comments