hung up flow-wave simulation - D-Flow Flexible Mesh - Delft3D
intro story D-Flow FM
D-Flow Flexible MeshD-Flow Flexible Mesh (D-Flow FM) is the new software engine for hydrodynamical simulations on unstructured grids in 1D-2D-3D. Together with the familiar curvilinear meshes from Delft3D 4, the unstructured grid can consist of triangles, pentagons (etc.) and 1D channel networks, all in one single mesh. It combines proven technology from the hydrodynamic engines of Delft3D 4 and SOBEK 2 and adds flexible administration, resulting in:
An overview of the current developments can be found here. The D-Flow FM - team would be delighted if you would participate in discussions on the generation of meshes, the specification of boundary conditions, the running of computations, and all kinds of other relevant topics. Feel free to share your smart questions and/or brilliant solutions!
======================================================= | Sub groups
|
Message Boards
hung up flow-wave simulation
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 8 Years ago.
RE: hung up flow-wave simulation
Jedi Council Member Posts: 610 Join Date: 3/2/11 Recent PostsThere 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
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 8 Years ago.
RE: hung up flow-wave simulation
Jedi Council Member Posts: 610 Join Date: 3/2/11 Recent PostsThe 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
Wim Ridderinkhof, modified 8 Years ago.
RE: hung up flow-wave simulation
Youngling Posts: 5 Join Date: 1/17/12 Recent PostsThe 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 8 Years ago.
RE: hung up flow-wave simulation
Yoda Posts: 1221 Join Date: 1/3/11 Recent PostsI 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
Wim Ridderinkhof, modified 8 Years ago.
RE: hung up flow-wave simulation
Youngling Posts: 5 Join Date: 1/17/12 Recent PostsThank 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
Wim Ridderinkhof, modified 8 Years ago.
RE: hung up flow-wave simulation
Youngling Posts: 5 Join Date: 1/17/12 Recent PostsThe 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.
Giovanni la Forgia, modified 1 Year ago.
RE: hung up flow-wave simulation
Youngling Posts: 1 Join Date: 5/21/18 Recent PostsI 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?