Skip to content

Initial multi channel trace file format specification #841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pmai merged 11 commits into from
Jul 11, 2025
Merged

Initial multi channel trace file format specification #841

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
ab9b6cb
Initial multi channel trace file format specification
pmai Nov 24, 2024
5584296
Minor fixes based on review feedback
pmai Nov 25, 2024
77fd4c6
Further clarifications and corrections from code review
pmai Nov 25, 2024
aa2b48a
Clarify extension bit of naming convention
pmai Nov 25, 2024
45f2578
Apply suggestions from code review
pmai Nov 26, 2024
f69b481
Update trace_file_formats.adoc
jdsika Nov 28, 2024
301790a
Clarify that only a single file global meta-data record is allowed
pmai Nov 29, 2024
15b043f
Provide example for creation_time based on review feedback
pmai May 27, 2025
1d96e47
Enhance discussion of non-top-level message types
pmai Jun 10, 2025
5ab48f9
Clarify rules on MCAP profile field in header
pmai Jul 1, 2025
c0bbdeb
Adjust wording to current normative modal verbs
pmai Jul 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Clarify rules on MCAP profile field in header 
Signed-off-by: Pierre R. Mai <[email protected]>
  • Loading branch information
@pmai
pmai authored Jul 1, 2025
commit 5ab48f9921302f549e9ba9931381244e16748667
3 changes: 3 additions & 0 deletions doc/architecture/trace_file_formats.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,9 @@ The OSI multi channel trace file format is based on the MCAP file format, which
The OSI multi channel trace file format is a specialization of the MCAP file format, with additional constraints and requirements specific to OSI.
Hence, any valid OSI multi channel trace file is also a valid MCAP file, but not the other way around.

The OSI multi channel trace file format does not specify an MCAP profile.
Therefore, it can be used with any or an empty profile field in the MCAP header record, as long as the given profile does not contradict or disallow any of the requirements of this specification.

The following rules apply to OSI multi channel trace files:

- The file extension to be used is `.mcap`.
Expand Down