Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OpenADx"
m (→Workshop 4 (Overall Meeting), November, 6th (Stuttgart, Germany)) |
m (→Workshop 4 (Overall Meeting), November, 6th (Stuttgart, Germany)) |
||
Line 289: | Line 289: | ||
- OpenADx Charta | - OpenADx Charta | ||
|Eclipse Foundation, Bosch | |Eclipse Foundation, Bosch | ||
− | |Angelika Wittek, Lars Geyer-Blaumeiser} | + | |Angelika Wittek, Lars Geyer-Blaumeiser |
+ | |-} | ||
=== Follow-up Workshop Testbed 1 (Simulation), May, 23rd (Stuttgart, Germany) - Results === | === Follow-up Workshop Testbed 1 (Simulation), May, 23rd (Stuttgart, Germany) - Results === |
Revision as of 08:24, 13 November 2018
Contents
- 1 Welcome to OpenADx
- 2 Challenge
- 3 Integrated tool chain for AD system development
- 4 Who We Are and How to Join
- 5 Testbed Candidates
- 6 Events
- 6.1 Workshop 4 (Overall Meeting), November, 6th (Stuttgart, Germany)
- 6.2 Follow-up Workshop Testbed 1 (Simulation), May, 23rd (Stuttgart, Germany) - Results
- 6.3 Bosch Connected World, Feb. 21st and 22nd, 2018 (Berlin, Germany) - Results
- 6.4 Workshop Testbed 1, Jan. 31st, 2018 (Waiblingen, Germany) - Results
- 6.5 Workshop 3, Oct. 23rd, 2017 (Ludwigsburg, Germany) - Results
- 6.6 Workshop 2, Sept. 19, 2017 (Stuttgart, Germany) - Results
- 6.7 Workshop 1, Aug. 2, 2017 (Redmond, US) - Results
- 7 Assets
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
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.
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.
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
- Verbalization of a task in use case form, which has potential for further work
- Contribution of the use cases by interested partners as testbed candidates
- 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
- Execution of the Hack-Fest
- Evaluation of the Hack-Fest results to decide on whether to follow the idea or to stop the effort
- 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
- German Aerospace Center (DLR)
- IPG Automotive GmbH
- itemis
- MathWorks
- Microsoft
- 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
- FOSDEM 2018 - Community Main Track: OpenADx – xcelerate your Automated Driving development
- TNG Big Tech Day: OpenADx – xcelerate your Automated Driving development – Slides: File:2018 05 18 OpenADxAtTNGBigTechDay.pdf
- Microsoft Automotive Summit - 5th June 2018: OpenADx – xcelerate your Automated Driving development
Upcoming Presentations
- EclipseCon Europe 2018 - 23 - 25 October 2018, Ludwigsburg, Germany: OpenADx - Leveraging open collaboration and open source to accelerate development of Autonomous Driving
- International Conference "Future of Automotive Software" - 10 & 11 December 2018, Holiday Inn Munich Westpark, Germany: OpenADx – xcelerate your Automated Driving development
Press releases
- Renesas published in Elektronik automotive: Vorteile von Open Source fuer ADAS und autonomes Fahren (only in German available)
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.
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
- Eclipse SUMO (Simulation of Urban Mobility) - http://www.dlr.de/ts/de/desktopdefault.aspx/tabid-9883/16931_read-41
- OpenPASS - https://projects.eclipse.org/proposals/simopenpass
- OpenMDM - https://www.openmdm.org
- OpenDrive - http://www.opendrive.org
- OpenScenario - http://www.openscenario.org
- OpenCRG - http://www.opencrg.org
- Open Simulation Interface - https://github.com/OpenSimulationInterface/open-simulation-interface/wiki
- AirSim - https://www.microsoft.com/en-us/research/project/aerial-informatics-robotics-platform
- Autonomous Driving Cookbook - https://github.com/Microsoft/AutonomousDrivingCookbook
- ROS - http://www.ros.org
- Gazebo - http://wiki.ros.org/gazebo
- Pegasus - http://www.pegasus-projekt.info/en/home
- Proprietary Tools
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
Workshop 4 (Overall Meeting), November, 6th (Stuttgart, Germany)
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
Presentation list - OpenADx Workshop #4 | ||
---|---|---|
Introduction to OpenADx | Bosch | Charles Degutis, Lars, Geyer-Blaumeiser, Andreas Riexinger |
Open Source Hardware – Simulation with Virtual Hardware | TU Braunschweig / University Lübeck | Jan Haase |
Software in the loop (SiL) – SiL Framework | Bosch | Thomas Huber |
ROS2 Tooling for (automotive) Middleware | Bosch | Johannes Jeising |
Cloe - Closed Loop Automated Driving Simulation Environment | Bosch | Thomas Grosser |
OpenADx "Autonomous Driving Simulation" | Renesas | Mark Walton |
Cross Domain Tool Coupling in the area of Simulation – Use Case @ Bosch | Bosch | Martin Johannaber, Uwe Wilbrand |
AD and Collaboration for Labeling | Microsoft | Markus Loosen |
Co Simulation - Challenges in the continous vehicle development process | AVL | Guenter Lang |
Kubernetes and Serverless Technologies for high-performance Applications | Red Hat | Michael Hausenblas |
Title will follow | Digitalwerk | Tobias Schmid |
OpenADx as Eclipse Working Group
- OpenADx Charta |
Eclipse Foundation, Bosch | Angelika Wittek, Lars Geyer-Blaumeiser |