Page tree
Skip to end of metadata
Go to start of metadata

Wanda is an advanced, interactive software package to support the hydraulic design process of your pipeline system. The program is used for the hydraulic analysis of steady and unsteady flow conditions in arbitrary configured pipeline networks.

Specific features

Steady/nonSteady run

Wanda can be run in steady state or nonsteady state. In the steady state setting, every timestep will be treated as independent of the previous or following timestep. In the non-steady state, the model will perform as a hydraulic model where disturbances can run through the system. If a timestep in one of the input timeseries contains a missing value in steady state modus, that timestep will not be simulated and the adapter will continue to the next timestep. In non-steady state, the wanda adapter will exit with a warning message.


For specific purposes it can be handy to combine multiple model simulations in one run. This is the case where the actual functioning of a pump is simulated, which is influenced by the other pumps in the same system. In the GeneralAdapter it is configured as one run, but the Model Adapter will run Wanda X times (X is the number of the pumps in the Wanda model). Every run, all pumps will be given the parameter: loopChoiceInputParameterId (see section below), except the pump that is being simulated: this pump will get the other parameters (water level suction side, pumpspeed). The result of this run will be the discharge for this pump. Looping this way through all pumps, the Module Adapter will collect the results for all pumps in the system and import it as the result of one model simulation.

Wanda adapter binary folder

The following files are part of the binary folder:

A logical place would be <Region>\Modules\Wanda\bin

Model folder can be placed in <Region>\Modules\Wanda

The Wanda Adapter does not need a separate configuration file, as does for example the SOBEK adapter. Instructions to the adapter are configured in the GeneralAdapter module file. This will be explained in the following sections

General Adapter Configuration

General section

The image below shows an example of the configuration of the general section. The following settings are of specific importance for Wanda:

  • rootDir: folder where the Wanda model is located
  • exportDir: folder where the Wanda input files should be stored
  • exportIdMap: the idMapFile for the export to Wanda: the external ID's are the Id's in the WANDA model
  • importDir: folder where Wanda stores the output
  • importIdMap: the idMapFile for the import from Wanda: the external ID's are the Id's in the WANDA model

ExportActivities Section

Important for Wanda here are the properties of the exportRunFileActivity. These properties are the actual Wanda settings.

  • key - runSteadyForEveryTimeStep: this setting can be true or false. If true, every timestep that is simulated is independent of every previous or following timestep. So every timestep is handled as a steady situation. If false, the model will run as a hydraulic model simulating a non-stationary situation.
  • key - wdi: this setting contains the name and path of the actual Wanda model
  • key - loopChoiceName (optional): required for pump loop setting
  • key - loopChoiceInputParameterId (optional): required for pump loop setting
  • key - loopChoiceSelectionIndex (optional): required for pump loop setting

ExecuteActivities Section

The following image shows an example of the settings of the ExecuteActivities section in the general Adapter module. Wanda specific elements are:

  • command - executable: this contains the path to java.exe
  • arguments: the several required arguments for java.exe to be able to run the Wanda adapter. Make sure the reference to the runInfo file is correct (as specified in exportActivities section).

ImportActivities Section

The following image is an example of the importActivities section. An important element here is the exportPlaceHolderFile: this should be set to true.

Example configuration

Example configuration files are attached, including IdMaps.

  • No labels