Self-Driving Car Engineer Nanodegree Program
- cmake >= 3.5
- All OSes: click here for installation instructions
- make >= 4.1(mac, linux), 3.81(Windows)
- Linux: make is installed by default on most Linux distros
- Mac: install Xcode command line tools to get make
- Windows: Click here for installation instructions
- gcc/g++ >= 5.4
- Linux: gcc / g++ is installed by default on most Linux distros
- Mac: same deal as make - [install Xcode command line tools]((https://developer.apple.com/xcode/features/)
- Windows: recommend using MinGW
- uWebSockets
- Run either
./install-mac.sh
or./install-ubuntu.sh
. - If you install from source, checkout to commit
e94b6e1
, i.e.Some function signatures have changed in v0.14.x. See this PR for more details.git clone https://github.com/uWebSockets/uWebSockets cd uWebSockets git checkout e94b6e1
- Run either
- Simulator. You can download these from the project intro page in the classroom.
Fellow students have put together a guide to Windows set-up for the project here if the environment you have set up for the Sensor Fusion projects does not work for this project. There's also an experimental patch for windows in this PR.
- Clone this repo.
- Make a build directory:
mkdir build && cd build
- Compile:
cmake .. && make
- Run it:
./pid
.
Tips for setting up your environment can be found here
We've purposefully kept editor configuration files out of this repo in order to keep it as simple and environment agnostic as possible. However, we recommend using the following settings:
- indent using spaces
- set tab width to 2 spaces (keeps the matrices in source code aligned)
Please (do your best to) stick to Google's C++ style guide.
Note: regardless of the changes you make, your project must be buildable using cmake and make!
More information is only accessible by people who are already enrolled in Term 2 of CarND. If you are enrolled, see the project page for instructions and the project rubric.
- You don't have to follow this directory structure, but if you do, your work will span all of the .cpp files here. Keep an eye out for TODOs.
Help your fellow students!
We decided to create Makefiles with cmake to keep this project as platform agnostic as possible. Similarly, we omitted IDE profiles in order to we ensure that students don't feel pressured to use one IDE or another.
However! I'd love to help people get up and running with their IDEs of choice. If you've created a profile for an IDE that you think other students would appreciate, we'd love to have you add the requisite profile files and instructions to ide_profiles/. For example if you wanted to add a VS Code profile, you'd add:
- /ide_profiles/vscode/.vscode
- /ide_profiles/vscode/README.md
The README should explain what the profile does, how to take advantage of it, and how to install it.
Frankly, I've never been involved in a project with multiple IDE profiles before. I believe the best way to handle this would be to keep them out of the repo root to avoid clutter. My expectation is that most profiles will include instructions to copy files to a new location to get picked up by the IDE, but that's just a guess.
One last note here: regardless of the IDE used, every submitted project must still be compilable with cmake and make./
A well written README file can enhance your project and portfolio. Develop your abilities to create professional README files by completing this free course.
The simulator will provide you the cross track error (CTE) and the velocity (mph) in order to compute the appropriate steering angle.
The goal of this project is to implement a PID controller in C++ to maneuver the vehicle around the track!
Project Steps:
- Implement PID controller for car's sterring
- Fine tuning the hyperparmater of the controller
A proportional–integral–derivative controller (PID controller or three-term controller) is a control loop mechanism employing feedback that is widely used in industrial control systems and a variety of other applications requiring continuously modulated control.
A PID controller continuously calculates an error value
-
P: Proportional
- Term P is proportional to the current value of the SP − PV error
${\displaystyle e(t)}$ . For example, if the error is large and positive, the control output will be proportionately large and positive, taking into account the gain factor "Kp". - Using proportional control alone will result in an error between the setpoint and the actual process value because it requires an error to generate the proportional response. If there is no error, there is no corrective response.
- Term P is proportional to the current value of the SP − PV error
It is the most effective component of the controller as the steeting value is proportional to the error. If we are using P-controller only, we will have an oscillation around the set value. So the P-controller is unstable.
As the gain of the P value increase the controller oscillate faster.
- I: Integral
- Term I accounts for past values of the SP − PV error and integrates them over time to produce the I term.
- For example, if there is a residual SP − PV error after the application of proportional control, the integral term seeks to eliminate the residual error by adding a control effect due to the historic cumulative value of the error.
- When the error is eliminated, the integral term will cease to grow. This will result in the proportional effect diminishing as the error decreases, but this is compensated for by the growing integral effect.
This component adjust for the bias in the sterring angle. This is measured by the sum of the CTE over time.
- D: Differential
- Term D is a best estimate of the future trend of the SP − PV error, based on its current rate of change. It is sometimes called "anticipatory control", as it is effectively seeking to reduce the effect of the SP − PV error by exerting a control influence generated by the rate of error change.
- The more rapid the change, the greater the controlling or damping effect.
This term solve the issue of oscillation of the P-Controller. This will allow to approach smoothly the target trajectory.
The twiddle algorithm is usually used to further optimize the values of the parameters after I set the initial values.
The main issue that I faced was that the simuator was not working correclty on windows without GPU. So I had to run the code of the workspace of Udacity to get to the correct behaviour. You can read more about it from in Link1
I stared the initial value of the parameter by
Kp = 0.1;
Ki = 0.004;
Kd = 3.0;
The steering value should be within [-1, 1], so I add a small code to fullfill this requirement
if(steer_value > 1)
{
steer_value = 1;
}
else if(steer_value < -1)
{
steer_value = -1;
}
else
{
/* Do Nothing */
}
If found that the controller is working fine, so I decided to increase the average velocity to 50mph
msgJson["throttle"] = 0.5;