SIMULATOR manual page
Table of Contents


simulator - interactive simulator with ASCII command-line interface


bcg_open [bcg_opt] spec[.bcg] [cc_opt] simulator

or: [exp_opt] spec[.exp] [cc_opt] simulator

or: [fsp_opt] spec[.lts] [cc_opt] simulator

or: [lnt_opt] spec[.lnt] [cc_opt] simulator

or: [lotos_opt] spec[.lotos] [cc_opt] simulator

or: [seq_opt] spec[.seq] [cc_opt] simulator


This program provides interactive simulation for the BCG graph, the composition expression spec.exp, the FSP program spec.lts, the LNT program spec.lnt, the LOTOS program spec.lotos, or the sequence file spec.seq.

It performs an infinite interpreter loop, reading commands on the standard input, executing these commands, and printing the result on the standard output.

A stack is used to maintain the execution sequence starting from the initial state and leading to the current state, thus making backtrack possible.

The list of available commands can be obtained by typing "help" or "?".


The options bcg_opt, if any, are passed to bcg_lib .

The options exp_opt, if any, are passed to .

The options fsp_opt, if any, are passed to .

The options lnt_opt, if any, are passed to .

The options lotos_opt, if any, are passed to caesar and to caesar.adt .

The options seq_opt, if any, are passed to .

The options cc_opt, if any, are passed to the C compiler.

Exit Status

Exit status is 0 if everything is alright, 1 otherwise.


When the source is erroneous, error messages are issued.


Hubert Garavel (INRIA Rhone-Alpes)

BCG graph (input)

network of communicating LTSs (input)

FSP specification (input)

LNT specification (input)

LOTOS specification (input)

sequence file (input)


The source code of this tool is available in file $CADP/src/open_caesar/{simulator.c,simulator.i}

See Also

OPEN/CAESAR Reference Manual, bcg , bcg_open , caesar , caesar.adt , exp , , , , lotos , , seq ,

Additional information is available from the CADP Web page located at

Directives for installation are given in files $CADP/INSTALLATION_*.

Recent changes and improvements to this software are reported and commented in file $CADP/HISTORY.


Please report new bugs to

Table of Contents