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

Nesting FLOW/WAVE with Dashboard - WAVE boundary information missing?

JK
James Kaihatu, modified 10 Months ago.

Nesting FLOW/WAVE with Dashboard - WAVE boundary information missing?

Youngling Posts: 3 Join Date: 8/8/19 Recent Posts
I am nesting a coarser FLOW/WAVE grid into a finer one. I'm using Dashboard for the nesting. When I run the finer model, the wave information at the boundary provided by the coarser model does not seem to make it into the finer model. The model does not crash, but there is little-to-no wave energy inside the finer nest. I am running a hurricane simulation, so the waves should be a good size. The history file of the coarser model (along the nested boundary, and which is used for the nest information for the finer model) does capture this energy, and that should be the input condition for WAVE for the finer model. The surge and currents are passed through to the finer model, and the .mdw file does have "use but don't extend" enacted. Any thoughts? All runs are using nonstationary mode.
JK
James Kaihatu, modified 10 Months ago.

RE: Nesting FLOW/WAVE with Dashboard - WAVE boundary information missing?

Youngling Posts: 3 Join Date: 8/8/19 Recent Posts
Let's try this question:
Is there a limit on the number of boundary points for nesting that DelftDashboard is able to write?