Migration status

  • Home Page: Activity map.

intro story DELWAQ

DELWAQ

DELWAQ is the engine of the D-Water Quality and D-Ecology programmes of the Delft3D suite. It is based on a rich library from which relevant substances and processes can be selected to quickly put water and sediment quality models together.

The processes library covers many aspects of water quality and ecology, from basic tracers, dissolved oxygen, nutrients, organic matter, inorganic suspended matter, heavy metals, bacteria and organic micro-pollutants, to complex algae and macrophyte dynamics. High performance solvers enable the simulation of long periods, often required to capture the full cycles of the processes being modelled.

The finite volume approach underlying DELWAQ allows it to be coupled to both the structured grid hydrodynamics of the current Delft3D-FLOW engine and the upcoming D-Flow Flexible Mesh engine (1D-2D-3D) of the Delft3D Flexible Mesh Suite (or even other models such as TELEMAC).

'DELWAQ in open source' is our invitation to all leading experts to collaborate in further development and research in the field of water quality, ecology and morphology using Delft3D. Feel free to post your DELWAQ related questions or comments in this dedicated forum space. If you are new to DELWAQ, the tutorial (in the user manual) is a good place to start. A list of DELWAQ related publications is available here.

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ

Cohesive sediments & muddy systems

 


Message Boards

Number of open boundaries too large

JK
Jonathan King, modified 4 Years ago.

Number of open boundaries too large

Youngling Posts: 16 Join Date: 9/8/15 Recent Posts
Hi all,

I'm transferring an existing ocean model in EFDC over to Delft 3D but am having trouble with the boundary conditions.

The boundary conditions are applied as time series' of water levels along open sea boundaries in the N, E, S & W of the domain. The .bnd and .bct files are in the correct format and accepted by the GUI during creation of the .mdf project file.

The problem arises when I try and run the model; I get an error saying that the number of open boundaries is too large:

********************************************************************************
***
*** Deltares, FLOW2D3D Version 6.00.01.000000, Sep 29 2015, 14:23:59
***
*** runid : csm_001
*** date,time : 2015-11-30, 12:55:10
***
********************************************************************************

*** ERROR Number of open boundaries too large. Contact Deltares

*** End of tdatom for model: csm_001 ***
*** 2015-11-30 12:55:10 ***

In total I have 1331 boundary conditions each with an associated water level time series containing 4320 records.

Is this a problem with Delft 3D running in series (or on Windows), will I also get this problem if I try and run it on Linux in parallel?


Thanks
Jon
JK
Jonathan King, modified 4 Years ago.

RE: Number of open boundaries too large

Youngling Posts: 16 Join Date: 9/8/15 Recent Posts
Another thought is that this is something I can easily change in the source code.

Does anyone know if there are variables which limit the size of the domain, number of open boundaries etc and if so where to find them?

Thanks
Jon
Qinghua Ye, modified 4 Years ago.

RE: Number of open boundaries too large (Answer)

Jedi Council Member Posts: 612 Join Date: 3/2/11 Recent Posts
HI Jon,

So far the maximum number of open boundary is 500. You might extend it in pardef.igd, the mxnto to a larger number, and compile the code again.

There are 2 places Delft3D will check this maximum number. One is in the preparation stage, the other is in the beginning of computation. I would think, if it is in parallel mode, for the 2nd stage it should be no problem. But most probably the first stage will stop the simulation already. You may give a try and share with us about the results.

Regards,

Qinghua
JK
Jonathan King, modified 4 Years ago.

RE: Number of open boundaries too large

Youngling Posts: 16 Join Date: 9/8/15 Recent Posts
Hi Qinghua,

Thank you. I managed to successfully compile the code but when I tried running a job it failed to start, giving me the same error that the number of boundary conditions was too large.

I've since managed to reduce the boundary data to 133 BCs which gives me good results so I'm going to stick with this for now as it's good enough for what I need.

Thanks again for your help

Regards
Jonathan
DS
Dwi Saputri, modified 3 Years ago.

RE: Number of open boundaries too large

Youngling Posts: 9 Join Date: 10/11/16 Recent Posts
Hi Qing Hua,

Thx for the answer solution.
I've changed mxnto to 1000, compiled again and successfully run a simulation.
I'm using code 6864.

Regardss,

Dwi