Meeting Minutes: 2025/03/21 OpenSCENARIO XML CCB Meeting
| Location | Online |
| Date | 21-03-2025 |
| Time | 13:00-14:00 CET |
| Note taker | CoPilot |
Antitrust reminder
Every participant acknowledges that they know the content of the antitrust reminder: ASAM Antitrust Reminder
Present Participants
| Participants |
|---|
| Simon Terres |
| Andreas Rauchert |
| Emil Knabe |
| Jakob Kaths |
| Andreas Biehn |
| Diego Sanchez |
| Ahmed Sadek |
Agenda/Goals
| TOP | Topic | Status |
|---|---|---|
| 1 | Meeting minutes storage/handling | |
| 2 | Projects roadmap - Kickoffs | |
| 3 | XML Maintenance working mode | |
| 4 |
Question: Turning at intersections in OpenSCENARIO XML 1.2 My name is Mihaly Balogh, and I am representing aiMotive Kft. We are currently developing our own OpenSCENARIO executor and have encountered a challenge that our engineers are finding difficult to resolve. The primary question we are attempting to address is how to describe a scenario where a vehicle is required to turn right at the next available opportunity. I would emphasize that our goal is to avoid specifying the exact intersection or target route, but rather to assign this behavior to an entity. Additionally, we are unclear whether the LaneChangeAction can be utilized to define turns at junctions. We would appreciate it if you could provide clarification on this matter. Furthermore, we are interested in understanding how to describe various scenarios at intersections in general. If you could share any relevant examples, guidelines, or materials, we would greatly appreciate your assistance. |
Minutes
Generated by AI. Be sure to check for accuracy.
Meeting notes:
-
Budget Proposals: Diego confirmed that the proposals have been discussed separately for each project and submitted with estimations. The final presentation will be in two weeks in the TSC for final approval.
- Proposal Discussions: Diego confirmed that the budget proposals have been discussed separately for each project. These proposals include estimations based on past experiences and are prepared for the Proof of Concept (POC) as well as individually for each project.
- Service Providers: Andreas Rauschert discussed with RA Consulting about the process of selecting service providers. Diego explained that they aim to find a service provider for the entire POC to minimize costs. If not possible, they will approach different providers for each project.
- Meeting Minutes Storage: Diego proposed using SharePoint to store meeting minutes instead of the repository to avoid mixing them with technical discussions. The dedicated SharePoint for the proof concept of OpenX will be finalized next week.
- Kickoff Meetings: Diego mentioned that kickoff meetings have started, and they are gathering information on active participants. They are refining the roadmap based on discussions in the kickoffs.
- Open Scenario XML Maintenance: Andreas Rauchert inquired about the Open Scenario XML maintenance project. Diego explained that maintenance will be done within the CCBs, except for OpenDrive, which may have a separate dedicated maintenance project.
- Turning at Intersections: Andreas Rauchert and Emil discussed the possibility of specifying turning at intersections in Open Scenario XML. They concluded that it is currently not possible, the existing options include specifying a route or using random route actions introduced in version 1.3. But there is potential for standardizing this feature in the future. This would involve investigating the use case further and possibly introducing a way to specify probabilities of turning left, right, or going straight at intersections.
- Maintenance Working Mode: Diego and Jakob discussed the maintenance working mode, including labeling and assigning milestones to issues. They agreed to review issues from their respective companies and classify them accordingly.
- Reviewing External Issues: The team agreed to review issues reported by external companies not existing in the current CCB group, i.e Andreas Rauchert will handle issues from RA Consulting and Ansys, while Diego will check with Johannes for issues from CARIAD,....
- Future Milestones: Jakob suggested creating a milestone for issues that will be addressed in future releases (greater than 1.3.2). The team agreed and created the milestone "greater 1.4".
Follow-up tasks:
- SharePoint Setup: Finalize the dedicated SharePoint for the proof concepts of OpenX and grant access to relevant participants. (ASAM)
- Kickoff Meetings: Send doodles for the remaining kickoff meetings and gather information on active participants. (ASAM)
- Roadmap Refinement: Refine the project roadmap based on discussions from the kickoff meetings and present any necessary adjustments. (ASAM)
- Open Scenario XML Maintenance: review the existing issues from each company in the CCB. (All)
- Intersection Turn Specification: Gather more details about the use case for specifying turns at intersections and invite the requester to the next meeting for discussion. (ASAM)
- Non-Participating Members: Contact non-participating members to check for technical issues and willingness to join future meetings, and present a list for potential removal if necessary. (ASAM)