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

flow2d-3d: libexpat.dll missing. VS2017 Community + Ifort 18 Windows 10

DR
Dennis de Ruiter, modified 2 Years ago.

flow2d-3d: libexpat.dll missing. VS2017 Community + Ifort 18 Windows 10

Youngling Posts: 1 Join Date: 5/31/18 Recent Posts

Hello all,

 

I am trying to compile Delft3D from trunk 7545 as recommended. I am using VS2017 Community edition with Ifort 2018, on Windows 10. With the help of David Gutiérrez's excellent post in this thread: https://oss.deltares.nl/web/delft3d/home/-/message_boards/message/1439326/maximized in where he outlays all steps for this combination I have managed to compile a somewhat working version. Somewhat working as in, examples which do not use flow2d-3d work (like example 7 to 11), but those which use flow2d-3d present the following error:

 

 

Checking the bin folder of the module it indeed seems the .dll file is nowhere to be found.

 

 

Now during compilation, at the end the whole process freezes and my computer runs out of memory. This seems to be a known issue with an outdated/deprecated module being compiled which is not nessecary for the end result I understood reading on the forums. The fact that the other examples work seems that there are some things going good, but something earlier is getting messed up in the compilation it seems.

What can be potential causes, and I think more importantly, what can I do to be able to find what is going wrong here so I can hopefully be guided towards a fully instead of half working compilation? I must admit that I am not particulary experienced in compiling programmes though now I have come this far I am adament to finish it.

Further information for completeness sake:

CPU: Core i7 5820k @ 4.2 ghz

Memory: 16GB

GPU: GTX 950

Windows 10 build 1803

 

EDIT 26-06:

I actually just found the .dll in C:\delft3d_repository\bin\win64\shared. Yet delft3d is unable to find it for some reason. I also saw Adri mention in a thread about this .dll being missing to try debug compilation. I REbuilt the solution in debug and unfortunally nothing changed. Wave module and such works, but flow is unable to run because it cannot find the .dll for some reason.

Many thanks in advance,

Dennis

 

 

Adri Mourits, modified 2 Years ago.

RE: flow2d-3d: libexpat.dll missing. VS2017 Community + Ifort 18 Windows 10

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

Hi Dennis,

The ad hoc workaround:
Open file "examples\01_standard\run_flow2d3d.bat" in a text editor and replace the line:
set PATH=%exedir%;%PATH%
by:
set PATH=%exedir%;%D3D_HOME%\%ARCH%\shared;%PATH%

An alternative is to copy the contents of subdirectory "shared" into the "flow2d3d\bin" directory.

This problem will not occur in the current trunk version, because the run scripts are changed.

Regards,

Adri