User Tools

Site Tools


pads:artisinst

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
pads:artisinst [2012/10/19 08:14] gdangelopads:artisinst [2019/11/15 13:03] (current) gda
Line 8: Line 8:
    * **Bash shell**: command line usage    * **Bash shell**: command line usage
    * **ARTÌS**: general structure, please see [[http://gdangelo.web.cs.unibo.it/pool/papers/gdangelo-PERF-2005.pdf|FIRB2005]].    * **ARTÌS**: general structure, please see [[http://gdangelo.web.cs.unibo.it/pool/papers/gdangelo-PERF-2005.pdf|FIRB2005]].
-   * **GAIA/GAIA+**: general structure, please see [[http://gdangelo.web.cs.unibo.it/pool/papers/gdangelo-IJSPM-2009.pdf|IJSPM09]].+   * **GAIA/GAIA+**: general structure, please see [[https://arxiv.org/abs/1610.01295|SIMPAT2017]].
  
 ===== Assumptions ===== ===== Assumptions =====
  
-   * **UBUNTU Linux 10.04.1**: desktop version, fully updated+   * **UBUNTU Linux 12.04.1**: desktop version, fully updated
  
-===== Basic Installation =====+===== Installation =====
  
 ==== Download ==== ==== Download ====
  
-The last version of the ARTÌS/GAIA software can be freely downloaded from the [[pads:download|downloads page]]. The runtime is available in both 32 and 64 bits versions, in the following we will assume a 32 bits architecture.+The last version of the ARTÌS/GAIA software can be freely downloaded from the [[pads:download|downloads page]]. The runtime is available in both 32 and 64 bits versions.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
-wget http://pads.cs.unibo.it/download/artis/ARTIS-2.0.2-LUNES-0.0.1a.tar.bz2+wget http://pads.cs.unibo.it/download/artis/ARTIS-2.0.4-i686.tar.bz2
 </code> </code>
  
 Untar the downloaded file in the chosen directory. Untar the downloaded file in the chosen directory.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
-tar xvfz ARTIS-2.0.2-LUNES-0.0.1a.tar.bz2+tar xvfj ARTIS-2.0.4-i686.tar.bz2
 </code> </code>
  
 ==== Missing libraries ==== ==== Missing libraries ====
  
-<fc #ff0000>MISSING LIBRARIES:</fc> the standard installation of Ubuntu 10.04.1 is missing some libraries that are needed by ARTÌS/GAIA. The following libraries have to be installed using the command line interface (as shown in the following) or the graphical tools provided in Ubuntu.+<color #ff0000>MISSING LIBRARIES:</color> the standard installation of Ubuntu 12.04.1 is missing some libraries that are needed by ARTÌS/GAIA. The following libraries have to be installed using the command line interface (as shown in the following) or the graphical tools provided in Ubuntu. Starting from ARTÌS+GAIA version 2.1.0 the "libgcrypt" libraries are no longer necessary.
  
-|  name            ^ description ^ +|  name            ^  description  
 ^ libgcrypt11    |  cryptographic functions  | ^ libgcrypt11    |  cryptographic functions  |
 ^ libgcrypt-dev    |  cryptographic functions, development files  | ^ libgcrypt-dev    |  cryptographic functions, development files  |
Line 42: Line 42:
 ^ libglib2.0-dev    |  library with useful C routines, development files  | ^ libglib2.0-dev    |  library with useful C routines, development files  |
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 sudo apt-get install libgcrypt11 libgcrypt-dev libglib2.0-0 libglib2.0-dev sudo apt-get install libgcrypt11 libgcrypt-dev libglib2.0-0 libglib2.0-dev
 </code> </code>
 +
 +===== Basic Usage =====
 +
  
 ==== A simple example ==== ==== A simple example ====
Line 51: Line 54:
 Now we are ready for testing our ARTÌS/GAIA installation. In the main directory of the software (e.g. the ARTIS-2.0.0 directory) there is the STRUCTURE.TXT file that describes the whole software structure including EXAMPLES and MODELS. We will start from the WIRELESS example that is contained in the EXAMPLES directory. In this simple model there is a set of wireless devices moving in a toroidal 2D space. The interactions among them are based on proximity. Now we are ready for testing our ARTÌS/GAIA installation. In the main directory of the software (e.g. the ARTIS-2.0.0 directory) there is the STRUCTURE.TXT file that describes the whole software structure including EXAMPLES and MODELS. We will start from the WIRELESS example that is contained in the EXAMPLES directory. In this simple model there is a set of wireless devices moving in a toroidal 2D space. The interactions among them are based on proximity.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
-cd ARTIS-2.0.2/EXAMPLES/WIRELESS+cd ARTIS-2.0.4/EXAMPLES/WIRELESS
 </code> </code>
  
 All the models and examples are provided as source code and therefore need to be compiled before usage, in all cases a Makefile is provided. All the models and examples are provided as source code and therefore need to be compiled before usage, in all cases a Makefile is provided.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 make make
Line 65: Line 68:
 If the compilation is successful then the **sima** and the **wireless** binaries have been created in the current directory. A couple of shell scripts are provided for running the example, in this case we will use the **run** script. Running the script with no parameters generates an error and shows the syntax to be used. If the compilation is successful then the **sima** and the **wireless** binaries have been created in the current directory. A couple of shell scripts are provided for running the example, in this case we will use the **run** script. Running the script with no parameters generates an error and shows the syntax to be used.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 ./run ./run
Line 74: Line 77:
 The first parameter (#LP) is the number of Logical Processes used in the simulation and the second one (#SMH) is the number of objects to simulate. The first parameter (#LP) is the number of Logical Processes used in the simulation and the second one (#SMH) is the number of objects to simulate.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 ./run 2 100 ./run 2 100
Line 85: Line 88:
 Both the LPs have completed the execution, the elapsed amount of time is shown in the output. The execution has produced one log file for each LP in which is reported a step-by-step evolution of simulated model. The log files are named {{:pads:0.out|}} and {{:pads:1.out|}}. Furthermore, two extra log files for runtime errors and low level diagnostic are produced: {{:pads:0.err|}} {{:pads:1.err|}}. Both the LPs have completed the execution, the elapsed amount of time is shown in the output. The execution has produced one log file for each LP in which is reported a step-by-step evolution of simulated model. The log files are named {{:pads:0.out|}} and {{:pads:1.out|}}. Furthermore, two extra log files for runtime errors and low level diagnostic are produced: {{:pads:0.err|}} {{:pads:1.err|}}.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 gedit 0.out gedit 0.out
Line 105: Line 108:
 Now we can proceed with a much more complex simulated model in which are used the features offered by the [[pads:gaia|GAIA]] framework. Now we can proceed with a much more complex simulated model in which are used the features offered by the [[pads:gaia|GAIA]] framework.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 cd.. cd..
Line 114: Line 117:
 Also in this case it is necessary to compile the simulated model using the provided Makefile. Also in this case it is necessary to compile the simulated model using the provided Makefile.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 make make
Line 121: Line 124:
 If the compilation is successful then the **sima** and the **mig-agents** binaries have been created in the current directory. As usual a shell script (i.e. **run**) can be executed to start the simulation. Running the script with no parameters generates an error and shows the syntax to be used. If the compilation is successful then the **sima** and the **mig-agents** binaries have been created in the current directory. As usual a shell script (i.e. **run**) can be executed to start the simulation. Running the script with no parameters generates an error and shows the syntax to be used.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 ./run ./run
Line 130: Line 133:
 The first parameter (#TOT_LP) is the total number of Logical Processes used in the simulation, the second one (#LP) is the amount of LPs to be run on this computer and, finally, (#IA) is the number of objects to simulate. The first parameter (#TOT_LP) is the total number of Logical Processes used in the simulation, the second one (#LP) is the amount of LPs to be run on this computer and, finally, (#IA) is the number of objects to simulate.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 ./run 2 2 100 ./run 2 2 100
Line 143: Line 146:
 In this case the useful information in the log file of the second LP. In this case the useful information in the log file of the second LP.
  
-<fc #ff6600>EXAMPLE:</fc>+<color #ff6600>EXAMPLE:</color>
 <code> <code>
 gedit 1.out gedit 1.out
pads/artisinst.1350634496.txt.gz · Last modified: 2012/10/19 08:14 by gdangelo

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki