diff --git a/docs/community/support/troubleshooting/index.md b/docs/community/support/troubleshooting/index.md index 52a0541355c..ff296250544 100644 --- a/docs/community/support/troubleshooting/index.md +++ b/docs/community/support/troubleshooting/index.md @@ -192,7 +192,7 @@ If you have any of these symptoms, please the [Performance Troubleshooting](perf ### Map does not display when running the Planning Simulator -When running the Planning Simulator, the most common reason for the map not being displayed in RViz is because [the map path has not been specified correctly in the launch command](../../../demos/planning-simulation.md#lane-driving-scenario). You can confirm if this is the case by searching for `Could not find lanelet map under {path-to-map-dir}/lanelet2_map.osm` errors in the log. +When running the Planning Simulator, the most common reason for the map not being displayed in RViz is because [the map path has not been specified correctly in the launch command](../../../demos/planning-sim/lane-driving.md). You can confirm if this is the case by searching for `Could not find lanelet map under {path-to-map-dir}/lanelet2_map.osm` errors in the log. Another possible reason is that map loading is taking a long time due to poor DDS performance. For this, please visit the [Performance Troubleshooting](performance-troubleshooting.md) page. @@ -208,7 +208,7 @@ colcon build --cmake-args -DCMAKE_BUILD_TYPE=Debug --packages-up-to B{"Pedestrian somewhere on the **crosswalk**?
(Pedestrian velocity is not important.)"} + B -- "No" --> C["Proceed without slowing down"] + B -- "Yes" --> D["Slow down and stop **one time**"] + D --> E["Wait a few seconds to confirm safe to proceed"] + E --> F{"Pedestrian or object on **planned path**?"} + F -- "Yes" --> G["Continue waiting / yield"] + F -- "No" --> H["Resume driving (will not stop again for this crosswalk)"] + H --> I["Crosswalk passed ➡️ behavior resets when encountering the same crosswalk again"] +``` + +!!! example "Experiment" + + We will test the expected “single stop then go” behavior: + + 1. Place a still dummy pedestrian on the crosswalk. (Not on the planned path, just on the crosswalk.) + + 2. The ego vehicle will decelerate and stop before the crosswalk. + + 3. After waiting for a few seconds, the ego vehicle will start driving again as usual. + +1. Set an initial pose and a goal pose for the ego vehicle to drive through a non-signalized crosswalk. A path will be planned. + + ![initial-setup](images/passing-crosswalk/non-signalized/initial-setup.png) + +2. Place an interactive dummy pedestrian on the crosswalk and set its pose as if it is crossing the street. It doesn't matter whether the dummy pedestrian is moving or not, as long as it is on the crosswalk. + + ![place-pedestrian](images/passing-crosswalk/non-signalized/place-pedestrian.png) + +3. Engage the ego vehicle by clicking on `Auto`. The ego vehicle will decelerate and stop before the crosswalk. The marked **crosswalk** in the figure indicates that the stopping behavior is caused by the objects on the **crosswalk**. + + ![wait-before-crosswalk](images/passing-crosswalk/non-signalized/wait-before-crosswalk.png) + +4. The ego vehicle will wait for about a few seconds. Then it will start moving again and pass the crosswalk. + + ![pass-crosswalk](images/passing-crosswalk/non-signalized/pass-crosswalk.png) + +## Signalized crosswalk (with traffic light) + +
+ ![test-location.png](images/passing-crosswalk/signalized/test-location.png) +
Location for signalized crosswalk experiments
+
+ +!!! example "Experiment 1: Pedestrian Present While Traffic Light Is GREEN" + + This experiment mirrors the previous one but at a signalized crosswalk. + +With the pedestrian near the path and the traffic light **GREEN**, the ego behaves **the same as at a non-signalized crosswalk**: +it slows, stops, waits, then continues. + +![wait-for-pedestrian](images/passing-crosswalk/signalized/wait-for-pedestrian.png) + +!!! example "Experiment 2: Interaction of Pedestrians and a RED Traffic Light" + + 1. Stop before the crosswalk when the traffic light is set to `RED`. (Without pedestrians.) + + 2. Add a dummy pedestrian on the crosswalk while the traffic light is `RED`. (Both the traffic light and the crosswalk should affect the stopping behavior.) + + 3. Finally, set the traffic light to `GREEN` again and the vehicle will pass normally. + +1. **Stop at red (no pedestrians).** + Remove any existing dummy pedestrians and set the traffic light to **RED**. + The ego vehicle will stop before the crosswalk and wait solely because of the **traffic_light** reason. + + ![stop-from-red-light](images/passing-crosswalk/signalized/stop-from-red-light.png) + +2. **Add a pedestrian while the light is RED.** + The ego remains stopped, now influenced by **both** the traffic light and the crosswalk object. + + ![stop-from-red-and-pedestrian](images/passing-crosswalk/signalized/stop-from-red-and-pedestrian.png) + +3. **Observe how the stop reasons update.** + After a short period, only **traffic_light** may remain displayed. + Moving the pedestrian slightly (with ++shift+"🖱️ Right Click"++ drag) reintroduces both markers, but the system stabilizes back to the traffic-light reason during the wait. + + ![stop-red-light-with-pedestrian.png](images/passing-crosswalk/signalized/stop-red-light-with-pedestrian.png) + +4. **Switch the light to GREEN.** + When set to green and `Auto` mode is engaged, the ego vehicle proceeds normally. + + ![move-after-red-to-green.png](images/passing-crosswalk/signalized/move-after-red-to-green.png) diff --git a/docs/demos/images/planning/avoidance/avoidance-driving.png b/docs/demos/planning-sim/images/avoidance/avoidance-driving.png similarity index 100% rename from docs/demos/images/planning/avoidance/avoidance-driving.png rename to docs/demos/planning-sim/images/avoidance/avoidance-driving.png diff --git a/docs/demos/images/planning/avoidance/set-dummy-bus.png b/docs/demos/planning-sim/images/avoidance/set-dummy-bus.png similarity index 100% rename from docs/demos/images/planning/avoidance/set-dummy-bus.png rename to docs/demos/planning-sim/images/avoidance/set-dummy-bus.png diff --git a/docs/demos/images/planning/avoidance/set-position-and-goal.png b/docs/demos/planning-sim/images/avoidance/set-position-and-goal.png similarity index 100% rename from docs/demos/images/planning/avoidance/set-position-and-goal.png rename to docs/demos/planning-sim/images/avoidance/set-position-and-goal.png diff --git a/docs/demos/images/planning/lane-change/lane-changing.png b/docs/demos/planning-sim/images/lane-change/lane-changing.png similarity index 100% rename from docs/demos/images/planning/lane-change/lane-changing.png rename to docs/demos/planning-sim/images/lane-change/lane-changing.png diff --git a/docs/demos/images/planning/lane-change/open-nishishinjuku-map.png b/docs/demos/planning-sim/images/lane-change/open-nishishinjuku-map.png similarity index 100% rename from docs/demos/images/planning/lane-change/open-nishishinjuku-map.png rename to docs/demos/planning-sim/images/lane-change/open-nishishinjuku-map.png diff --git a/docs/demos/images/planning/lane-change/set-position-and-goal.png b/docs/demos/planning-sim/images/lane-change/set-position-and-goal.png similarity index 100% rename from docs/demos/images/planning/lane-change/set-position-and-goal.png rename to docs/demos/planning-sim/images/lane-change/set-position-and-goal.png diff --git a/docs/demos/images/planning/lane-following/after-autoware-launch.png b/docs/demos/planning-sim/images/lane-following/after-autoware-launch.png similarity index 100% rename from docs/demos/images/planning/lane-following/after-autoware-launch.png rename to docs/demos/planning-sim/images/lane-following/after-autoware-launch.png diff --git a/docs/demos/images/planning/lane-following/check-interactive.png b/docs/demos/planning-sim/images/lane-following/check-interactive.png similarity index 100% rename from docs/demos/images/planning/lane-following/check-interactive.png rename to docs/demos/planning-sim/images/lane-following/check-interactive.png diff --git a/docs/demos/images/planning/lane-following/place-dummy-car.png b/docs/demos/planning-sim/images/lane-following/place-dummy-car.png similarity index 100% rename from docs/demos/images/planning/lane-following/place-dummy-car.png rename to docs/demos/planning-sim/images/lane-following/place-dummy-car.png diff --git a/docs/demos/images/planning/lane-following/set-goal-pose.png b/docs/demos/planning-sim/images/lane-following/set-goal-pose.png similarity index 100% rename from docs/demos/images/planning/lane-following/set-goal-pose.png rename to docs/demos/planning-sim/images/lane-following/set-goal-pose.png diff --git a/docs/demos/images/planning/lane-following/set-initial-pose.png b/docs/demos/planning-sim/images/lane-following/set-initial-pose.png similarity index 100% rename from docs/demos/images/planning/lane-following/set-initial-pose.png rename to docs/demos/planning-sim/images/lane-following/set-initial-pose.png diff --git a/docs/demos/images/planning/lane-following/start-driving.png b/docs/demos/planning-sim/images/lane-following/start-driving.png similarity index 100% rename from docs/demos/images/planning/lane-following/start-driving.png rename to docs/demos/planning-sim/images/lane-following/start-driving.png diff --git a/docs/demos/images/planning/launch-gui/customizing-parameters1.png b/docs/demos/planning-sim/images/launch-gui/customizing-parameters1.png similarity index 100% rename from docs/demos/images/planning/launch-gui/customizing-parameters1.png rename to docs/demos/planning-sim/images/launch-gui/customizing-parameters1.png diff --git a/docs/demos/images/planning/launch-gui/customizing-parameters2.png b/docs/demos/planning-sim/images/launch-gui/customizing-parameters2.png similarity index 100% rename from docs/demos/images/planning/launch-gui/customizing-parameters2.png rename to docs/demos/planning-sim/images/launch-gui/customizing-parameters2.png diff --git a/docs/demos/images/planning/launch-gui/launch_gui_main.png b/docs/demos/planning-sim/images/launch-gui/launch_gui_main.png similarity index 100% rename from docs/demos/images/planning/launch-gui/launch_gui_main.png rename to docs/demos/planning-sim/images/launch-gui/launch_gui_main.png diff --git a/docs/demos/images/planning/launch-gui/launch_gui_setup.png b/docs/demos/planning-sim/images/launch-gui/launch_gui_setup.png similarity index 100% rename from docs/demos/images/planning/launch-gui/launch_gui_setup.png rename to docs/demos/planning-sim/images/launch-gui/launch_gui_setup.png diff --git a/docs/demos/images/planning/launch-gui/selecting_launch_file.png b/docs/demos/planning-sim/images/launch-gui/selecting_launch_file.png similarity index 100% rename from docs/demos/images/planning/launch-gui/selecting_launch_file.png rename to docs/demos/planning-sim/images/launch-gui/selecting_launch_file.png diff --git a/docs/demos/images/planning/launch-gui/starting_simulation.png b/docs/demos/planning-sim/images/launch-gui/starting_simulation.png similarity index 100% rename from docs/demos/images/planning/launch-gui/starting_simulation.png rename to docs/demos/planning-sim/images/launch-gui/starting_simulation.png diff --git a/docs/demos/images/planning/others/increase-max-velocity.png b/docs/demos/planning-sim/images/others/increase-max-velocity.png similarity index 100% rename from docs/demos/images/planning/others/increase-max-velocity.png rename to docs/demos/planning-sim/images/others/increase-max-velocity.png diff --git a/docs/demos/images/planning/parking/after-set-goal-pose.png b/docs/demos/planning-sim/images/parking/after-set-goal-pose.png similarity index 100% rename from docs/demos/images/planning/parking/after-set-goal-pose.png rename to docs/demos/planning-sim/images/parking/after-set-goal-pose.png diff --git a/docs/demos/images/planning/parking/parking-maneuver.png b/docs/demos/planning-sim/images/parking/parking-maneuver.png similarity index 100% rename from docs/demos/images/planning/parking/parking-maneuver.png rename to docs/demos/planning-sim/images/parking/parking-maneuver.png diff --git a/docs/demos/images/planning/passing-crosswalk/non-signalized/initial-setup.png b/docs/demos/planning-sim/images/passing-crosswalk/non-signalized/initial-setup.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/non-signalized/initial-setup.png rename to docs/demos/planning-sim/images/passing-crosswalk/non-signalized/initial-setup.png diff --git a/docs/demos/images/planning/passing-crosswalk/non-signalized/pass-crosswalk.png b/docs/demos/planning-sim/images/passing-crosswalk/non-signalized/pass-crosswalk.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/non-signalized/pass-crosswalk.png rename to docs/demos/planning-sim/images/passing-crosswalk/non-signalized/pass-crosswalk.png diff --git a/docs/demos/images/planning/passing-crosswalk/non-signalized/place-pedestrian.png b/docs/demos/planning-sim/images/passing-crosswalk/non-signalized/place-pedestrian.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/non-signalized/place-pedestrian.png rename to docs/demos/planning-sim/images/passing-crosswalk/non-signalized/place-pedestrian.png diff --git a/docs/demos/images/planning/passing-crosswalk/non-signalized/wait-before-crosswalk.png b/docs/demos/planning-sim/images/passing-crosswalk/non-signalized/wait-before-crosswalk.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/non-signalized/wait-before-crosswalk.png rename to docs/demos/planning-sim/images/passing-crosswalk/non-signalized/wait-before-crosswalk.png diff --git a/docs/demos/images/planning/passing-crosswalk/signalized/move-after-red-to-green.png b/docs/demos/planning-sim/images/passing-crosswalk/signalized/move-after-red-to-green.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/signalized/move-after-red-to-green.png rename to docs/demos/planning-sim/images/passing-crosswalk/signalized/move-after-red-to-green.png diff --git a/docs/demos/images/planning/passing-crosswalk/signalized/stop-from-red-and-pedestrian.png b/docs/demos/planning-sim/images/passing-crosswalk/signalized/stop-from-red-and-pedestrian.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/signalized/stop-from-red-and-pedestrian.png rename to docs/demos/planning-sim/images/passing-crosswalk/signalized/stop-from-red-and-pedestrian.png diff --git a/docs/demos/images/planning/passing-crosswalk/signalized/stop-from-red-light.png b/docs/demos/planning-sim/images/passing-crosswalk/signalized/stop-from-red-light.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/signalized/stop-from-red-light.png rename to docs/demos/planning-sim/images/passing-crosswalk/signalized/stop-from-red-light.png diff --git a/docs/demos/images/planning/passing-crosswalk/signalized/stop-red-light-with-pedestrian.png b/docs/demos/planning-sim/images/passing-crosswalk/signalized/stop-red-light-with-pedestrian.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/signalized/stop-red-light-with-pedestrian.png rename to docs/demos/planning-sim/images/passing-crosswalk/signalized/stop-red-light-with-pedestrian.png diff --git a/docs/demos/images/planning/passing-crosswalk/signalized/test-location.png b/docs/demos/planning-sim/images/passing-crosswalk/signalized/test-location.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/signalized/test-location.png rename to docs/demos/planning-sim/images/passing-crosswalk/signalized/test-location.png diff --git a/docs/demos/images/planning/passing-crosswalk/signalized/wait-for-pedestrian.png b/docs/demos/planning-sim/images/passing-crosswalk/signalized/wait-for-pedestrian.png similarity index 100% rename from docs/demos/images/planning/passing-crosswalk/signalized/wait-for-pedestrian.png rename to docs/demos/planning-sim/images/passing-crosswalk/signalized/wait-for-pedestrian.png diff --git a/docs/demos/images/planning/pullover-pullout/pullover-pullout.png b/docs/demos/planning-sim/images/pullover-pullout/pullover-pullout.png similarity index 100% rename from docs/demos/images/planning/pullover-pullout/pullover-pullout.png rename to docs/demos/planning-sim/images/pullover-pullout/pullover-pullout.png diff --git a/docs/demos/images/planning/traffic-light/after-traffic-light-color-update.png b/docs/demos/planning-sim/images/traffic-light/after-traffic-light-color-update.png similarity index 100% rename from docs/demos/images/planning/traffic-light/after-traffic-light-color-update.png rename to docs/demos/planning-sim/images/traffic-light/after-traffic-light-color-update.png diff --git a/docs/demos/images/planning/traffic-light/see-traffic-light-ID.png b/docs/demos/planning-sim/images/traffic-light/see-traffic-light-ID.png similarity index 100% rename from docs/demos/images/planning/traffic-light/see-traffic-light-ID.png rename to docs/demos/planning-sim/images/traffic-light/see-traffic-light-ID.png diff --git a/docs/demos/images/planning/traffic-light/send-traffic-light-color.png b/docs/demos/planning-sim/images/traffic-light/send-traffic-light-color.png similarity index 100% rename from docs/demos/images/planning/traffic-light/send-traffic-light-color.png rename to docs/demos/planning-sim/images/traffic-light/send-traffic-light-color.png diff --git a/docs/demos/images/planning/traffic-light/set-traffic-light.png b/docs/demos/planning-sim/images/traffic-light/set-traffic-light.png similarity index 100% rename from docs/demos/images/planning/traffic-light/set-traffic-light.png rename to docs/demos/planning-sim/images/traffic-light/set-traffic-light.png diff --git a/docs/demos/planning-sim/index.md b/docs/demos/planning-sim/index.md new file mode 100644 index 00000000000..6f4c1f27f61 --- /dev/null +++ b/docs/demos/planning-sim/index.md @@ -0,0 +1,92 @@ +# Planning simulation + +## Preparation + +### Download the sample map + +```bash +gdown -O ~/autoware_map/ 'https://docs.google.com/uc?export=download&id=1499_nsbUbIeturZaDj7jhUownh5fvXHd' +unzip -d ~/autoware_map ~/autoware_map/sample-map-planning.zip +``` + +- You can also download [the map](https://drive.google.com/file/d/1499_nsbUbIeturZaDj7jhUownh5fvXHd/view?usp=sharing) manually. + +!!! info + + Sample map: Copyright 2020 TIER IV, Inc. + +### Make sure the artifacts are downloaded + +Check if you have `~/autoware_data` folder and files in it. + +```bash +$ cd ~/autoware_data +$ ls -C -w 30 +image_projection_based_fusion +lidar_apollo_instance_segmentation +lidar_centerpoint +tensorrt_yolo +tensorrt_yolox +traffic_light_classifier +traffic_light_fine_detector +traffic_light_ssd_fine_detector +yabloc_pose_initializer +``` + +If not, please, follow [Manual downloading of artifacts](https://github.com/autowarefoundation/autoware/tree/main/ansible/roles/artifacts). + +--- + +!!! info "[Using Autoware Launch GUI](using-launch-gui.md)" + + If you prefer a graphical user interface (GUI) over the command line for launching and managing your simulations, refer to the [Using Autoware Launch GUI](using-launch-gui.md) section at the end of this document for a step-by-step guide. + +--- + +
+ +[:fa-cl-s fa-film: Reference Video Tutorials](https://drive.google.com/file/d/1bs_dX1JJ76qHk-SGvS6YF9gmekkN8fz7/view?usp=sharing){ .md-button style="margin: 5px" } + +
+ +--- + +## Basic simulations + +
+ +[Lane Driving](lane-driving.md){ .md-button style="margin: 5px" } +[Parking](parking.md){ .md-button style="margin: 5px" } +[Pull out and pull over](pull-over-out.md){ .md-button style="margin: 5px" } +[Lane Change](lane-change.md){ .md-button style="margin: 5px" } + +
+ +## Advanced simulations + +
+ +[:fa-cl-s fa-cube: Placing Dummy Objects](placing-objects.md){ .md-button style="margin: 5px" } +[Avoidance](avoidance.md){ .md-button style="margin: 5px" } +[Traffic Light Recognition Simulation](traffic-light.md){ .md-button style="margin: 5px" } +[Driving Through a Crosswalk](crosswalk.md){ .md-button style="margin: 5px" } + +
+ +## Increase the maximum velocity + +The original Autoware is designed to operate at a wide speed range. But for safety reasons, the default maximum velocity has been limited to **15 km/h**. +Because of this, even if you drag the slider to a higher speed in the RViz panel, the system will not allow it. + +To run Autoware at a higher speed, you can modify the `max_vel` parameter in the config file [autoware_launch/config/planning/scenario_planning/common/common.param.yaml](https://github.com/autowarefoundation/autoware_launch/blob/main/autoware_launch/config/planning/scenario_planning/common/common.param.yaml) located in the `autoware_launch` repository. + +!!! example + + Set `max_vel` to `20.0` (20 m/s = 72 km/h). + Then launch the planning simulator, place the vehicle and set the velocity limit with the slider. + +![increase-max-velocity](images/others/increase-max-velocity.png) + +## Create your own map + +The content above takes place in the planning simulator using a sample map. If you are interested in running Autoware with maps of your own environment, please visit the [How to Create Vector Map](../../tutorials/integrating-autoware/creating-maps/index.md) section for guidance. diff --git a/docs/demos/planning-sim/lane-change.md b/docs/demos/planning-sim/lane-change.md new file mode 100644 index 00000000000..9ccc99fbd3f --- /dev/null +++ b/docs/demos/planning-sim/lane-change.md @@ -0,0 +1,25 @@ +# Lane change scenario + +1. Download and unpack Nishishinjuku map. + + ```bash + gdown -O ~/autoware_map/ 'https://github.com/tier4/AWSIM/releases/download/v1.1.0/nishishinjuku_autoware_map.zip' + unzip -d ~/autoware_map ~/autoware_map/nishishinjuku_autoware_map.zip + ``` + +2. Launch autoware with Nishishinjuku map with following command: + + ```bash + source ~/autoware/install/setup.bash + ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/nishishinjuku_autoware_map vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit + ``` + + ![open-nishishinjuku-map](images/lane-change/open-nishishinjuku-map.png) + +3. Set an initial pose and a goal pose in adjacent lanes. + + ![set-position-and-goal](images/lane-change/set-position-and-goal.png) + +4. Engage the ego vehicle. It will make a lane change along the planned path. + + ![lane-changing](images/lane-change/lane-changing.png) diff --git a/docs/demos/planning-sim/lane-driving.md b/docs/demos/planning-sim/lane-driving.md new file mode 100644 index 00000000000..4239f489758 --- /dev/null +++ b/docs/demos/planning-sim/lane-driving.md @@ -0,0 +1,52 @@ +# Lane driving scenario + +## 1. Launch Autoware + +```bash +source ~/autoware/install/setup.bash +ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit +``` + +!!! warning + + Note that you cannot use `~` instead of `$HOME` here. + + If `~` is used, the map will fail to load. + +![after-autoware-launch](images/lane-following/after-autoware-launch.png) + +## 2. Set an initial pose for the ego vehicle + +![set-initial-pose](images/lane-following/set-initial-pose.png) + +a) Click the `2D Pose estimate` button in the toolbar, or hit the `P` key. + +b) In the 3D View pane, click and hold the left-mouse button, and then drag to set the direction for the initial pose. An image representing the vehicle should now be displayed. + +!!! warning + + Remember to set the initial pose of the car in the same direction as the lane. + + To confirm the direction of the lane, check the arrowheads displayed on the map. + +## 3. Set a goal pose for the ego vehicle + +a) Click the `2D Goal Pose` button in the toolbar, or hit the `G` key. + +b) In the 3D View pane, click and hold the left-mouse button, and then drag to set the direction for the goal pose. If done correctly, you will see a planned path from initial pose to goal pose. + +![set-goal-pose](images/lane-following/set-goal-pose.png) + +## 4. Start the ego vehicle + +Now you can start the ego vehicle driving by clicking the `Auto` button in the `AutowareStatePanel`. +Alternatively, you can manually start the vehicle by running the following command: + +```bash +source ~/autoware/install/setup.bash +ros2 service call /api/operation_mode/change_to_autonomous autoware_adapi_v1_msgs/srv/ChangeOperationMode {} +``` + +After that, `Auto` button will be selected and grayed out. + +![start-driving](images/lane-following/start-driving.png) diff --git a/docs/demos/planning-sim/parking.md b/docs/demos/planning-sim/parking.md new file mode 100644 index 00000000000..8c17d8da2b4 --- /dev/null +++ b/docs/demos/planning-sim/parking.md @@ -0,0 +1,10 @@ +# Parking scenario + +1. Set an initial pose and a goal pose, and engage the ego vehicle. + + ![after-set-goal-pose](images/parking/after-set-goal-pose.png) + +2. When the vehicle approaches the goal, it will switch from lane driving mode to parking mode. +3. After that, the vehicle will maneuver into the destination parking spot. + + ![parking-maneuver](images/parking/parking-maneuver.png) diff --git a/docs/demos/planning-sim/placing-objects.md b/docs/demos/planning-sim/placing-objects.md new file mode 100644 index 00000000000..a9f8b649f72 --- /dev/null +++ b/docs/demos/planning-sim/placing-objects.md @@ -0,0 +1,27 @@ +# Placing dummy objects + +1. Click the `2D Dummy Car` or `2D Dummy Pedestrian` button in the toolbar. +2. Set the pose of the dummy object by clicking and dragging on the map. +3. Set the velocity of the object in `Tool Properties -> 2D Dummy Car/Pedestrian` panel. + +!!! note + + Changes to the `velocity` parameter will only affect objects placed after the parameter is changed. + +![set-dummy-car](images/lane-following/place-dummy-car.png) + +!!! tip "Delete all dummy objects" + + Click the `Delete All Objects` button in the toolbar and then click anywhere in the 3D View pane to complete it. + +## Placing interactive dummy objects + +Click the `Interactive` button in the toolbar to create the next dummy object in interactive mode. + +![set-interactive-dummy-car](images/lane-following/check-interactive.png) + +!!! info + + - **Add an interactive dummy object:** ++shift+"🖱️ Right Click"++ on the map. + - **Delete an interactive dummy object:** ++alt+"🖱️ Right Click"++ on the object. + - **Move an existing interactive dummy object:** ++"🖱️ Right Click"++ and hold on the object. Then drag and drop it to the desired location. diff --git a/docs/demos/planning-sim/pull-over-out.md b/docs/demos/planning-sim/pull-over-out.md new file mode 100644 index 00000000000..67ec98c6f3b --- /dev/null +++ b/docs/demos/planning-sim/pull-over-out.md @@ -0,0 +1,9 @@ +# Pull out and pull over scenario + +1. In a pull out scenario, set the ego vehicle at the road shoulder. + + ![pullover-pullout](images/pullover-pullout/pullover-pullout.png) + +2. Set a goal and then engage the ego vehicle. + +3. In a pull over scenario, similarly set the ego vehicle in a lane and set a goal on the road shoulder. diff --git a/docs/demos/planning-sim/traffic-light.md b/docs/demos/planning-sim/traffic-light.md new file mode 100644 index 00000000000..377c5bb437d --- /dev/null +++ b/docs/demos/planning-sim/traffic-light.md @@ -0,0 +1,36 @@ +# Traffic light recognition simulation + +By default, traffic lights on the map are all treated as if they are set to green. As a result, when a path is created that passed through an intersection with a traffic light, the ego vehicle will drive through the intersection without stopping. + +The following steps explain how to set and reset traffic lights in order to test how the Planning component will respond. + +## Set traffic light + +By default, Rviz doesn't display the IDs of traffic lights on the map. +To enable the display of traffic light IDs, follow these steps: + +1. In the `Displays` panel, find the `traffic_light_id` topic by toggling the triangle icons next to `Map > Lanelet2VectorMap > Namespaces`. +2. Check the `traffic_light_id` checkbox. +3. Reload the topic by clicking the `Map` checkbox twice. +4. Have a closer look at the IDs by zooming in the region or by changing the View type. + +![see-traffic-light-ID](images/traffic-light/see-traffic-light-ID.png) + +1. Go to `Panels -> Add new panel`, select `tier4_traffic_light_rviz_plugin/TrafficLightPublishPanel`, and then press `OK`. + +2. In `TrafficLightPublishPanel`, set the `ID` and color of the traffic light. + +3. Click the `SET` button. + ![set-traffic-light](images/traffic-light/set-traffic-light.png) + +4. Finally, click the `PUBLISH` button to send the traffic light status to the simulator. Any planned path that goes past the selected traffic light will then change accordingly. + +![send-traffic-light-color](images/traffic-light/send-traffic-light-color.png) + +## Update/Reset traffic light + +You can update the color of the traffic light by selecting the next color (in the image it is `GREEN`) and clicking `SET` button. In the image the traffic light in front of the ego vehicle changed from `RED` to `GREEN` and the vehicle restarted. + +![after-traffic-light-color-update](images/traffic-light/after-traffic-light-color-update.png) + +To remove a traffic light from `TrafficLightPublishPanel`, click the `RESET` button. diff --git a/docs/demos/planning-sim/using-launch-gui.md b/docs/demos/planning-sim/using-launch-gui.md new file mode 100644 index 00000000000..d887549a2f0 --- /dev/null +++ b/docs/demos/planning-sim/using-launch-gui.md @@ -0,0 +1,40 @@ +# Planning simulator demo with Autoware Launch GUI + +This section provides a step-by-step guide on using the Autoware Launch GUI for planning simulations, offering an alternative to the command-line instructions provided in the Basic simulations section. + +## Getting Started with Autoware Launch GUI + +1. **Installation:** Ensure you have installed the Autoware Launch GUI. [Installation instructions](https://github.com/autowarefoundation/autoware-launch-gui#installation). + +2. **Launching the GUI:** Open the Autoware Launch GUI from your applications menu. + + ![GUI screenshot for launching the GUI](images/launch-gui/launch_gui_main.png) + +## Launching a Planning Simulation + +### Lane Driving Scenario + +1. **Set Autoware Path:** In the GUI, set the path to your Autoware installation. + + ![GUI_screenshot_for_setting_Autoware_path](images/launch-gui/launch_gui_setup.png) + +2. **Select Launch File:** Choose `planning_simulator.launch.xml` for the lane driving scenario. + + ![GUI screenshot for selecting launch file](images/launch-gui/selecting_launch_file.png) + +3. **Customize Parameters:** Adjust parameters such as `map_path`, `vehicle_model`, and `sensor_model` as needed. + + ![GUI screenshot for customizing parameters](images/launch-gui/customizing-parameters1.png) + ![GUI screenshot for customizing parameters](images/launch-gui/customizing-parameters2.png) + +4. **Start Simulation:** Click the launch button to start the simulation. + + ![GUI screenshot for starting simulation](images/launch-gui/starting_simulation.png) + +5. **Any Scenario:** From here, you can follow the instructions in the [Planning Scenario Simulations](index.md#basic-simulations). + +## Monitoring and Managing the Simulation + +- **Real-Time Monitoring:** Use the GUI to monitor CPU/Memory usage and Autoware logs in real-time. +- **Profile Management:** Save your simulation profiles for quick access in future simulations. +- **Adjusting Parameters:** Easily modify simulation parameters on-the-fly through the GUI. diff --git a/docs/demos/planning-simulation.md b/docs/demos/planning-simulation.md deleted file mode 100644 index cb258297a09..00000000000 --- a/docs/demos/planning-simulation.md +++ /dev/null @@ -1,394 +0,0 @@ -# Planning simulation - -## Preparation - -Download and unpack a sample map. - -- You can also download [the map](https://drive.google.com/file/d/1499_nsbUbIeturZaDj7jhUownh5fvXHd/view?usp=sharing) manually. - -```bash -gdown -O ~/autoware_map/ 'https://docs.google.com/uc?export=download&id=1499_nsbUbIeturZaDj7jhUownh5fvXHd' -unzip -d ~/autoware_map ~/autoware_map/sample-map-planning.zip -``` - -!!! Note - - Sample map: Copyright 2020 TIER IV, Inc. - -Check if you have `~/autoware_data` folder and files in it. - -```bash -$ cd ~/autoware_data -$ ls -C -w 30 -image_projection_based_fusion -lidar_apollo_instance_segmentation -lidar_centerpoint -tensorrt_yolo -tensorrt_yolox -traffic_light_classifier -traffic_light_fine_detector -traffic_light_ssd_fine_detector -yabloc_pose_initializer -``` - -If not, please, follow [Manual downloading of artifacts](https://github.com/autowarefoundation/autoware/tree/main/ansible/roles/artifacts). - -Change the [maximum velocity](https://github.com/autowarefoundation/autoware_launch/blob/c03bd4bdb70117efffc328e5fe6e57426f169b3b/autoware_launch/config/planning/scenario_planning/common/common.param.yaml#L3), that is 15km/h by default. - -## Basic simulations - -!!! info "[Using Autoware Launch GUI](#using-autoware-launch-gui)" - - If you prefer a graphical user interface (GUI) over the command line for launching and managing your simulations, refer to the [Using Autoware Launch GUI](#using-autoware-launch-gui) section at the end of this document for a step-by-step guide. - -### Lane driving scenario - -#### 1. Launch Autoware - -```bash -source ~/autoware/install/setup.bash -ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/sample-map-planning vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit -``` - -!!! warning - - Note that you cannot use `~` instead of `$HOME` here. - - If `~` is used, the map will fail to load. - -![after-autoware-launch](images/planning/lane-following/after-autoware-launch.png) - -#### 2. Set an initial pose for the ego vehicle - -![set-initial-pose](images/planning/lane-following/set-initial-pose.png) - -a) Click the `2D Pose estimate` button in the toolbar, or hit the `P` key. - -b) In the 3D View pane, click and hold the left-mouse button, and then drag to set the direction for the initial pose. An image representing the vehicle should now be displayed. - -!!! warning - - Remember to set the initial pose of the car in the same direction as the lane. - - To confirm the direction of the lane, check the arrowheads displayed on the map. - -#### 3. Set a goal pose for the ego vehicle - -a) Click the `2D Goal Pose` button in the toolbar, or hit the `G` key. - -b) In the 3D View pane, click and hold the left-mouse button, and then drag to set the direction for the goal pose. If done correctly, you will see a planned path from initial pose to goal pose. - -![set-goal-pose](images/planning/lane-following/set-goal-pose.png) - -#### 4. Start the ego vehicle - -Now you can start the ego vehicle driving by clicking the `Auto` button in the `AutowareStatePanel`. -Alternatively, you can manually start the vehicle by running the following command: - -```bash -source ~/autoware/install/setup.bash -ros2 service call /api/operation_mode/change_to_autonomous autoware_adapi_v1_msgs/srv/ChangeOperationMode {} -``` - -After that, `Auto` button will be selected and grayed out. - -![start-driving](images/planning/lane-following/start-driving.png) - -### Parking scenario - -1. Set an initial pose and a goal pose, and engage the ego vehicle. - - ![after-set-goal-pose](images/planning/parking/after-set-goal-pose.png) - -2. When the vehicle approaches the goal, it will switch from lane driving mode to parking mode. -3. After that, the vehicle will maneuver into the destination parking spot. - - ![parking-maneuver](images/planning/parking/parking-maneuver.png) - -### Pull out and pull over scenario - -1. In a pull out scenario, set the ego vehicle at the road shoulder. - - ![pullover-pullout](images/planning/pullover-pullout/pullover-pullout.png) - -2. Set a goal and then engage the ego vehicle. - -3. In a pull over scenario, similarly set the ego vehicle in a lane and set a goal on the road shoulder. - -### Lane change scenario - -1. Download and unpack Nishishinjuku map. - - ```bash - gdown -O ~/autoware_map/ 'https://github.com/tier4/AWSIM/releases/download/v1.1.0/nishishinjuku_autoware_map.zip' - unzip -d ~/autoware_map ~/autoware_map/nishishinjuku_autoware_map.zip - ``` - -2. Launch autoware with Nishishinjuku map with following command: - - ```bash - source ~/autoware/install/setup.bash - ros2 launch autoware_launch planning_simulator.launch.xml map_path:=$HOME/autoware_map/nishishinjuku_autoware_map vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit - ``` - - ![open-nishishinjuku-map](images/planning/lane-change/open-nishishinjuku-map.png) - -3. Set an initial pose and a goal pose in adjacent lanes. - - ![set-position-and-goal](images/planning/lane-change/set-position-and-goal.png) - -4. Engage the ego vehicle. It will make a lane change along the planned path. - - ![lane-changing](images/planning/lane-change/lane-changing.png) - -### Avoidance scenario - -1. Set an initial pose and a goal pose in the same lane. A path will be planned. - - ![set-position-and-goal](images/planning/avoidance/set-position-and-goal.png) - -2. Set a "2D Dummy Bus" on the roadside. A new path will be planned. - - ![set-dummy-bus](images/planning/avoidance/set-dummy-bus.png) - -3. Engage the ego vehicle. It will avoid the obstacle along the newly planned path. - - ![avoidance-driving](images/planning/avoidance/avoidance-driving.png) - -## Advanced Simulations - -### Placing dummy objects - -1. Click the `2D Dummy Car` or `2D Dummy Pedestrian` button in the toolbar. -2. Set the pose of the dummy object by clicking and dragging on the map. -3. Set the velocity of the object in `Tool Properties -> 2D Dummy Car/Pedestrian` panel. - - !!! note - - Changes to the `velocity` parameter will only affect objects placed after the parameter is changed. - - ![set-dummy-car](images/planning/lane-following/place-dummy-car.png) - -4. Delete any dummy objects placed in the view by clicking the `Delete All Objects` button in the toolbar and then click anywhere in the 3D View pane to complete it. - -#### Placing interactive dummy objects - -Click the `Interactive` button in the toolbar to create the next dummy object in interactive mode. - -![set-interactive-dummy-car](images/planning/lane-following/check-interactive.png) - -!!! info - - - **Add an interactive dummy object:** ++shift+"🖱️ Right Click"++ on the map. - - **Delete an interactive dummy object:** ++alt+"🖱️ Right Click"++ on the object. - - **Move an existing interactive dummy object:** ++"🖱️ Right Click"++ and hold on the object. Then drag and drop it to the desired location. - -### Traffic light recognition simulation - -By default, traffic lights on the map are all treated as if they are set to green. As a result, when a path is created that passed through an intersection with a traffic light, the ego vehicle will drive through the intersection without stopping. - -The following steps explain how to set and reset traffic lights in order to test how the Planning component will respond. - -#### Set traffic light - -By default, Rviz doesn't display the IDs of traffic lights on the map. -To enable the display of traffic light IDs, follow these steps: - -1. In the `Displays` panel, find the `traffic_light_id` topic by toggling the triangle icons next to `Map > Lanelet2VectorMap > Namespaces`. -2. Check the `traffic_light_id` checkbox. -3. Reload the topic by clicking the `Map` checkbox twice. -4. Have a closer look at the IDs by zooming in the region or by changing the View type. - -![see-traffic-light-ID](images/planning/traffic-light/see-traffic-light-ID.png) - -1. Go to `Panels -> Add new panel`, select `tier4_traffic_light_rviz_plugin/TrafficLightPublishPanel`, and then press `OK`. - -2. In `TrafficLightPublishPanel`, set the `ID` and color of the traffic light. - -3. Click the `SET` button. - ![set-traffic-light](images/planning/traffic-light/set-traffic-light.png) - -4. Finally, click the `PUBLISH` button to send the traffic light status to the simulator. Any planned path that goes past the selected traffic light will then change accordingly. - -![send-traffic-light-color](images/planning/traffic-light/send-traffic-light-color.png) - -#### Update/Reset traffic light - -You can update the color of the traffic light by selecting the next color (in the image it is `GREEN`) and clicking `SET` button. In the image the traffic light in front of the ego vehicle changed from `RED` to `GREEN` and the vehicle restarted. - -![after-traffic-light-color-update](images/planning/traffic-light/after-traffic-light-color-update.png) - -To remove a traffic light from `TrafficLightPublishPanel`, click the `RESET` button. - -[Reference video tutorials](https://drive.google.com/file/d/1bs_dX1JJ76qHk-SGvS6YF9gmekkN8fz7/view?usp=sharing) - -### Driving through a crosswalk - -When driving through a crosswalk, the ego vehicle evaluates **both** the presence of pedestrians/objects **and** the state of any associated traffic lights. - -!!! info - - For more technical details, refer to the [**autoware_behavior_velocity_crosswalk_module** documentation](https://autowarefoundation.github.io/autoware_universe/main/planning/behavior_velocity_planner/autoware_behavior_velocity_crosswalk_module/). - -!!! info - - These examples use the **Nishishinjuku** map, the same one used in the [lane change scenario](#lane-change-scenario). - -!!! tip - - For these tutorials, it is easier to use **interactive dummy pedestrians** (see [Placing interactive dummy objects](#placing-interactive-dummy-objects) above). - - This way you can quickly add, move, and delete dummy pedestrians as needed. - -#### Non-signalized crosswalk (no traffic light) - -##### Behavior logic - -```mermaid -flowchart TD - A["Approach **crosswalk**"] --> B{"Pedestrian somewhere on the **crosswalk**?
(Pedestrian velocity is not important.)"} - B -- "No" --> C["Proceed without slowing down"] - B -- "Yes" --> D["Slow down and stop **one time**"] - D --> E["Wait a few seconds to confirm safe to proceed"] - E --> F{"Pedestrian or object on **planned path**?"} - F -- "Yes" --> G["Continue waiting / yield"] - F -- "No" --> H["Resume driving (will not stop again for this crosswalk)"] - H --> I["Crosswalk passed ➡️ behavior resets when encountering the same crosswalk again"] -``` - -!!! example "Experiment" - - We will test the expected “single stop then go” behavior: - - 1. Place a still dummy pedestrian on the crosswalk. (Not on the planned path, just on the crosswalk.) - - 2. The ego vehicle will decelerate and stop before the crosswalk. - - 3. After waiting for a few seconds, the ego vehicle will start driving again as usual. - -1. Set an initial pose and a goal pose for the ego vehicle to drive through a non-signalized crosswalk. A path will be planned. - - ![initial-setup](images/planning/passing-crosswalk/non-signalized/initial-setup.png) - -2. Place an interactive dummy pedestrian on the crosswalk and set its pose as if it is crossing the street. It doesn't matter whether the dummy pedestrian is moving or not, as long as it is on the crosswalk. - - ![place-pedestrian](images/planning/passing-crosswalk/non-signalized/place-pedestrian.png) - -3. Engage the ego vehicle by clicking on `Auto`. The ego vehicle will decelerate and stop before the crosswalk. The marked **crosswalk** in the figure indicates that the stopping behavior is caused by the objects on the **crosswalk**. - - ![wait-before-crosswalk](images/planning/passing-crosswalk/non-signalized/wait-before-crosswalk.png) - -4. The ego vehicle will wait for about a few seconds. Then it will start moving again and pass the crosswalk. - - ![pass-crosswalk](images/planning/passing-crosswalk/non-signalized/pass-crosswalk.png) - -#### Signalized crosswalk (with traffic light) - -
- ![test-location.png](images/planning/passing-crosswalk/signalized/test-location.png) -
Location for signalized crosswalk experiments
-
- -!!! example "Experiment 1: Pedestrian Present While Traffic Light Is GREEN" - - This experiment mirrors the previous one but at a signalized crosswalk. - -With the pedestrian near the path and the traffic light **GREEN**, the ego behaves **the same as at a non-signalized crosswalk**: -it slows, stops, waits, then continues. - -![wait-for-pedestrian](images/planning/passing-crosswalk/signalized/wait-for-pedestrian.png) - -!!! example "Experiment 2: Interaction of Pedestrians and a RED Traffic Light" - - 1. Stop before the crosswalk when the traffic light is set to `RED`. (Without pedestrians.) - - 2. Add a dummy pedestrian on the crosswalk while the traffic light is `RED`. (Both the traffic light and the crosswalk should affect the stopping behavior.) - - 3. Finally, set the traffic light to `GREEN` again and the vehicle will pass normally. - -1. **Stop at red (no pedestrians).** - Remove any existing dummy pedestrians and set the traffic light to **RED**. - The ego vehicle will stop before the crosswalk and wait solely because of the **traffic_light** reason. - - ![stop-from-red-light](images/planning/passing-crosswalk/signalized/stop-from-red-light.png) - -2. **Add a pedestrian while the light is RED.** - The ego remains stopped, now influenced by **both** the traffic light and the crosswalk object. - - ![stop-from-red-and-pedestrian](images/planning/passing-crosswalk/signalized/stop-from-red-and-pedestrian.png) - -3. **Observe how the stop reasons update.** - After a short period, only **traffic_light** may remain displayed. - Moving the pedestrian slightly (with ++shift+"🖱️ Right Click"++ drag) reintroduces both markers, but the system stabilizes back to the traffic-light reason during the wait. - - ![stop-red-light-with-pedestrian.png](images/planning/passing-crosswalk/signalized/stop-red-light-with-pedestrian.png) - -4. **Switch the light to GREEN.** - When set to green and `Auto` mode is engaged, the ego vehicle proceeds normally. - - ![move-after-red-to-green.png](images/planning/passing-crosswalk/signalized/move-after-red-to-green.png) - -## Using Autoware Launch GUI - -This section provides a step-by-step guide on using the Autoware Launch GUI for planning simulations, offering an alternative to the command-line instructions provided in the Basic simulations section. - -### Getting Started with Autoware Launch GUI - -1. **Installation:** Ensure you have installed the Autoware Launch GUI. [Installation instructions](https://github.com/autowarefoundation/autoware-launch-gui#installation). - -2. **Launching the GUI:** Open the Autoware Launch GUI from your applications menu. - - ![GUI screenshot for launching the GUI](images/planning/launch-gui/launch_gui_main.png) - -### Launching a Planning Simulation - -#### Lane Driving Scenario - -1. **Set Autoware Path:** In the GUI, set the path to your Autoware installation. - - ![GUI_screenshot_for_setting_Autoware_path](images/planning/launch-gui/launch_gui_setup.png) - -2. **Select Launch File:** Choose `planning_simulator.launch.xml` for the lane driving scenario. - - ![GUI screenshot for selecting launch file](images/planning/launch-gui/selecting_launch_file.png) - -3. **Customize Parameters:** Adjust parameters such as `map_path`, `vehicle_model`, and `sensor_model` as needed. - - ![GUI screenshot for customizing parameters](images/planning/launch-gui/customizing-parameters1.png) - ![GUI screenshot for customizing parameters](images/planning/launch-gui/customizing-parameters2.png) - -4. **Start Simulation:** Click the launch button to start the simulation. - - ![GUI screenshot for starting simulation](images/planning/launch-gui/starting_simulation.png) - -5. **Any Scenario:** From here, you can follow the instructions in the - -- Lane driving scenario: [Lane Driving Scenario](#lane-driving-scenario) -- Parking scenario: [Parking scenario](#parking-scenario) -- Lane change scenario: [Lane change scenario](#lane-change-scenario) -- Avoidance scenario: [Avoidance scenario](#avoidance-scenario) -- Advanced Simulations: [Advanced Simulations](#advanced-simulations) - -### Monitoring and Managing the Simulation - -- **Real-Time Monitoring:** Use the GUI to monitor CPU/Memory usage and Autoware logs in real-time. -- **Profile Management:** Save your simulation profiles for quick access in future simulations. -- **Adjusting Parameters:** Easily modify simulation parameters on-the-fly through the GUI. - -## Want to Try Autoware with Your Custom Map? - -The above content describes the process for conducting some operations in the planning simulator using a sample map. If you are interested in running Autoware with maps of your own environment, please visit the [How to Create Vector Map](../tutorials/integrating-autoware/creating-maps/index.md) section for guidance. - -## Want to Try Autoware with Higher Speed? - -The original Autoware is designed to operate at a wide speed range. But for safety reasons, the default maximum velocity has been limited to **15 km/h**. -Because of that, even you drag the slider to a higher speed in rviz panel, the system will not allow it. - -If you want to run Autoware at a higher speed, you can modify the `max_vel` parameter in the config file [autoware_launch/config/planning/scenario_planning/common/common.param.yaml](https://github.com/autowarefoundation/autoware_launch/blob/main/autoware_launch/config/planning/scenario_planning/common/common.param.yaml) located in the `autoware_launch` repository. - -!!! example - - Set `max_vel` to `20.0` (20 m/s = 72 km/h). - Then launch the planning simulator, place the vehicle and set the velocity limit with the slider. - -![increase-max-velocity](images/planning/others/increase-max-velocity.png) diff --git a/docs/installation/autoware/docker-installation.md b/docs/installation/autoware/docker-installation.md index 48cbb06afc5..4fa952571f6 100644 --- a/docs/installation/autoware/docker-installation.md +++ b/docs/installation/autoware/docker-installation.md @@ -70,7 +70,7 @@ Here is an example of running the runtime container with a custom launch command Inside the container, run the Autoware tutorials by following these links: -[Planning Simulation](../../demos/planning-simulation.md) +[Planning Simulation](../../demos/planning-sim/index.md) [Rosbag Replay Simulation](../../demos/rosbag-replay-simulation.md). diff --git a/mkdocs.yaml b/mkdocs.yaml index 672608a8fce..1350739da67 100644 --- a/mkdocs.yaml +++ b/mkdocs.yaml @@ -3,7 +3,7 @@ site_url: https://autowarefoundation.github.io/autoware-documentation repo_url: https://github.com/autowarefoundation/autoware edit_uri: https://github.com/autowarefoundation/autoware-documentation/edit/main/docs/ docs_dir: docs -copyright: Copyright © 2023 The Autoware Foundation +copyright: Copyright © 2025 The Autoware Foundation theme: name: material