intro story Coast / Estuary

Coast / Estuary

Coastal systems are among the most dynamic physical systems on earth and are subject to a large variety of forces. The morphodynamic changes occurring to coastlines worldwide are of great interest and importance. These changes occur as a result of the erosion of sediments, its subsequent transport as bed load or suspended load, and eventual deposition. 
 
Estuaries are partly enclosed water bodies that have an open connection to the coast. Estuaries generally have one or more branching channels, intertidal mudflats and/or salt marshes. Intertidal areas are of high ecological importance and trap sediments (sands, silts, clays and organic matter).
Within the Delft3D modelling package a large variation of coastal and estuarine physical and chemical processes can be simulated. These include waves, tidal propagation, wind- or wave-induced water level setup, flow induced by salinity or temperature gradients, sand and mud transport, water quality and changing bathymetry (morphology). Delft3D can also be used operationally e.g. storm, surge and algal bloom forecasting. 
 
On this discussion page you can post questions, research discussions or just share your experience about modelling coastal and/or estuarine systems with Delft3D FM. 
 

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ
Cohesive sediments & muddy systems

 

 

Message Boards

Compiling using Win10, VS2017 Enterprise + .NET Framework 4.7 and IFORT18

BO
Bernardo Oliveira, modified 2 Years ago.

Compiling using Win10, VS2017 Enterprise + .NET Framework 4.7 and IFORT18

Youngling Posts: 4 Join Date: 12/7/16 Recent Posts

Dear All,

 

I am trying to compile the latest trunk version of DELFT 3D (8712) using the following requisites:

- Microsoft Visual Studio 2015 Enterprise (Update 3)

- Intel Parallel Studio XE 2018 (Update 2)

- Microsoft .NET Framework 4.7.02556

- Python 2.7 and 3.6

 

I successfully generated the solutions using prepare_sln.py using the configuartion above. I have added the modules below in VS2015:

- "Common Tools for Visual C++ 2015"
- "Microsoft Foundation Classes for C++"

 

Then, I have opened the delft3d_open solution and started to compiled, which process went well until I got the following message:

86>------ Skipped Build: Project: flow2d3d_openda, Configuration: Release x64 ------
86>Project not selected to build for this solution configuration 

 

And then the build process didn't go any further. I have stopped the compilation and killed VS2015 through Task Manager.

 

I have installed the VS2017 Enterprise with all C, C++ and Fortran modules and downloaded the source code again from trunk version. I have followed the same process to generate the solution and opened it in VS2017, but the build process freezes at the same message. Then I killed VS 2017 through Task Manager.

 

The curious thing about this is that I am running all the examples, but I am not sure if not compiling flow2d3d_openda will change the binaries generated.

 

I have uninstalled and reinstalled the programs and tried again, but I am struggling at the same point. Please find attached the Output file.

 

Please could you give me a hand on this thread?

 

Many thanks in advance,

 

Bernardo Oliveira

KS
Kostia Shiian, modified 2 Years ago.

RE: Compiling using Win10, VS2017 Enterprise + .NET Framework 4.7 and IFORT

Youngling Posts: 3 Join Date: 5/3/18 Recent Posts

It seems that the problem is with flex.exe and byacc.exe. You can easily check this by runinng one of this file. This causes high CPU consuming and memory leak.

Adri Mourits, modified 2 Years ago.

RE: Compiling using Win10, VS2017 Enterprise + .NET Framework 4.7 and IFORT

Yoda Posts: 1212 Join Date: 1/3/11 Recent Posts

Hi Bernardo,

Kostia is right: flow2d3d_openda finished normally (it should indeed not be used), but another build step is hanging: the compilation of the tool "vs". You can see this in your file "Output-Build.txt"; the las line refers to build step number 29.

Fortunately, you probably will not need the tool "vs". So you can skip it.

Scanning your file "Output-Build.txt", I do see some messages that I don't expect, but they don't seem blocking. If the examples run fine, you can continue.

Regards,

Adri