Autoware.AI 1.12.0 with LGSVL Simulator
The software and source code in this repository are intended only for use with the LGSVL simulator and should not be used in a real vehicle.
Table of Contents
General top#
This guide goes through how to run Autoware.AI with the LGSVL simulator.
In order to run Autoware with the LGSVL simulator, it is easiest to pull the official Autoware Docker image (see the official guide, Case 1 for more details), but it is also possible to build Autoware from source.
Autoware communicates with the LGSVL simulator using the rosbridge_suite, which provides JSON interfacing with ROS publishers/subscribers. The official Autoware Docker containers have rosbridge_suite included.
Setup top#
Requirements top#
- Linux operating system
- NVIDIA graphics card
Install Docker CE top#
To install Docker CE please refer to theĀ official documentation. We also suggest following through with theĀ post installation steps to run docker as a non-root user.
Install NVIDIA Container Toolkit top#
Before installing the NVIDIA Container Toolkit (nvidia-docker), make sure that you have an appropriate NVIDIA driver installed. To test if the NVIDIA drivers are properly installed enter nvidia-smi
in a terminal. If the drivers are installed properly an output similar to the following should appear:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.59 Driver Version: 440.59 CUDA Version: 10.2 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 108... Off | 00000000:65:00.0 On | N/A |
| 0% 59C P5 22W / 250W | 1490MiB / 11175MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1187 G /usr/lib/xorg/Xorg 863MiB |
| 0 3816 G /usr/bin/gnome-shell 305MiB |
| 0 4161 G ...-token=7171B24E50C2F2C595566F55F1E4D257 68MiB |
| 0 4480 G ...quest-channel-token=3330599186510203656 147MiB |
| 0 17936 G ...-token=5299D28BAAD9F3087B25687A764851BB 103MiB |
+-----------------------------------------------------------------------------+
Install the NVIDIA Container Toolkit by following the instructions here.
Install LGSVL Simulator top#
Follow the instructions here.
Install Autoware top#
Make sure you have Git Large File Storage (LFS) installed before cloning the repository in the next step. If git lfs
outputs git: 'lfs' is not a git command.
, then you need to install it:
-
Instructions for installation are here.
-
Verify the installation:
$ git lfs install Git LFS initialized.
Create a directory called shared_dir
in your home directory to hold HD maps and launch files for the simulator. The Autoware Docker container will mount this folder.
mkdir ~/shared_dir
cd ~/shared_dir
git clone https://github.com/lgsvl/autoware-data.git
If there wasn't a line beginning with Filtering content:
output, then Git LFS hasn't been installed. Remove the autoware-data
directory, install Git LFS with git lfs install
, and then re-issue the git clone
.
Clone the docker
repository from autoware.ai
into a working directory:
cd $WORKING_DIRECTORY
git clone https://gitlab.com/autowarefoundation/autoware.ai/docker.git
If you are using the latest Docker and NVIDIA Container Toolkit, the docker/generic/run.sh
script will need to be modified. To determine whether you need to do this run type nvidia-docker
in a terminal. If you get output similar to: nvidia-docker is /usr/bin/nvidia-docker
, the script will work as is. If not, then modify it as described below:
- In
docker/generic/run.sh
, find the following block at line 139:
if [ $CUDA == "on" ]; then
SUFFIX=$SUFFIX"-cuda"
RUNTIME="--runtime=nvidia"
fi
- Replace it with:
DOCKER_VERSION=$(docker version --format '{{.Client.Version}}' | cut -d'.' -f1)
if [ $CUDA == "on" ]; then
SUFFIX=$SUFFIX"-cuda"
if [[ $DOCKER_VERSION -ge "19" ]] && ! type nvidia-docker; then
RUNTIME="--gpus all"
else
RUNTIME="--runtime=nvidia"
fi
fi
Launch Autoware Alongside LGSVL Simulator top#
Run the Autoware 1.12.0 container and enter into it:
cd $WORKING_DIRECTORY/docker/generic
./run.sh -t 1.12.0
Once inside the container, install a missing ROS package:
sudo apt update && sudo apt install ros-$ROS_DISTRO-image-transport-plugins -y
If you need to check which $ROS_DISTRO you have installed run the following:
ls /opt/ros/
Launch the runtime manager:
roslaunch runtime_manager runtime_manager.launch
A few terminals will open, as well as a GUI for the runtime manager. In the runtime manager, click on the 'Quick Start' tab and load the following launch files from ~/shared_dir/autoware-data/BorregasAve/
by clicking "Ref" to the right of each text box:
my_map.launch
my_sensing_simulator.launch
my_localization.launch
my_detection.launch
my_mission_planning.launch
Click "Map" to load the launch file pertaining to the HD maps. An "Ok" should appear to the right of the "Ref" button when successfully loaded. Then click "Sensing" which also launches rosbridge.
- Run the LGSVL simulator
- Create a Simulation choosing
BorregasAve
map andJaguar2015XE (Autoware)
or another Autoware compatible vehicle. - Enter
localhost:9090
for the Bridge Connection String. - Run the created Simulation
A vehicle should appear in Borregas Ave in Sunnyvale, CA.
In the Autoware Runtime Manager, continue loading the other launch files - click "Localization" and wait for the time to display to the right of "Ref".
Then click "Rviz" to launch Rviz - the vector map and location of the vehicle in the map should show.
The vehicle may be mis-localized as the initial pose is important for NDT matching. To fix this, click "2D Pose Estimate" in Rviz, then click an approximate position for the vehicle on the map and drag in the direction it is facing before releasing the mouse button. This should allow NDT matching to find the vehicle pose (it may take a few tries). Note that the point cloud will not show up in rviz until ndt matching starts publishing a pose.
An alternative would be to use GNSS for an inital pose or for localization but the current Autoware release (1.12.0) does not support GNSS coordinates outside of Japan. Fix for this is available in following pull requests: utilities#27, common#20, core_perception#26 These are not yet merged in Autoware master.
Driving by following vector map:#
To drive following the HD map follow these steps:
- in rviz, mark a destination by clicking '2D Nav Goal' and clicking at the destination and dragging along the road direction. Make sure to only choose a route that looks valid along the lane centerlines that are marked with orange lines in rviz. If an invalid destination is selected nothing will change in rviz, and you will need to relaunch the Mission Planning
launch file in the Quick Launch
tab to try another destination.
After choosing a valid destination the route will be highlighted in blue in rviz.
To follow the selected route launch these nodes:
- Enable lane_rule
, lane_stop
, and lane_select
to follow traffic rules based on the vector map.
- Enable astar_avoid
and velocity_set
.
- Enable pure_pursuit
and twist_filter
to start driving.
Driving by following prerecorded waypoints:#
A basic functionality of Autoware is to follow a prerecorded map while obeying traffic rules. To do this you will need to record a route first. Switch to the Computing
tab and check the box for waypoint_saver
. Make sure to select an appropriate location and file name by clicking on the app
button.
Now you can drive around the map using the keyboard. Once you are satisfied with your route, uncheck the box for waypoint_saver
to end the route.
To drive the route using Autoware:
- Enable
waypoint_loader
while making sure the correct route file is selected in theapp
settings. - Enable
lane_rule
,lane_stop
, andlane_select
to follow traffic rules based on the vector map. - Enable
astar_avoid
andvelocity_set
. - Enable
pure_pursuit
andtwist_filter
to start driving.
The ego vehicle should try to follow the waypoints at the velocity which they were originally recorded at. You can modify this velocity by manually editing the values csv file.
Adding a Vehicle top#
The default vehicles have the calibration files included in the LGSVL Autoware Data Github repository.
Adding an HD Map top#
The default maps have the Vector map files included in the LGSVL Autoware Data Github repository.
Copyright and License top#
Copyright (c) 2019 LG Electronics, Inc.
This software contains code licensed as described in LICENSE.