Skip to main content
Jump to: navigation, search

Difference between revisions of "OpenADx"

(Meeting Minutes)
m (Integrated tool chain for AD system development)
Line 129: Line 129:
 
Leveraging the current tool landscape and tying in players from industry and academia is a must. Therefore, our approach is two-fold. First, we will fine-tune the development tool chain to the needs of our industry. We do this by integrating existing products in the market, adjusting existing tools to our needs, and developing additional tools through Open Source Software (OSS) where none today currently exist. Second, we will bring areas of expertise together in order to make the complex AD tool landscape more easily accessible for all stakeholders.  
 
Leveraging the current tool landscape and tying in players from industry and academia is a must. Therefore, our approach is two-fold. First, we will fine-tune the development tool chain to the needs of our industry. We do this by integrating existing products in the market, adjusting existing tools to our needs, and developing additional tools through Open Source Software (OSS) where none today currently exist. Second, we will bring areas of expertise together in order to make the complex AD tool landscape more easily accessible for all stakeholders.  
  
[[File:OpenADx Grafiken weiß 72dpi Integrated toolchain for AD system development .jpg]]
+
[[File:OpenADx Grafiken integrated toolchain fo AD system development.jpg]]
  
 
=== Approach ===
 
=== Approach ===

Revision as of 10:00, 12 August 2019

Openadx-logo.png

The OpenADx Working Group wants to serve in the field of software tools for the realization of autonomous driving (AD) by defining open interfacing standards for software for use in vehicle based systems and in testing environments, where the second will typically be realized by means of cloud services doing at least software builds, virtual test runs and collecting results. The name OpenADx thus stands for "Open, Autonomous Driving Accelerator". The group is formed by a multitude of parties from various parts of the world and supported by several well-known industry companies. The OpenADx Working Group is set up as a working group under the governance of the Eclipse Foundation.

Please find the home page and the news ticker of the OpenADx Working Group here (https://openadx.eclipse.org).

Contents

Welcome to OpenADx

Automated Driving (AD) is clustered into three equally important technology areas:

1) In-vehicle technology

2) Cloud technology (backend)

3) Design, development, test and validation tools (tool chain)

OpenADx is focused on the AD tool chain. The goal is to accelerate AD development through open collaboration and open source.

OpenADx' vision is to ensure transparency and make the complex AD tool landscape more easily accessible for enterprise users.


Watch the video on OpenADx here on YouTube: https://youtu.be/7gHLkSzWNKA

OpenADx video.jpeg

News

Members

Company Role
AVL List GmbH Participant Member
JC Information Management GmbH Participant Member
eteration A.S. Participant Member
IBM Participant Member
itemis AG Participant Member
RedHat Participant Member
Robert Bosch GmbH Participant Member
Siemens AG Participant Member

Steering Committee 2019/2020

Company Name
AVL List GmbH Josef Zehetner
JC Information Management GmbH Fleur Ruetz
eteration A.S. Suat Eker
IBM Christian Muszynski
itemis AG Andreas Graf
RedHat Wolfram Richter
Robert Bosch GmbH Andreas Riexinger
Siemens AG Robin van der Made

Related Projects and Project Proposals

Eclipse Cloe

Eclipse Cloe is an enhanced middleware solution for closed-loop simulations, with a focus on functional software tests on system level. Cloe is used as a development tool for interactive and scripted workstation simulations, for code debugging, and for automated tests on servers. Cloe covers a central part of the verification and validation strategy, needed by all vendors in the field of Automated Driving.

Status: Project Proposal

Challenge

AD is a complex challenge and therefore requires a multifaceted development process incorporating a variety of software tools. The tools the industry currently uses are very good, but they don’t seamlessly work with one another. This is a result of the tools not being designed to work together. This is an industry-wide issue that slows us down in the race to AD development. By pooling resources, we can remove the “friction” between widely used tools. We can create something of use to all of us: open, compatible and accessible.

OpenADx Grafiken weiß 72dpi Automated driving is a complex challenge.jpg

Problem and benefits for OEMs and Tier1s

User insight: "Developing automated driving functions is extremely complicated and requires the use of many complex software tools which do not work efficiently with one another. What I need is a set of tools which work with each other seamlessly so that my teams can move through the development process more quickly and efficiently."

Benefit: The automated driving tool chain allows your team to work together more efficiently with a suite of highly integrated tools by enabling seamless transfer of data and code through each step of the automated driving development process.

Problem and benefits for tool and technology providers

User insight: "Currently, tools used to create automated driving applications do not work efficiently with one another. If our tool/technology is compatible with other widely used technologies and tools, it will ease the development process for our customers and make our products even more attractive to them."

Benefit: The seamless integration of your technology in the automated driving tool chain makes it more attractive to organizations developing automated driving applications by increasing their development efficiency.

Integrated tool chain for AD system development

Leveraging the current tool landscape and tying in players from industry and academia is a must. Therefore, our approach is two-fold. First, we will fine-tune the development tool chain to the needs of our industry. We do this by integrating existing products in the market, adjusting existing tools to our needs, and developing additional tools through Open Source Software (OSS) where none today currently exist. Second, we will bring areas of expertise together in order to make the complex AD tool landscape more easily accessible for all stakeholders.

OpenADx Grafiken integrated toolchain fo AD system development.jpg

Approach

We believe an initiative like this should be inclusive, not exclusive. It’s about removing barriers to efficient development with widely established tools. It’s about bundling industry competencies and sharing development. We plan to demonstrate our ability to work together on joint testbeds in an open source setting. This allows potential partners to engage with a limited initial investment. The testbeds produce demonstrable results and strengthen confidence in the approach.

