Open AD Kit WG Meeting 2022/03/24

[ghost]

Administrative

Previous meeting minutes

Attendees

Chaired by Lalith

• Anthony Tran (Marvell)
• Armağan Arslan (LeoDrive.ai)
• Christian John (AWF)
• David W (A3VG)
• Daisuke Hashimoto (T4)
• Eiji Sekiya (T4)
• Fumihito Ito (T4)
• Hiroshi Igata (T4)
• John Crosbie (Excelfore)
• Kasper Ornstein Mecklenburg (Arm)
• Kei Kato (T4)
• Lalith Vipulananthan (T4)
• Madhurika Joshi (Marvell)
• Mark Singer (Excelfore)
• Naoyori Tanzawa (T4)
• Petter Markkula (TomTom)
• Richard Jiang ()
• Rick Liu (FXN)
• Ryohsuke Mitsudome (T4)
• Siavash Shakeri (TomTom)
• Stephen Li (Autocore)
• Srikant Acharya (Excelfore)
• Tsigigenet Dessalgn
• Wood Wang (TomTom)
• Yoshiya Fujii (T4)

Agenda

• Introduction of new attendees if present - 5 mins
• Announcements (David) - 5 mins
• Review of backlog actions (Lalith) - 5 mins
• Discussion topics
  • Open AD Kit 2.0 plan (Lalith) - 5 mins
  • TomTom Autostream presentation - 20 mins
  • eSync presentation - 20 mins
• Relationship between artifacts in AWF working groups（Hashimoto) - 10 mins

Introduction of new members

• Introduction of new attendees if present - 5 mins
  • Excelfore
    • Mark Singer
    • John Crosbie
    • Srikant Acharya
  • Richard Jiang
  • TomTom
    • Petter Markkula
    • Siavash Shakeri
    • Wood Wang

Announcements

• General Autoware related discussion has moved from Slack to Discord!
  • Invitation link: https://discord.gg/Q94UsPvReQ
• TSC updates
  • Merge of the Open AD Kit and Hardware working groups has been approved, with David, Lalith and Armagn as co-chairs, rotating over three time slots
  • Currently working on reimagining the mission, vision of goals of the new group
  • CJ noted that there was a discussion about safety and whether this should also fall under the Open AD Kit umbrella Further discussions taking place with the SPC.
• Working group meetings will move to a weekly schedule to accomodate the additional topics from the Hardware WG
  • Next meeting will be on March 31st!

Backlog

• Set up a new Zoom meeting for the WG that allows participants to join from a browser instead of having to install the Zoom client
  • In progress
• Create a Discussion for the Open AD Kit WG to assess the suitability of ITRI's Bus ODD current demo hardware for use with the Open AD Kit
  • Since this was a specific task, an issue was created instead.
  • If anyone has any comments or questions, then please add them to the issue:
    • Assess ITRI's hardware spec for Open AD Kit suitability autoware-projects#12
• Create a Discussion for Open AD Kit 2.0 scope definition
  • https://github.com/autowarefoundation/autoware/discussions/89

Discussion topics

Open AD Kit 2.0 plan (Lalith)

• Determine scope of Open AD Kit 2.0, based on Bus ODD and ITRI bus project
  • Confirm how much of ITRI's bus project can be shared with AWF
  • Ask ITRI to confirm which components of the Bus project can be shared, and by when
  • WG to agree on scope
• Determine use cases
  • List the current use cases that are met by Open AD Kit 1.0 (due 03/18)
  • WG to propose use cases via GitHub discussion after scope has been confirmed
    Determine hardware configuration
• Determine hardware configuration
  • Evaluate ITRI hardware for Open AD Kit suitability (March 18th): created .gitignore #88
  • Work with Hardware WG to set baseline hardware spec to meet the ODD use cases
• Determine software changes required to meet the use cases
  • Open AD Kit 1.0 currently uses Autoware.Auto, so target Autoware Core for 2.0
  • Determine when Autoware Core/Universe will be ready for use with the Open AD Kit
  • Create an Autoware Core/Universe Docker container that can works on the currently supported Open AD Kit hardware
  • Test and confirm that the Core/Universe Docker container runs on the Open AD Kit 2.0 hardware specification]
• Plan is to visualise these high-level tasks as a Gantt chart to show dependent and independent tasks

TomTom Autostream presentation

20220324 TomTom AutoStream Intro - Autoware Open AD Kit WG.pdf

• TODO: Add summary of main points

Questions

Armagn - Is traffic light information planned for the converter?
Petter - Current scope is for highways and very few traffic lights. Currently planning lower-class coverage to include traffic lights

Armagn - Can TomTom provide PCD data?
Petter - Not in scope, just aiming for OTA updates and PCD is too large

Armagn - Can tiles be used to determine where to go?
Petter - TomTom has navigation maps and HD maps, but navigation maps are not delivered via AutoStream.

Richard Jiang: What typical bandwidth need for HD map updating?
Petter: About 100MB per year for OTA update for a "normal" use. But of course will depend on the driver behavior as map data in AutoStream is updated on demand as

David: If there was a custom, closed circuit route for a bus or shuttle for example around a corporate or college campus, could the TomTom map be supplemented with this route?

eSync presentation

eSync_Alliance_Presentation_AWF_OpenAD-WG_23Mar2022.pdf

• TODO: Add summary of main points

Questions

Armagan: Wind River Studio was acquired by Aptiv. Is Aptiv part of the eSync Alliance?
Mark: Aptiv is a member of the eSync Alliance and is on the board of the eSync Alliance. We note that eSync Alliance is inclusionary, not exclusionary, so OEMs may use eSync and non-eSync applications in their vehicles.

Richard Jiang: Can eSync server deploy to on-prem?
Mark: Some eSync servers are being used to deploy to private clouds. Excelfore (as an Alliance member) has a preference to offer hosting as a service, since it is more fluent/fluid to provide
John: eSync Server is cloud-agnostic and has been deployed on AWS, Google Cloud, Azure and OpenShift. Flexible, so if your system supports Kubernetes and OpenShift or Helm, then it can be done. Managed services are used where possible (eg: Amazon RDS for database), but on-premise installation is possible.
Mark: RedHat has published a whitepaper on eSync and the OpenShift environment. Can be provided directly via Mark.

Richard Jiang: x86 and RPi architectures are supported. What about ARM?
Mark: eSync has been implemented on Qualcomm, NXP, Texas Instruments for a variety of automotive components. Model is to be agnostic to processor and OS as much as possible.

Relationship between artifacts in AWF working groups（Hashimoto)

• Due to time constraints, it was agreed to remove this agenda item and to set up a GitHub discussion instead
  KLT based Multi Tracking #116

Action Items