Repository Summary
Description | Build robotics applications with AWS DeepRacer device software and hardware: https://www.amazon.com/dp/B07JMHRKQG |
Checkout URI | https://github.com/aws-deepracer/aws-deepracer-launcher.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2024-05-15 |
Dev Status | UNKNOWN |
CI status | No Continuous Integration |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Packages
Name | Version |
---|---|
deepracer_launcher | 0.0.1 |
README
AWS DeepRacer core application overview
The AWS DeepRacer vehicle is a Wi-Fi enabled physical vehicle that can drive itself on a physical track by using a reinforcement learning model. This repository contains the robot application code shipped with the AWS DeepRacer hardware. It also includes examples demonstrating how you can extend the AWS DeepRacer application for new scenarios. For example, the Follow the Leader (FTL) sample project shows how you can use object detection and navigation to modify the vehicle application to follow you as you move about in a room.
If you are a first-time user, do the following:
- Read What Is AWS DeepRacer?. This is the documentation for AWS DeepRacer. It provides more details about the AWS DeepRacer vehicle, training and evaluating models, and more.
- Read Getting started with AWS DeepRacer. In this tutorial, you learn how to install the latest AWS DeepRacer code and then build and run the AWS DeepRacer application.
- Explore the Follow the Leader (FTL) sample project. This sample project changes the behavior of the vehicle application. Your vehicle will try to follow you as you move about a room.
- Explore the Mapping sample project with ROS Noetic on Ubuntu 20.04. This sample project uses SLAM with a RealSense™ D435/D435i camera on ROS to map and localize an environment.
- Learn about the Robot Operating System (ROS) 2. The AWS DeepRacer application is based on ROS 2 Foxy.
Build your sample project
Create a simple HelloDeepRacerWorld
example application to understand the basics needed to build your own sample project. Read the Create your sample project guide.
CONTRIBUTING
Contributing guidelines
Thank you for your interest in contributing to our project. Whether it’s a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
Reporting bugs and requesting features
Use the GitHub issue tracker to report bugs or suggest features.
When filing an issue, check existing open and recently closed issues to make sure someone else hasn’t already reported the issue. Try to include as much information as you can. Details like these are incredibly useful:
- A reproducible test case or series of steps
- The version of our code being used
- Any modifications you’ve made relevant to the bug
- Anything unusual about your environment or deployment
Contributing through pull requests
Contributions made through pull requests are much appreciated. Before sending us a pull request, ensure that:
- You are working against the latest source on the
main
branch. - You check existing open and recently merged pull requests to make sure someone else hasn’t addressed the problem already.
- You open an issue to discuss any significant work; we would hate for your time to be wasted.
To send us a pull request:
- Fork the repository.
- Modify the source; focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
- Ensure local tests pass.
- Commit to your fork using clear commit messages.
- Send us a pull request, answering any default questions in the pull request interface.
- Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
GitHub provides additional documentation on forking a repository and creating a pull request.
Finding ways to contribute
Looking at the existing issues is a great way to find something on which to contribute. As our projects, by default, use the default GitHub issue labels (enhancement
, bug
, duplicate
, help wanted
, invalid
, question
, wontfix
), looking at any help wanted
issues is a great place to start.
Code of Conduct
This project has adopted the Amazon Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opensource-codeofconduct@amazon.com with any additional questions or comments.
Security issue notifications
If you discover a potential security issue in this project we ask that you notify Amazon Security via our vulnerability reporting page. Please do not create a public GitHub issue.
Licensing
See the LICENSE file for our project’s licensing. We will ask you to confirm the licensing of your contribution.