ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Autoware Reference Platform Working Group Meeting #2

The next Reference Platform working group meeting will be held on

Please join if you have an interest in contributing to the Autoware Reference Platform.

Here is the current agenda:

  1. Introduction of the Working Group to all participants
  2. Intents and targets of the Working Group
  3. Discussion on Reference Platform requirements strategy

Please post any additional discussion items if you have them.

If joining by phone
+1 646 558 8656 États-Unis (New York)
+1 669 900 6833 États-Unis (San Jose)
+49 30 3080 6188 Allemagne
+49 30 5679 5800 Allemagne
+49 69 7104 9922 Allemagne
+43 670 309 0165 Austria
+43 72 011 5988 Austria
+32 2 290 9360 Belgique
+32 2 588 4188 Belgique
+1 647 558 0588 Canada
+82 2 6022 2322 Corée [du Sud], République de
+82 2 6105 4111 Corée [du Sud], République de
+385 1300 0988 Croatia
+385 1777 6333 Croatia
+372 660 1699 Estonie
+372 880 1188 Estonie
+33 1 7037 9729 France
+33 7 5678 4048 France
+36 1 408 8456 Hongrie
+36 1 701 0488 Hongrie
+852 5808 6088 Hong Kong, Chine
+353 1 513 3247 Ireland
+353 1 653 3895 Ireland
+353 6 163 9031 Ireland
+972 3 978 6688 Israël
+972 55 330 1762 Israël
+39 020 066 7245 Italie
+39 069 480 6488 Italie
+81 3 4578 1488 Japon
+81 524 564 439 Japon
+60 3 3099 2229 Malaysia
+60 3 9212 1727 Malaysia
+31 20 241 0288 Pays-Bas
+31 20 794 0854 Pays-Bas
+48 22 307 3488 Pologne
+48 22 398 7356 Pologne
+40 31 630 1088 Roumanie
+40 37 170 0418 Roumanie
+44 131 460 1196 Royaume-Uni
+44 203 051 2874 Royaume-Uni
+44 203 481 5237 Royaume-Uni
+44 203 966 3809 Royaume-Uni
+65 3158 7288 Singapour
+65 3165 1065 Singapour
+41 22 518 89 78 Suisse
+41 31 528 09 88 Suisse
+41 43 210 70 42 Suisse
Meeting Id : 457 533 372
Find other local numbers

Thank you everyone for having attended these meetings !
Please find minutes.

Meeting 2019-10-15 & 2019-10-16 Reference Platform Working Group Call #2

Agenda

  • Introduction of the role of the Reference Platform Working Group
  • Process
  • Requirements
  • Initial Reference Platform
  • AOB

Introduction

Process

  • The process is being defined by Autoware TSC - In Progress
  • This will be iterative process with review and approval

Requirements

  • Very initial lists

High Level Requirements for Platform

  • De facto usable platform for Autoware.Auto
  • Reference Platform must be road testing capable platform (in car)
  • Code base available to the relevant gitlab
  • Using silicon from our members
  • Using software from our members
  • Privilege/Promote of Autoware and foundation members technologies
  • Not supporting only development but validation/testing
  • Getting hardware into the testing in the loop
  • Out-of-the-box experience is a key for success
  • AWF is testing code on those platforms
  • Comments Tuesday
    • Alignment with existing development for Autoware.Auto HW support (e.g. LiDAR => listing sensors such as Velodyne)
    • Code for drivers should be pushed upstreamed as much as possible (limiting maintenance)
    • Drivers for boards should be provided by members
  • Wednesday’s Comments
    • Safety related requirements

High Level Requirements for Working Group

  • Maintenance facilitation
  • Proving which Autoware functions is working on which Autoware platforms
  • WG must define information acceptance, and specifications
  • Definition of specs by WG is about silicon, sensors, capabilities
  • WG must coordinate the system validation and members to make the acceptance
  • Responsibility of setting up the board for use cases is up to the user
  • To define level of acceptance of platform+software
  • Tuesday’s Comments
    • Hardware agnostic interfaces definition
    • Definition of vehicle interfaces
    • Open :: to figure out how RP WG is working with .IO
    • Physical level interface with the car, while msg should be defined by .IO
    • RP WG must interact with Vehicle Interface WG to ensure consistency for RP
  • Wednesday’s Comments
    • Architecture definition (specs/arch)
    • System level test cases and test plans (integration within vehicle as a system)

Initial Reference Platform

  • Activity started already

/Ref Platform 1st map.png

  • Driven by Autocore + 96boards, supported by Kalray
  • Initiated prior creation of Working Group
  • Aligning with Working Group as very first platform, helping on defining Working Group and adoption of platform
  • Current status
    • Board designed
    • Board bring-up in progress, expecting first samples out of Autocore end of October
  • Next steps
    • Integration Autoware 1.12 => Autocore
    • Integration of Accelerator (CNN) => Kalray
    • Submission to Working Group for review and adoption
  • Short description
    • TI + NXP Apps chips
    • MPPA Bostan Accelerator Chip
    • Autocore 1.12

/1st PCU Autocore.png

  • Yang introduction (Tuesday’s Comment)
    • Answering desire to have first and perfect platform at first: never happening
    • Proposing to have the ball rolling, by having active work going on
    • Creating tangible way to capture requirements and support activities
    • Enabling development (integration, ROS2, Autoware.AUTO…)
    • Sensor fusion and apps running on NXP (on the board) and on Xilinx
    • Mezzanine card developed for Xilinx chip
    • Intents is to keep a modular approach to demonstrate the actual flexibility of the SW stack
    • Design contributed by Autocore (https://discourse.ros.org/t/wg-rp-autoware-reference-platform-definition-documentation/9949)
    • Will use this environment for contributing requirements as well

AOB

  • Wednesday’s Comments
    • Safety links activity
    • Schematics from Autocore for HCP

Attendees

  • Tuesday’s session
    • Stephane (Kalray)
    • Yang (96boards)
    • Geoff (TierIV)
    • Leo Surico (NXP)
    • Arthur Rocks (HiSilicon)
    • Cheng Chen (Autocore)
    • Josh Whitley (AutonomouStuff)
    • Emmanuel Toillon (Kalray)
    • Dan (Xilinx)
  • Wednesday’s session
    • Vincent Richard (Kalray)
    • Arnaud (NXP)
    • Poonam (NXP)
    • Stephane (Kalray)
    • Emmanuel Toillon (Kalray)

Next Meetings

  • Wednesday 16th of October 9:00AM CET => TOMORROW (APAC friendly)
  • Tuesday 29th of October 5:00PM CET (NA friendly | be careful about Daylight saving Time)
  • Wednesday 30th of October 5:00PM CET (APAC friendly | be careful about Daylight saving Time)

@sstrahm can you share the ical link of that google calendar so that we can import/sync it into our outlook calendars?

See here for the iCal link.

1 Like