The Idea of Testbeds

Testbeds are setup to produce demonstrable results that incubate potential open source projects. To realize a testbed the idea is to prepare a use case/topic in a series of workshops and to execute so called Hack-Fests which assemble developers from the cooperation partners for a defined period of time, e.g. 3-4 days, in which they realize a demonstrator or prototype.

To identify testbed candidates, everybody is invited to propose ideas here to build a starting point for development of the idea towards the requirements for the execution of a Hack-Fest and for winning further interested parties.

To execute a Hack-Fest, we have identified these minimum requirements to make this a fruitful event:

  • A minimum of two partners collaborating on the testbed, be it companies, universities or research organizations
  • A minimum of 5 committed participants

Workflow for testbed candidates

  1. Verbalization of a task in use case form, which has potential for further work
  2. Contribution of the use cases by interested partners as testbed candidates
  3. Preparation of the testbed candidates in one or a series of workshops to a state that is sufficient for the participants of a HackFest to produce results
  4. Execution of the Hack-Fest
  5. Evaluation of the Hack-Fest results to decide on whether to follow the idea or to stop the effort
  6. Reworking the Hack-Fest results to build a contribution either to an existing project or as an initial contribution of a new open source project

Who We Are and How to Join

The initiative is still in an early stage, but more then twenty organizations have already shown interest. As we have a public website now it would be nice to give newcomers an understanding who is involved and how to interact with us.

Interested Parties

Please add the name of your organization if you are interested in OpenADx or tell us to do it for you.

  • AVL
  • Bosch
  • CEA
  • Continental (ITS)
  • Dassault Systemes (3DS)
  • Elektrobit
  • Eteration
  • German Aerospace Center (DLR)
  • IPG Automotive GmbH
  • itemis
  • Kontrol GmbH
  • MathWorks
  • Microsoft
  • Red Hat
  • Renesas
  • Samsung
  • TESIS DYNAware GmbH
  • ZF Friedrichshafen AG
  • Vattenfall AB

Communication

  • We have a mailing list: Subscribe for news and discussions: Mailing list
  • We have workshops with introduction sessions and have just started to work on concrete testbeds to identify topics that we agree to collaborate on. Currently these workshops are weekly telecons. Please check the mailing list for invitations or ask questions regarding content or participation

Presentations

Upcoming Presentations

  • to be planned

Press releases

Blog posts


Our logo design contest is finished, please find here the winning design.

OpenADx-Logo-CMYK 320 128.png

Copyright Eclipse Foundation

Testbed Candidates

Candidate 1: Simulation

Challenge

The challenge in the simulation of AD functions is the big amount of test cases which can be easily generated by variation of parameters. This big amount of test cases should be handled with parallel execution of test case in multiple instances of the simulation environment.

Use Case Step 1

Target for step 1 of the testbed is the easy integration of simulation tools and function under test allowing to feed a test scenario into the simulation and to get out data for further analysis and visualization.

Acceptance Criteria:

  • The simulation can easily be set up, necessary functionality for integrating and coordinating the different components of the simulation is available.
  • Sinks for simulation data out of the single components but also out of the communication between the components can be attached and the data can be logged and processed during the simulation.
  • The framework allows to integrate multiple simulation tools and offers a standard communication mechanism. New tools can be integrated by providing a connector between the communication mechanism and the tool.
  • The simulation execution setup is prepared for containerization in order to support easy setup and execution in parallel on a scalable hardware platform without extensive installation and maintenance efforts.

Goal for Step 1: Create demonstrators that combine a simple function under test provided by Bosch and the different simulation tools which come with a relevant plant model. For scenarios to demonstrate it is planned to look into Pegasus with the potential addition of a traffic simulated by Eclipse Sumo. The scenario should be based on a closed-loop simulation that uses a model of identified objects as input for the control algorithm.

Base Architecture Step 1

The following picture shows the basic idea for the realization of step 1.

OpenADxTestbed1FuncArch.png

The base decision is to use DDS as the central messaging service between the simulation components. The DDS component has to be chosen in a ROS2 compatible way in order to use the ROS2 mechanisms for data access. DDS/ROS2 compliant components are connected directly to the DDS layer, whereas simulation components not compatible with DDS are attached using a dedicated connector between the component and the DDS-API.

The Simulation Framework is basically a conglomeration of support functionality which builds the glue between the participating components. It offers functionality like the above mentioned connectors, but also time management and other functionality needed to smoothly run the simulation. This component is the main target for the testbeds step 1, since it contains the stuff needed but not provided by existing tools.

On top of these base functionalities, there are simulation tools and the function under test which build the core of the simulation, i.e., the representation of the environment and the control algorithms which observe or even act in this environment. Both provide information on the simulation state in addition to ROS2 means which record the communication between the components.

All recorded data is stored in defined measurement data formats that are stored for further processing. This is represented by the Measurement Data component in the picture which is basically an interface to testbed candidate 2, resp., storing and further processing the recorded data in offline analysis.

For online analysis, tools for visualization or introspection can connect to the DDS communication in the same fashion as the simulation components. This connection allows to control the simulation, e.g., for debugging purposes. The mechanisms rely on the possibilities of ROS2 for interacting with the simulation components.

Tools under investigation concerning usage in the demonstrator currently are:

  • DDS - implementation (tbd)
  • ROS2/RVIZ
  • Matlab/Simulink
  • DYNA4
  • AirSim
  • Gazebo
  • Dymola (Modelica) ?

Topics for Step 2

