Open AD Kit Working Group

Inspired by Scalable Open Architecture For Embedded Edge’s (SOAFEE) take on how to enable the Software Defined Vehicle (SDV), Open Autonomous Drive Kit (Open AD Kit) aims to democratize autonomous drive (AD) systems by bringing the cloud and edge closer together. In doing so, Open AD Kit will lower the threshold for developing and deploying the Autoware software stack.

Working Group Leaders

• Armağan Arslan (LeoDrive.ai)
• David Walmroth (Ann Arbor Autonomous Vehicle Group)
• Lalith Vipulananthan (Tier IV)

Working Group Goals

The Open AD Kit working group's main goals are to:

• Introduce modern cloud-native development methodologies in Autoware's CI/CD
• Add virtualization in the software stack
  • Use a hypervisor to run multiple VMs with the required OS
  • Enable applications to be deployed in a container environment
• Deploy Autoware as a microservices architecture
  • Enable deployment both in the cloud and at the edge
  • Use a mixed-critical aware orchestrator to manage containers
• Provide a consistent production environment in which to deploy Autoware by leveraging Edge Workload Abstraction and Orchestration Layer (EWAOL), a hardware-agnostic custom Linux distro built using Yocto

Benefits of Open AD Kit

• Developers will be able to include their software alongside Autoware
• Ease of deployment of Autoware in a production environment
• Reduce the need to test at the edge, as testing will be moved into the cloud

Open AD Kit Architecture

Relationships between Autoware, Reference Designs, and Open AD Kit

• Autonomous Driving System (ADS) means a system installed in an autonomous vehicle
• DevOps platform supports the ADS during its development and operation stages
• Reference Design is a design document that exhibits the architecture of ADS and a usage guideline of DevOps Platform
• Open AD Kit implements software tools and data pipelines of DevOps platform, provides hardware and system software, and supports Autoware

Out of Scope

The Open AD Kit working group does not develop software features.

Current Activities

Overview

• Planning the scope of Open AD Kit 2.0
• Adding new features to Autoware's CI/CD to enable a multi-container build pipeline
• Listing ROS packages and dependencies for each of Autoware's main components (Sensing, Localization, Mapping, Perception, Planning, Control, DBW interface)

Refer to the Open AD Kit project page for the status of on-going tasks.

Autoware and Open AD Kit roadmap

• The ultimate goal is to achieve a Robotaxi MaaS platform:
  • Level 4 autonomous driving in dense urban environments.
  • A ride-hailing platform that allows riders to hail an autonomous car with their smartphone and take a trip.

Meeting Minutes

From March 10th 2022 onward, meeting minutes can be found in GitHub discussions with the Meeting:openadkit_wg label.

How to Participate

The Open AD Kit working group meets every week on a rotating schedule as follows:

• Even months: Wednesday 10pm UTC
• Odd months: Wednesday 3pm UTC

For meeting information, see the Autoware Foundation event calendar for when 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.

from autoware-documentation.

@samet-kutuk Just to confirm, were you able to work with @kasperornmeck on the proposed changes? Failing that, have you had time to review the proposed changes to give any feedback?

from autoware-documentation.

@LalithVipulananthan
I updated the description, making some clarifications I realized were needed after the WG call this week. I'm happy with the state of it now.

from autoware-documentation.

@samet-kutuk Just to confirm, were you able to work with @kasperornmeck on the proposed changes? Failing that, have you had time to review the proposed changes to give any feedback?

Hi Lalith, I just had the time to look into it.

When I previously looked at it there were some unfinished sentences but Kasper fixed that with revision. I have no feedback to provide as I believe it's sufficient for Github purposes.

from autoware-documentation.

@samet-kutuk
Thanks for reviewing the updated revision, and I did indeed update it after our call last week. Girish has reviewed this and had no comments.

@LalithVipulananthan
If there are no other reviews pending, I think we can update the Open AD Kit page?

from autoware-documentation.

@kasperornmeck Thank you for the proposal!
Can we leave "Relationship between Autoware, Reference Design, and Open AD Kit" and "Proposal of Detailing The Autoware High Level ODD Roadmap" from the current one?

from autoware-documentation.

@kasperornmeck The plan was to wait until this week's WG meeting for any other feedback, so if we have received no other comments by that time, then the wiki can be updated.

And just in case, please note Tanzawa-san's comment above about leaving in the slides from the current wiki page (@samet-kutuk).

from autoware-documentation.

Updated the wiki with the agreed draft above, so closing out issue

from autoware-documentation.