several years ago, it seemed like a good idea to incorporate the link between nominal time and wall-clock time into a dedicated anchor point, which also regulates the continued frame planning. But it turned out that such a design mixes up several concepts and introduces confusion regarding the meaning of "real time" - latency can not be reasonably defined for a whole planning chunk - skipping or sliding due to missed deadlines can not reasonably handled within such an abstract entity; it must be handled rather at the level of a playback process - linking the frame grid generation directly to a planning chunk undercuts the possible abstraction of a planning pipeline |
||
|---|---|---|
| .. | ||
| diagnostic-output.hpp | ||
| event-log.cpp | ||
| event-log.hpp | ||
| microbenchmark.hpp | ||
| run.hpp | ||
| suite.cpp | ||
| suite.hpp | ||
| test-coll.hpp | ||
| test-helper.cpp | ||
| test-helper.hpp | ||
| test.h | ||
| testdummy.hpp | ||
| testoption.cpp | ||
| testoption.hpp | ||