Step 1 creates a simulation environment, that can run "out-of-the-box" with simple configuration. A logical step is to embed this stuff in a management framework that allows to manage scenarios and test cases and on the other hand side supports in gathering the results and evaluate the outcome whether important test criteria have been met or whether test cases have failed while doing that on a large scale in a parallel fashion.

Glossary

Relevant technologies for this testbed are

Candidate 2: Massive data ingest and management

Challenge

Developing and validating AD functions requires the collection of data from various sensors, actuators and other sources. This ideally takes place in a fleet operation. However, due to the required scale and diversity of measurement systems, the AD community faces a massive amount of complex and heterogeneous data.

Descriptions / Goal

This Challenge, i.e. AD data, fulfills all aspects of 'Big Data'. It is of massive volume, there exists a large variety, it is recorded in a high velocity, and usually exists in various formats. However, most available, automotive systems for handling data captured in such an environment cannot process this data in an efficient workflow. Additionally, there exists a painful gap between measurement system and tools, and data analytics and processing platforms.

To solve this challenge, there is the need for a common and open-source handling of measurement data. This should ideally be in the form of common ETL processes, which fill the gap between the heterogeneous measurement data and a suitable backend that already as an industry standard for data analysis.

This solution should incorporate the various formats such as ADTFs .dat, ROS .bag, Vectors .mdf, ...

Suggested work packages

Work package 1 - Problem space

Understand all necessary aspects to clearly define a common problem space. The above the description of the challenge may only cover some parts and is only in the perspective of one stakeholder.

Work package 2 - ETL

Start a sample ETL implementation that provides an efficient ingest of ROS .bag files into a Hadoop environment.

Work package 3 - Data management

Evaluated what is needed to manage this massive, heterogeneous and globally distributed data.

Events

OpenADx Workshop - Forming an Eclipse Working Group - June, 25th 2019 (Filderhalle, Leinfelden-Echterdingen, Germany)

As we presented at the OpenADx Workshop #4 in Leinfelden-Echterdingen on 6 November 2018, we would like to become an Eclipse Working Group. We are happy to invite you to our first meeting about forming the Eclipse OpenADx Working Group.

Several companies have already agreed to help form the OpenADx WG, such as Renesas, itemis, Red Hat, Tesis, Microsoft, IBM, and Bosch.

This event will bring all interested parties together for information about the Eclipse Working Group idea.

Everyone is invited!

We will also discuss technical aspects and continue our open exchange.

Participant lists and contributions will be published on the wiki.

Please let us know who will be founding member and sign the participation agreement. (Link to Working Group Participation Agreement)

The meeting is organized by the Eclipse Foundation and Bosch as an Eclipse member, and will be held under the Eclipse Foundation Bylaws (Eclipse Bylaws, Industry Working Group Process, Eclipse Intellectual Property Policy, Eclipse Anti-Trust Policy).

For questions about the event, please contact Andy Riexinger, Angelika Wittek, or Ralph Müller.


Agenda

09:00 Registration

09:45 Welcome

10:00 Introduction to Eclipse Foundation - Why do we want to become an Eclipse Working Group?

10:30 Presentation and interpretation of OpenADx Charter Proposal

OpenADx Charter Proposal

11:00 Coffee and networking break

11:30 Two phases to form the working group - Phase 1

Incubation period (One year, starts after community review. See also Working Group Process.)

  • Open charter
  • Preparation of working group collaboration and charter
  • Initiation of first work package(s)
  • Process creation
  • Work package proposals
  • Working group funding
  • Steering Committee and decision-making


12:15 Two phases to form the working group - Phase 2

  • Final charter for working group work
  • Established work packages
  • Defined processes
  • Funding


12:30 Lunch

13:30 Steering Committee

(Steering Committee participation is only possible with a signed participation agreement.)

  • Election of the members: please think about what role you will fill, and who will be the chair
  • Define regular meetings and recurring appointments
  • Define meeting minutes publishing


15:30 Coffee and networking break

16:00 Status of OpenADx projects

16:30 Next steps for OpenADx

17:00 End of OpenADx Working Group Forming Meeting


Please register here for the event!

Find here information about the location Filderhalle and directions.

Presentations

Overall Presentation during the Event

SysML Papyrus

AVL@OpenADx

Workshop 4 (Overall Meeting), November, 6th 2018 (Stuttgart, Germany)

Blog Post

OpenADx reaches next level

Participating companies

  • 3DS / Dassault Systemes
  • AUDI
  • AVL
  • Bosch
  • Continental
  • Digitalwerk
  • Eclipse Foundation
  • ETAS
  • Fraunhofer IOSB
  • Hella Aglaia
  • IBM
  • IPG Automotive
  • itemis
  • Linaro
  • Mathworks
  • Microsoft
  • nttdata
  • Prostep
  • Red Hat
  • Renesas
  • Siemens Industry Software
  • Silexica
  • Streetscooter
  • Tesis
  • TU Lübeck
  • University of Oulu
  • Valeo
  • Vector
  • ZF Friedrichshafen

Group Picture

OpenADx Workshop 4.jpg


Presentations

