ADTF
Loading...
Searching...
No Matches
Operation Modes

Description

In ADTF we differ between live setups (like in-car measurement) and virtual setups (like replay of the recording).
Both modes should operate the same regarding data-flow, timing/schedulung and more to enable a ground-truth for validation and verification.

Online Mode (Live)

In this mode the ADTF Session interacts with the outer world. This might be a car setup or HIL/SIL environments.
So ADTF processes data that originates from somewhere else. The time source for the ADTF Stream Time is the Reference Clock Service with one of its registered clocks (which in most cases represents the real progress of time).

If you need to synchronize timestamps in Live mode, see TimeStamp Synchronizer.

Offline Mode (Playback/Re-Simulation)

Most of the time this mode is defined by the presence of a Player and Playback Service.
The progress of the ADTF Stream Time is defined by the ADTFDAT File (or other container formats) that the Playback Service processes and other ADTF Components that use the Time Barriers. Therefore it can be paused, accelerated, resumed etc.

It is also possible to define whether the chunk timestamp (default) or sample timestamp should be used for replay, depending of your post-processing or resimulation setup. See Resimulation of data sources (sample vs chunk timestamp) for more information.

Note
Please keep in mind that during playback the progress of time does not necessarily correlate to real time.
ADTF processes only input data from the files that are played back with their stored time stamps.
It might of course write/send output data to other systems.
Warning
Mixing both operation modes (which means combining a Player with a real streaming source like hardware devices with own internal clocks) is neither recommended nor supported due to timing violations!
There might be use cases e.g. in early development processes but we advise to use such setups carefully and only for pre-development evaluation or purpose!