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

Reducing Coupled FLOW/WAVE Model Output File Size

John McDowell, modified 3 Months ago.

Reducing Coupled FLOW/WAVE Model Output File Size

Youngling Posts: 13 Join Date: 9/6/17 Recent Posts
Hello all,

I've successfully run a coupled FLOW/WAVE model for a large area. The results look very good but the output files are huge (GBs large).

In terms of outputs, I'm only interested in Depth, Flow Velocity, Significant Wave Height (Hs) and Peak Period (Tp). For the FLOW module, it is possible to reduce the amount of outputs in the map files by setting the following designations:

SMhydr= #YYYYY#
SMproc= ## 
SMderv= ## 

This just ouputs the water level, U- and V-velocities and W-velocities, and reduces the size of the FLOW output files by at least 30%.

However, the WAVE output files are still very large. Does anyone know of the input line designation to store only some of the variables?

Also, as a side note, alongside the WAVE map and history files, a "" file is also created. What is the purpose of this file? It is larger than all of my FLOW and WAVE outputs combined - why is it so large? And if it is not essential, can its generation be suppressed?

Thank you all very much for your help.

Best regards,