Presentation list - OpenADx Workshop #4
Introduction to OpenADx Bosch Charles Degutis, Lars, Geyer-Blaumeiser, Andreas Riexinger File:181106 - OpenADx Workshop 4 - Agenda and Presentation.zip
Open Source Hardware – Simulation with Virtual Hardware TU Braunschweig / University Lübeck Jan Haase File:OpenADxWorkshop Haase 061118.pdf
Software in the loop (SiL) – SiL Framework Bosch Thomas Huber File:Open ADX 061118 SIL standardization.pdf
ROS2 Tooling for (automotive) Middleware Bosch Johannes Jeising Sorry! Presentation not released for external.
Cloe - Closed Loop Automated Driving Simulation Environment Bosch Thomas Grosser File:181106 - OpenADx Workshop 4 - Cloe.zip
OpenADx "Autonomous Driving Simulation" Renesas Mark Walton File:181106 - OpenADx - Renesas.pdf
Cross Domain Tool Coupling in the area of Simulation – Use Case @ Bosch Bosch Martin Johannaber, Uwe Wilbrand Sorry! Presentation not released for external.
AD and Collaboration for Labeling Microsoft Markus Loosen File:Standards for Labeling - Proposal external.pdf
Co Simulation - Challenges in the continous vehicle development process AVL Guenter Lang Sorry! Presentation not released for external.
Kubernetes and Serverless Technologies for high-performance Applications Red Hat Michael Hausenblas Kubernetes and Serverless Technologies for high-performance Applications
Title will follow (abstract: aspects of operating tool pipelines as a company) Digitalwerk Tobias Schmid File:OpenADX-ADTF.pdf

Proposed Projects / Project Book

File:181214 - OpenADx - Project Book.pdf

Follow-up Workshop Testbed 1 (Simulation), May, 23rd 2018 (Stuttgart, Germany) - Results

Participating Companies

  • AVL
  • Bosch
  • Elektrobit
  • MathWorks
  • Microsoft
  • Renesas
  • TESISdynaware
  • TNG


Results Goal of the workshop was a first demonstrator combining tools of the participating members. We achieved a first demonstrator, that connected the tools. Some screenshots below:

RVIZ in use:

OpenADx screenshot1.png


Dyna4 in use:

OpenADx screenshot2.png OpenADx screenshot3.png

Bosch Connected World, Feb. 21st and 22nd, 2018 (Berlin, Germany) - Results

We conducted the Autonomous Driving Hackathon on the Bosch Connected Experience. It was a great success, roughly 70 people were working on autonomous driving topics using technologies from Microsoft, Mathworks, German Aerospace Center (DLR), the Dart Racing Team, the European research project Appstacle and Bosch. In the conference we had an interesting keynote from Mr. Hoheisel, a Bosch Board member who announced officially Bosch's participation in the OpenADx initiative. OpenADx was also promoted on the booth of the Eclipse Foundation, were we had lots of inspiring conversations.

Get some impressions on the Bosch Connected World here:

Also be aware of the blog posts that were created in the context of the Bosch Connected World about OpenADx:

Workshop Testbed 1, Jan. 31st, 2018 (Waiblingen, Germany) - Results

Agenda

  • 9:30 Introduction
  • 9:45 Presentation and discussion of general architecture (DDS, ROS2)
  • 10:00 Presentation from each party about brought tools, data, expertise (10-15 minutes)
  • 12:00 Brainstorming Use Cases in small groups
  • 12:15 Lunch
  • 13:15 Presentation of Use Cases and prioritization to identify demonstrators
  • 14:00 Separation into groups per use case to detail demonstrator implementation planning
  • 15:45 Presentation of work group results
  • 16:00 Conclusions and next steps
  • 16:30 End of workshop

Participants

  • Johannes Jeising, Bosch
  • Paul Bell, Renesas Uk
  • Terry Howe, Renesas Uk
  • Steffen Lange, AVL
  • Josko Balic, AVL
  • Tobias Düser, AVL
  • Jonas Rübsam, AVL
  • Jörg Teßmer, Bosch
  • Arndt-Michael Meyer, ETAS
  • Andreas Holzner, TNG
  • Robert Lock, Bosch
  • Stephan Steinfurt, TNG
  • Jürgen Ludwig, Elektrobit
  • Rolf Jung, HS Kempten
  • Daniel Schneider, HS Kempten
  • Arun Sojan, University of Oulu
  • Robert Gorbahn, Microsoft Dtl. GmbH
  • Pasi Kuvaja, University of Oulu, M3S
  • Michael Langhammer, Itemis AG
  • Andreas Riexinger, Bosch
  • Eliane Fourgeau, Dassault Systèmes
  • Guillaume Belloncle, Dassault Systèmes
  • Franck Corbier, Dassault Systèmes
  • Frederic Chucholowski, TESIS DYNAware GmbH
  • Maximilian Chucholowski, TESIS DYNAware GmbH
  • Tomas Tichy, MathWorks
  • Diego Barral, MathWorks
  • Lars Geyer-Blaumeiser, Bosch

OpenADx - Simulation Testbed

Idea

For the function of an emergency breaking assist all voluntary parties provide parts for an integrated solution. In a first step this means, that all tools can talk to each other. Therefore there are defined messages for the exchange. It seems reasonable to use DDS as transport layer for it provides desired functionalities and most tools have the possibility to integrate it.

Areas of Activities

  1. Sensor Simulation
    1. Video
    2. Lidar
  2. Sensor Data Processing
    1. Video
    2. Lidar
  3. Algorithm (Function under Test)
  4. Vehicle under Test
  5. Scenario
  6. Environment
  7. Introspection & Visualization

Overview Diagram

Testbed1UseCaseStructure.png

Addition Information:

  • This picture contains an initial draft for the message exchange
  • OSI-like means: There is only the structure of the message reused but Google protobuf is not included
  • Usage of Point Cloud message
  • Potentially use Laser Scan message
  • T/B/S: Throttle, Brake and Steering Angle

