-
Notifications
You must be signed in to change notification settings - Fork 0
Autonomy Software working group
The Software Working Group is responsible for the overall architecture of Autoware, managing the Autoware Specification creation process, and providing a venue for discussion of topics that do not fit in another working group.
- Ryohsuke Mitsudome (The Autoware Foundation, TSC Chair)
- M. Fatih Cırıt (The Autoware Foundation, Software Architect)
- Bonolo Mathibela (The Autoware Foundation, Project Manager)
- Autoware contributors list
The goals of the Software Working Group are:
- Manage the development of Autoware.Universe, the reference implementation of the Autoware Specification.
- Manage the code quality maintenance processes, such as code reviews and test coverage.
- Coordinate cross-functionality infrastructure, such as release processes, Docker images, continuous integration infrastructure, etc.
- Coordinate the implementations produced by the various contributors and working groups.
The first completed ODD was the creation of Autonomous Valet Parking (AVP) functionality in Autoware.Auto. For details of this activity, see the dedicated AVP hackathon and demonstration wiki page. To run the demos visit our documentation page.
The bus ODD was completed in December 2021 with a demonstration.
- Cargo ODD vehicle platform progress
- Cargo ODD data gathering progress
- Cargo ODD simulation environment creation
- Cargo ODD architecture
- Cargo ODD feature list
- Cargo ODD work breakdown structure
- Autoware.Auto contributors list
- Cargo ODD pointcloud map and overhead route
The main activity of the ASWG is the autonomous bus project.
- Bus ODD software architecture proposal
- Bus ODD architecture design discussions
- Bus ODD candidate simulator comparisons
- Bus ODD milestone development plan
- Bus ODD Project Board
The Software working group drives development of Autoware.Universe to achieve the project milestones defined by the Autoware Foundation's TSC. For a general list of things being done for Autoware.Universe, see the project's issues overview and pull requests overview.
See the discussions with the Meeting:software_wg label
Archived Meeting minutes from Gitlab
The Software working group meets weekly in a time that rotates through three timezones. For meeting information, see the the Autoware Foundation's events calendar for when the upcoming meetings will be held. If you use Google Calendar, you can subscribe to this calendar directly to have it displayed alongside your own calendar events. To do this, click the "+ Google Calendar" link in the bottom right corner of that site. Note that this will not add the events to your own calendar, meaning you may not receive notifications about meetings starting soon. For those not using Google Calendar, you can add the calendar to your own by downloading it as an ICS file and importing that into your calendar software.
The Software working group may announce meetings on the ROS Discourse in the Autoware category. Keep an eye on that category for meeting announcements, then simply join the meeting to participate.
Autoware.AI lives in a collection of GitHub repositories under the Autoware.AI organisation.
Autoware.Auto lives in a collection of GitLab repostories under the Autoware.Auto group.
Autoware.Universe lives in a collection of GitHub repositories under the Autoware organisation.
Both projects are fully open-source and welcome contributions from anyone. Open an issue against the appropriate project to request a feature or open a merge request to add a new feature or fix a bug.
Discussion for the Software working group happens in the following places.
- Technical discussion about particular features and bugs should be done in the GitLab issue tracker for the project and repository in question. See the software project groups for where these live.
- General discussion should be held in the dedicated Autoware category at the ROS Discourse.
- Note that the meeting invite group is not used for discussion. It is only used for managing event invitations. Discussion is disabled for this group.