User Forum of Software BASEMENT / Coupling of domains

Sequential coupling of two 1D domains: HYDRAULICS

dummy@example.com (Pascal) — Wed, 06 Sep 2023 14:51:20 +0000

Dear BASEMENT Team
Once I modeled a 1D domain it with an external source (only one domain), to model a tributary and once with 2 subdomains and in between a BC: a junction respectively a confluence_wse. The results of all simulations are completely different. The only plausible solution is given by the external source. The solutions modeling with two subdomains gives a huge energy loss. Is there an explanation for that?
Thanks a lot
Pascal

Lateral Coupling 1D-2D: Problem with steady-state simulation

dummy@example.com (Nils) — Wed, 16 Nov 2022 16:38:22 +0000

Hi everyone

for my master thesis I´m trying to create a 1D-2D coupled model and got some problems and questions.

I´ve created the danube as 1D cross sections and the floodplain on the left danube side as 2D mesh.
The water enters and leaves the system only in the 1D subdomain.
(similar to BASEMENT Tutorial Nr. 6)

1. I ran my model to get steady-state conditions.
Until 154.900s I had mass loss, at 154.900s Input_Q was the same as Output_Q, after this time I got more Output_Q as Input_Q.
Now I´m wondering if there are steady-state conditions possible for my model, as I have some branches in my 2D mesh, where the water might take a long time to flow through?

2. I sometimes have small mass loss at some cross sections even before the 2D subdomain and at the coupling interface but without having branches etc... Is it normal for BASEMENT that the discharge Q rises and falls between the cross sections in very small amount? (xxxx.02 m³/s)

3. The help-Button in BASEMENT recommend for HYDRAULICS - BOUNDARY to use "coupling_hydrograph" and "coupling_hqrelation" instead of "hydrograph" and "hqrelation", but BASEMENT crashs when I try to use them. Is this because I don´t have a boundary for my 2D mesh?

4. Can someone maybe check my Input Structure, and if there are improvements to get shorter running times?
I have a huge floodplain, which I wanted to simulate as precisely as possible, but first tests gave me running times of more than 1 week (RTS < 0.5).

I really hope someone can help me, as I´m completely new to BASEMENT and hydrodynamic-numeric modelling.

Here is the output of the time 154.900 and underneath my BASEMENT structure:

time_s: 154900 time_step_s: 0.12803867852198891342
velocity_u_[m/s]: 1.5525291845234230337 wave_speed_c_[m/s]: 7.0390423498937231273 Element responsible for time step: 1907500
Edge_number Mass_Flux_[m3/s] Momentum_Flux_[m4/s2]    Total_Bedload_Flux_[m3/s]    Advective_Susp_Flux_[-]    Diffusive_Susp_Flux_[-]
0 1930 3086.01    0    0    0
1 1930 3091.71    0    0    0
2 1930 3153.63    0    0    0
3 1930 3162.89    0    0    0
4 1930 3329.69    0    0    0
5 1930.01    3310.91    0    0    0
6 1930.01    3279.64    0    0    0
7 1930.01    3491.34    0    0    0
8 1930.01    3445.39    0    0    0
9 1930.01    3494.09    0    0    0
10    1930.01    3460.39    0    0    0
11    1930 3393.99    0    0    0
12    1930 3366.98    0    0    0
13    1930 3517.17    0    0    0
14    1930 3476.71    0    0    0
15    1930 3336.61    0    0    0
16    1930 3394.5 0    0    0
17    1930 3228.42    0    0    0
18    1929.99    3308.06    0    0    0
19    1929.99    3309.47    0    0    0
20    1929.99    3216.21    0    0    0
21    1930.02    3137.19    0    0    0
22    1930.04    2928.1 0    0    0
23    1929.74    2971.97    0    0    0
24    1929.73    3023.44    0    0    0
25    1929.7 3008.77    0    0    0
26    1929.72    3204.24    0    0    0
27    1929.73    3245.07    0    0    0
28    1929.76    3330.96    0    0    0
29    1929.8 3454.8 0    0    0
30    1929.77    3417.01    0    0    0
31    1929.77    3533.83    0    0    0
32    1929.77    3665.63    0    0    0
33    1929.76    3613.11    0    0    0
34    1929.76    3622.36    0    0    0
35    1929.75    3652.2 0    0    0
36    1929.75    3641.09    0    0    0
37    1929.74    3539.73    0    0    0
38    1929.74    3317.55    0    0    0
39    1929.74    3337.88    0    0    0
40    1929.74    3524.06    0    0    0
41    1929.74    3622.4 0    0    0
42    1929.74    3477.03    0    0    0
43    1929.74    3489.14    0    0    0
44    1929.74    3584.08    0    0    0
45    1929.74    3603.49    0    0    0
46    1929.74    3603.93    0    0    0
47    1929.74    3675.45    0    0    0
48    1929.74    3729.32    0    0    0
49    1929.74    3975.98    0    0    0
50    1929.73    3870.46    0    0    0
51    1929.72    3472.22    0    0    0
52    1929.72    3371.76    0    0    0
53    1929.72    3259.59    0    0    0
54    1929.72    3413.24    0    0    0
55    1929.72    3479.56    0    0    0
56    1922.61    3511.71    0    0    0
57    1929.96    3636.23    0    0    0
58    1930.03    3730.75    0    0    0
59    1930.03    3890.47    0    0    0
60    1930.03    3844.97    0    0    0
61    1930.03    3923.12    0    0    0
62    1930.03    3659.91    0    0    0
63    1930.02    3459.26    0    0    0
64    1930.01    3371.03    0    0    0
65    1930.01    3619.22    0    0    0
66    1930.01    3594.27    0    0    0
67    1930.01    3208.31    0    0    0
68    1930 3352.77    0    0    0
69    1930 3399.92    0    0    0
70    1930 3801.24    0    0    0
71    1930 3964.72    0    0    0
72    1930 3998.75    0    0    0
73    1930 3720.92    0    0    0
74    1930 3149.86    0    0    0

