Graph-Based Local Trajectory Planner
The graph-based local trajectory planner is python-based and comes with open interfaces as well as debug, visualization and development tools. The local planner is designed in a way to return an action set (e.g. keep straight, pass left, pass right), where each action is the globally cost optimal solution for that task. If any of the action primitives is not feasible, it is not returned in the set. That way, one can either select available actions based on a priority list (e.g. try to pass if possible) or use an own dedicated behaviour planner.
The planner was used on a real race vehicle during the Roborace Season Alpha and achieved speeds above 200kph. A video of the performance at the Monteblanco track can be found here.
Disclaimer
This software is provided as-is and has not been subject to a certified safety validation. Autonomous Driving is a highly complex and dangerous task. In case you plan to use this software on a vehicle, it is by all means required that you assess the overall safety of your project as a whole. By no means is this software a replacement for a valid safety-concept. See the license for more details.
Documentation
The documentation of the project can be found here.
Contributions
[1] T. Stahl, A. Wischnewski, J. Betz, and M. Lienkamp,
“Multilayer Graph-Based Trajectory Planning for Race Vehicles in Dynamic Scenarios,”
in 2019 IEEE Intelligent Transportation Systems Conference (ITSC), Oct. 2019, pp. 3149–3154.
(view pre-print)
Contact: Tim Stahl.
If you find our work useful in your research, please consider citing:
@inproceedings{stahl2019,
title = {Multilayer Graph-Based Trajectory Planning for Race Vehicles in Dynamic Scenarios},
booktitle = {2019 IEEE Intelligent Transportation Systems Conference (ITSC)},
author = {Stahl, Tim and Wischnewski, Alexander and Betz, Johannes and Lienkamp, Markus},
year = {2019},
pages = {3149--3154}
}
Metadata
Release files for graph-ltpl 0.48
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| graph_ltpl-0.48.tar.gz | 78.8 kB | Without provenance | Details for graph_ltpl-0.48.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| graph_ltpl-0.48-py3-none-any.whl | Python 3 | none | any | Details for graph_ltpl-0.48-py3-none-any.whl |
Total release size: 177.6 kB
Release files / graph_ltpl-0.48.tar.gz
| Download URL | graph_ltpl-0.48.tar.gz |
|---|---|
| Size | 78.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3454e6569e22d622dc8ebf5d375d06a4db27fe907283c88bc5c4412f06823db9
|
|
BLAKE2b-256 checksum How to use checksums |
32d9e339015300eedfb3aaacae682f93c53aa4f31d8dc4a83889d511b587a7ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.5.2
|
Release files / graph_ltpl-0.48-py3-none-any.whl
| Download URL | graph_ltpl-0.48-py3-none-any.whl |
|---|---|
| Size | 98.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ea3e4c68733399200de83941c04bad20cc383aa3b6478c9c6078e40dd56ee35
|
|
BLAKE2b-256 checksum How to use checksums |
8369466530a5b91c4642f2b3c12ba1516ac4c0bc564913b7d0a075f24ba9dfe8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.5.2
|
Security for graph-ltpl 0.48
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.