Active Parties

  • Sensor Simulation
    • Video: Microsoft, TESIS, Mathworks
    • Lidar: TESIS
  • Sensor Data Processing
    • Video: Renesas
    • Lidar: University of Oulu
  • Sensor Simulation & Sensor Data Processing - Combined: TESIS
  • Algorithm: University of Oulu, Elektrobit, Mathworks, Dassault Systèmes, Bosch
  • Vehicle under Test: Dassault Systèmes, Simulink, AVL
  • Scenario & Environment - Combined: TESIS
  • Introspection & Visualisation: AVL, Bosch (Ros2)

Next Steps

  • Prepare .msg files and idl files for the different msgs
  • Each interested party is capable to send and receive the mentioned msgs via DDS
  • Each interested party provides a minimal implementation of its area to demonstrate the use case
  • In the hackathon we integrate the different tools into one solution

On Top

It is clear that data exchange is not enough. It is possible to think of next steps like:

  • Common Simulation Time (Stop on debug breakpoint, etc.)
  • ...

Workshop 3, Oct. 23rd, 2017 (Ludwigsburg, Germany) - Results

The workshop took place on the Unconference day of Eclipse Con Europe 2017.

Agenda:

  • 08:30 - 09:00: Welcome Coffee and Registration
  • 09:00 - 12:30: Automotive Unconference including an introduction of OpenADx
  • 12:30 - 14:00: Lunch and Poster Session
  • 14:00 - 17:30: Working sessions on OpenADx testbed candidates
  • 17:30 - 18:30: Meet & Greet

Sessions for testbed candidates:

Testbed candidate 1 (simulation), Moderator: Lars Geyer-Blaumeiser (Bosch)

Participants:

  • Lars Geyer-Blaumeiser, Bosch Software Innovations
  • Thomas Titze, Microsoft
  • Maximilian Chucholowski, TESIS DYNAware GmbH
  • Diego Barral, MathWorks
  • Joachim Stroop, dSpace
  • Boutheina Bannour, CEA
  • Michael Langhammer, ITEMIS
  • Adam Fuhl, Bosch
  • Stefan Griesche, Bosch
  • Johannes Jeising, Bosch
  • Gerald Stieglbauer, AVL
  • Andreas Holzner, TNG
  • Andreas Graf, ITEMIS
  • Loic Cantat, SYSTEMX
  • Christof Hammel, Bosch

Identified and classfied technologies:

  • Category Simulation Input:
    • Open Drive
    • Open CRG
    • Open Scenario
    • Oddlot
    • Pegasus
    • Matlab
    • Diversity Testcase Generator
    • Enable S3
  • Category Simulation:
    • Matlab/Simulink
    • VTD
    • OpenPass
    • DYNA4
    • CarMaker
    • Gazebo
    • Sumo
    • AirSim
    • Dymola (Modelica)
  • Category Data Evaluation:
    • Matlab
    • Diversity Test Verdict Computation (Log Analysis)
    • ROS
  • Category Visualization:
    • DYNA4 / Unity
    • AirSim / Unreal
    • ROS/Rviz
  • Category Simulation Framework:
    • Test Management Tools
    • FMU
    • Open Simulation Interface
    • DDS
    • ROS
    • Franca IDL
    • Arcosar
    • Autosar Adaptive

Possible Use Cases for Testbed Simulation:

  • Open loop simulation with recorded sensor data, DuT: Perception
  • Closed loop simulation without artificial sensor data, DuT: Planning
  • Closed look simulation with artificial sensor data, DuT: Whole Car/System

Decision: First use case is closed loop simulation without artificial sensor data

Focus Technologies for Testbed Simulation:

  • Simulation Input: Open Drive, Open Scenario
  • Simulation: DYNA4, Matlab/Simulink, AirSim, Gazebo
  • Simulation Evaluation: Matlab
  • Visualization: AirSim, DYNA4, Rviz
  • Simulation Framework: DDS, ROS

Technology selection is furthermore based on participation of interested parties

Known contact persons:

  • DYNA4: TESIS, Maximilian Chucholowski
  • AirSim: Microsoft, Thomas Titze
  • Matlab/Simulink: MathWorks, Diego Barral
  • ROS: Bosch, Johannes Jeising

Open Issues:

  • Open Drive/Open Scenario: Potential Contact Orga Automotive Simulation Center Stuttgart of Univ. Stuttgart, they provide Oddlot as editor for scenarios, idea is to use contacts, e.g., from OpenPass to get in touch
  • Gazebo: Open Robotics, if they are interested
  • DDS: DDS is only specification, concrete implementation is needed. All used tools need to have a DDS connection to ensure data transport from tool to tool. DDS should be ROS compatible for the Testbed, Potential DDS Contact Orgas: PrismTech, Eprosima

Potential constraints for the simulation:

  • Multiple scenario simulation in parallel
  • One simulation time throughout all simulation tools

Next steps:

  • The first HackFest is planned for the first two weeks in December. Prior to that an architecture workshop will take place most likely as phone conference mid of November.
  • As a preparation, the testbed idea above has to be made more precise, for that one or two preparation calls will be scheduled.
  • We will ask for concrete commitments for HackFest participation, the concrete testbed content is of course driven by the participating organisations.

Testbed candidate 2 (massive data ingest), Moderator: Thomas Reinhardt (Bosch)

The idea:

The core vision for this testbed candidate, is to close the gap between 'data generation' optimized infrastructure, i.e. measurement electronics, and state-of-the-art 'data analytic' frameworks. This gap is ever so present in the struggle with heterogeneous data formats and the use case specific tool suites that come along. A global, query-able index that offers a (integrated) analytic engine has yet not been established.

