null

Message Boards

using hydrodynamic output from parallel computing for WAQ/PART module

U
Anonymous, modified 2 Years ago.

using hydrodynamic output from parallel computing for WAQ/PART module

Posts: 1
Hello community,

i am fairly new to the DELFT3D-WAQ/PART modules and I would like to create an oil spill (just to test functionality, later I plan to use other chemicals with the WAQ module) on the base of a 3D hydrodynamic model done with parallel computing. As a result of the parallel computing i receive multiple output-files (com-, hyd etc) depending on the number of servers i use to do the calculations.

Is there a way to merge the output-files into one, so that i can feed it to the WAQ/PART input? Or can I somehow tell the WAQ module to use multiple files as input?

Thank you very much for any help with this.
Michel Jeuken, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module (Answer)

Jedi Knight Posts: 156 Join Date: 1/21/13 Recent Posts
KW
Karoline Wischnewski, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 10 Join Date: 12/1/16 Recent Posts
Thank you Michel for the quick reply.

I ran ddcouple and it works nicely for the WAQModule-input, but for the Particle Tracking Module it seems to be missing the .lgt-file. My simulation produces them, so that i got the multiple files, but they do not get merged by the ddcoupling tool. Could i have been missing something in my hydrodynamics model output specifically for particle tracking?
DG
David Gutiérrez, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 15 Join Date: 1/6/12 Recent Posts
Hi Karoline,

did you manage to run the PART simulation with MPI-parallel-FLOW input without the lgt file?

David
KW
Karoline Wischnewski, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 10 Join Date: 12/1/16 Recent Posts
Hi David,

no, the PART GUI, crashes every time I try to open my .hyd-file. But since I aim to use the WAQ Module I did not put more time on the issue, would still love to know a workaround for that though, since I might need that module in the future.

Cheers,
Karoline
DG
David Gutiérrez, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 15 Join Date: 1/6/12 Recent Posts
Hi Karoline,

After some struggling a bit I have been able to run it.
I don't know about your platform details.
In my case, I am using the current trunk revision (6906) under windows 7, compiled with IFORT15 using VS2013.

I have basically followed the instructions from Michel, that is:

- Prepare FLOW run asking for "Export WAQ Input".
- Run FLOW with mpiexec
- Run ddcouple.exe xxxxxxx.ddb -parallel
Here, xxxxxxx.ddb is created by FLOW when run with mpiexec
- Prepare the PART simulation with the GUI (using the hyd file created by ddcouple)
- Run PART

What are your errors? What does PART complain about? In my case it doesn't say anything about the lgt file...

David
KW
Karoline Wischnewski, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 10 Join Date: 12/1/16 Recent Posts
Hey David,

does ddcouple produce the combined lgt file though? PART does not complain or give errors. It just freezes. SO I looked through the empty shell and saw its expecting the lgt file but i am not certain that this actually is the error. But since everything is fine in the WAQ shell I figured it might be related.

Cheers,
Karoline
DG
David Gutiérrez, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 15 Join Date: 1/6/12 Recent Posts
Hi Karoline,

ddcouple does not produce the combined lgt file.

By freezing, you mean when it says "Input file succesfully read"?
If that is the case, it is normal that it takes some minutes for the real simulation to run.
I am having a look at the code to see if it is easy to get any "progress information" at that stage of the run, because it is really annoying waiting that much for any info.
Just in case: did you let the run go for some time before killing the process?

David
KW
Karoline Wischnewski, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 10 Join Date: 12/1/16 Recent Posts
Hey David,

no I am not even at trying to let it run. It is just at the define input stage. Trying to set up the run. Right at the very first step where you point to the hyd-file. When I hit open hyd-file, that is when the application just freezes (you know the typical, windows "any-application-no-response" its suddenly becoming fogged over and I get a message from the system that the application needs to be closed...).

So, I guess you did not encounter that problem if you were able to start a simulation.

Cheers Karoline
Michel Jeuken, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Jedi Knight Posts: 156 Join Date: 1/21/13 Recent Posts
Hi David and Karoline,

Good to see you are trying to sort this out among your selves, but I think there is a little mix up about the GUI/define input and the actual PART/delpar kernel. It seems that Karoline's GUI is not accepting the hyd-file. What I would like to know is what version of the PART-GUI, and what version of ddcouple you are using.

