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

Sediment variables in NetCDF history file all 0

Chris Flanary, modified 2 Years ago.

Sediment variables in NetCDF history file all 0

Youngling Posts: 4 Join Date: 10/10/14 Recent Posts


I'm running a FLOW with sediment simulation with a structured grid and have been using the NetCDF history file for comparing hydro model output at observation stations I defined.  When I enable sediment and run the simulation, new sediment variables are created in the history file, but their values are all 0 (specifically, ZRSDEQ, ZBDSED, and ZDPSED).  However, when I look at the R1 and MSED variables in the NetCDF map file, there are values throughout the model domain for the entire model simulation, based on my sediment bed initial conditions and boundary conditions.


Are ZRSDEQ and ZBDSED in the history file and R1 and MSED in the map file equivalent variables, respectively?


My goal is to compare model and measured suspended sediment concentration at my defined observation stations.  Any thoughts as to why this is occurring?