donkeycar: a python self driving library
Donkeycar is minimalist and modular self driving library for Python. It is developed for hobbyists and students with a focus on allowing fast experimentation and easy community contributions.
NOTE: this package is a non-official build by the AICoE. Please check the upstream project links for official information.
Quick Links
Use Donkey if you want to:
- Make an RC car drive its self.
- Compete in self driving races like DIY Robocars
- Experiment with autopilots, mapping computer vision and neural networks.
- Log sensor data. (images, user inputs, sensor readings)
- Drive your car via a web or game controller.
- Leverage community contributed driving data.
- Use existing CAD models for design upgrades.
Get driving.
After building a Donkey2 you can turn on your car and go to http://localhost:8887 to drive.
Modify your cars behavior.
The donkey car is controlled by running a sequence of events
#Define a vehicle to take and record pictures 10 times per second.
import time
from donkeycar import Vehicle
from donkeycar.parts.cv import CvCam
from donkeycar.parts.tub_v2 import TubWriter
V = Vehicle()
IMAGE_W = 160
IMAGE_H = 120
IMAGE_DEPTH = 3
#Add a camera part
cam = CvCam(image_w=IMAGE_W, image_h=IMAGE_H, image_d=IMAGE_DEPTH)
V.add(cam, outputs=['image'], threaded=True)
#warmup camera
while cam.run() is None:
time.sleep(1)
#add tub part to record images
tub = TubWriter(path='./dat', inputs=['image'], types=['image_array'])
V.add(tub, inputs=['image'], outputs=['num_records'])
#start the drive loop at 10 Hz
V.start(rate_hz=10)
See home page, docs or join the Discord server to learn more.
Metadata
Release files for aicoe-donkeycar 4.3.0.post1
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 |
|---|---|---|---|---|
| aicoe-donkeycar-4.3.0.post1.tar.gz | 425.2 kB | Without provenance | Details for aicoe-donkeycar-4.3.0.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aicoe_donkeycar-4.3.0.post1-py3-none-any.whl | Python 3 | none | any | Details for aicoe_donkeycar-4.3.0.post1-py3-none-any.whl |
Total release size: 907.0 kB
Release files / aicoe-donkeycar-4.3.0.post1.tar.gz
| Download URL | aicoe-donkeycar-4.3.0.post1.tar.gz |
|---|---|
| Size | 425.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5de9ec34ab99402630e7ffd489f363b7ce808b1aa8ea2fb869c42309b2703384
|
|
BLAKE2b-256 checksum How to use checksums |
3f61872832cf7cb4ddff604407a94468b97a86b8e88f8c263e4163d4997091f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Release files / aicoe_donkeycar-4.3.0.post1-py3-none-any.whl
| Download URL | aicoe_donkeycar-4.3.0.post1-py3-none-any.whl |
|---|---|
| Size | 481.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e1b5b2d5b81fe1d9c3019d6c33b6ffe2f3eda3658eacac64b63a94c104370b7
|
|
BLAKE2b-256 checksum How to use checksums |
a513bc190c78b776cf7cf305606ecb209b798c736e9af027149dad7da5c0f9db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.12
|
Security for aicoe-donkeycar 4.3.0.post1
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.