Coupled Simulation stops without a message of what's wrong

sajjad · 2015-06-14 09:28:58

Dear all,

I have set up a calc. in which two 2d subdomains are included : flooddomain and retention basin. The coupling BC is 'coupling_zhydrograph'. The calculation stops right after calculating the 'first time steps'. No message displayed. Basement v.2.5.1 used. Pl. give me some suggestions or help.

Regards

Matteo Facchini · 2015-06-15 10:41:54

Hi sajjad,

It would be optimal for us to have your log file to have a better understanding of your problem.

Maybe you can copy + paste it here, or send it to us per e-mail.

Thanks!

Bests,

Matteo

sajjad · 2015-06-15 21:53:28

Dear sir,

sending you the log file. I have been changing things and now the program displays message but still does not work.
the file for zhydrograph is as follows
//t wse
0 49.8
10000 49.8
40000 49.8

Regards

// --------------------------------------------------
// BASEMENT log file:
// Version: 2.5.1 R// bmc file: E:\LocalF\Basement\simulComplet\retentB\newLocation\run.bmc
// started: Tue Jun 16 01:43:26 2015
// --------------------------------------------------
/*
-> InputParser: reading input from bmc file
'E:\LocalF\Basement\simulComplet\retentB\newLocation\run.bmc'
*/
PROJECT {
title = RetentB_integration_floodModel
author = SH
date = 14.6.2015
}
DOMAIN {
multiregion = Nime
PARALLEL {
number_threads = 2
}
PHYSICAL_PROPERTIES {
gravity = 9.81
viscosity = 0.000001
rho_fluid = 1000
}
BASEPLANE_2D {
region_name = city
GEOMETRY {
type = 2dm
file = nim5.2dm
STRINGDEF {
name = to_basin
node_ids = (3009 7618 7609 7616)
upstream_direction = left
}
STRINGDEF {
name = Inflow1
node_ids = ( 13 19199 3536 17919 17899 17904 14 )
upstream_direction = left
}
STRINGDEF {
name = Inflow2
node_ids = (2 26206 26196 26205 3)
upstream_direction = left
}
STRINGDEF {
name = Outflow1
node_ids = (1612 24212 92 )
upstream_direction = left
}
STRINGDEF {
name = Outflow2
node_ids = (86 24933 85 )
upstream_direction = left
}
STRINGDEF {
name = Outflow3
node_ids = (57 27970 56)
upstream_direction = left
}
STRINGDEF {
name = Outflow4
node_ids = (89 30017 88)
upstream_direction = left
}
STRINGDEF {
name = Outflow5
node_ids = (82 29985 81 )
upstream_direction = left
}
STRINGDEF {
name = Outflow6
node_ids = (68 28342 28340 67)
upstream_direction = left
}
STRINGDEF {
name = Outflow7
node_ids = (72 29910 71)
upstream_direction = left
}
STRINGDEF {
name = Outflow8
node_ids = (76 27947 75)
upstream_direction = left
}
STRINGDEF {
name = Outflow9
node_ids = (64 22583 22559 22570 2881 22556 22543 22577 63 )
upstream_direction = left
}
STRINGDEF {
name = Outflow10
node_ids = (61 28280 28268 28275 60 )
upstream_direction = left
}
STRINGDEF {
name = Outflow11
node_ids = (3320 21852 21284 21854 3315 21868 21856 21857 53 )
upstream_direction = left
}
STRINGDEF {
name = pitotStOutlet
node_ids = (1753 30243 30235 )
upstream_direction = left
}
}
HYDRAULICS {
PARAMETER {
simulation_scheme = exp
riemann_solver = exact
minimum_water_depth = 0.001
velocity_update_partial = volume_area
dynamic_depth_solver = on
riemann_tolerance = 1.0e-6
geo_min_area_ratio = 0.05
geo_max_angle_quadrilateral = 45
geo_min_aspect_ratio = 0.06
}
FRICTION {
type = strickler
default_friction = 30
input_type = index_table
index = ( 1 )
friction = ( 30)
wall_friction = off
grain_size_friction = no
}
BOUNDARY {
type = hydrograph
string_name = Inflow1
file = maxinflow1.txt
slope = 10.0
max_interval = 20
number_of_iterations = 5000
weighting_type = conveyance
precision = -1.0
wse_calc_method = average
}
BOUNDARY {
type = hydrograph
string_name = Inflow2
file = inflow2.txt
slope = 10.0
max_interval = 20
number_of_iterations = 5000
weighting_type = conveyance
precision = -1.0
wse_calc_method = average
}
BOUNDARY {
type = zero_gradient
string_name = Outflow1
}
BOUNDARY {
type = zero_gradient
string_name = Outflow2
}
BOUNDARY {
type = zero_gradient
string_name = Outflow3
}
BOUNDARY {
type = zero_gradient
string_name = Outflow4
}
BOUNDARY {
type = zero_gradient
string_name = Outflow5
}
BOUNDARY {
type = zero_gradient
string_name = Outflow6
}
BOUNDARY {
type = zero_gradient
string_name = Outflow7
}
BOUNDARY {
type = zero_gradient
string_name = Outflow8
}
BOUNDARY {
type = zero_gradient
string_name = Outflow9
}
BOUNDARY {
type = zero_gradient
string_name = Outflow10
}
BOUNDARY {
type = zero_gradient
string_name = Outflow11
}
BOUNDARY {
type = zero_gradient
string_name = pitotStOutlet
}
BOUNDARY {
type = coupling_zhydrograph
string_name = to_basin
name = interf_city
file = outflow2basin.txt
zero_velocity = yes
inflow_possible = yes
}
INITIAL {
type = dry
}
}
TIMESTEP {
CFL = 0.95
total_run_time = 10000
minimum_time_step = 0.0001
maximum_time_step = 100.0
initial_time_step = 1.0
start_time = -1.0
ignore_wave_celerity = off
morph_cycle = off
}
OUTPUT {
output_time_step = 10000
console_time_step = 300
restart_time_step = 2000
}
}
BASEPLANE_2D {
region_name = basin
GEOMETRY {
type = 2dm
file = retentbs.2dm
STRINGDEF {
name = inflow_cross_section
node_ids = ( 46 37 29 22 )
upstream_direction = right
}
}
HYDRAULICS {
PARAMETER {
simulation_scheme = exp
riemann_solver = exact
minimum_water_depth = 0.05
riemann_tolerance = 1.0e-6
velocity_update_partial = volume_area
dynamic_depth_solver = on
geo_min_area_ratio = 0.05
geo_max_angle_quadrilateral = 45
geo_min_aspect_ratio = 0.06
}
FRICTION {
type = strickler
default_friction = 30
wall_friction = off
grain_size_friction = no
}
BOUNDARY {
type = coupling_zhydrograph
string_name = inflow_cross_section
slope = 1.25
name = interf_retentB
inflow_possible = yes
zero_velocity = no
}
INITIAL {
type = dry
}
}
TIMESTEP {
CFL = 0.95
total_run_time = 10000
minimum_time_step = 0.0001
initial_time_step = 0.001
maximum_time_step = 100.0
start_time = -1.0
ignore_wave_celerity = off
morph_cycle = off
}
OUTPUT {
output_time_step = 10000.0
console_time_step = 300.0
restart_time_step = 1E32
SPECIAL_OUTPUT {
type = element_centered
format = ascii
output_time_step = 5000
values = ( depth )
ids_instead_coords = no
threshold_wse = -1000000
}
SPECIAL_OUTPUT {
type = element_centered
format = ascii
output_time_step = 500
values = ( wse)
ids_instead_coords = no
threshold_wse = -1000000
}
SPECIAL_OUTPUT {
type = stringdef_history
output_time_step = 100
stringdefs = ( inflow_cross_section )
stringdef_values = ( Q )
flush_all_num_steps = 0
history_one_file = no
threshold_wse = -1000000
}
SPECIAL_OUTPUT {
type = balance
balance_values = (water_volume)
output_time_step = 200
threshold_wse = -1000000
}
}
}
COUPLINGS {
PARAMETER {
max_time_level = 4
factor_time_step_reduction = 1.0
server = yes
ip_address = localhost
port = 5000
max_buffer = 2000
packet_size = 1000
log_network = off
}
COUPLING {
type = sequential
upstream_subdomain = city
downstream_subdomain = basin
two_way_coupling = no
average_steps = 1
print_series = no
espilon = 1E-6
HYDRAULICS {
upstream_interface = interf_city
downstream_interface = interf_retentB
}
}
}
}

