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

z-layer initial condition specification (Delft3D 4.02.03)

Kevin Hanegan, modified 1 Year ago.

z-layer initial condition specification (Delft3D 4.02.03)

Youngling Posts: 6 Join Date: 7/2/11 Recent Posts
Hi,
Are any non-uniform initial condition specification options available for z-layer models? The manual pg. 43 states that using .ini files is not yet available for the Z-model, but can restart or map files be used instead?

Here is some more information on my problem for your information. I'm simulating a large estuary with salinities ranging from 0 to 35 psu. Spinup from uniform conditions would take multiple weeks of runtime to achieve a realistic salinity gradient, so I would like to be able to initialize with spatially-varying salinities derived from measurements. Developing the .ini file using quickin and OET was fairly straightforward, though I'm realizing now that this method will never work. Hoping that I can hot-start from a cold-start run using restart files or (ideally) cold-start with a manually edited trim-file that would reflect measured salinities.

Thank you,
Kevin