PROJECT {
title = 1D-2D Modell
author = Nils
date = 16.11.2022
}
DOMAIN {
PHYSICAL_PROPERTIES {
gravity = 9.81
viscosity = 1e-06
rho_fluid = 1000
}
BASECHAIN_1D {
region_name = Donau
GEOMETRY {
file = Donau.bmg
cross_section_order = (1907500 1907400 1907300 1907200 1907100 1907000 1906900 1906800 1906700 1906600 1906500 1906400 1906300 1906200 1906100 1906000 1905900 1905800 1905700 1905600 1905500 1905400 1905300 1905200 1905100 1905000 1904900 1904800 1904700 1904600 1904500 1904400 1904300 1904200 1904100 1904000 1903900 1903800 1903700 1903600 1903500 1903400 1903300 1903200 1903100 1903000 1902900 1902800 1902700 1902600 1902500 1902400 1902300 1902200 1902100 1902000 1901900 1901800 1901700 1901600 1901500 1901400 1901300 1901200 1901100 1901000 1900900 1900800 1900700 1900600 1900500 1900400 1900300 1900200)
}
HYDRAULICS {
BOUNDARY {
type = hydrograph
string = upstream
file = Hydrograph.txt
slope = 0.46
precision = 0.001
number_of_iterations = 100
}
BOUNDARY {
type = hqrelation
string = downstream
slope = 0.46
}
FRICTION {
type = strickler
default_friction = 35
}
INITIAL {
type = continue
file = Donau_restart_86400.dat
}
PARAMETER {
minimum_water_depth = 0.01
simulation_scheme = explicit
riemann_solver = roe
SECTION_COMPUTATION {
type = table
min_interval = 0.0025
max_interval = 0.2025
}
}
}
TIMESTEP {
total_run_time = 172800
initial_time_step = 1.0
maximum_time_step = 60.0
CFL = 0.95
}
OUTPUT {
output_time_step = 100
console_time_step = 100
}
}
BASEPLANE_2D {
region_name = DonauAuen
GEOMETRY {
type = 2dm
file = DonauAuen.2dm
}
HYDRAULICS {
PARAMETER {
minimum_water_depth = 0.01
}
FRICTION {
type = strickler
wall_friction = off
index = (1 2)
friction = (35 35)
input_type = index_table
default_friction = 35
}
INITIAL {
type = continue
file = DonauAuen_restart.cgns
restart_solution_time = 86400
}
}
TIMESTEP {
total_run_time = 172800
CFL = 0.95
}
OUTPUT {
console_time_step = 100
restart_time_step = 500
SPECIAL_OUTPUT {
type = node_centered
format = sms
values = (velocity depth wse)
output_time_step = 1000
}
SPECIAL_OUTPUT {
type = BASEviz
output_time_step = 1000
}
}
}
COUPLINGS {
PARAMETER {
max_time_level = 1
}
COUPLING_LATERAL {
basechain = Donau
baseplane = DonauAuen
connections_automatic = no
connections_distance = 50.0
connections_index = (1 2)
connections_filename = lateral_connections_created.dat
weir_from_dyke1D = no
damping_factor = 0.5
}
}
PARALLEL {
number_threads = 4
}
}

Lateral coupling: between sequential 1D and 2D domains

dummy@example.com (Matthias Bürgler) — Tue, 23 Nov 2021 14:49:30 +0000

Hi
The error message is not related to the coupling-setup of the model, but to the SPECIAL_OUTPUT of type BASEviz. BASEviz seems to be affected by a bug in version 2.8.1. This will be fixed in the next release of version 2.

Best
Matthias

coupling river junction with sediment transport

dummy@example.com (maarnold) — Thu, 20 Aug 2020 08:59:22 +0000

Dear fellow modellers,

I try to model a river junction with BASMENT v2.8 in 1D. I have created three domains, two domains for the main river and a third domain for the smaller river which flows into the main river.

