Difference between revisions of "Model Samples"

From CD++
Jump to: navigation, search
Line 1: Line 1:
 
'''A comprehensive list of models [http://www.sce.carleton.ca/faculty/wainer/wbgraf/samplesmain_1.htm can be found here]'''  
 
'''A comprehensive list of models [http://www.sce.carleton.ca/faculty/wainer/wbgraf/samplesmain_1.htm can be found here]'''  
  
<p>There is a more detailed description of each model in the file <b> README.TXT
+
 
</b>located in every subdirectory.<br>
+
<p>Each of the files described in the model respository contain a generic description. The user can find a more detailed description of each model in the different document files found on the archives.
<br>
+
 
<b><i>More information:</i></b>
+
<p>All of the above samples include the following files:
 
</p>
 
</p>
<p>All of the above samples include:
+
<p><b><i>FileName.MA</i></b>: Model description file. In the case of a DEVS model, this describes the coupled model and initial parameters. In the case of Cell-DEVS models, it includes the whole model<br>
</p>
+
 
<p><b><i>FileName.MA</i></b>: The model description file<br>
+
 
<b><i>FileName.EV</i></b> (optional): external events file <br>
 
<b><i>FileName.EV</i></b> (optional): external events file <br>
 +
<b><i>FileName.VAL</i></b> (optional): A file with initial values for a Cell-DEVS model <br>
 +
<b><i>FileName.BAT</i></b>: A script used to run the simulation with the correct parameters (available for Windows platforms only; it can be simply modified to be used under other platforms). It executes the simulation and it generates a LOG file <br>
 +
<b><i>FileNameDRW.BAT</i></b> (optional): A script used to activate the DRAWLOG tool, where the results can be seen in a matrix (only available with some cellular models)<br>
  
 
<b><i>FileName.LOG</i></b> (optional): A log file generated by the simulator <br>
 
<b><i>FileName.LOG</i></b> (optional): A log file generated by the simulator <br>
<b><i>FileName.DRW</i></b> (optional): A file generated by the DRAWLOG tool, where the results can be seen in a matrix (only available with some cellular models) <br>
+
<b><i>FileName.DRW</i></b> (optional): A file generated by DRAWLOG, where the results can be seen in a matrix <br>
<b><i>FileName.VAL</i></b> (optional): A file with initial values for the model  <br>
+
<b><i>FileName.BAT</i></b>: A script used to run the simulation with the correct parameters (Windows platforms only, but it can be simply modified to be used under other platforms). Generates a LOG file <br>
+
<b><i>FileNameDRW.BAT</i></b> (optional): A script used to generate the .drw file <br>
+
  
 
<br>
 
<br>

Revision as of 17:45, 30 April 2008

A comprehensive list of models can be found here


Each of the files described in the model respository contain a generic description. The user can find a more detailed description of each model in the different document files found on the archives. <p>All of the above samples include the following files:

FileName.MA: Model description file. In the case of a DEVS model, this describes the coupled model and initial parameters. In the case of Cell-DEVS models, it includes the whole model
FileName.EV (optional): external events file
FileName.VAL (optional): A file with initial values for a Cell-DEVS model
FileName.BAT: A script used to run the simulation with the correct parameters (available for Windows platforms only; it can be simply modified to be used under other platforms). It executes the simulation and it generates a LOG file
FileNameDRW.BAT (optional): A script used to activate the DRAWLOG tool, where the results can be seen in a matrix (only available with some cellular models)
FileName.LOG (optional): A log file generated by the simulator
FileName.DRW (optional): A file generated by DRAWLOG, where the results can be seen in a matrix

The DEVS models are written in C++, and includes :
NAME.CPP: The C++ source code file of the NAME model. This file is needed to recompile the simulator properly (Download an example here!)
NAME.H: The C++ header file of the NAME model. This file is needed to recompile the simulator properly (Download an example here!)