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

D3D-WAVE: Multiple segment boundaries cause runtime segmentation fault

Ruairi MacIver, modified 5 Years ago.

D3D-WAVE: Multiple segment boundaries cause runtime segmentation fault

Padawan Posts: 45 Join Date: 5/1/13 Recent Posts
Running Delft3D-WAVE in standalone mode on an Ubuntu 12.04 platform. The model domain is rectangular (see PFOW_Domain.pdf) with a rectilinear grid consisting of 145 by 122 (m by n) nodes.
I am attempting to specify spatially varying boundary conditions on three named boundaries defined by m,n grid coordinates:
  • NW - running from the land-sea junction on the west boundary [e.g. node (1,39)] to part way along north boundary [e.g. node (51,122)]
  • NE - running from part way along north boundary [e.g. node (51,122)] to part way along east boundary [e.g. node (145,177)]
  • SE - running from part way along east boundary [e.g. node (145,177)] to the land-sea junction on the south boundary [e.g. node (57,1)]

Each named boundary consists of three or four segments on which time varying wave conditions are specified via TPAR files.

The execution fails with the following error message "forrtl: severe (174): SIGSEGV, segmentation fault occurred" [see *.scn for context]. I understand a common cause of this error is exceeding the stacksize limit. However the error still occurs after forcing unlimited stacksize using the command line "ulimit -s unlimited".

Interestingly the error doesn't occur when just one boundary (e.g. NW) is defined. It occurs when two or more boundaries are defined.

[Aside: The model executes successfully using four named boundaries defined by orientation (west, north, east & south) with spatially-varying conditions specified via the same TPAR files.]

Can anyone provide any insights?

Cheers,
Ruairi