Open AD Kit WG Meeting 2022/07/20

[ghost]

Administrative

• Previous meeting minutes
• Open AD Kit project board
• Open AD Kit 2.0 schedule

Attendees

Chaired by Lalith

• CJ (AWF)
• Daisuke Hashimoto (T4)
• David W (A3VG)
• Eiji Sekiya (T4)
• Fumihito Ito (T4)
• Hiroshi Igata (T4)
• Kasper Ornstein Mecklenburg (ARM)
• Lalith Vipulananthan (T4)
• Naoyori Tanzawa (T4)
• Ryohsuke Mitsudome (T4)
• Stephen Li (AutoCore)
• Yoshi Takashima (T4)
• Xinyu Wang (T4)

Agenda

• Introduction of new members
• Announcements
• Review of backlog actions
• Discussion topics

Introduction of new attendees/members

• Xinyu Wang (TIER IV)
  • Joined the company about half a year ago and has been mostly attending the software WG meetings, but will be attending Open AD Kit meetings from this week.

Announcements

• N/A

Review of backlog actions / open issues / schedule

Actions

• CJ and Armağan to discuss the Foxglove alliance proposal offline
  • Armağan will reach out to Foxglove about the alliance discussion
• CJ to work with Armağan to bring the topic of GDPR compliance to the SPC and AWF board
  • Armağan will bring this topic to the TSC meeting this week
• WG to write up a test matrix for Open AD Kit 1.0 and desired hardware, and then create a discussion to seek more testers who have access to that hardware
  • https://github.com/orgs/autowarefoundation/discussions/2738
  • Please add comments/feedback to the discussion!
• Create an autoware.org meeting invitation group for the Open AD Kit WG and add it to each meeting as an invitee
  • New group created: https://groups.google.com/a/autoware.org/g/open-ad-kit-working-group-meeting-invitations/
  • Contacted AWF admin and waiting for an update

Issues

• Integrate Autoware Universe with Open AD Kit and review the results
  • Verify that Autoware Universe can be run with Open AD Kit 1.0 autoware-projects#32
  • Was T4 able to provide Kasper with logs so he can investigate the map display problem with the latest yocto build on AVA?
    • T4 will aim to provide the information by the end of next week.
      • Although errors could be seen in the console, errors were the same on both AVA and Ito-san's laptop
      • Provide error logs for both old yocto version and latest yocto version tests so that Kasper can compare
      • Ito-san to add the steps required (download the ARM Docker image for Autoware, download map data, build scenario simulator on x86 host etc)
  • Has AutoCore been able to write up their test report?
    • Stephen to ping Shark about updating the issue, and also to ask if Shark is still able to do the same tests on a Jetson AGX Xavier
• Create separate containers for testing Open AD Kit #2454
  • Fatih was originally planning to test this PoC work on x86, locally compiling
  • If he is able to share the Docker container with Kasper (assuming no x86 dependencies in the source code) then Kasper can pick up the work from that point if Fatih is not able to also test on ARM with Ubuntu 20.04

Schedule review

• MIH demo
  • CJ had a planning call with Kasper, Daniel, Tanzawa-san, Sekiya-san, and is aiming to do weekly calls to explore the lower-level details of the demo and execution
  • Aiming for ARM DevSummit first in October (26th-27th), and then MIH in November (6th-7th)
  • For the ARM DevSummit, other LiDARs are being explored (Foxconn LiDAR will be for the MIH demo)
  • Should we define a cut-off date for the microservice PoC work?
    • If we don't have that work complete by XX/YY, then we need to move to plan B (updating a monolithic container using eSync)
    • Even we don't meet the cut-off date, we're not planning to drop the idea entirely. We just need to be realistic about what can be achieved for the demo!
  • Could Fatih describe the challenges involved in containerizing Perception only, so that ARM could potentially assist or provide advice on how to approach the problem?
    • Lalith to find the previous discussion on this topic and add it to the existing issue
• OTA updates
  • No progress to report at this time
• Use cases with ConOps/OpsCons
  • https://docs.google.com/spreadsheets/d/17CSw6mkl4HHQ6Dy9RSp1JHi3oPKlNedhw5fAO0Gi6WE/edit?usp=sharing
  • Hashimoto-san created the spreadsheet above with a list of minimum necessary use cases
    • Each use case has a goal, primary actor (eg: SDV developer), secondary actor, trigger, preconditions, basic flow, alternative low and postconditions
    • Still working on basic flow and alternative flow
    • Not sure about granularity of use cases. Is the level of granularity of use cases in the spreadsheet appropriate, or should it go into more detail or not?
  • David noted that Armağan is passionate about the data collection use case, so will probably give feedback when he is back
  • Next step will be to create a discussion for these use cases to get additional feedback

Discussion topics

• None

Actions

• Ito-san to add the steps required for Verify that Autoware Universe can be run with Open AD Kit 1.0 autoware-projects#32, and to add logs for both old and new yocto versions for Kasper to repro and investigate
• Stephen to ping Shark about updating Verify that Autoware Universe can be run with Open AD Kit 1.0 autoware-projects#32, and also to ask if Shark is still able to do the same tests on a Jetson AGX Xavier
• WG to agree on a cut-off date for the microservice PoC work
• Lalith to add the challenges in containerizing just Perception to Create separate containers for testing Open AD Kit #2454
• Hashimoto-san to create a discussion to get feedback on his Open AD Kit 2.0 use cases