Jitter
When an event occurs regularly following a repetitive pattern, one may want to allow occurrences to take place late according to the pattern but within a bounded time window, and without impact on the subsequent occurrences. This authorized delay is called jitter.

Relationships
Main Description

Short Description

When an event occurs regularly following a repetitive pattern, one may want to allow occurrences to take place late according to the pattern but within a bounded time window, and without impact on the subsequent occurrences. This authorized delay is called jitter.

 

Links to TADL2 concepts

A bound on the jitter can be represented within a Repetition constraint as there is a specific parameter for it. It can also be defined for some constraints derived from Repetition, namely the Periodic, Sporadic and Pattern constraints.

·         RepetitionConstraint

·         PeriodicConstraint

·         SporadicConstraint

·         PatternConstraint

 

Abstraction level specific list of applicable events

---

 

Context Specific Example

An acquisition of wheel sensors must be done every 10 ms with a jitter of at most 0.5 ms. Denote acq the event describing the acquisition. The constraint PERIODIC(acq, 10, 0.5, 0) would accept trace 1 but not trace 2.

 

More Information