Skip to content

Commit

Permalink
Update trace_file_formats.adoc
Browse files Browse the repository at this point in the history
* Make zero_time and creation_time recommended

Signed-off-by: Carlo van Driesten <carlo.van-driesten@bmw.de>
  • Loading branch information
jdsika authored Nov 28, 2024
1 parent 151ea10 commit 53511b9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/architecture/trace_file_formats.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,8 @@ This is a string in the format `major.minor.patch`, for example `3.17.3`.
The version of the protobuf implementation used in the trace file.
This is a string in the format `major.minor.patch`, for example `3.26.0`.

The `net.asam.osi.trace` meta-data record may also contain the following recommended `metadata` entries:

`zero_time`::
The point in real or simulated calendar time corresponding to time 0 in all timestamps in the trace file.
Must be provided as a full ISO8601 formatted date time string, including timezone data, conforming to the https://www.w3.org/TR/xmlschema11-2/#dateTimeStamp[XML Schema dateTimeStamp] lexical space.
Expand All @@ -94,8 +96,6 @@ NOTE: Even in pure simulation use cases there is usually a relationship to a sim
The point in real calendar time when the recording of the data in the trace file was started.
Must be provided as a full ISO8601 formatted date time string, including timezone data, conforming to the https://www.w3.org/TR/xmlschema11-2/#dateTimeStamp[XML Schema dateTimeStamp] lexical space.

The `net.asam.osi.trace` meta-data record may also contain the following recommended `metadata` entries:

`description`::
A human-readable description of the data contained in the multi channel trace file.

Expand Down

0 comments on commit 53511b9

Please sign in to comment.