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

FLOW - WAQ integration consuming memory

JC
José Rafael Cavalcanti, modified 3 Months ago.

FLOW - WAQ integration consuming memory

Youngling Posts: 6 Join Date: 10/21/18 Recent Posts

Hello all,

 

I am trying to export a WAQ input file from my FLOW simulations but the process is consuming too much space in my disk. If I save a comm file for further conversion it only takes 1.7 Gb. When I activate the on-line conversion to WAQ my disk memory is almost completely filled with temporary huge files, in addition to the ones I actually need for WAQ. Is it normal?

 

Cheers,

AM
Arjen Markus, modified 3 Months ago.

RE: FLOW - WAQ integration consuming memory

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

This is rather unusual - I am assuming you are referring to Delft3D-FLOW (not D-Flow FM, its successor). I just tried it myself on an example, but I see no large temporary files appear - only the ones that are to be expected.

Can you tell us the names of these files?