pads:lunes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pads:lunes [2011/01/14 05:47] – gdangelo | pads:lunes [2012/12/13 08:46] – gdangelo | ||
---|---|---|---|
Line 3: | Line 3: | ||
The main goal of LUNES is the efficient simulation of complex protocols on top of large scale, unstructured networks. | The main goal of LUNES is the efficient simulation of complex protocols on top of large scale, unstructured networks. | ||
- | It offers an efficient and easy-to-use tool for the simulation of complex protocols on top of large graphs. In practice, | + | It offers an efficient and easy-to-use tool for the simulation of complex protocols on top of large graphs. In practice, LUNES is able to import the graph topologies generated by other tools (e.g. igraph) and provides the functionalities that are needed for the performance evaluation of simulated protocols. |
- | LUNES is able to import the graph topologies generated by other tools (e.g. igraph) and provides the functionalities that are needed for the performance evaluation of simulated protocols. | + | |
LUNES has been designed to clearly split the fundamental phases: | LUNES has been designed to clearly split the fundamental phases: | ||
Line 13: | Line 12: | ||
This modular approach permits the easy integration of external software tools. In practice, such integration is based on very simple template files (such as the graphviz dot language) and provides a good level of extensibility. Under the performance and scalability viewpoint, the most demanding points are the protocol simulation and the traces analysis. | This modular approach permits the easy integration of external software tools. In practice, such integration is based on very simple template files (such as the graphviz dot language) and provides a good level of extensibility. Under the performance and scalability viewpoint, the most demanding points are the protocol simulation and the traces analysis. | ||
- | The first one is demanded to the ARTÌS middleware and the GAIA+ framework, such tools are based on the Parallel And Distribute Simulation (PADS) approach and provide a very good level of scalability. LUNES has been written in such a way to be able to exploit the adaptive re-configuration features provided by GAIA+. | + | The first one is demanded to the [[pads: |
The second one, that is the traces analysis, has been excluded from the simulation tasks and some specific software tools have been implemented. Also in this case, the design and implementation of such tools has been done in such a way to exploit all the computational resources provided by parallel (multi-processor or multi-core) architectures. | The second one, that is the traces analysis, has been excluded from the simulation tasks and some specific software tools have been implemented. Also in this case, the design and implementation of such tools has been done in such a way to exploit all the computational resources provided by parallel (multi-processor or multi-core) architectures. | ||
- | **The first public | + | ===== Download ===== |
+ | |||
+ | **The last version of LUNES can be freely downloaded from the [[pads: | ||
+ | |||
+ | ===== Documentation ===== | ||
+ | |||
+ | **For more information on the LUNES design, implementation and performance please see [[http:// | ||
+ | |||
+ | **For a short guide on the LUNES installation and usage please see the [[pads: | ||
+ | |||
+ | ===== Known bugs ===== | ||
+ | |||
+ | Up to now there are no known bugs. Bug reports are appreciated but please follow the instructions at the end of the [[pads: | ||
+ | |||
+ | |||
+ |
pads/lunes.txt · Last modified: 2020/04/20 12:16 by gda