WET is an open source QGIS plugin for application and user adaptation of aquatic ecosystem models. The WET installer and the WET source code is available through Gitlab:

To download the installer or the source code, you first need to set up a (free) Gitlab account. Please read the download instructions and watch the associated video tutorial on how to download the software.

Development log

WET 1.3.2 (05. APR. 2018)

  • Updated scenario tool to handle formatting of model files across text editors.
  • Other minor updates.

To upgrade from WET 1.3.1 to WET 1.3.2 simply install WET 1.3.2. You may contact us and we will try to assist you with a project update.

WET 1.3.1 (19. JAN. 2018)

  • Improved plotting functionality for obs vs. simulation regarding warmup period etc.
  • From the updated core model executable (code version from 21. Nov. 2017) a linkage file was skipped in WET version 1.3, but the file is now included in version 1.3.1.
  • Other minor updates.

To upgrade from WET 1.3 to WET 1.3.1 simply install WET 1.3.1. Older WET projects may still be run in WET 1.3.1, but to activate updates (the linkage file) you need to create a new WET 1.3.1 project for your study case. Alternatively you may contact us and we will try to assist you with a project update.

WET 1.3 (20. DEC. 2017)

  • Fixing issues with deleting scenarios.
  • Better check of python dependencies to allow limited usage.
  • Enabling depth range plotting for visualization of observations vs. simulations.
  • Integrating compatibilities for matplotlib with newer versions of QGIS.
  • Fixing issues with problems when using long decimals for parameters.
  • Updated core model executable (code version from 21. Nov. 2017) and corresponding parameter files.
  • Other minor updates.

To upgrade from WET 1.2 to WET 1.3 simply install WET 1.3. Older WET projects may still be run in WET 1.3, but to activate updates in the core model you need to create a new WET 1.3 project for your study case. Alternatively you may contact us and we will try to assist you with a project update.

WET 1.2 (3. Nov. 2017)

  • Fixing issues with auto-generated simulation ranges.
  • Implementing user-info when viewing observations vs. simulations.
  • Minor interface updates.
  • Other minor fixes and updates.

To upgrade from WET 1.1 to WET 1.2 simply install WET1.2 and open your existing WET project.

Let us know if you run into problems.

WET 1.1 (9. Oct. 2017)

  • Updated to match the new FABM-PCLake core code (e.g. additional fractions of nutrients, 9. Oct. 2017).
  • Fixed issues to support high DPI screens with a semi-adaptive layout.
  • New tab implemented where observations may be added and compared to simulated output. 
  • Fix of minor bugs.
  • Updated references in the "about" tab.


FABM-PCLake is the aquatic ecosystem engine of WET, and describes interactions between multiple trophic levels, including piscivorous, zooplanktivorous and benthivorous fish, zooplankton, zoobenthos, phytoplankton and rooted macrophytes. The ecosystem model also accounts for oxygen dynamics and a fully closed nutrient cycle for nitrogen and phosphorus. An executable of the coupled one-dimensional hydrodynamic-ecosystem model GOTM-FABM-PCLake is part of the WET installation package.

The complete source code for FABM-PCLake is also available through Gitlab:

To download the source code, you first need to set up a (free) Gitlab account. Please read the download instructions for more information.

Development log

(21. Nov. 2017)

  • Code clean-up including removal of redundant code.
  • Fixed bug relating to the maturing of juvenile fish.
  • Fixed bug relating to light function for cyanobacteria.
  • Added diagnostic output for oxic-layer fraction in sediment.

(9. Oct. 2017)

  • General clean of code and removal of minor bugs.
  • Implementation of an additional nutrient fraction to distinguish between dissolved and particulate organic nutrients in both the pelagic and benthic domain.
  • Updated parameter naming of default values for settling and sedimentation rates.


WET and FABM-PCLake are continuously being developed, to account for new discoveries within aquatic ecosystem functioning, to enable simulations of new relevant management interventions and also for outputting key diagnostics of ecosystem health. The ongoing development of WET and FABM-PCLake is dependent on incoming projects. If you have ideas for further developments these can be posted on the “Issues board” of the Gitlab page of WET and FABM-PCLake, respectively (using the issue label “ideas”).

Examples of potential new developments to WET include:

  • Enhanced use of the various functionalities available in QGIS. For instance allowing users to draw inlets, outlets, monitoring stations on the map canvas and subsequently configuration in the GUI of WET.
  • Incorporation of greater flexibility for the user in configuration of number of inflows/outflows and evaporation calculations.
  • Implementation of sensitivity analysis and auto-calibration tools to support model application and adaptation for a specific aquatic system.
  • Wider flexibility regarding configuration of the core aquatic model where users may choose among different varieties of models already developed and published, which may prove better for a specific system.
  • A feature for analyzing past climate data and processing that to simulate into the near future (e.g., 10-20 years), e.g., for simulating the resilience and temporal response lag of an ecosystem after a management intervention.
  • A feature for exporting a standard report of a WET application (e.g., exporting a standardized pdf report based on the user-adapted WET application).
  • Additional management interventions, including harvesting or transplanting of rooted macrophytes, sediment dredging, oxygenation and mineral dosing of P-binding agents.
  • Functionality within WET to enable selection, download and formatting of ECMWF meteorological time series for any location in the world.

Examples of potential new developments to FABM-PCLake include:

  • Several of the potentially new functionalities of WET, as listed above, will require some further development of the FABM-PCLake model, including, for example, descriptions of processes and state variables involved during dosing of a P-binding agent.
  • A new module for simulating key green-house gas emission dynamics.
  • Explicit behavior of fish (e.g., a new IBM-based fish module).

Related software



  • The General Ocean Turbulence Model (GOTM) is a one-dimensional hydrodynamic model, developed by an international community of scientists. GOTM is open source, and the source code is available through Github: Further information on GOTM is available through


  • The Framework for Aquatic Biogeochemical Models (FABM) enables coupling between several hydrodynamic and biogeochemical models, and was developed by Bolding and Bruggeman ApS. FABM is open source, and the source code and further information is available through Github:


  • Simulations in WET can read output from the QSWAT model, which is an eco-hydrological model that describes processes in a watershed. QSWAT is open source, and is available for download here:



SWAT2lake is a tool to assist in the delineation of lake or reservoir watersheds with QSWAT. The tool, intended to work in parallel with QSWAT, allows the user to delineate a watershed that is tailored to the waterbody outline, thus accounting for the entire drainage area flowing into it. This capability covers an existent gap when modelling lakes and reservoirs watershed with SWAT.

Download instructions

To download the SWAT2lake installation package, you must first register a free Gitlab account. When signing into the SWAT2lake Gitlab page, you will get access to the software, an "Issues" board (effectively a discussion and user support forum) and wikis.

We have prepared a short instructional video on how to register a Gitlab account, and then downloading and installing WET, the procedure for SWAT2lake is fully equivalent to the procedure for downloading WET.

Why do you need to register to access SWAT2lake?

SWAT2lake are free, open source, software packages. However, in order for the developer team at Aarhus University to have internal support for offering ongoing maintenance and future improvements, we need to demonstrate the strength and impact of the software tools through the collection of some basic information on how many is using the software.