The usual way to give the semantics of an automata theoretic structure is to describe the execution of such a structure as a run (cf. figure 5.5).
Whether we have a deterministic or an indeterministic version of an automaton it does not matter: in every execution cycle only one command line will be executed.
An execution cycle is to be understood as an operation where we have an automaton at cycle time
(usually '1' for the beginning, can be also '0') and a state counter
. If
is a start state with
then
5.1. The tape starts with position '1' (or '0') with one section for reading and one for writing and can be infinite. In the beginning
all clocks
connected to states have to be set to zero '0'.
A simple version of a run -or an execution- of an automaton can then be interpreted as a protocol of the cycles described above. The statement of each cycle which does not cause an error contains the following elements:
Thus we get the following line:
A complete run
of an automaton
based on a sequence of input events
is then a sequence
such that
.
In this version is a timed automaton a different automaton compared to the usual finite automaton! The execution of the automaton not only examines whether a certain state q and a certain input 'in' is given, but additionally whether the clock c has a certain value and that this value satisfies a condition . If the input 'in' is given but the clock does not satisfy the condition, then the operation will not be executed. This changes the behavior of a timed finite automaton compared to an 'usual' finite automaton.
The set of all possible executions of a finite automaton a can then be defined as
For a run
of an automaton
we can also describe an element, which is reachable at position
in
as
The set of all reachable heads can then be defined as
Gerd Doeben-Henisch 2010-03-03