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

Compiling the trunk - issues and suggestions (Linux)

BH
Bogdan Hlevca, modified 7 Years ago.

Compiling the trunk - issues and suggestions (Linux)

Youngling Posts: 23 Join Date: 3/28/12 Recent Posts
I managed to compile the trunk today. It was not easy, but eventually I had almost complete success and I thought of sharing my experience here so others have an easier time.

I used the first recommended approach:

autogen.sh
./configure   (some defines before configure can be found in the README file)
make ds_install

The other option with build.sh is too buggy.

1) I use gfortran and the openmpi libs are on in the loader path. I added them in the ld.so.conf.d

2) the make file in
./utils_lgpl/nefis/tests/test_20
has a bug. it expects to compile main.c instead of
test_20.c
. The issue can be fixed either by changing the file name to main.c or changing the target to
test_20.c/o


3) in
src/tools_gpl/mormerge/packages/mormerge/src merge.f90
does not compile because some fortran modules are not in the path. The solution is to add the location of 2 modules to the include path in the Makefile. you can find the path to the respective modules by doing a find . -name <name>.mod

4) make ds_install fails at the last step again by trying to install files in the ../bin directory. It fails because it depends on "ruby". Installing ruby fixes (partially) the problem. WHY was ruby necessary to do this when a shell script was enough beats me!! I said partially because the
<name>_sp.so
libraries are not build and the installer silently fails. I don't know if they are supposed to be built, but if they are not to be built they should be removed from the installer


I hope that someone at Deltares sees this and improves things. I don't know if the is an official bug reporting site and I am using this forum as such.

Cheers,
Bogdan
Adri Mourits, modified 7 Years ago.

RE: Compiling the trunk - issues and suggestions (Linux)

Yoda Posts: 1221 Join Date: 1/3/11 Recent Posts
Hi Bogdan,

Thanks for sharing this.

About 2) and 3): You probably used the trunk version. The modifications you mentioned are not needed when using the latest tagged version, currently https://svn.oss.deltares.nl/repos/delft3d/tags/2703/

About 4):
Ruby is available by default on most Linux systems. I added it to the list of prerequisites. Replacement by a shell script will be discussed.

Depending on your settings, OR the double precision version (default) OR the single precision version of Delft3D-FLOW is build. The copying script tries to copy both versions and will always complain that one of them is missing. This message can be neglected. Improving this will be discussed.

Regards,

Adri