Skip to content
CarND Term 2 Model Predictive Control (MPC) Project
Branch: master
Clone or download
mvirgo Refactor: Improved code style for readability
Refactored all Udacity code files to use consistent code styling and removed too expansive namespaces
Latest commit 49050ec Jan 18, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Refactor: Improved code style for readability Jan 18, 2019
.gitignore initial commit Apr 10, 2017
CMakeLists.txt Generalize libuv version requirement Nov 7, 2017
CODEOWNERS Create CODEOWNERS Jul 7, 2017
DATA.md better formatting May 2, 2017
Dockerfile
LICENSE Add license Feb 10, 2018
README.md Merge pull request #32 from KaixunYao/master Nov 19, 2018
cmakepatch.txt initial commit Apr 10, 2017
docker-compose.yml run project with docker-compose May 21, 2018
install-mac.sh Update install-mac.sh Sep 8, 2017
install-ubuntu.sh Update install-ubuntu.sh May 30, 2017
install_Ipopt_CppAD.md fixed install_Ipopt_CppAD.md Nov 23, 2018
install_ipopt.sh Removing sudo from sudo make install Jan 8, 2019
ipopt.rb
lake_track_waypoints.csv add file with waypoint positions Apr 28, 2017
mumps.rb
scotch.rb Add homebrew license to scotch.rb Jan 10, 2019
scotch5.rb Add homebrew license to scotch5.rb Jan 10, 2019
set_git.sh

README.md

CarND-Controls-MPC

Self-Driving Car Engineer Nanodegree Program


Dependencies

Basic Build Instructions

  1. Clone this repo.
  2. Make a build directory: mkdir build && cd build
  3. Compile: cmake .. && make
  4. Run it: ./mpc.

Build with Docker-Compose

The docker-compose can run the project into a container and exposes the port required by the simulator to run.

  1. Clone this repo.
  2. Build image: docker-compose build
  3. Run Container: docker-compose up
  4. On code changes repeat steps 2 and 3.

Tips

  1. The MPC is recommended to be tested on examples to see if implementation behaves as desired. One possible example is the vehicle offset of a straight line (reference). If the MPC implementation is correct, it tracks the reference line after some timesteps(not too many).
  2. The lake_track_waypoints.csv file has waypoints of the lake track. This could fit polynomials and points and see of how well your model tracks curve. NOTE: This file might be not completely in sync with the simulator so your solution should NOT depend on it.
  3. For visualization this C++ matplotlib wrapper could be helpful.)
  4. Tips for setting up your environment are available here
  5. VM Latency: Some students have reported differences in behavior using VM's ostensibly a result of latency. Please let us know if issues arise as a result of a VM environment.

Editor Settings

We have kept editor configuration files out of this repo 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)

Code Style

Please (do your best to) stick to Google's C++ style guide.

Project Instructions and Rubric

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.

Hints!

  • 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.

Call for IDE Profiles Pull Requests

Help your fellow students!

We decided to create Makefiles with cmake to keep this project as platform agnostic as possible. We omitted IDE profiles to ensure 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 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. 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./

How to write a README

A well written README file can enhance your project and portfolio and develop your abilities to create professional README files by completing this free course.

You can’t perform that action at this time.