| [ Home | What's New | Contents | Overview | Contributors | Distribution | Examples | Documentation | Manual | Publications | Mailing List Archive | Problems ] | This page was last updated by Axel Belinfante on 2006-02-15 | |
| TorX Test Tool Information | ||
| Prev | Next | |
When invoked with the -d flag, autexp writes a dot(1) representation of the automaton to standard output, and exits. The dot node names correspond to the state numbers of the automaton, and with each dot edge (depicting a transition of the automaton) a dot attribute name is associated, which is given a unique value.
When invoked with the -m flag, autexp writes the connection matrix of the automaton to standard output, and exits.
The dot(1)
output can be used for animation, because autexp encodes the dot state
and edge (transition) names in the state identifiers that it uses in the
torx-explorer(5) interface. These identifiers can be extracted from a torx-log(5)
file using log2jararacy(1) such that a trace of a run of autexp can be
animated using anifsm(1) and jararacy(1).
This is the main advantage of using autexp over using the equivalent Aldebaran
(.aut) file explorer availabe via the CADP package (see mkprimer-cadp(1)).
| Prev | Table of Contents | Next |
| Appendix D: TorX Manual Pages: aut2fsmview(1) - translate Aldebaran (.aut) to FSMView input |
|
Appendix D: TorX Manual Pages: autsimplify(1) - simplify automaton Aldebaran (.aut) file |