DUCKS supports an extensible model for storing result data. How results are saved - you guess it - is set up in the simulation study config file.

One implementation can save all simulation results in a relational database, currently MySQL. The usage of a database may be somehow oversized, but with a query language like SQL, result selection and aggregation is easy task. This is a major disadvantage when writing results to text files.

Setting up the database server

We currently use MySQL as database server, but this could also be changed by implementing another storage provider.

Setting up the server is rather simple. Just create a database (e.g. named "jist-swans") and give the required connection parameters in the DUCKS simulation study config file. Make sure that the database user has rights to create and alter tables.

The database structure is added dynamically by the MySQL connector implemented in DUCKS. First, it distinguished between input parameters and output values. Input parameters are saved as well to be able to select the appropriate results accordingly. The field names are derived from the properties:


ducks.routing.dsr.rreq.sent.orig=5545
...


... will be saved to the result database in the results table, field "routing.dsr.rreq.sent.orig".

Excluding/Including result parameters

Note that in many cases, a simulation will deliver much more result parameters that you would like to investigate. For instance, if you are interested in application-level results, routing and all other layers will also generate results. For this case, you can explicitly include or exclude certain result parameters from being saved by setting a parameter in the simulation study config file.

The same holds for input parameters; if you always use IEEE 802.11 as wireless
technology, you probably don't want to save this information in the database as selection criterion. Thus, you may define explicitly included or excluded parameters.

If you define both include and exclude, then first include and then exclude will be evaluated.