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

Problems compiling on Windows 7, x64

André Pacheco, modified 8 Years ago.

Problems compiling on Windows 7, x64

Youngling Posts: 2 Join Date: 7/18/12 Recent Posts
Dear all,

I am having problems compiling the code and I will very greatfull of your help.
I first succefully downloaded the source code using tartoise.
I then installed the Visual Basic 2010 and the Intel Composer 2013 XF 2013, whic has the Foltran Libraries.

I then proceeded as the webinar given by Mourits from February 2012.
First I get a lot of Message erros when opening MV2010, and only have 30 projects in mine Solution explorer, when I compile I get:

30>LINK : fatal error LNK1181: cannot open input file 'lib\Release\flow2d3d_openda_lib.lib'
========== Build: 24 succeeded, 6 failed, 0 up-to-date, 0 skipped ==========

Any ideas?
Thanks in advance

André
André Pacheco, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Youngling Posts: 2 Join Date: 7/18/12 Recent Posts
Problem solved!
HJ
Hoonshin Jung, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Youngling Posts: 2 Join Date: 9/14/12 Recent Posts
Hey!

I tried to compile version 5.00.00.1234 with Windows 7, VS 2010 and Intel Visual Fortran 2013, x64, and got more than 54 errors (non-built).

1) Could you please let me know how you were able to fix the problem and compile the code.

2) Which Delft3D version(s) were you able to compile?

Thanks a lot in advance for the help.

Kind Regards,

Hoon
Adri Mourits, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

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

Currently, on Windows only the 32-bit version of Delft3D works fine. You can use a 64-bit machine and operating system, but the compilers (C and Fortran) must be 32-bit compilers.

The best version to start with is the latest tagged version, currently version 5.00.08.1855.

Regards,

Adri
HJ
Hoonshin Jung, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Youngling Posts: 2 Join Date: 9/14/12 Recent Posts
Thanks for your reply
EA
Ed Atkin, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Padawan Posts: 27 Join Date: 3/27/12 Recent Posts
Hi André,

Like you I am trying to compile with VS2010 and Intel Composer 2013. (XE not XF). I am still getting errors.

I was wondering if you could pass on some tips about the process you went through, perhaps the settings you changed?

Thanks Ed
Adri Mourits, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Yoda Posts: 1221 Join Date: 1/3/11 Recent Posts
Hi Ed and Andre,

These errors are probably caused by a hard coded reference to Intel Fortran 12 version while you are using Intel Fortran 13. We are working on a generic solution for this.

For you, the easiest way to solve this is the following quick and dirty solution:

Open the 6 files listed below in a text editor
Replace all occurences (22 in total) of "IFORT_COMPILER12" with "IFORT_COMPILER13"
The 6 files are:
1) engines_gpl\flow2d3d\packages\flow2d3d\flow2d3d.vcxproj
2) engines_gpl\flow2d3d\packages\flow2d3d_openda\flow2d3d_openda.vcxproj
3) engines_gpl\wave\packages\wave\wave_vs2010.vfproj
4) tools_gpl\datsel\packages\datsel\datsel.vcxproj
5) tools_gpl\kubint\packages\kubint\kubint.vcxproj
6) tools_gpl\lint\packages\lint\lint.vcxproj

Regards,

Adri
Adri Mourits, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

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

I added "d_hydro_open_source_vs2010_intel13.sln" to the trunk (revision 1930). But I cannot test it. Can you test it and give some feedback?

Thanks,

Adri
EA
Ed Atkin, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Padawan Posts: 27 Join Date: 3/27/12 Recent Posts
Hi Adri,

Build went with:

0 Errors, 407 Warnings, 67 Messages.

See list of warnings attached. Couldnt find an actual log of the build

The messages are all the same:

"remark #8291: Recommended relationship between field width 'W' and the number of fractional digits 'D' in this edit descriptor is 'W>=D+7'."

But referecned to different files.

All test cases ran without error


FYI
The previous method worked as well:

Open the 6 files listed below in a text editor
Replace all occurences (22 in total) of "IFORT_COMPILER12" with "IFORT_COMPILER13"
The 6 files are:
1) engines_gpl\flow2d3d\packages\flow2d3d\flow2d3d.vcxproj
2) engines_gpl\flow2d3d\packages\flow2d3d_openda\flow2d3d_openda.vcxproj
3) engines_gpl\wave\packages\wave\wave_vs2010.vfproj
4) tools_gpl\datsel\packages\datsel\datsel.vcxproj
5) tools_gpl\kubint\packages\kubint\kubint.vcxproj
6) tools_gpl\lint\packages\lint\lint.vcxproj

Again, 0 Errors, but 409 Warnings and 67 Messages.

However, "System cannot find the path specified" when running the batch examples.

Cheers

Attachments:

Adri Mourits, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

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

Thanks for testing.

About these warnings: yes, we have some work to do.

But at least you can now run simulations.

If you want the "System cannot find the path specified" problem to be solved, can you copy/paste the full contents of the output window in VisualStudio when compiling and post it here?

Thanks.

Regards,

Adri
EA
Ed Atkin, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Padawan Posts: 27 Join Date: 3/27/12 Recent Posts
Adri, see output below.

If I can continue to help to remove the warnings for the Intel Fortran 13 solution then let me know.

Regards

Ed

Attachments:

Adri Mourits, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

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

That looks fine. All freshly built binaries and needed dlls are copied to "D:\deflt_repo\tags\5.00.08.1855\bin\win32\flow2d3d\bin" and "D:\deflt_repo\tags\5.00.08.1855\bin\win32\flow2d3d\lib".

Assuming that your examples are in directory "D:\deflt_repo\tags\5.00.08.1855\examples", I don't understand why you get the error "System cannot find the path specified". Can you double check that script "D:\deflt_repo\tags\5.00.08.1855\examples\01_standard\run_flow2d3d.bat" is not changed and that the two directories mentioned above contain "deltares_hydro.exe", "d_hydro.exe" and "flow2d3d.dll"?

Must be somthing stupid.

Regards,

Adri
EA
Ed Atkin, modified 8 Years ago.

RE: Problems compiling on Windows 7, x64

Padawan Posts: 27 Join Date: 3/27/12 Recent Posts
Adri,

I just tried running the examples again and all went well.
I have know idea what the issue could have been.

Regards

Ed