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

Error in DELWAQ-PAR settling velocity when using multiple fractions

Ben Williams, modified 3 Years ago.

Error in DELWAQ-PAR settling velocity when using multiple fractions

Jedi Knight Posts: 114 Join Date: 3/23/11 Recent Posts
Hi, I have posted on this topic elsewhere on the forums but got no traction so I am re-posting here.

I have noticed what seems to be a fundamental limitation of the particle tracking model: If one specifies multiple particle fractions in a simulation, each fraction with it's own settling velocity, then DELWAQ-PAR seems to calculate the average (possibly weighted average) value across all fractions and then just use that single value. Obviously this makes quite a difference to the fate of particles.

Does anyone else encounter this problem? It is annoying as one then has to have multiple simulations, one for each particle fraction, instead of simulating all together.

A second question: There are a lot of extra files (such as the 'map' file) generated by DELWAQ-PAR that are not needed to post-process the results. It seems to be an exact copy of the '.dat' file also produced. Thus doubling the amount of space taken up on the hard drive. Is there a way to suppress the generation of particular files?

Best regards,