In this directory, you will find the following files and directory:
AAREADME The directory of the documentation.
vt.gpk is the main Signal file. It has to be loaded by the graphical user interface "polychrony". This Signal program contains different processes.
|
|- CONTEXT: used to perform Simulation
|
|- VT_Foo: your application
|
|- vt: This process is simply the process VT_Foo to which you add some SIGALI functions and/or some assertions that have to be checked by the inputs. The name is the same for technical reasons than the main program. This is this one that you have to compile in order to obtain the corresponding polynomial dynamical system on which synthesis will be performed.
vt.sim, vt.res are file generated by Sigali in order to perform simulation. They contains in a internal format the result of the sigali computations (i.e. the controller). They will be used by the polychrony tool to encapsulate the controller within the global Signal program (see below).
These files have been imported here from vt/ directory (see below).
vt Directory used by the Polychrony compiler (code generation: c code, z3z code).
vt.PAR Signal program parameters.
Spec_Liaison.dir Directory that contains the C/JAVA inteface for the simulation.
Demo Directory that contains some specific java programs for the simulation.
-> set_reorder(?) perform an automatic reordering of the underlying BDD. For some applications it is better to use set_reorder(1); (another kind of reordering).
At this point, the files vt.sim and vt.res must have been generated.
Goto the root directory of the example (i.e. up directory)
Copy the vt.sim and vt.res (generated in 4) in the "current" directory.
Under polychrony GUI, goto the vt_Foo process and load the resolver by the following command
"Tools -> prove -> build_resolv " command.
After this command, the file vt.SIG.SIG has been generated. IMPORTANT: Do not save the program (vt.gpk) after this action (as this program, contains some hidden lines of Signal code that have been automatically added)
Use the "makeLib" command (see above). This compilation will basically produce a library that will be used further for the JAVA simulation. (The compiler will produce some C files in vt directory...)
For simulate, execute the command
run_demo
Generated on Fri Oct 6 09:23:58 2006 for AAREADME by
1.4.6