Migration status

  • Home Page: Activity map.

intro story DELWAQ


DELWAQ is the engine of the D-Water Quality and D-Ecology programmes of the Delft3D suite. It is based on a rich library from which relevant substances and processes can be selected to quickly put water and sediment quality models together.

The processes library covers many aspects of water quality and ecology, from basic tracers, dissolved oxygen, nutrients, organic matter, inorganic suspended matter, heavy metals, bacteria and organic micro-pollutants, to complex algae and macrophyte dynamics. High performance solvers enable the simulation of long periods, often required to capture the full cycles of the processes being modelled.

The finite volume approach underlying DELWAQ allows it to be coupled to both the structured grid hydrodynamics of the current Delft3D-FLOW engine and the upcoming D-Flow Flexible Mesh engine (1D-2D-3D) of the Delft3D Flexible Mesh Suite (or even other models such as TELEMAC).

'DELWAQ in open source' is our invitation to all leading experts to collaborate in further development and research in the field of water quality, ecology and morphology using Delft3D. Feel free to post your DELWAQ related questions or comments in this dedicated forum space. If you are new to DELWAQ, the tutorial (in the user manual) is a good place to start. A list of DELWAQ related publications is available here.




Sub groups
D-Flow Flexible Mesh

Cohesive sediments & muddy systems


Message Boards

Error with AverageAtEachOutputTime

Pushpa Dissanayake, modified 6 Days ago.

Error with AverageAtEachOutputTime

Youngling Posts: 24 Join Date: 5/3/11 Recent Posts
Good day all,
A model was simulated with Windows and Linux.Windows: FLOW2D3D Version, no errors completed.Linux: FLOW2D3D Version, completed with the error,ERROR AverageAtEachOutputTime is set to true, but could not read valid AverageSedmorOutputInterval
I interest average sediment transport at each map interval. I then try to deactivate by setting,
AverageAtEachOutputTime = false, in *.mor, and also *.map files separately, but the error still appeared.
Is this an issue with versions or interface? why does it occur? How can I avoid? Anyway, both windows and Linux had same results as this is related to outputs .
Many thanks for your concern!Cheers,