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 Delft3d on OS X Yosemite successful but...

YK
Yitping Kok, modified 2 Years ago.

Compiling Delft3d on OS X Yosemite successful but...

Youngling Posts: 2 Join Date: 11/6/17 Recent Posts
Hi all,

I followed this post and managed to successfully compile Delft3d on my OS X Yosemite (10.10.5) using necessary libraries I installed from MacPorts.

But when I test run the examples I have some runtime errors associated with date and time.

For example, when I run an example in example/01_standard (after modifying the paths in run_flow2d3d.sh), I got the following:

--------------------------------------------------------------------------------
Deltares, FLOW2D3D Version 6.02.13.7803, Nov 14 2017, 23:11:10
libflow2d3d.so entry Flow2D3D::Run
--------------------------------------------------------------------------------

Part I - Initialisation Time Dep. Data module...
runid : f34
At line 92 of file vermdf.f90
Fortran runtime error: Bad value during integer read


The run generated 2 files before terminating,
td-diag.f34 and
f34.url.

The date and time in td-diag.f34 was bad (has unprintable ^@ characters, see below).

********************************************************************************
***
*** Deltares, FLOW2D3D Version 6.02.13.7803, Nov 14 2017, 23:11:10
*** built from : https://svn.oss.deltares.nl/repos/delft3d/tags/7545
***
*** runid : f34
*** date,time : 2017-1^@-^@1,^@^@^@:21:07
***
********************************************************************************


I suspect this has to do with some differences in c/c++ time structures between Linux and OS X.
This is not surprising when I look again in the config.log file. In OS X, the -lrt library is not available and hence produced an error in the configuration stage.

Here's a snippet from my config.log.
configure:25486: checking for clock_gettime in -lrt
configure:25519: gcc-mp-7 -o conftest -O2 -I/opt/local/include -L/opt/local/li
ld: library not found for -lrt
collect2: error: ld returned 1 exit status


Can someone point me to some suspected parts of the code where this can be fixed?

Thanks very much for your attention and help.

Yitping