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

My associate statically doled out an unused IP address to a test worker on

Antidi MG, modified 3 Months ago.

My associate statically doled out an unused IP address to a test worker on

Youngling Posts: 1 Join Date: 8/8/20 Recent Posts
. We could ping and ssh into the case with no issues, anyway in the course of recent days we have been encountering an IP struggle where ssh and pings to the tinychat worker have brought about reactions from two gadgets (one being the test worker, and the other being an obscure gadget on the system). The system and the test worker have both been up since the IP was statically allotted. I was instructed that DHCP doesn't dole out IP tends to that are presently being utilized, regardless of whether the IP address is static. I can't help thinking that another gadget on the system was allotted this IP address, and coincidentally was disconnected, bringing about the IP address seeming, by all accounts, to be unused. Am I missing something?