Open AD Kit WG Meeting 2022/04/21

[armaganarsln]

Administrative

Previous meeting minutes

Attendees

Chaired by Armağan

• Andreas Färber (SUSE)
• Armağan Arslan (LeoDrive.ai)
• Christian John (SPC)
• Daisuke Hashimoto (T4)
• David W (A3VG)
• Eiji Sekiya (T4)
• Esteve (AWF)
• Girish (Arm)
• Fumihito Ito (T4)
• Kasper Ornstein Mecklenberg (Arm)
• Hiroshi Igata (T4)
• Lalith Vipulananthan (TierIV)
• M. Fatih Cirit (AWF)
• Mark Lambe (KLAS)
• Matt Spencer (Arm)
• Naoyori Tanzawa (T4)
• Özkan Köroğlu (Robeff Technology)
• Ryohsuke Mitsudome (T4)
• Samet Kütük (Leodrive)
• Stephen Li (Autocore)
• Tsigigenet Dessalgn (Marvell)

Agenda

• Introduction of new member (KLAS) presentation
• Announcement of TSC WG activity roles & responsibilities
• Announcement of hardware work to be discussed every 3 weeks
• Presentation of hardware work status:
• Question about the driver status of ROS2 hardware
• Announcement of GTM (CJ, Samet)
• Review of backlog actions
  • Data recording minimum requirements
  • Clarify the license that will be provided with the eSync Autoware PoC
• Review of open discussions
  • KLT based Multi Tracking #116
  • https://github.com/autowarefoundation/autoware/discussions/89

Introduction of new members

• Mark Lambe (Product Marketing Manager, KLAS)
  • Joining to give a presentation on KLAS, who recently joined the Autoware Foundation
• Ozkan Koroglu (Managing Director of Product Delivery for Robeff Technology)
  • Provide last mile delivery solutions

KLAS company presentation

• Mark Lambe (Product Marketing manager) presenting
• Kasey Kolyno (US-based systems engineer)
• KLAS provide intelligent edge solutions (relatively new to automotive, but 30 year company history)
  • specialise in designing rugged/hardened gear (eg: network infrastructure for the edge)
• How did KLAS get involved in automotive?
  • Asked to design an edge platform for a OEM
  • RAVEN = Ruggedized Autonomous Vehicle Network (19"x9"x9")
  • modular components can be plugged into RAVEN
• TRXD8 - compute+storage
  • can store between 240-480TB!
  • ingest Server that can take the cassette and then upload to the public/private cloud
  • includes CAN and network interface (can plug straight into the car's CAN network)
• Did some initial testing with RAVEN and Autoware.Auto
  • Virtualisation - Virtualisation layer allows for multiple Autoware stacks to run on the same platform on a single test vehicle
  • Automation - Orchestration using Ansible
  • Deploying Autoware.Auto on KLAS's RAVEN platform

Announcements

• Announcements of TSC WG activity roles & responsibilities
  • idea is that Project Leaders will be in charge of the roadmap/requirements (based on high-level directions from the BoD)
  • For any new development tasks, need to make a proposal to project leaders
    • Proposers will have responsibility for the task!
    • If additional resource is needed, or new people need to be invited to assist with the planned task, the proposer should also discuss this with the project leaders
• Announcement of hardware work to be discussed every 3 weeks

Introduction of current hardware design

• https://drive.google.com/drive/folders/1Gp29y6896Yc9wc8Eg0BssYiDyz9MUt4I?usp=sharing
• Hardware project files are available for modification, but output is a PDF file showing all of the hardware and networking
• Also discussing with two other companies (ADASTEC and ?) who may also be able to test the bus ODD, so may finish with three companies testing!
• Need to also consider FOV of sensors, how they are positioned wrt to the vehicle

Review of backlog actions

• Create a discussion for the Open AD Kit WG to discuss data recording requirements with the Software WG (eg: which topics are required for a minimum data set) @mitsudome-r - due 04/13

  • Done! Develop multi lane #166

• Ask Excelfore to clarify the license that will be provided with the eSync Autoware PoC @LalithVipulananthan - due 04/08

  • Done! License question was added to the existing Q&A discussion and is currently pending a response

Review of open discussions

Open AD Kit 2.0 scope

The overall comments & discussions on the scope

• Integrate Autoware Universe with Open-ADKit and review the results
• Prepare and share with everyone the benefits, problems that could be addressed, target users, and applications of Open AD Kit architecture
• Define candidate computing platforms for demonstration of the final work
• Define an operational concept demonstration and create issues around it
• Investigate orchestration methods for self-driving vehicles
• Create a microservices application around Bus-ODD for field testing (live sensor data)
• Integration testing using containers and orchestrator (cloud deployment, CI/CD)
• OTA field application (esync or similar)
• Find more researchers or groups who are willing to contribute, test & demonstrate

Discussion topics

Open AD Kit GTM Proposal

• Postponed last meeting at CJ's request

Q&A follow-up

Automotive Safety

• Check with CJ if he is interested to bring safety as a topic to the WG.

SUSE

• No additional comments or questions.

eSync

• No additional comments or questions.

Action Items

• [ ]

[mitsudome-r]

I we have time, I would like to review some of the concerns that I have regarding Kasper's slide.

• If we achieve all the items that are listed on the slides, what would be the benefit to the users of Open AD Kit?
• To me, it only seems to achieve the red box in the diagram. With this, users might get out-of-the-box-"runtime" of Autoware but not development platform. (That alone can be achieved just by distributing a docker image of Autoware)
• How does the user of Open AD Kit able to improve Autoware on cloud when they find any issues on their site? If we are saying Open AD Kit is a cloud-native development platform, then shouldn't tools that run on cloud (data collection, MLOPs, simulation, etc) also needed to be provided?
• What are the limitation in Open AD Kit v2.0 if we proceed with Kasper's slide? Are those acceptable from GTM point of view?
• Also, it seems to be ambiguous about who would work on which task. (e.g., Who is setting up k3s orchestrator on vehicle/cloud? Who is setting up the pipeline to upload artefacts to container registry and who would be doing the maintenance? ... ) Is Arm going to be able to do the initial setup if we give access to the repository, or are you expecting work done by the other members of AWF? If so, do we have any companies who have expertise to do the tasks?