intro story D-Flow FM


D-Flow Flexible Mesh

D-Flow Flexible Mesh (D-Flow FM) is the new software engine for hydrodynamical simulations on unstructured grids in 1D-2D-3D. Together with the familiar curvilinear meshes from Delft3D 4, the unstructured grid can consist of triangles, pentagons (etc.) and 1D channel networks, all in one single mesh. It combines proven technology from the hydrodynamic engines of Delft3D 4 and SOBEK 2 and adds flexible administration, resulting in:

  • Easier 1D-2D-3D model coupling, intuitive setup of boundary conditions and meteorological forcings (amongst others).
  • More flexible 2D gridding in delta regions, river junctions, harbours, intertidal flats and more.
  • High performance by smart use of multicore architectures, and grid computing clusters.
An overview of the current developments can be found here.
The D-Flow FM - team would be delighted if you would participate in discussions on the generation of meshes, the specification of boundary conditions, the running of computations, and all kinds of other relevant topics. Feel free to share your smart questions and/or brilliant solutions! 


We have launched a new website (still under construction so expect continuous improvements) and a new forum dedicated to Delft3D Flexible Mesh.

Please follow this link to the new forum: 

Post your questions, issues, suggestions, difficulties related to our Delft3D Flexible Mesh Suite on the new forum.





Sub groups
D-Flow Flexible Mesh
Cohesive sediments & muddy systems


Message Boards

Delft3D-WAVE: Wind forcing quirks

Ruairi MacIver, modified 5 Years ago.

Delft3D-WAVE: Wind forcing quirks

Padawan Posts: 45 Join Date: 5/1/13 Recent Posts
I have it on good authority that specifying a MeteoFile keyword in the .mdw file, in either the [General] section or [Domain] section, results in the WindSpeed keyword data specified in the [General] section being superseded by the wind data provided by the MeteoFile keyword file.

Deleting (or otherwise omitting) the WindSpeed keyword or leaving it set to zero can result in wind-forcing not being implemented. This is particularly the case if the .mdw file is re-edited in the GUI as a missing or zero WindSpeed keyword results in the wind forcing & quadruplet interaction keywords being set to false when opening the .mdw file.

So if you are going to use MeteoFiles, it seems sensible to specify a (small) non-zero WindSpeed keyword value.

The back-story to this post can be found at this post

Hope this helps someone.