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

Errors at first step of Linux compilation

GJ
Geoff Johnson, modified 4 Years ago.

Errors at first step of Linux compilation

Youngling Posts: 4 Join Date: 2/26/16 Recent Posts
I've tried both 1.a and 1.b of the section "Compiling on Linux" that are given in src/README and both fail at the aclocal step because of the error:

configure.ac:104: error: AC_LANG_FUNC_LINK_TRY: unknown language: Fortran


This page suggests that it's an error in autoconf.

What distribution and release should I be trying to install the open source FLOW on? RHEL 6 doesn't appear to work, and neither does Fedora 21/22/23. Before I go launching into installing various versions of Debian and Ubuntu it would be nice to know where I'm most likely to succeed.

Thanks
Adri Mourits, modified 4 Years ago.

RE: Errors at first step of Linux compilation (Answer)

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

Most commonly the Fortran compiler that you installed on your machine can not be found. If you have a look at the "src/build.sh" script, at "Initialize Fortran compiler", you will see examples to get this done. The exact statement to use depends on where you have put the Fortran compiler on your machine.

Regards,

Adri
GJ
Geoff Johnson, modified 4 Years ago.

RE: Errors at first step of Linux compilation

Youngling Posts: 4 Join Date: 2/26/16 Recent Posts
The error is generated from aclocal, it's not even making it to a build step so I can't see how that would help. I'm not unfamiliar with compiling software using autotools and this error comes out before any CFLAGS or LIBS sections would ever be touched by a Makefile, this is most likely an issue with what's in configure.ac and the version of the autotools packages that I have on my system. I presume though that someone has gotten this to work before, hence the question, what distribution is best to use for compiling this software on?
Adri Mourits, modified 4 Years ago.

RE: Errors at first step of Linux compilation (Answer)

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

We compile on CentOS 6.6.
You can check version numbers of related tools on this page.

Regards,

Adri
GJ
Geoff Johnson, modified 4 Years ago.

RE: Errors at first step of Linux compilation (Answer)

Youngling Posts: 4 Join Date: 2/26/16 Recent Posts
I'd seen that list of prereqs before but convinced myself that I had autoconf 2.65 and not 2.63. Building automake/autoconf/libtool from source got me passed my issue. Thanks for the reminder to RTFM.