To close this gap, this testbed suggests the implementation of ETL (Extraction, Transformation and Lad) processes that ingests a complete raw measurement data set into an data analytic data structure and perform evaluations / processes. In other words, use well established "Big Data" driven analytic methods to enrich, get better insight and easy access.

The scope:

To narrow down the scope of this testbed, only a development data pipeline should be in focus. This pipeline outputs extreme amounts of raw and processed data, with a limited size of (fleet) vehicles. The testbed implements a suitable ETL to ingest major data formats into a unified view (i.e. into a suitable data structure). A set of simple queries allows to access this transformed data, independent from its original format. As a second step, the testbed implements a data enrichment by demonstrating an easy "plug-and-play" of existing open source components, e.g. by using a neuronal network to create new labels. This newly created (or enriched) information is then feed back into the unified view. As a stretch goal, the testbed implements a connection to feed back this information into existing (automotive) development tools. For example, the testbed offers a playback of queried and enriched data using an Rviz visualization.

The challenge:

  • High complexity of measurement data. AD data consists of 1D, 2D and 3D time series with a high velocity. Rates can be as high as up to 3GB/s
  • Source of usable data.

Open Questions

  • All about the data? A to some extent complex and open source-able raw data set is required.
    • Is it possible to record a new data set for the testbed?
    • Clear an internal data set of a testbed partner?
    • Use data from an autonomous racing team?


Next Steps

More Marketing

Invitation for more participants.

Follow-Up Call

Follow up Skype call on Monday, November 6th at 2pm CEST. Meeting will be provided by Microsoft (to be added here). Invitation also via OpenADx mailing list.

