This page contains the test case 4 of the UK benchmark named ''Test 4 – Speed of flood propagation over an extended floodplain'' as well as its result generated by the [[Water Module]] in the {{software}}.__NOTOC__
This page reports on the performance of the {{software}}'s [[Water Module]] by means of the UK EA Benchmark '''Test 4 – Speed of flood propagation over an extended floodplain'''.__NOTOC__
: Text boxes in ''italic'' are largely based on the description provided in Néelz and Pender (2013)<ref name="Néelz"/>.
The objective of this test is to assess the package’s ability to simulate the celerity of propagation of a flood wave and predict transient velocities and depths at the leading edge of the advancing flood front. It is relevant to fluvial and coastal inundation resulting from breached embankments.<ref name="Néelz"/>
''The objective of the test is to assess the package’s ability to simulate the celerity of propagation of a flood wave and predict transient velocities and depths at the leading edge of the advancing flood front. It is relevant to fluvial and coastal inundation resulting from breached embankments.''
==Description==
==Description==
''This test is designed to simulate the rate of flood wave propagation over a 1,000 x 2,000 m floodplain following a defence failure (Figure (a)). The floodplain surface is horizontal, at elevation 0 m. One inflow boundary condition will be used, simulating the failure of an embankment by breaching or overtopping, with a peak flow of 20 m<sup>3</sup>/s and time base of ~6 h. The boundary condition is applied along a 20-m line in the middle of the western side of the floodplain.''
This test is designed to simulate the rate of flood wave propagation over a 1,000 x 2,000 m floodplain following a defence failure (Fig. (a)). The floodplain surface is horizontal, at datum (= 0 m). One inflow boundary condition will be used, simulating the failure of an embankment by breaching or overtopping, with a peak flow of 20 m<sup>3</sup>/s and time base of ~6 h. The boundary condition is applied along a 20-m line in the middle of the western side of the floodplain.<ref name="Néelz"/>
[[File:topdown_case4_ukbm.png|thumb|left|Figure (a): Modelled domain, showing the location of the 20-m inflow, 6 output points, and possible 0.1 m and 0.2 m contour lines at t = 1 h (dashed) and t = 3 h (solid).]]
[[File:topdown_case4_ukbm.png|thumb|left|Figure (a): Modelled domain and the locations of the 20-m line of inflow, 6 output points, and the aimed for 0.1-m and 0.2-m contour lines at t = 1 h (dashed) and t = 3 h (solid), respectively.]]
[[File:UK_test_4.gif|right|Animation of the test result for case 4, generated by the {{software}}. Map dimensions = 1,000 x 2,000 m. Grid-cell size = 5 m.]]
[[File:UK_test_4.gif|right|Animation of the test result for case 4, generated by the {{software}}. Map dimensions = 1,000 x 2,000 m. Grid-cell size = 5 m.]]
[[File:hydrograph_case4_ukbm.png|thumb|center|Figure (b): Hydrograph applied as inflow boundary condition.]]
[[File:hydrograph_case4_ukbm.png|thumb|center|Figure (b): Hydrograph applied as inflow boundary condition.]]
Line 14:
Line 12:
==Boundary and initial condition==
==Boundary and initial condition==
*''Inflow boundary condition as shown in Figure (b). Table provided as part of dataset.''
* Inflow boundary condition as shown in Fig. (b)
*''All other boundaries are closed.''
* All other boundaries are closed
*''Initial condition: Dry bed.''
* Initial condition: dry bed
==Parameter values==
==Parameter values==
*''Manning’s n: 0.05 (uniform)''
* Manning’s n: 0.05 (uniform)
*''Model grid resolution: 5m (or ~80000 nodes in the area modelled)''
* Model grid resolution: 5m (or ~80000 nodes in the area modelled)
*''Time of end: the model is to be run until time t = 5 hours (if an alternative end time is used run times must be reported for t=5 hours)''
* Time of end: the model is to be run until time t = 5 hours (if an alternative end time is used run times must be reported for t=5 hours)
==Required output==
==Required output==
* ''Software package used: version and numerical scheme.''
* Software package used: version and numerical scheme.
* ''Specification of hardware used to undertake the simulation: processor type and speed,RAM.''
* Specification of hardware used to undertake the simulation: processor type and speed, RAM.
* ''Minimum recommended hardware specification for a simulation of this type.''
* Minimum recommended hardware specification for a simulation of this type.''
* ''Time increment used, grid resolution (or number of nodes in area modelled) and total simulation time to specified time of end.''
* Time increment used, grid resolution (or number of nodes in area modelled) and total simulation time to specified time of end.
* ''Raster grids (or TIN) at the model resolution consisting of:''
* Raster grids (or TIN) at the model resolution consisting of:
** ''Depths at times 30mins, 1 hour, 2 hours 3 hours, 4 hours.''
** Depths at times 30mins, 1 hour, 2 hours 3 hours, 4 hours.
** ''Velocities (scalar) at times 30mins, 1 hour, 2 hours 3 hours, 4 hours.''
** Velocities (scalar) at times 30mins, 1 hour, 2 hours 3 hours, 4 hours.
* ''Plots of velocity and water elevation versus time (suggested output frequency 20s) at the six locations represented in Figure (a) and provided as part of dataset.''
* Plots of velocity and water elevation versus time (suggested output frequency 20s) at the six locations represented in Figure (a) and provided as part of dataset.
: These locations are:
: These locations are:
{|class=wikitable
{|class=wikitable
Line 64:
Line 62:
==Dataset content==
==Dataset content==
*''Upstream boundary condition table (inflow vs. time). Filename: Test4BC.csv''
* Upstream boundary condition table (inflow vs. time). Filename: Test4BC.csv
*''Location of output points. Filename: Test4Output.csv''
* Location of output points. Filename: Test4Output.csv
''The model geometry is as specified in Section 2. No DEM is provided as the ground
The model geometry is as specified in Section 2. No DEM is provided as the ground
*Specification of hardware used to undertake the simulation:
* Specification of hardware used to undertake the simulation:
** Processor: Intel Xeon @2.10GHz x 8,
** Processor: Intel Xeon @2.10GHz x 8,
** RAM 62.8 GiB,
** RAM 62.8 GiB,
** GPU: 2x NVidia 1080
** GPU: 2x NVidia 1080
** Operating system: Linux 4.13
** Operating system: Linux 4.13
*Time increment used: adaptive:
* Time increment used: adaptive:
*Grid resolution: 5 m.
* Grid resolution: 5 m.
*Simulation time: 29 seconds for 900 timeframes
* Simulation time: 29 seconds for 900 timeframes
*Inlet q M3: 283723.8 m<sup>3</sup>
* Inlet q M3: 283723.8 m<sup>3</sup>
*Remaining volume water: 283606.9 m<sup>3</sup>
* Remaining volume water: 283606.9 m<sup>3</sup>
===Raster grids (or TIN) at the model resolution consisting of waterlevels and velocities===
===Raster grids (or TIN) at the model resolution consisting of waterlevels and velocities===
Revision as of 13:08, 2 May 2019
This page reports on the performance of the Tygron Platform's Water Module by means of the UK EA Benchmark Test 4 – Speed of flood propagation over an extended floodplain.
The objective of this test is to assess the package’s ability to simulate the celerity of propagation of a flood wave and predict transient velocities and depths at the leading edge of the advancing flood front. It is relevant to fluvial and coastal inundation resulting from breached embankments.[1]
Description
This test is designed to simulate the rate of flood wave propagation over a 1,000 x 2,000 m floodplain following a defence failure (Fig. (a)). The floodplain surface is horizontal, at datum (= 0 m). One inflow boundary condition will be used, simulating the failure of an embankment by breaching or overtopping, with a peak flow of 20 m3/s and time base of ~6 h. The boundary condition is applied along a 20-m line in the middle of the western side of the floodplain.[1]
Figure (a): Modelled domain and the locations of the 20-m line of inflow, 6 output points, and the aimed for 0.1-m and 0.2-m contour lines at t = 1 h (dashed) and t = 3 h (solid), respectively.Animation of the test result for case 4, generated by the Tygron Platform. Map dimensions = 1,000 x 2,000 m. Grid-cell size = 5 m.Figure (b): Hydrograph applied as inflow boundary condition.
Boundary and initial condition
Inflow boundary condition as shown in Fig. (b)
All other boundaries are closed
Initial condition: dry bed
Parameter values
Manning’s n: 0.05 (uniform)
Model grid resolution: 5m (or ~80000 nodes in the area modelled)
Time of end: the model is to be run until time t = 5 hours (if an alternative end time is used run times must be reported for t=5 hours)
Required output
Software package used: version and numerical scheme.
Specification of hardware used to undertake the simulation: processor type and speed, RAM.
Minimum recommended hardware specification for a simulation of this type.
Time increment used, grid resolution (or number of nodes in area modelled) and total simulation time to specified time of end.
Raster grids (or TIN) at the model resolution consisting of:
Depths at times 30mins, 1 hour, 2 hours 3 hours, 4 hours.
Velocities (scalar) at times 30mins, 1 hour, 2 hours 3 hours, 4 hours.
Plots of velocity and water elevation versus time (suggested output frequency 20s) at the six locations represented in Figure (a) and provided as part of dataset.
These locations are:
Point ID
X
Y
1
50
1000
2
100
1000
3
200
1000
4
300
1000
5
300
1000
6
300
1300
Dataset content
Upstream boundary condition table (inflow vs. time). Filename: Test4BC.csv
Location of output points. Filename: Test4Output.csv
The model geometry is as specified in Section 2. No DEM is provided as the ground
elevation is uniformly 0.[1]
Technical setup
The setup in this case is a flat surface. It does not require the import of a dem file, since all height values are set to 0.
Other stats:
The grid cell size: 5 m.
The area size: 1010x2010, which includes a border of 5 meters and the required domain of 1000m, x 2000m.
The measurement points have been put on the correct positions, see the image below.
Setup of case 4 used by the Tygron Platform
In order to regulate the water level according to the water level graph, we used the following setup: Only two inlets are used. These are put on the cells above and below the center line indicated by the green line. Each inlet had its own grid cell. The inlets were configured as:
