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

Receiving error: "Wrong Coupling Point" when running Flow+Wave and DD

MU
Michael Ulmgren, modified 1 Year ago.

Receiving error: "Wrong Coupling Point" when running Flow+Wave and DD

Youngling Posts: 5 Join Date: 1/19/17 Recent Posts

Hello!

So I have built a Delft3D model for the Beaufort Sea in Alaska and I plan on running this model to simulate surge and wave conditions along the coast. I have used domain decomposition (DD) to improve the resolution at two locations along the coast. The large coarse grid has a resolution of about 3.3 km while the highest resolution domain has a resolution of about 124 m. I have already run this model setup to simulate surge without any troubles. However, I now want to add waves and I'm running into problems.

To start off, I'm using Delft3D GUI 4.03 and I compiled Source Code#7545 using Intel compiler 2015.

I have 7 domains so I have 7 .mdf files and 7 .mdw files.

When starting the model I get the following error message:

1) Error during initialization of subdomains: check tri-diag files.
OR
2) "Prudhoe_Bay_Low_Res": Wrong coupling point at (41, 2) Kcs=0 KcsInside=0
d_hydro ABORT: [Iterator]
1) Error during initialization of subdomains: check tri-diag files.
OR
2) "Prudhoe_Bay_Low_Res": Wrong coupling point at ( 2,41) Kcs=0 KcsInside=0
d_hydro ABORT: [Iterator]
1) Error during initialization of subdomains: check tri-diag files.
OR
2) "Baseline": Wrong coupling point at (86,52) Kcs=0 KcsInside=0
d_hydro ABORT: [Iterator]
1) Error during initialization of subdomains: check tri-diag files.
OR
2) "Baseline": Wrong coupling point at (86,52) Kcs=0 KcsInside=0

child process exited abnormally
 

The cell points that are mentioned above are located at the corners of the domain with the higher resolution. By the way, I'm using a 1-3 ratio between the domains. As this model works fine when I don't simulate waves, I'm thinking there is some issue when running waves with DD. Are there any known issues?

When I just simulated surge I used a timestep of 1 min without any problems. After I added waves, I lowered the timestep to 0.2 min, but the I keep getting the same error code.

I have attached the files for my model.

I would really appreciate any input to help solve this issue.

Cheers!

Michael 

MU
Michael Ulmgren, modified 1 Year ago.

RE: Receiving error: "Wrong Coupling Point" when running Flow+Wave and DD

Youngling Posts: 5 Join Date: 1/19/17 Recent Posts

Update:

It seems I did not understand correctly how the FLOW and WAVE modules communicate. I thought each .mdf file, representing a FLOW domain, needed a .mdw file associated with it (so I had 7 .mdw files in my directory). I understand now that it's not the case. Now I have my 7 FLOW domains connected with DD boundaries and a single computational grid, which covers the area of the 7 FLOW domains, in a single .mdw file. For improved accuracy in the computational grid I'm now using nesting as a tool. This method now yields no errors.

Michael