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

Pair programming

priya impex, modified 1 Month ago.

Pair programming

Jedi Master Posts: 274 Join Date: 10/15/20 Recent Posts
Pair programmingPair programming is a strong tool kit in extreme programming’s tool box.  Two programmers works on same workstation one wearing a driver’s hat and the other one wearing an observer’s hat, exchange  their roles at frequent intervals of time that they agree upon, steer the program to its conclusion. The dual perspective on same problem is at the core of this technique. Tough there are two brains working on same problem, they should have a conscientious to collaborate and not to compete. While the implementation is on its way, the same is being reviewed as its being written. So it saves a big time on future defects and code review requirements while engaging two people on same task.
It’s important to have some house rules for any such collaboration happening to achieve a task to its done state. Team work is as challenging as much its efficient. Still there’s no need of a handbook for these rules. It’s the best practices that learned during the journey. We inspect and adapt, we discard few rules as we feel them redundant or destructive for our goals and form new ones to make our pair programming more fruitful.To list an example of such rule, we sometimes get carried away in the midst of the task that we start feeling possessive to hand over the precious piece of code that we are coding, to the pairing person. This slowly sweeps in the division of the module that we are coding. This obviously kills the very purpose of pair programming. We do have time bounding to make the perspective neutral. Switching may at first seem inefficient but would reaps on as it continues. <!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}-->Devops Online Training