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: 
/web/delft3dfm/forum

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

=======================================================

** PLEASE TAG YOUR POST! **

 

 

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

 


Message Boards

ABOUT NEW GUI AND BINARY FILE STRUCTURE

GA
Germán Aragón, modified 2 Years ago.

ABOUT NEW GUI AND BINARY FILE STRUCTURE

Youngling Posts: 10 Join Date: 6/18/13 Recent Posts

Hello everybody!

I asked for delft3d team for a new licence and now in the server the new GUI is the version 4.04. This version brings a new file structure for lastest trunk versions (I supose) which binaries are collected in a "x64" folder instead of the older "win64". Also I observed that the batch flow to run the examples change and now the executable file in the example folder call to the clasic "run_***.bat" or "run_***.sh" file wich is save in the binaries folder.

With this new structure i don't know wich is the best way to work with different code versions beacouse I think that this new structure is prepared to work with some environmental variables that are create in the OS when the GUI is installed. ¿Could you mind to clarify this process for run from batch file and from GUI?

thank you in advance! Best regards!