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

Hot Start problem in DELWAQ

Yahia Kala, modified 5 Years ago.

Hot Start problem in DELWAQ

Youngling Posts: 12 Join Date: 7/11/13 Recent Posts

I have set up a DELWAQ run using the last time step of my previous run as the initial conditions for the new run. To do this, I am going through the GUI and specifying each relevant substance as a scalar field which is imported from a [oldrunname]_res.map file. I have two questions:

1. When I do this for a few parameters, I can see the difference in the [newrunname].scn file where some parameters are imported from the map file and some are not. However, the initial conditions section of the [newrunname].inp file (eighth block) only specifies the associated binary file [newrunname].res for the initial conditions. This leads me to believe that all of the initial conditions, whether they are imported scalar fields or constant values, are written to the [newrunname].res file when the [newrunname].scn file is saved through the GUI. This is then read by the .inp file at the beginning of the simulation. Is this true?

2. Whatever gets written to this [newrunname].res file is not consistent with the last time step of my model run. Attached is a screenshot of the actual thickness of S1 at the end of the old simulation and then at the beginning of the hot start simulation. It is three orders of magnitude too small. My first thought is that this could be a problem with unit conversion, but I am using the same version of D3D to run both simulations. Is there a way that I can manually specify some parameters in the [newrunname].inp file while still using the [newrunname].res file for the other parameters?

Yahia Kala