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.
AICE OpenLab WG
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 AICE
Automated Driving (AD) is clustered into three equally important technology areas:
1) Artificial Intelligence
2) Cloud
3) Edge
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.
News
Please have a look to our latest news on our official OpenADx web site
Participants
| Organisation | |
|---|---|
| ATB | |
| Castalia Solutions | |
| Continental | |
| Engineering Group | |
| Eurotech | |
| Fraunhofer FOKUS | |
| Huawei | |
| Itemis | |
| Kairos | |
| Konduit | |
| OpenADx | |
| Ortelio | |
| SmartClide | |
| University of Macedonia | |
| University of Skövde | |
| Warren.io | |
Steering Committee 2021/2022
| Company | Name | Role |
|---|---|---|
TBD
Related Projects and Project ProposalsEclipse iceoryxIn domains like automotive, robotics or gaming, a huge amount of data must be transferred between different parts of the system. If these parts are actually different processes on a POSIX based operating system like Linux, this huge amount of data has to be transferred via an inter-process-communication (IPC) mechanism. The mechanisms provided by the operating system, like message queues, normally require to copy the data and are subject to context switches between user and kernel space. In fact, it is often not only one but many copies of the transferred data between the sender and the receiver. If it comes to GBytes/s data exchange rates, avoiding these copies becomes a crucial factor. Eclipse iceoryx is a middleware with a zero-copy shared memory approach which is optimized for the huge data inter-process-communication. Status: Project Eclipse iceoryx GitHub repository: Eclipse iceoryx GitHub ChallengeAD 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 Tier1sUser 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 providersUser 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.
ApproachWe 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 TestbedsTestbeds 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:
Workflow for testbed candidates
Who We Are and How to JoinAs we have a public website it would be nice to give newcomers an understanding who is involved and how to interact with us. How to participate in OpenADx?OpenADx is still in an early stage, means, since 25th June 2019 we are an official Eclipse Working Group which consists of more than 10 member companies, who are shaping the Working Group, which is done in the Steering Committee. We are currently in the “Incubation Phase” where we define the future proceeding of the working group. OpenADx is an open working group so everyone can participate! Feel free to use our mailing list to start a discussion or to be part of one, to get answers to your questions around OpenADx and of course to stay tuned! You can use the solutions we provide in compliance with the open source license of the specific product. From time to time, there will be also some workshops, which will be announced via our website, wiki and mailing list. So feel free to participate! If you would like to engage more, e.g. to shape the working group together with us, you have to fulfil some prerequisites:
Our recommendation is “Participant Member” for the incubation phase and “Driver Member” after the incubation phase to have the biggest possible influence in the working group. For further questions, you can use our mailing list. ;-) Interested PartiesPlease add the name of your organization if you are interested in AICE or tell us to do it for you.
Communication
Presentations
Upcoming Presentations
Press releases
Blog posts
AICE logoA logo design contest is to be scheduled, please check the mailinglist for further details (hot link!).
Testbed CandidatesCandidate 1: SimulationChallenge 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 1Target 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:
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 1The 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:
Topics for Step 2Step 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. GlossaryRelevant technologies for this testbed are
Candidate 2: Massive data ingest and managementChallenge 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. EventsMeeting MinutesLink to the Meeting Minutes AssetsPitch deck to be used inside of respective organizations File:AICEInformationDeck.zip |
