You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »


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

Combined pre- and post- adapter

A common practice for development of FEWS model adapters is to develop two separate adapters for pre- and post processing of model input and output. For Wanda this resulted in two adapters, the WandaPreadapter and WandaPostAdapter. However on request of the users an additional, combined adapter has been added, the WandaAdapter which performs both the pre-and post processing tasks as wel as ex

Wanda adapter binary folder

The following files are part of the binary folder for the Wanda adapter and are provided in the fews-wanda-adapter-bin.<version>.zip artifact of the "install adapters" teamcity builds:

  • fews-wanda-adapter.jar
  • Wanda.Java.jar
  • castor-0.9.5p.jar
  • Delft_PI.jar
  • Delft_PI_castor.jar
  • Delft_Util.jar
  • FastInfoset-1.2.6.jar
  • hamcrest-core-1.3.jar
  • jna-3.5.1.jar
  • log4j-1.2-api-2.11.1p.jar
  • log4j-api-2.11.1.jar
  • log4j-core-2.11.1.jar
  • log4j-slf4j-impl-2.11.1.jar
  • slf4j-api-1.7.13.jar
  • xercesImpl.jar

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

Wanda model binary folder

The Wanda model binaries currently consist of 221 files so this package is a bit large to list the complete content here. TODO: refer to source 

The Wanda Model folder can be placed in <Region>\Modules\Wanda\bin\wanda or other folder of your choice which can be configured separately from the adapter binaries using a property in the runinfo xml file.

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 module is located.
  • workDir: folder where the Wanda model files (*.wdi, *.wdo, *.wdx) files are located and where the Wanda model is executed.
  • exportDir: folder where the Wanda adapter input files (*.xml) 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 adapter stores its output file (*.xml)
  • importIdMap: the idMapFile for the import from Wanda: the external ID's are the Id's in the WANDA model
  • diagnosticFile: the path of the PI diagnostic file written by the Wanda adapter.

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

Disclaimer