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

FLOW - WAQ integration consuming memory

JC
José Rafael Cavalcanti, modified 3 Months ago.

FLOW - WAQ integration consuming memory

Youngling Posts: 6 Join Date: 10/21/18 Recent Posts

Hello all,

 

I am trying to export a WAQ input file from my FLOW simulations but the process is consuming too much space in my disk. If I save a comm file for further conversion it only takes 1.7 Gb. When I activate the on-line conversion to WAQ my disk memory is almost completely filled with temporary huge files, in addition to the ones I actually need for WAQ. Is it normal?

 

Cheers,

AM
Arjen Markus, modified 3 Months ago.

RE: FLOW - WAQ integration consuming memory

Jedi Knight Posts: 222 Join Date: 1/26/11 Recent Posts

This is rather unusual - I am assuming you are referring to Delft3D-FLOW (not D-Flow FM, its successor). I just tried it myself on an example, but I see no large temporary files appear - only the ones that are to be expected.

Can you tell us the names of these files?