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

Compile Error on SLES 11 with 6075

DS
Dirk Smit, modified 4 Years ago.

Compile Error on SLES 11 with 6075

Youngling Posts: 21 Join Date: 6/18/13 Recent Posts
Hi,

i am currently trying to compile the latest tagged Version on a SuSe Machine, but am running into some errors during make and it fails with the following:
Making install in src
make[5]: Entering directory `/usr/local/src/delft3d_release/6.02.06.6075/src/engines_gpl/part/packages/delpar/src'
mpif77   -DWITH_DELFTONLINE -openmp -O2  -132 -recursive -reentrancy threaded -traceback -c -o main.o main.f
main.f(56): error #5082: Syntax error, found '(' when expecting one of: <END-OF-STATEMENT> ; <IDENTIFIER> <CHAR_CON_KIND_PARAM> <CHAR_NAM_KIND_PARAM> <CHARACTER_CONSTANT> ...
               stop(1)
-------------------^
main.f(73): error #5082: Syntax error, found '(' when expecting one of: <END-OF-STATEMENT> ; <IDENTIFIER> <CHAR_CON_KIND_PARAM> <CHAR_NAM_KIND_PARAM> <CHARACTER_CONSTANT> ...
               stop(1)
-------------------^
main.f(80): error #5082: Syntax error, found '(' when expecting one of: <END-OF-STATEMENT> ; <IDENTIFIER> <CHAR_CON_KIND_PARAM> <CHAR_NAM_KIND_PARAM> <CHARACTER_CONSTANT> ...
            stop(1)
----------------^
main.f(56): error #6052: This label has not been defined as a FORMAT label.   [1]
               stop(1)
--------------------^
main.f(73): error #6052: This label has not been defined as a FORMAT label.   [1]
               stop(1)
--------------------^
main.f(80): error #6052: This label has not been defined as a FORMAT label.   [1]
            stop(1)
-----------------^
main.f(56): error #6323: This label is not defined in this scoping unit.   [1]
               stop(1)
--------------------^
compilation aborted for main.f (code 1)
make[5]: *** [main.o] Error 1
make[5]: Leaving directory `/usr/local/src/delft3d_release/6.02.06.6075/src/engines_gpl/part/packages/delpar/src'




My Setup: SuSE Linux Enterprise Server 11 (x86_84)
Compiler: Intel 11.1
MPI: MPICH 3.2
NETCDF: 4.4.0
NETCDF-Fortran: 4.4.3

Any suggestions where i might search for an error?

Regards,

Dirk
MJ
Michel Jeuken, modified 1 Year ago.

RE: Compile Error on SLES 11 with 6075

Jedi Knight Posts: 156 Join Date: 1/21/13 Recent Posts
<p>Hi Drik, Apparently stop(1) is not allowed in standard Fortran, but our compilers didn&#39;t complain about it. I guess your compiler (or compiler settings) were a bit more strict than ours. In fact the &#39;stop(1)&#39; should actually have been &#39;call stop_exit(1)&#39;. Then it shouldn&#39;t be a problem any more. I&#39;ve committed a fix in revision 6140.</p>