I know that ddcouple had some extra keywords in the file that (older versions of) the PART-GUI couldn't handle (although it should have ignored them). I'll have to look up if you need a newer ddcouple and/or a newer GUI.

greetings,
Michel
DG
David Gutiérrez, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Youngling Posts: 15 Join Date: 1/6/12 Recent Posts
Hi Michel,

after the last message from Karoline I have been reviewing my test runs and I think I have found something:
After running ddcouple, there are two sets of hyd files in the run's directory.
The error mentioned by Karoline appeared when I clicked one of the wrong ones (the ones with the -XXX "simulation partition" id).
When clicking the right one (the one generated by ddcouple), the GUI does not complain.

Apart from this, you are right about the version checking. More than once I have suffered from version mixing struggle...

Cheers
David
ZW
Zhanxian Wang, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Padawan Posts: 35 Join Date: 4/11/12 Recent Posts
I got the same problem with PART model after using DDCOUPLE Version 1.02.00.39551, Apr 3 2015, posted on the forum. PART GUI did not accept the combined hyd file and crashed. My PART GUI version is 2.27.00 coming with Delft3d 4.01.00 Windows version. I tried the same hyd file with Delft3D-WAQ GUI (version 3.32.15), it was accepted without crashing. Is there any newer version of PART GUI available that compatible with the 2015 DDCOUPLE? If so, how can I get it? I need to run PART very soon this month and hopefully to get this issue resolved very quickly. Thanks.



Michel Jeuken:
Hi David and Karoline,

Good to see you are trying to sort this out among your selves, but I think there is a little mix up about the GUI/define input and the actual PART/delpar kernel. It seems that Karoline's GUI is not accepting the hyd-file. What I would like to know is what version of the PART-GUI, and what version of ddcouple you are using.

I know that ddcouple had some extra keywords in the file that (older versions of) the PART-GUI couldn't handle (although it should have ignored them). I'll have to look up if you need a newer ddcouple and/or a newer GUI.

greetings,
Michel
ZW
Zhanxian Wang, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module

Padawan Posts: 35 Join Date: 4/11/12 Recent Posts
After downloaded the posted version of PART GUI (2.30.38828:38829) from another post on the forum, the combined hyd file can be accepted to set up particle tracking in the new GUI. However, when I ran the PART setup, delpar crashed with the following message:

---------------------------------------------------------------------------

Command: {C:\Delft3D_401/win32/part/bin/delpar.exe}


PART - Particle tracking
Water quality simulation in 2D/3D models
Deltares, PART Version 3.76.0.33151, Apr 1 2014, 15:45:04



child killed: segmentation violation

---------------------------------------------------------------------------

Could somebody help to figure out the problem? is the delpar version I currently have not compatible with the setup file created with the new PART GUI?

Thanks,
Jonathan

Zhanxian Wang:
I got the same problem with PART model after using DDCOUPLE Version 1.02.00.39551, Apr 3 2015, posted on the forum. PART GUI did not accept the combined hyd file and crashed. My PART GUI version is 2.27.00 coming with Delft3d 4.01.00 Windows version. I tried the same hyd file with Delft3D-WAQ GUI (version 3.32.15), it was accepted without crashing. Is there any newer version of PART GUI available that compatible with the 2015 DDCOUPLE? If so, how can I get it? I need to run PART very soon this month and hopefully to get this issue resolved very quickly. Thanks.



Michel Jeuken:
Hi David and Karoline,

Good to see you are trying to sort this out among your selves, but I think there is a little mix up about the GUI/define input and the actual PART/delpar kernel. It seems that Karoline's GUI is not accepting the hyd-file. What I would like to know is what version of the PART-GUI, and what version of ddcouple you are using.

I know that ddcouple had some extra keywords in the file that (older versions of) the PART-GUI couldn't handle (although it should have ignored them). I'll have to look up if you need a newer ddcouple and/or a newer GUI.

greetings,
Michel
ZW
Zhanxian Wang, modified 2 Years ago.

RE: using hydrodynamic output from parallel computing for WAQ/PART module (Answer)

Padawan Posts: 35 Join Date: 4/11/12 Recent Posts
After update the service package to 4.02.03. Everything is fine now.