DUCKS uses config files to define a complete setup of a simulation study. This means that both the setup of the simulation (e.g. nodes, scene, mobility etc.) and the DUCKS runtime environment (e.g. how to log, which servers to use etc.) can be included in one large file in the common Java properties format.

Sections

As mentioned, a simulation study config file consists of basically two sections. One of them defines the setup of the simulation, which is important for the driver. Because the driver is modular, this section is highly driver dependent.

The second section is used by the DUCKS Controller. It is not required, if simulations are only run using the DUCKS Generic Driver, without using the features of multiplexing, distribution and collection of results, as offered by the Controller.

Moreover, the first, driver-related section my contain so called multi-values when the Controller interprets the config file. This is for the purpose of specifying varied values for single parameters, e.g. a number of different field sizes. Within the Controller, a extensible Multiplexer class takes care of creating multiple, unique simulation parameter sets out of the configuration file. An example implementation of the multiplexer e.g. allows comma-separated values.

Format

The config file adopts the Java properties format and thus also allows hierachical configuration parameters. This is extensively used in DUCKS, particularly in the Generic Driver.

Example

to be done