/*
-> Domain: Input file has 1 warning and 0 errors:
*WARNING: Tag slope from Block BOUNDARY (on line 255 in file
'E:\LocalF\Basement\simulComplet\retentB\newLocation\run.bmc') has 1
warnings:
The value for tag 'slope' will not be used as tag 'type' != 'hydrograph' or
'coupling_hydrograph' or 'hqrelation' or 'coupling_hqrelation'

-> *** Start Simulation ***
-> OpenMP: Computation is executed in parallel using 2 threads
-> Domain Initialized
-> initialize domain done
-> do network communicator
-> chars done
-> do network communicator for done
-> network communication done
-> initialize networkcommunication done
-> BASEplane: Initialization of SubDomain 'city
-> Reserving the vectors for nodes, elements & edges
-> InputSMS: Number of Nodes = 31311
-> InputSMS: Number of Elements = 48751
-> Checking disjoint nodes ...
-> Checking the area of elements ...
-> Checking the aspect ratio of elements ...

*******************************************************************************
*!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Warning !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!*
*******************************************************************************
-> Some elements in the mesh are too thin!
These elements may cause instabilities in the program!
See the file geofile_Grid.err for the element numbers.
-> Checking for concave quadrilateral elements ...
-> Checking for ambiguous quadrilateral elements ...

*******************************************************************************
*!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Warning !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!*
*******************************************************************************
-> Some ambiguous quadrilateral elements were found !
These elements may cause instabilities in the program!
See the file XXX_Grid.err for the element numbers
where XXX is the name of the grid File.
-> InputSMS: Number of Edges = 80139
-> InputSMS: Total mesh area = 171517 m2

*******************************************************************************
*!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Warning !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!*
*******************************************************************************
-> A boundary_file is specified for a coupling hydraulic boundary condition
of type 'zhydrograph'. But no boundary file can be used because the input is
taken from the coupled subdomain.
-> BASEplane: Initialization of SubDomain 'basin
-> Reserving the vectors for nodes, elements & edges
-> InputSMS: Number of Nodes = 169
-> InputSMS: Number of Elements = 144
-> Checking disjoint nodes ...
-> Checking the area of elements ...
-> Checking the aspect ratio of elements ...
-> Checking for concave quadrilateral elements ...
-> Checking for ambiguous quadrilateral elements ...
-> InputSMS: Number of Edges = 312
-> InputSMS: Total mesh area = 57600 m2

*******************************************************************************
*!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!*
*******************************************************************************
-> The zhydrograph must have an input serie.
Program can not continue, please correct the input data!
-> Domain: Simulation stopped due to errors

Stephan Kammerer · 2015-06-16 11:23:14

Hi Sajjad,

coupling_zhydrograph can only be used as downstream boundary condition. This is described in the documentation of the tag 'type' in the 'BOUNDARY' block.
Since the inflow into your downstream subdomain 'basin' comes from the coupled upstream subdomain 'city', you have to use a boundary condition of type 'coupling_hydrograph' for the domain 'basin'.

Hope this helps!
Stephan

sajjad · 2015-06-16 11:38:54

Thank you for your kind reply. kindly consider improving the doc, if possible, by explicitly indicating this limitation.

I wanted to use this bc for a particular reason. I want the retention basin to be filled upto a certain elevation only and since by using zhydrograph I can define the reservoir level which the domain water level tries to match so I thought maybe I could stop the filling process of the basin once that elevation is attained in the basin. Once again thanks a lot.

Regards

User Forum of Software BASEMENT

#1 2015-06-14 09:28:58

Coupled Simulation stops without a message of what's wrong

#2 2015-06-15 10:41:54

Re: Coupled Simulation stops without a message of what's wrong

#3 2015-06-15 21:53:28

Re: Coupled Simulation stops without a message of what's wrong

#4 2015-06-16 11:23:14

Re: Coupled Simulation stops without a message of what's wrong

#5 2015-06-16 11:38:54

Re: Coupled Simulation stops without a message of what's wrong

Board footer