Follow-Up Architecture Workshop (OpenADx Workshop #4)

Architecture Workshop to refine testbed idea. In preparation for the upcoming hackfest:

  • Data sets for 'base line'.
  • Definition of concrete interfacing tools, formats, requirements, ...
  • Definition of a common architecture for a Data Ingest testbed.
  • Coordination of hackfest details


Workshop 2, Sept. 19, 2017 (Stuttgart, Germany) - Results

Strategy discussion results


Partners

- Certification organizations

- Universities

- Research institutes

- Standardization organizations like AUTOSAR can provide areas to watch out for

- These are in addition to already identified OEM, tier1, hi-tech, tool providers, silicon chip


Communication

- Need slide deck with a narrative to socialize inside of respective organizations

- Set up a public community under Eclipse management for contribution and preparation work prior to next workshop 23 October

- Weekly telecom to disseminate information – attendance voluntary based on availability

- Hosted communication at e.g. 3D Experience Forums by e.g. Dassault


Execution and milestones

- Further workshop to detail testbeds/incubators - October eclipsecon Europe

- Testbed/incubator execution (Hackathon/Hackfest) – November 2017

- Group composition for hackathon to be determined based on results of testbed/incubator layout

- Testbed/incubator completed by the end of 2017

- Announcement – venue dependent on testbed/incubator results and feasible timing (forums: CES, BCW, Software in Automobiles, Toulouse, Embedded World, WCX – sponsor is SAE International)


Forms of contribution by community members

- Manpower – e.g. programming capacity

- Monetary investment

- Material support - e.g. a car for demonstration purposes


Testbed/Incubator discussion results

1. Perception simulation and high quality rendering vs functional validation & simulation (FX to handle different simulation use cases)

- Simulation (formerly #11) – Workshop 1

- ROS in the loop


2. Driver to Driver communications

- Hybrid human -vs- autonomous driving behavior differenced – very hard problem


3. Car to X communications


4. Standardization

- Reference / canonical data set - Data Sharing across companies

- Share crash incident data across companies rapidly to accelerate safety resolution

- Open Scenarios - Common ways of defining scenarios


5. API standardization – common way of calling / creating API’s


6. Management & usage of big data

- Massive data ingest


7. Standardization interface for authority approvals based on defined data (independent of producer tool chain)

- There’s major value in driving agreement on how data is stored; can we drive agreement in which sensors are used and the format of the sensor data.

- This could benefit government agency that will test using the data to determine the safety of the vehicles


8. Heterogeneous data formats and data fusion

- Compatibility of measured data

- Visualization of data from different sources (lidar, video, measurements) could be very valuable

OpenADx testbed incubator discussion results.png


Conclusion:

- It was agreed that we should concentrate on the top ranked topics #4, #6, #8.

- Proposed procedure is to set up a frequent call to discuss the topics and identify concrete tasks to be executed in "Hackfests“

- On the Unconference of the EclipseCon Europe on Oct. 23rd, the topics should be discussed further. Ideal result is to have them prepared for a "Hackfest".

- General agreement for participation in the concretization of the topics by XXXXXXX and XXXXX employees.

Workshop 1, Aug. 2, 2017 (Redmond, US) - Results

1. Gain points and pain points to address

Opportunities / gains

- Manage complexity / risk

- Reallocate portions of resource pool to more user relevant activities

- Commonality reduces risk

- Reduce cost in a non-automobile implementation area; the tool chain is outside of the vehicle

- AD development accelerator consists of known and certified components and services => ensure


Risks / pains

- What if this group of companies come together but is not actually able to complete the project

- Will this be fast enough to satisfy TTM needs of the OEMs

- How will sufficient safety levels be reached and assured

- Preserve independence: This initiative might actually preserve the second source needs OEM and Tier1 somewhat fearful of IT industry


2. Value proposition

- Reduced investment risk and cost reduction through shared development

- Improved capability to focus resources in more saleable areas

- Improved SW reliability and safety

- Standardization facilitates greater AD understanding and therefore greater acceptance in the political, legal and insurance communities

- Standardization promotes interchangeability @ OEM


3. Key success factors

=> Build momentum for the initiative


- Demonstrate that we can deliver; lofty vision is OK, but initial projects must be

=> Realistic / achievable

=> Clearly scoped

=> Measurable


- Start with a “coalition of the willing”

=> Not everyone will want to participate initially; reduce skepticism with results


- A common data pool to accelerate development


- Limit scope to non-differentiating factors


- Open APIs, Open framework and open collaboration => industry standard

=> Mix of multiple partners in each area… ”coopetition”


- Extensibility within the system to add modules without the OEM being required to open up all data access – that must remain a choice@OEM


Potential naming options

OpenADx Naming Options.jpg

Meeting Minutes

Steering Committee Workshop, 13th August 2019

Agenda

  • Business Canvas
  • OpenADx Working Group Scope definition
    • OpenADx pitch deck (in 15 Minutes -> What is OpenADx and why should we participate?)
  • Communication Channels like LinkedIn and Twitter is “state-of-the-art” and should be used.
  • How do we activate the community?
  • Participation of OEMs in OpenADx
    • How can we activate them to participate?
    • Lead Management - Who can help whom to contact xyz?
  • Automotive Flyer

Steering Committee Meeting, 31st July 2019

Agenda

  • Welcome, Agenda (15:00)
  • Presentation about Cloe – current state
  • Eclipse Automotive Flyer
  • EclipseCon Community Day – 21st October 2019
  • Open topics
  • F2F Workshop in Zwingenberg
  • Upcoming Events
  • Projects, Project Proposals
  • Next steps
  • End (~16:30)

Attendees (signed Participant Members)

  • Naci Dai (Eteration)
  • Wolfram Richter (Red Hat GmbH)
  • Christian Muszynski (IBM Deutschland GmbH)
  • Ralph Mueller (Eclipse Foundation Europe)
  • Josef Zehetner (AVL List GmbH)
  • Andreas Graf (itemis)
  • Thomas Grosser (Robert Bosch GmbH)
  • Henning Classen (Robert Bosch GmbH)
  • Andy Riexinger (Robert Bosch GmbH)

Meeting Minutes

  • Presentation about Eclipse Cloe – current state
    • Presentation done, recording failed, we will record Eclipse Cloe in an offline-session -> Andy will setup a meeting
    • Eclispe Cloe Presentation upload on the Eclipse Channel, Link should be on the Wiki and the OpenADx Web Page
    • Eclipse Cloe could work with SUMO and Model Connect.
      • Josef checks, when we can start with working together e.g. IF discussion)
      • Andy starts talks with SUMO and will invite Thomas and Henning
  • Eclipse Automotive Flyer
    • Will be handled in the F2F Workshop in Zwingenberg on 13th August
  • EclipseCon Community Day – 21st October 2019
  • Open topics
  • F2F Workshop in Zwingenberg
    • Date is scheduled to the 13th of August, invitation is sent out! Zoom will be also available.
  • Upcoming Events
    • have a look in the presentation
    • do not forget to fill our dudle list
  • Projects, Project Proposals
  • Next steps
  • End

Steering Committee Meeting, 16th July 2019

Agenda

  • Welcome, Agenda (15:00)
  • Approval of partner logo usage for web page
  • Roles and responsibilities within the OpenADx Steering Committee
    • Mailing list
    • Responder
    • Web Page Maintainer
    • ...
  • Participation of OEMs in OpenADx
    • How can we activate them to participate?
    • Lead Management - Who can help whom to contact xyz?
  • Further partner recruiting
  • Collaboration with other working groups
  • Building a Sales / Marketing Kit (Content, Templates, …)
  • Communication Channels?
    • What do we need? (Twitter, LinkedIn, …)
    • Who can do regular postings?
  • Setup F2F Meeting - Q4/2019
    • Offices are possible?
    • Proposals
  • Upcoming Events (maybe one of them could be used for a F2F meeting?)
  • Projects, Project Proposals
  • Next steps
  • End (~ 16:30)

Attendees (signed Participant Members)

  • Naci Dai (Eteration)
  • Robin van der Made (Siemens Industry Software and Services)
  • Wolfram Richter (Red Hat GmbH)
  • Christian Muszynski (IBM Deutschland GmbH)
  • Ralph Mueller (Eclipse Foundation Europe)
  • Josef Zehetner (AVL List GmbH)
  • Andreas Graf (itemis)
  • Andy Riexinger (Robert Bosch GmbH)

Meeting Minutes

Approval of partner logo usage for web page

  • Part of the membership agreement, we can use the logos on our web page


Roles and responsibilities within the OpenADx Steering Committee

  • It would be good, if someone tracks the mails. For mails, which could not be answered ad-hoc or which are to technical, please ask for help within the SC.

Wolfram will have a look on the requests via the mailing list and will take care of them, if there will be no answer within e.g. 1 day.

  • Naci´s team can help with maintaining the web pages. Most of the content will be tracked with Bugzilla.

Andy will connect Naci with the Eclipse team for a introduction to Hugo.

  • Meeting minutes will be in a “round robin” way
    • next will be Josef


Participation of OEMs in OpenADx

  • There are some activities going around regarding OEM activation.
  • What content do we have to activate them? We need some “products” to convince them. (see also Marketing kit)
  • We need a coordination of approaching OEMs (maybe a closed wiki page) -> Andy will make a proposal
  • Who is our target audience? (OEMs, Tier1, AD SW stack provider)
  • We should do a F2F workshop e.g. in Zwingenberg (Eclipse office) to build a business canvas, what we want to sell.

(in near future, Andy will search a meeting date for that, that we can establish a business canvas)


Further partner recruiting

  • Andy is in talks with Tier1s and will meet them
  • Focus on AD start-ups around Detroit and San Francisco to widen the partner, because they are not aware of Eclipse and open source.
    • We will add a chapter on our wiki / web page a Q&A about how to participate in OpenADx and so on.


Collaboration with other working groups

  • Scope for our WG is necessary and we should see what is feasible, Therefore we need to know, what the others are doing or what they have done.

We should be careful on defining our scope, we should reduce complexity. Scope definition is important, scope discussion also part of the F2F workshop in Zwingenberg.

  • Can we create a landscape of the WG, what are they doing?
    • Who is playing in what area, list of GitHub repositories, …
    • Git/GitHub for the Steering Committee -> can Eclipse provide us this? (Andy contacts Wayne)


Building a Sales / Marketing Kit (Content, Templates, …)

  • We need a slide deck to pitch OpenADx in 15 Minutes
    • What is OpenADx and why should we participate?
    • Topic also for the Workshop in Zwingenberg with the business canvas.


Communication Channels?

  • LinkedIn and Twitter is “state-of-the-art” and should be used.
    • Also a topic for the F2F workshop in Zwingenberg


Setup F2F Meeting - Q4/2019

  • Setup a F2F meeting for the next community meeting
  • Andy creates 2 doodle lists for finfing a meeting slot during the Eclipsecon and one further for the workksop in Zwingenberg


Upcoming Events (maybe one of them could be used for a F2F meeting?)

  • Make a list on Git/GitHub to extend the current list with important events/conferences/meetings


Projects, Project Proposals

  • 2 project proposal are at Eclipse, will be soon in the community review


How do we activate the community?

  • Define and finish the scope of OpenADx
    • What is in, what`s not? What do I want to achieve?
  • Create a culture of sharing and engagement!
  • How can we get activity on the mailing list?
    • We need the first contributions of technologies, then we think, the activity will increase.
  • Would we become the mailing list as a discussion platform e.g. articles, legal aspects...
    • Start a kind of survey with the community, what they want with the mailing list.

Next steps

  • Can we shift the next SC meeting on July 30 to July 31, same time?

End (16:30)

Agenda Slides with Meeting Minutes


Steering Committee Meeting, 25th June 2019

Attendees (signed Participant Members)

  • Suat Eker (Eteration)
  • Robin van der Made (Siemens Industry Software and Services)
  • Fleur Ruetz (JC Information Management)
  • Wolfram Richter (Red Hat GmbH)
  • Christian Muszynski (IBM Deutschland GmbH)
  • Ralph Mueller (Eclipse Foundation Europe)
  • Josef Zehetner (AVL List GmbH)
  • Angelika Wittek (Eclipse Foundation Europe)
  • Andy Riexinger (Robert Bosch GmbH)
  • (Andreas Graf (itemis) - absent)

Charter Change Proposal

Proposal: Add "The Steering Committee elects among its members a chairman." to Charter.

Decision: Charter Change is approved with one consent.

Election of Steering Committe Chair

Proposal: for SC Chair: Andy Riexinger, Robert Bosch GmbH

Decision: Andy is elected as SC Chair with one consent

Working mode SC

  • SC has to meet twice a year
    • a kind of Doodle will be used as timefinder
  • We start with regular telecons, 2 times a month
  • Agenda for every meeting will be prepared, SC Chair will collect the topics and organizes the meeting
  • Zoom will be used as telecon tool
  • Meeting Minutes via Wiki (OpenADx Wiki) or Tuleap,
    • for OpenADx a private Tuleap instance is existing and a public one can be established, therefore you need an Eclipse Acoount
  • For decisions, you need at least a min of 50% of the SC members
  • Communitcation via official mailing list, e.g. publish proposed agenda for SC meeting, publish meeting minutes
  • List of other mailing lists in the automotive area will be provided
  • "Marketing" - Who will be responsible for the mailing list?
    • E.g. for questions, for publishing project progress, call for action (help to test, help to improve, …)
    • Topic for Andy -> Invite every single person of my private mailing list to the official one
  • Defined roles in the SC (maybe in turning) which has to be covered within the SC
    • Web page maintenance have to be done
  • Every SC member should think about the roles he will cover
  • We will set up a OpenADx SC mailing list, only for SC topics!
  • For SC meetings it is also possible to send a delegate

Most important topic for the next months is to gain momentum!

Show what you/we are doing, write user stories out of that, e.g. we want to create a demonstrator out of the toolchain and talk about it! (via mailing list)

Next meetings

  • 16.07.2019, 15:00 - 16:30 (German time)
  • 30.07.2019, 15:00 - 16:30 (German time)
  • 20.08.2019, 15:00 - 16:30 (German time)


Ralph will setup the meetings with Zoom

Agenda for the next meeting (16.07.2019)

  • Discuss roles and responsibilities within SC
    • Mailing list
    • Responder
    • Web Page Maintainer
  • Presentation about Cloe - current state
    • Can we record this part of the presentation? (voice and presentation)
    • With Q&A session?
  • Participation of OEMs in OpenADx
    • How can we activate them to participate?
    • Lead Management - Who can help whom to contact xyz?
  • Setup F2F Meeting - Q4/2019
    • Offices are possible?
    • Proposals
  • Building a Sales / Marketing Kit

Assets

Pitch deck to be used inside of respective organizations File:OpenADxInformationDeck.zip

Back to the top