Event-based NFA to DFA automaton conversion
The event-based NFA to DFA automaton conversion takes a non-deterministic automaton and produces a deterministic automaton with the same language. It thus determinizes the NFA to a DFA.
The tool takes a .cif file containing one automaton. In addition, the general event-based restrictions apply as well.
The output is a .cif file containing a deterministic automaton that is language equivalent with the input automaton. The resulting automaton has the same supervisory kind as the input automaton. The resulting DFA is not necessarily minimal, but can be minimized using the DFA minimizer.
Starting the NFA to DFA automaton conversion tool
The tool can be started in the following ways:
-
In Eclipse, right click a
.ciffile in the Project Explorer tab or Package Explorer tab and choose . -
In Eclipse, right click an open text editor for a
.ciffile and choose . -
Use the
cifnfadfatool in a ToolDef script. See the scripting documentation and tools overview page for details. -
Use the
cifnfadfacommand line tool.
Options
Besides the general application options, this application has the following options:
-
Input file: The absolute or relative local file system path to the input CIF specification.
-
Output file: The absolute or relative local file system path to the output CIF specification. If not specified, defaults to the input file path, where the
.ciffile extension is removed (if present), and a_dfa.ciffile extension is added. Thedfapart of the default extension depends on the Result name option. -
Result name: The name to use for the projected automaton. If not specified, defaults to
dfa. Also affects the Output file option. -
Add state annotations: Add state annotations to the locations of the automaton in the output CIF file. This option is enabled by default. If the output CIF file has an automaton with only a single non-initial location, then the location does not get a state annotation, regardless of whether the option is enabled or not.