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

bloominp.blm growing to 400 GB in Size!!!

Daniel Harrison, modified 3 Years ago.

bloominp.blm growing to 400 GB in Size!!!

Youngling Posts: 4 Join Date: 1/11/16 Recent Posts
Hi There,

I have a problem when I run a water quality simulation with DWAQ the file bloominp.blm grows in size to be almost 400 GB in size at the completion of the 1 year simulation I am running. This is in contrast to for example the map output file which output at 6 hourly intervals only reaches 2 GB for the entire run.

While this does not seem to preclude a 'normal completion' it is causing me HDD space issues as well as I/O failures if I try to run more than 1 simulation concurrently.

It seems that bloominp.blm is perhaps having the full grid written to it (in binary) every computation timestep. If this is the case is there any way to prevent this behavior?

See attached head of file, the remainder is more 'binary type' characters.

Kind Regards,

Dr Daniel Harrison
University of Sydney
Michel Jeuken, modified 3 Years ago.

RE: bloominp.blm growing to 400 GB in Size!!!

Jedi Knight Posts: 156 Join Date: 1/21/13 Recent Posts
Hi Daniel,

I'm sorry, that was a very nasty bug in the BLOOM section of the code. Accidentally the writing of debug information was always switch on. I hope it didn't cause too much trouble.

It has been in the code between revision 6008 and 6150, and was removed with revision 6151 and is caused by changes in /trunk/src/engines_gpl/waq/packages/waq_kernel/src/bloom/bloutc.f. Please use a version of the full code/this file outside this range of revisions.