Migration status

  • Home Page: Activity map.

intro story DELWAQ

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.

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ

Cohesive sediments & muddy systems

 


Message Boards

z-layer initial condition specification (Delft3D 4.02.03)

KH
Kevin Hanegan, modified 2 Years ago.

z-layer initial condition specification (Delft3D 4.02.03)

Youngling Posts: 6 Join Date: 7/2/11 Recent Posts
Hi,
Are any non-uniform initial condition specification options available for z-layer models? The manual pg. 43 states that using .ini files is not yet available for the Z-model, but can restart or map files be used instead?

Here is some more information on my problem for your information. I'm simulating a large estuary with salinities ranging from 0 to 35 psu. Spinup from uniform conditions would take multiple weeks of runtime to achieve a realistic salinity gradient, so I would like to be able to initialize with spatially-varying salinities derived from measurements. Developing the .ini file using quickin and OET was fairly straightforward, though I'm realizing now that this method will never work. Hoping that I can hot-start from a cold-start run using restart files or (ideally) cold-start with a manually edited trim-file that would reflect measured salinities.

Thank you,
Kevin