The ECRTS / WATERS industrial challenge has been originally created as a satellite event to the International Workshop on Analysis Tools and Methodologies for Embedded Real-Time Systems (WATERS). The purpose of the industrial challenge is to share ideas, experiences, use cases and solutions to concrete timing design and verification problems issued from real industrial case studies. Our goal is to promote discussions, closer interactions and cross fertilization of ideas within the real-time community as a whole, in particular bridging between researchers in academia and industrial practitioners from different application domains.
Current Challenge
Past Challenges
- Bosch – Real-world automotive software benchmarks
- Dassault – Middleware for drone-like cyber-physical systems
- Thales – Aerial video system to detect and track a moving object, e.g. a vehicle on a roadway
Discuss and Collaborate
Mailing List
Discussion, collaboration, and additional information on the challenge(s) is done via a public google group (a mailing list). Note that a google account is not required to participate, and that all interactions on the group are possible also via email only.
https://groups.google.com/g/ecrts-industrial-challenge
The group has public visibility, and previous threads are searchable by everybody. Only group members can post on the group.
To subscribe without a google account, send an email to:
ecrts-industrial-challenge+subscribe@googlegroups.com
Github
Material related to the challenge(s) and accepted solutions are made available on a public GitHub:
Discussion for the Previous Challenges
Information and discussions on previous challenges can be found in the archive of the phpBB forum:
Contribute a Solution
The ECRTS industrial challenge aims to facilitate discussion and gathering feedback on the solutions and welcomes the submission of two types of contributions:
- Early stage proposals that present preliminary results and roadmaps to achieve a complete solution
- Full solutions, possibly focusing only on selected aspects of the challenge
The authors of both types of contributions will be required to prepare a poster to explain their solutions and discuss culprits and trade-offs. Authors of full solutions will have the opportunity to present a summary of their results with a short presentation before the poster session.
Full solutions should present the strengths and limitations of the used approach. Authors are strongly encouraged to implement their solution and make it available along with the submission. The proposed solutions should also discuss how much time and effort was needed by the authors to (a) understand the challenge and (b) solve it.
Submission Instructions
Submission are managed via easychair.
NOTE: The copyright remains with the authors. By submitting a solution, the authors agree and confirm that, if accepted, at least one author will register for ECRTS, and present the solution in person.
The accepted solutions will be made available online on github (https://github.com/ecrtsorg) before the conference so that contributions can be examined prior to the event.
Early Stage Proposals
Authors should submit a short abstract following the IEEE conference format. The abstract should not exceed 3/4 column (10 pt, single-line spacing, images and references excluded).
Submissions can be made at any time until the final submission deadline. The industrial challenge committee will provide a feedback on the abstracts within one week from submission.
| Final submission deadline (hard) | June 26, 2023 |
Full Solutions
For full solutions, the submission will be in two steps.
- Authors should submit by the early submission deadline of a one-page abstract following the IEEE conference format (2 columns, 10 pt, single-line spacing, images and references excluded). The abstract will be reviewed by the industrial challenge committee.
- Authors of accepted abstracts should submit by the final version deadline the full solution: a 6-page max paper in IEEE conference format (2 columns, 10 pt, single-line spacing, references excluded) describing the proposed solution and a link to the associated code.
| Early submission deadline (hard) | May 18, 2023 |
| Notification of acceptance for early submission | May 30, 2023 |
| Final submission deadline (hard) | June 26, 2023 |