导航

Perception

The Perception module has been upgraded completely to handle comprehensive sensor fusion of our brand-new sensor suite and also keep up with the brand new scenario-based planning.

Introduction

Apollo Perception has following new features:

  • Support for VLS-128 Line LiDAR

  • Obstacle detection through multiple cameras

  • Advanced traffic light detection

  • Configurable sensor fusion

The perception module incorporates the capability of using 5 cameras (2 front, 2 on either side and 1 rear) and 2 radars (front and rear) along with 3 16-line LiDARs (2 rear and 1 front) and 1 128-line LiDAR to recognize obstacles and fuse their individual tracks to obtain a final track list. The obstacle sub-module detects, classifies and tracks obstacles. This sub-module also predicts obstacle motion and position information (e.g., heading and velocity). For lane line, we construct lane instances by postprocessing lane parsing pixels and calculate the lane relative location to the ego-vehicle (L0, L1, R0, R1, etc.).

Architecture

The general architecture of the perception module is shown:

The detailed perception modules are displayed below.

Input

The perception module inputs are:

  • 128 channel LiDAR data (cyber channel /apollo/sensor/velodyne128)

  • 16 channel LiDAR data (cyber channel /apollo/sensor/lidar_front, lidar_rear_left, lidar_rear_right)

  • Radar data (cyber channel /apollo/sensor/radar_front, radar_rear)

  • Image data (cyber channel /apollo/sensor/camera/front_6mm, front_12mm)

  • Extrinsic parameters of radar sensor calibration (from YAML files)

  • Extrinsic and Intrinsic parameters of front camera calibration (from YAML files)

  • Velocity and Angular Velocity of host vehicle (cyber channel /apollo/localization/pose)

Output

The perception module outputs are:

  • The 3D obstacle tracks with the heading, velocity and classification information (cyber channel /apollo/perception/obstacles)

  • The output of traffic light detection and recognition (cyber channel /apollo/perception/traffic_light)

Setup Instructions

  1. Set up the general settings in the configuration file modules/perception/conf/perception_lowcost.conf.

  2. Run the command ./scripts/bootstrap.sh to launch the web GUI.

  3. Select the vehicle model in the web GUI.

  4. Launch the perception module using the command ./scripts/perception_lowcost_vis.sh start or by enabling the perception button on the Module Controller page of the web GUI. The command for stopping perception is ./scripts/perception_lowcost_vis.sh stop. Note: please do not try to use GUI to enable perception but use script to stop it, vice versa.

  5. Download the demo data from the Apollo Open Data Platform.

Note:
    If you are redirected to the Baidu Cloud login page, complete the login and Repeat step 5 (click on the Open Data Platform link)

Note

  1. Nvidia GPU and CUDA are required to run the perception module with Caffe. Apollo provides the CUDA and Caffe libraries in the release docker image. However, the Nvidia GPU driver is not installed in the dev docker image.

  2. To run the perception module with CUDA acceleration, install the exact same version of the Nvidia driver in the docker image that is installed on your host machine, and then build Apollo with the GPU option (i.e., using ./apollo.sh build_gpu or ./apollo.sh build_opt_gpu).

    See How to Run Perception Module on Your Local Computer.

  3. This module contains a redistribution in binary form of a modified version of caffe. A copy of the caffe’s original copyright statement is included below:

    COPYRIGHT

All contributions by the University of California:
Copyright (c) 2014-2017 The Regents of the University of California (Regents)
All rights reserved.

All other contributions:
Copyright (c) 2014-2017, the respective contributors
All rights reserved.

Caffe uses a shared copyright model: each contributor holds copyright over their contributions to Caffe. The project versioning records all such contribution and copyright details. If a contributor wants to further mark their specific copyright on a particular contribution, they should indicate their copyright solely in the commit message of the change when it is committed.

LICENSE

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

    1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

    CONTRIBUTION AGREEMENT

    By contributing to the BVLC/caffe repository through pull-request, comment, or otherwise, the contributor releases their content to the license and copyright terms herein.

上一页

perception

下一页

Perception