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. 




Sub groups
D-Flow Flexible Mesh
Cohesive sediments & muddy systems



Message Boards

Delwaq and FLOW - Constituents not transported through culverts

Edward Divita, modified 7 Years ago.

Delwaq and FLOW - Constituents not transported through culverts

Youngling Posts: 3 Join Date: 10/18/12 Recent Posts
Is there a way to get DELWAQ to track discharges and transport through culverts in a coupled FLOW model?

I have a coupled Flow-DELWAQ model which represents a series of ponds linked together by a system of culverts and open water channels. The preliminary results seem to show that DELWAQ is not allowing constituents to pass through the culverts, while the hydrodynamic model shows quite a lot of discharge passing through these culverts. I have tried a couple different culvert configurations and but best as I can tell the DELWAQ results seem to completely ignore all flows through the culvert structures.

Am I doing something wrong or is DELWAQ simply unable to track flows through culverts modeled in FLOW?

I am running a 2D model with online coupling and I am not using grid aggregation.
Stephanie Zeunert, modified 6 Years ago.

RE: Delwaq and FLOW - Constituents not transported through culverts

Youngling Posts: 14 Join Date: 6/2/14 Recent Posts

I'm currently trying to couple my FLOW results with DELWAQ. I've got the same problem as Edward. DELWAQ seems unable to simulate the transport of substances through a culvert. Is this not implemented for DELWAQ or do I have to change any configurations? I couldn't find anything regarding this topic in the manuals.

Kind regards
Arjen Markus, modified 6 Years ago.

RE: Delwaq and FLOW - Constituents not transported through culverts

Jedi Knight Posts: 223 Join Date: 1/26/11 Recent Posts

the problem is that the two parts of a culvert need to be linked up explicitly, as this information is not transferred automatically from Delft3D-FLOW to Delft3D-WAQ. The current method works as follows:

Assign the name "INLET1" to one part of the culvert and the name "OUTLET1" to the other part. Similarly, INLET2/OUTLET2 for the second culvert and so on. That way Delft3D-WAQ can take out the mass associated with the flow on one side and release it on the other side.

Warning: this mechanism is usually used for coupling inlets to outlets, so the transport is unidirectional. I checked the source code: there is an implicit assumption that the flow is indeed from the inlet to the outlet. For a culvert this may change over time of course, so you probably need to define a similar pair the other way around, that is: for each culvert define an outlet on the location of the inlet and vice versa.

(Culverts are sufficiently rare in our projects that we have simply never gotten around to implementing a more appropriate solution.)

The alternative - which is much better in the longer run - is to define a waste load module that explicitly takes care of this type of waste loads. Not all that hard to do ;). And actually this has been the sort of things why we introduced the waste load module in the first place.