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

flow2d-3d: libexpat.dll missing. VS2017 Community + Ifort 18 Windows 10

Dennis de Ruiter, modified 2 Years ago.

flow2d-3d: libexpat.dll missing. VS2017 Community + Ifort 18 Windows 10

Youngling Posts: 1 Join Date: 5/31/18 Recent Posts

Hello all,


I am trying to compile Delft3D from trunk 7545 as recommended. I am using VS2017 Community edition with Ifort 2018, on Windows 10. With the help of David Gutiérrez's excellent post in this thread: https://oss.deltares.nl/web/delft3d/home/-/message_boards/message/1439326/maximized in where he outlays all steps for this combination I have managed to compile a somewhat working version. Somewhat working as in, examples which do not use flow2d-3d work (like example 7 to 11), but those which use flow2d-3d present the following error:



Checking the bin folder of the module it indeed seems the .dll file is nowhere to be found.



Now during compilation, at the end the whole process freezes and my computer runs out of memory. This seems to be a known issue with an outdated/deprecated module being compiled which is not nessecary for the end result I understood reading on the forums. The fact that the other examples work seems that there are some things going good, but something earlier is getting messed up in the compilation it seems.

What can be potential causes, and I think more importantly, what can I do to be able to find what is going wrong here so I can hopefully be guided towards a fully instead of half working compilation? I must admit that I am not particulary experienced in compiling programmes though now I have come this far I am adament to finish it.

Further information for completeness sake:

CPU: Core i7 5820k @ 4.2 ghz

Memory: 16GB

GPU: GTX 950

Windows 10 build 1803


EDIT 26-06:

I actually just found the .dll in C:\delft3d_repository\bin\win64\shared. Yet delft3d is unable to find it for some reason. I also saw Adri mention in a thread about this .dll being missing to try debug compilation. I REbuilt the solution in debug and unfortunally nothing changed. Wave module and such works, but flow is unable to run because it cannot find the .dll for some reason.

Many thanks in advance,




Adri Mourits, modified 2 Years ago.

RE: flow2d-3d: libexpat.dll missing. VS2017 Community + Ifort 18 Windows 10

Yoda Posts: 1212 Join Date: 1/3/11 Recent Posts

Hi Dennis,

The ad hoc workaround:
Open file "examples\01_standard\run_flow2d3d.bat" in a text editor and replace the line:
set PATH=%exedir%;%PATH%
set PATH=%exedir%;%D3D_HOME%\%ARCH%\shared;%PATH%

An alternative is to copy the contents of subdirectory "shared" into the "flow2d3d\bin" directory.

This problem will not occur in the current trunk version, because the run scripts are changed.