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

 

 

Back

RE: hung up flow-wave simulation

SC
Susan Clark, modified 6 Years ago.

hung up flow-wave simulation

Youngling Posts: 7 Join Date: 1/6/12 Recent Posts
Back again with a new problem...

I'm trying to run my own coupled wave-flow simulation on a Linux cluster. My pre-processing is all done on the GUI for windows, and I move these files onto the cluster (which has a remote login) where I run the simulations. The examples on the cluster work fine, and I have been able to run a standalone Flow simulation.

I have not been able to complete the flow-wave online simulation, however. The simulation hangs after the following lines:

Part VIII - Start Simulation...

Time to finish 0s, 0.0% completed, time steps left 4464


There is no error in the tri-diag file, and a swn-diag file is not written. In comparing the .mdw files for the 03_flow-wave example and my simulation, I found that they look completely different. Furthermore, the example files also include the now obsolete .mdm file. Is it possible that the wave GUI is producing the wrong format .mdw file? The Delft GUI is version 4.00.01 and the Linux version on the cluster is 4.00.07.

Any other ideas as to why my simulation is getting hung up are also welcome.
Qinghua Ye, modified 6 Years ago.

RE: hung up flow-wave simulation

Jedi Council Member Posts: 612 Join Date: 3/2/11 Recent Posts
Hi Susan,

There are two versions of the mdw files. From the new GUI, you will get a keyword-based version. In the example 03, it is a free version. Both of them should work. You can try to open the example 03 and save it. A keyword-based version should be prepared then. Compare this version with your own version and see what happened.

Regards,

Qinghua
SC
Susan Clark, modified 6 Years ago.

RE: hung up flow-wave simulation

Youngling Posts: 7 Join Date: 1/6/12 Recent Posts
Thank you, I will look into that and see if I can find anything wrong with mine.

Another question-I have to prepare my own .ini files because I am moving back and forth between the GUI and my cluster. Is there any documentation on the file dioconfig.ini? I based mine off of the one in the example, but I really can't tell what the file is supposed to actually do, especially the last few fields.

Thanks again!
Qinghua Ye, modified 6 Years ago.

RE: hung up flow-wave simulation

Jedi Council Member Posts: 612 Join Date: 3/2/11 Recent Posts
Hi Susan,

The dioconfig.ini is necessary for both linux and windows environment. It is used to configure the delftio communication between wave and flow modules. You don't have to configure by yourself, but just copy one from the installation directory to your working directory.

Hope this help a bit,

Qinghua
WR
Wim Ridderinkhof, modified 6 Years ago.

RE: hung up flow-wave simulation

Youngling Posts: 5 Join Date: 1/17/12 Recent Posts
I have the exact same problem.

The examples do run, also when I run them with a new mdw-file build by the GUI. However, I cannot get my own Flow-Wave model to run. Susan did you solve this problem? or is there anyone else who knows the solution?
Adri Mourits, modified 6 Years ago.

RE: hung up flow-wave simulation

Yoda Posts: 1219 Join Date: 1/3/11 Recent Posts
Hi Wim and Susan,

I don't expect that the keyword-based mdw-file can cause a hanging calculation as described. The most common problem when doing a FLOW calculation with WAVE online is caused by the sensitive communication via files between the two engines. To solve this, remove all temporary files produced by a previous run in the run directory. Especially files starting with "com-", "FLOW2WAVE", "WAVE2FLOW", "TMP", "tri-diag" must be removed when (re)starting a calculation.

Regards,

Adri
WR
Wim Ridderinkhof, modified 6 Years ago.

RE: hung up flow-wave simulation

Youngling Posts: 5 Join Date: 1/17/12 Recent Posts
Hi Adri,

Thank you for your fast respons!

Unfortunately this does not solve my problem, as I already deleted all temporary files before starting the simulation. Can it be a problem with the dioconfig.ini file? This file was not present after I prepared the run with use of the GUI, therefore I just copied the one that was in the folder /examples/03_flow-wave.

Wim
WR
Wim Ridderinkhof, modified 6 Years ago.

RE: hung up flow-wave simulation

Youngling Posts: 5 Join Date: 1/17/12 Recent Posts
This problem was solved by changing a line in my mdf file.

The line
Waqmod= #Y#
Should be either removed or changed to:
Waqmod= #N#

With Waqmod = #Y# the flow module tries to communicate with two different wave modules, this does not work

Hope this is of help for the next who encounters this problem.
GL
Giovanni la Forgia, modified 12 Days ago.

RE: hung up flow-wave simulation

Youngling Posts: 1 Join Date: 5/21/18 Recent Posts

I have the same issue. No errors, just the simulation does not go on after the following message

 

"*** MESSAGE: Connected to the following 1 FLOW domain(s):
             mdf
  Initialising grids and grid mappings
Part VIII - Start Simulation...                             
 
  Time to finish   0s,    0.0% completed, time steps left 100

 

Surprisingly dioconfig.ini disappears from the folder, and everytime I want to try to run again the simulation I have to manually paste this file in the folder. 

 

How to solve this problem?