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

Compilation on Windows: general remarks

Adri Mourits, modified 5 Years ago.

Compilation on Windows: general remarks

Yoda Posts: 1224 Join Date: 1/3/11 Recent Posts
Hi All,

Read file "src/README" in the source code.
See also the description here.
See also the FAQ.

Compiling with Microsoft Visual Studio and Intel Fortran compiler
IFORT_COMPILERxx references in project files.
Some main programs are written in C and use Fortran libraries. During linking, it is necessary that the path to the Intel libraries is included. The environment parameter IFORT_COMPILERxx is used to obtain this path. Unfortunately the exact name of this parameter depends on the Intel version being used (IFORT_COMPILER11, IFORT_COMPILER12, etc.).
- VS2008 with Intel11: "d_hydro_open_source.sln" is ready to be used.
- VS2010 with Intel12: "d_hydro_open_source_vs2010.sln" is ready to be used.
- VS2010 with Intel13: "d_hydro_open_source_vs2010_intel13.sln" is ready to be used. This configuration is not our default configuration and is not tested.
- VS201x with Intel12: "d_hydro_open_source_vs2010.sln" is ready to be used. VisualStudio will update the sln file automatically.
- VS201x with Intel13: "d_hydro_open_source_vs2010_intel13.sln" is ready to be used. VisualStudio will update the sln file automatically. This configuration is not our default configuration and is not tested.
- VS201x with Intel14, Intel15, ...:
Use "d_hydro_open_source_vs2010.sln". VisualStudio will update the sln file automatically. First open the project files listed below in a text editor and replace all occurrences of IFORT_COMPILER12 by the appropriate version:
- engines_gpl\flow2d3d\packages\flow2d3d\flow2d3d.vcxproj
- engines_gpl\flow2d3d\packages\flow2d3d_openda\flow2d3d_openda.vcxproj
- engines_gpl\part\packages\delpar\delpar.vfproj
- engines_gpl\waq\packages\delwaq1\delwaq1.vfproj
- engines_gpl\waq\packages\delwaq2\delwaq2.vfproj
- engines_gpl\waq\packages\delwaq2_openda_lib\delwaq2_openda_lib.vfproj
- engines_gpl\wave\packages\wave\wave_vs2010.vfproj
- tools_gpl\datsel\packages\datsel\datsel.vcxproj
- tools_gpl\kubint\packages\kubint\kubint.vcxproj
- tools_gpl\lint\packages\lint\lint.vcxproj
This IFORT_COMPILER issue is having our attention. Suggestions for proper solutions are welcome.

NetCDF
NetCDF usage is recently added. The related libraries must be compiled with exactly the same compiler as used for compiling Delft3D.
In directory "c:\code\oss\src\third_party_open\netcdf\lib\win32", NetCDF libraries are available compiled with:
- Intel10 (32bit)
- Intel12 (32bit)
- Intel13 (32bit)
- Intel14 (32bit)
- Intel13 (64bit)
- Intel14 (64bit)
If you need NetCDF being compiled with another compiler version, you have to take care of that yourself.
If you encounter problems related to compiling with NetCDF, check (and correct to the proper version) the references to the netcdf directory in the following project files:
- engines_gpl\flow2d3d\packages\data\data.vfproj
- engines_gpl\flow2d3d\packages\flow2d3d\flow2d3d.vcxproj
- engines_gpl\flow2d3d\packages\flow2d3d_openda\flow2d3d_openda.vcxproj
- engines_gpl\flow2d3d\packages\io\io.vfproj
This NetCDF reference issue is having our attention. The directory structure may change in the near future.

Regards,

Adri
Adri Mourits, modified 4 Years ago.

RE: Compilation on Windows: general remarks

Yoda Posts: 1224 Join Date: 1/3/11 Recent Posts
Hi All,

The following tagged version should make life easier: https://svn.oss.deltares.nl/repos/delft3d/tags/5389/
You will need Python to execute a script that prepares a sln file that fits to the tools you use. See "src/README" and this page.

Regards,

Adri