Open AD Kit WG Meeting 2022/07/14

[ghost]

Administrative

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

Attendees

Chaired by David

• CJ (AWF)
• Daisuke Hashimoto (T4)
• David W (A3VG)
• Eiji Sekiya (T4)
• Fumihito Ito (T4)
• Hiroshi Igata (T4)
• Kasper Ornstein Mecklenburg (ARM)
• Kei Kato (T4)
• Lalith Vipulananthan (T4)
• Naoyori Tanzawa (T4)
• Ryohsuke Mitsudome (T4)
• Stephen Li (Autocore)
• Tsigigenet Dessalgn (Marvell)
• Yoshi Takashima (T4)

Agenda

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

Introduction of new attendees/members

• N/A

Announcements

• We may need to revisit the current scheduling of the WG meetings since attendence is down since moving to the 10pm UTC slot for July
  • Would more attendees from Europe join if we made the meeting 3pm UTC for every meeting?
  • Does the ODD group get more attendance or is it the same?
    • Hiroshi: Need to repeatedly announce the meeting time change. Attendee number fluctuates, but it's still a viable solution.
  • For now, the WG leads will monitor attendence for this month and next and confirm if there is a large difference

Review of backlog actions / open issues / schedule

Actions

• CJ and Armağan to discuss the Foxglove alliance proposal offline
  • CJ will talk with Armağan next week, since Turkey is mostly on holiday this week
• Stephen to confirm whether Autocore is using pre-built Docker images or building from source to test Open AD Kit 1.0 with Universe
  • Pre-built Docker images were used
• CJ to work with Armağan to bring the topic of GDPR compliance to the SPC and AWF board
  • Will also be doing this next week
• Lalith to create a discussion about where the supported hardware list should go to get feedback from the community
  • https://github.com/orgs/autowarefoundation/discussions/2710
• CJ and Samet to write up a more detailed plan for the MIH demo
  • MIH AD WG_ MIH Open AD Kit Demo 20220707.pdf
  • This is a high-level storyboard. CJ is working on the details with Daniel and Yoshi from T4, so Daniel can start prototyping the demo at his lab in Taiwan. This demo would also form the basis for the ARM DevSummit, since the MIH event was pushed back to November
• David: Is Daniel expected to help work on containerization efforts as well?
  • CJ: Demo is running on the ADLINK AVA platform. What the WG is doing on the containerisation side with Fatih will be the basis of what goes into the demo. If we end up with two containers as discussed (planning+control, and then everything else), we will be running those containers as pre-built images
  • Plan is to show this as demonstrated, using eSync to push the update, but need to understand how long that update will take in real-time
  • Although the demo talks about an update to the Perception algorithm, the fact that we are splitting off Planning and Control into one container and Perception will be in the bigger container with everything else is fine. We will just update the larger container.
  • Tanazawa: T4 is currently working on estimating the time required to update (will depend on the size of the container), using eSync for OTA updates.
  • CJ: Is it possible to have both container versions already on the container, and switch them out that way?
  • Tanzawa: That may be possible, but we need to check

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
  • T4 has successfully tested the Planning Simulator on AVA (single container with the old yocto builds)
    • Is it okay to use older versions of EWAOL for the demo? If not, then we need to investigate the issue.
    • ARM have run the AVP demo on version 1.0, on both versions of meta-ewaol with no issues
    • Kasper asked if is it possible to provide more information on the errors. Ito-san will look into this and provide info to Kasper
  • Autocore has finished testing Autoware Universe on PCU with pre-built Docker images, and no issues found. A report will be added to the issue once finished.
• 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/
  • Invitation group is not quite configured correctly -> need to ask the AWF admin to take a look
• Create separate containers for testing Open AD Kit #2454
  • Turkey is on holiday this week, so no updates from Fatih
  • Kasper has not had a chance to look at the build.sh file since returning from his recent holiday

Schedule review

• Use cases with ConOps/OpsCons
  • Hashimoto-san is updating this and will present in next week's WG meeting
• OTA updates
  • T4 are in the process of testing update times with eSync

Discussion topics

Microservices Autoware PoC

• David: Can Fatih test with an ARM device?
  • Lalith noted that Fatih said he was only planning to do the PoC using Ubuntu on x86, and may not have room to test on an ARM device since he still has Software WG commitments
  • In terms of documenting his work, that information should be added to the issue and can be added to the main Autoware documentation afterwards
  • David also asked if Shark could potentially help with testing on an ARM device (like the AGX)
  • Stephen suggested writing up a test matrix and creating a discussion to ask for more testers to help out. Doing so would allow the WG to to coordinate who is testing on which hardware.

Actions

• 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