Most network simulators lack the ability of controlling large simulation setups with dozens of different parameter sets and tons of output data. DUCKS tries to fill this gap - it contains:

• A generic driver (simulation builder), controlled by config files
• Distribution of simulations to multiple compute servers (optional)
• Structured collection and storage of simulation results to a database server (optional)

DUCKS Architecture

Documentation