We are migrating our GitLab environment. Temporary outages may occur until January 9, 2026. Services will continue to operate normally. For questions, please contact infrastructure@asam.net.

P_2025_02-008: ASAM OSI Multi Trace File Format

Description: The current OSI trace file format is quickly becoming a lingua franca for the exchange of measured or generated non-interactive (i.e. open loop) scenarios, as well as being used for simulation and measured result recordings, validation of OSI generating tools etc. However the current format is very bare-bones, so not supporting multiple time related traces, time-based indexing, metadata, etc. An enhanced trace file format needs to be specified that can serve besides the current format for more advanced use cases.

Detailed Background: The scope of the use case shall encompass the transfer of multiple OSI message streams with a common time-base. Out of scope is arbitrary bundling of unrelated message streams (i.e. this is not a database of unrelated traces). The solution should be based on commonly supported light-weight message trace file formats suitable for simulation use, like e.g. MCAP, that are supported by existing tools and provide for mechanisms that also support the carrying of related non-OSI message streams, as well as common and arbitrary meta-data. Quick access to essential meta-data (e.g. number of messages/time span of included messages) as well as random access capabilities are essential. Optionally a common specification for the recording of OSI message streams using ASAM MDF can be included in this Epic for purely low-level recording based work-flows, with a clear guidance on conversion to the common trace file format.

See ASAM OSI Issues:

Affected Standards: OSI (potentially ASAM MDF, however no changes in MDF are expected).

Completion Criteria:

  • The OSI trace file format specification is enhanced with a section on the new multi-trace file format.
  • Optionally: A section on the use of MDF for OSI message recording and extraction is added to the OSI specification.
  • The current python trace file reading/writing module included with OSI is split out to a separate package (as this is tooling/library and not specification) and enhanced with support for the new file format(s).

Enrolled Companies: PMSF, BMW, Persival, AVL

ASAM Office Responsible (OR): @AhmedSadek Ahmed Sadek

Assignee Project Lead: @pmai (Pierre R. Mai/PMSF)

Estimated Start Date: 24 February 2025

Estimated End Date: 30 June 2025

Budget Request: None.

Budget Use: None.

image Enrollment: https://forms.office.com/e/6sTgGPCEY6

Edited by Ahmed Sadek (ASAM)