As for the coupling type, I have used "junction" with two upstream subdomains and one downstream subdomain.

		COUPLING {
			type                 = junction
			upstream_subdomain1  = rotten_upstream
			upstream_subdomain2  = saltina_kanal
			downstream_subdomain = rotten_downstream
			two_way_coupling     = yes
			HYDRAULICS {
				upstream_interface1  = rotten_outflow_upstream
				upstream_interface2  = outflow_saltina
				downstream_interface = rotten_inflow_downstream
			}
			BEDLOAD {
				upstream_interface1  = rotten_outflow_upstreamsed
				upstream_interface2  = outflow_saltinased
				downstream_interface = rotten_inflow_downstreamsed
			}

Running the model without sediment transport seems to be working. If I add the morphology blocks and create a bedload coupling, BASEMENT crashes without any error message.

Have you experienced similar issues? If so, have you found a solution?

Cheers

Mathias

2D to 1D coupling: WSE conservation

dummy@example.com (MarcDiebold) — Mon, 04 Feb 2019 15:14:20 +0000

Hello everybody,

I'm working on models involving 2D to 1D couplings and often encounter the problem described hereafter:

- The upstream condition of the 2D model is a hydrograph (hydrograph, file = Hydrographe_SarAar160.txt, slope = 0.05)
- The downstream condition of the 1D-model is fixed at a constant level (zhydrograph, file = Zhydrographe_SarAarOUT.txt)
- The downstream of the 2D model (coupling_zhydrograph) is coupled with the upstream of the 1D model (coupling_hydrograph, precision = 0.0001, number_of_iterations = 250, slope = 0.05)

Two_ways_coupling is "on" but for some reason, the WSE of my downstream 1D model (461.11 m at the upstream border) is not taken back to the upstream 2D area (461.28 m at the downstream border).

Any suggestions on how to avoid these "WSE-jumps" would be greatly appreciated.

Best regards,
Marc

PS: if useful, the complete model with some results are here: https://www.dropbox.com/sh/amrbid94yvlp … 14aaa?dl=0

stability issues when refining the mesh

dummy@example.com (Stephan Kammerer) — Tue, 17 Jan 2017 09:21:09 +0000

In the "COUPLINGS" block you can define parameters and set the "max_time_level" to 1, which means that all sub domains run with the same minimum timestep. It's recommended to use this configuration for laterally coupled simulations.

COUPLINGS {
PARAMETER {
max_time_level = 1
}

BaseEXTERN tutorial

dummy@example.com (Adnan) — Wed, 17 Aug 2016 07:37:31 +0000

hi developers

kindly provide us with an example / tutorial of BaseEXTERN . so we can understand and use the BaseEXTERN module for external coupling of BASEMENT.

regards

Assumptions

dummy@example.com (Adnan) — Tue, 26 Jul 2016 10:06:38 +0000

hello dear staff

i want to know what are the assumption for bifurcation and junction type of coupling ?

i searched for these in manuals but could not find . can anyone give me some reference about these .

regards

from 2D to 1D

dummy@example.com (sajjad) — Tue, 17 May 2016 19:09:16 +0000

Dear Stephan,

very very kind of you to have given your time to see and correct the files.The problem, as before, is that the flow does not enter the 2D domain from the leftchan and topchan. However, with corrected restart files, flow does enter the 1d domains 'topchan' and 'leftchan'. maybe I should try some less stringent coupling b. conds.

Thanks and regards

1d-2d coupling BC error

dummy@example.com (sajjad) — Tue, 01 Mar 2016 19:27:26 +0000

Dear sir,

referring to your reply, are not the steps 2 and 3 in contradiction to each other? coz when i refine the 2d mesh at the interface, i had to increase the no . of nodes and had to increase nodes at the interface( which is advised to be reduced in step 3).

Regards

network couplng

dummy@example.com (Adnan) — Tue, 25 Aug 2015 09:30:08 +0000

Sir,

here is the link to my file which is causing the error . kindly check this file and find me the reason for which i am keep getting problem

http://www31.zippyshare.com/v/uTTzbaok/file.html

regards Adnan

1D/2D coupling

dummy@example.com (LydiaSeitz) — Mon, 20 Jul 2015 07:30:14 +0000

Hi Stephan,

thanks for your reply. Actually the sequential coupling looks like you described above. I have a 2D part within a long 1D model, that means first I have a sequential coupling from 1D -> 2D and than a sequential coupling from 2D -> 1D.

Do you think it´s a problem to couple three models?

It would be great if you could provide me a updated version. So I can try if it´s running.

Best wishes
Lydia

Error with Seq.Coupling of 2D to 1D with sediment transport

dummy@example.com (Lukas Vonwiller) — Thu, 21 May 2015 11:35:34 +0000

Yes, you can send your model to basement@ethz.ch.

We try to check if it is an application error or a bug.
If it is a bug will put it on our todo-list for the next release.
cheers
Lukas