studian/sdc_term3_final_carnd-capstone_non_train_version

Udacity Self-Driving Car - Capstone Project (GiantCar Team)

Udacity Self-Driving Car - Capstone Project

This is the project repo for the final project of the Udacity Self-Driving Car Nanodegree: Programming a Real Self-Driving Car. For more information about the project, see the project introduction here.

• Team : GiantCar

Name	Udacity account	Slack Handle	Time Zone
Kim HyunKoo	[email protected]	@hkkim	UTC+9 (KST)
Duong Hai Long	[email protected]	@3x3eyes	UTC+8 (Singapore)
Lee Wonjun	[email protected]	@mymamyma	UTC -8 (PST)
Xing Jin	[email protected]	@xing2017	UTC -8 (PST)
Zhao Minming	[email protected]	@minmingzhao	UTC -8 (PST)

1) Introduction

• This is the final capstone project in Udacity’s Self-Driving Car (SDC) Nanodegree.
• In this project, we write code that will autonomously drive Udacity’s self-driving car Carla, an actual car equipped with necessary sensors and actuators, around a small test track.
• We test and develop the code on a simulated car using a simulator provided by Udacity.
• The project brings together several modules taught in the Nanodegree: Perception, Motion Planning, Control, etc. The code is written using the well-known Robotics Operating System (ROS) framework which works both on the simulator as well as the actual car.

2) System Architecture

• The architecture of the system is depicted below.
• The system consists of three key modules: Perception, Planning, and Control.
• Each module consists of one or more ROS nodes, which utilize publish/subscribe (pub-sub) and request/response patterns to communicate critical information with each other while processing information that helps to drive the car.
• At a high level perspective, the Perception module includes functionality that perceives the environment using attached sensors (cameras, lidars, radars, etc.), such as lane lines, traffic lights, obstacles on the road, state of traffic lights, etc.
• This information is passed to the Planning module, which includes functionality to ingest the perceived environment, and uses that to publish a series of waypoints ahead of the car along with target velocities. The waypoints constitute a projected trajectory for the car.
• The Control module takes the waypoints and executes the target velocities on the car’s controller.
• The car is equipped with a drive-by-wire (DBW) functionality that allows the controller to set its throttle (acceleration and deceleration), brake and steering angle commands.
• When the commands are executed, the car drives itself on the calculated trajectory.
• The entire cycle repeats itself continually so that the car continues driving.
• The modules are implemented as a set of ROS Nodes.
• Some nodes are implemented by Udacity, while other nodes are implemented by my self.

Figure 1. System Architecture

3) Implementation

• As the Figure 1 above shows, there are six ROS nodes in three different modules.
• Of these, I implement three ROS nodes: Traffic Light Detector, Waypoint Updater and Drive-by-Wire (DBW).
• Of the other three nodes, two are implemented by Udacity: Waypoint Loader node, and Waypoint Follower.
• The last one (Obstacle Detector) is implemented as part of Traffic Light Detector.

1. Perception module

• In this project, the Perception module has two ROS nodes: Obstacle Detector and Traffic Light Detector.
• The Obstacle Detector is not required by the project rubric.
• The discussion below is for the Traffic Light Detector node.

1-1. Traffic light detector

• subscribed topics:

  • /base_waypoints: provides a complete list of waypoints on the course
  • /current_pose : provides the car’s current position on the course
  • /image_color : provides an image stream from the car’s camera

• published topics:

  • /traffic_waypoint:

• helper topics:

  • /vehicle/traffic_lights: simulator publishes the location and current color state of all traffic lights in the simulator. It can be used for training data collection or as a stub for testing of other components.

• node files:

  • tl_detector/tl_detector.py: node file
  • tl_detector/light_classification/tl_classifier.py: classifier file

1-2. Obstacle Detector

• NOT implement

2. Planning module

Figure 2. Planning Module

• This project implements the Waypoint Updater node.
• The purpose of the Waypoint Updater node is to update the target velocities of final waypoints, based on traffic lights, state of the lights, and other obstacles.

2-1. Waypoint Updater

• subscribed topics:

  • /base_waypoints : containing all the waypoints in front of, and behind, the vehicle
  • /obstacle_waypoints : the waypoints that are obstacles (not used). This information comes from the Perception module
  • /traffic_waypoint : the waypoint of the ​ red traffic light ahead of the car. This information comes from the Perception module
  • /current_pose : the current position of the vehicle, as obtained by the actual car, or the simulator

• published topics:

  • /final_waypoints : this is a list of waypoints ahead of the car (in order from closest to farthest) and the target velocities for those waypoints.

• node files:

  • waypoint_updater/waypoint_updater.py: node file

3. Control module

Figure 3. Control Module

• Our project implements the Drive-by-Wire (DBW) node.
• The DBW node commands the car or the simulator by providing it with appropriate commands to control the throttle(acceleration/deceleration), brake and steering angle.
• The DBW node instantiates two controllers (longitudinal contoller and lateral contoller)
• Longitudinal contoller
  • takes as input the target speed (as mentioned in the /twist_cmd), the current speed and time delta.
  • control throttle and brake using PID contol algorithm.
• Lateral contoller
  • takes a target yaw rate, the current speed, current position, the following waypoints.
  • calculates the required steering angle, while attempting to be within required tolerance limits for minimum and maximum steering angles.

3-1. Drive-by-Wire (DBW)

• subscribed topics:

  • /twist_cmd : contains commands for proposed linear and angular velocities
  • /vehicle/dbw_enabled : a flag to show if the car is under DBW control or Driver control
  • /current_pose : contains current position of the car
  • /current_velocity : contains current velocity of the car
  • /final_waypoints : contains the list of final waypoints

• published topics:

  • /vehicle/throttle_cmd : the throttle value
  • /vehicle/steer_cmd : the steering angle value
  • /vehicle/brake_cmd : the brake value

• node files:

  • twist_controller/dbw_node.py

4) Project Simulation Result

Figure 4. Project Result

5) Simulation Method

1. Setup Environment

• This project is running Ubuntu 16.04.
• Follow these instructions to install ROS
  • ROS Kinetic if you have Ubuntu 16.04.
• Dataspeed DBW
  • Use this option to install the SDK on a workstation that already has ROS installed: One Line SDK Install (binary)
• Download the Udacity Simulator.

2. Usage Simulation

2-1. Clone the project repository

git clone https://github.com/udacity/CarND-Capstone.git

2-2. Install python dependencies

cd CarND-Capstone
pip install -r requirements.txt

2-3. Make and run styx

cd ros
catkin_make
source devel/setup.sh
roslaunch launch/styx.launch

Run the simulator

2-4. Real world testing

1. Download training bag that was recorded on the Udacity self-driving car (a bag demonstraing the correct predictions in autonomous mode can be found here)

2. Unzip the file

unzip traffic_light_bag_files.zip

3. Play the bag file

rosbag play -l traffic_light_bag_files/loop_with_traffic_light.bag

4. Launch your project in site mode

cd CarND-Capstone/ros
roslaunch launch/site.launch

5. Confirm that traffic light detection works on real life images