Difference between revisions of "TUFLOW 2D Cell Size Selection"

From Tuflow
Jump to navigation Jump to search
Line 118: Line 118:
 
{| class="wikitable "  
 
{| class="wikitable "  
  
| '''Cell Resolution, Model Size and Run Time''' || '''Simulation Run Time <br> (hrs)'''|| '''Difference in Water Level Result <br> (Relative to 10ft Resolution Model)''' || '''Sample Peak Water Level Result'''
+
| '''Cell Resolution, Model Size and Simulation Run Time''' || '''Simulation Run Time <br> (hrs)'''|| '''Difference in Water Level Result <br> (Relative to 10ft Resolution Model)''' || '''Sample Peak Water Level Result'''
 
|-
 
|-
 
| '''10ft (3.0m) cell size <br> 20.3hr run time'''||N/A <br><br>The histogram graphs below are calculated by subtracting <br>their peak (maximum) flood level result from the 10ft cell <br>resolution model results shown to the right || [[File:Mesh_Converge_Direct_Rainfall_10ft_002.png|500px]]  
 
| '''10ft (3.0m) cell size <br> 20.3hr run time'''||N/A <br><br>The histogram graphs below are calculated by subtracting <br>their peak (maximum) flood level result from the 10ft cell <br>resolution model results shown to the right || [[File:Mesh_Converge_Direct_Rainfall_10ft_002.png|500px]]  
 
|-
 
|-
| '''12.5ft (3.8m) cell size<br>5,821,533 cell count<br> 13.9hr run time'''||[[File:Mesh_Converge_Direct_Rainfall_12ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_12ft_002.png|500px]]
+
| '''12.5ft (3.8m) cell size<br>5,821,533 cell count<br> 13.9hr simulation run time'''||[[File:Mesh_Converge_Direct_Rainfall_12ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_12ft_002.png|500px]]
 
|-
 
|-
| '''15ft (4.6m) cell size<br>3,725,781 cell count<br> 9.2hr run time'''||[[File:Mesh_Converge_Direct_Rainfall_15ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_15ft_002.png|500px]]
+
| '''15ft (4.6m) cell size<br>3,725,781 cell count<br> 9.2hr simulation run time'''||[[File:Mesh_Converge_Direct_Rainfall_15ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_15ft_002.png|500px]]
 
|-
 
|-
| '''20ft (6.1m) cell size<br>2,587,629 cell count<br> 3.8hr run time'''|| [[File:Mesh_Converge_Direct_Rainfall_20ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_20ft_002.png|500px]]
+
| '''20ft (6.1m) cell size<br>2,587,629 cell count<br> 3.8hr simulation run time'''|| [[File:Mesh_Converge_Direct_Rainfall_20ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_20ft_002.png|500px]]
 
|-
 
|-
| '''30ft (9.1m) cell size<br>1,455,869 cell count<br> 1.4hr run time'''|| [[File:Mesh_Converge_Direct_Rainfall_30ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_30ft_002.png|500px]]
+
| '''30ft (9.1m) cell size<br>1,455,869 cell count<br> 1.4hr simulation run time'''|| [[File:Mesh_Converge_Direct_Rainfall_30ft_HIST.png|550px]] || [[File:Mesh_Converge_Direct_Rainfall_30ft_002.png|500px]]
 
|-
 
|-
| '''50ft (15.2m) cell size<br>232,957 cell count<br> 0.5hr run time''' ||[[File:Mesh_Converge_Direct_Rainfall_50ft_HIST.png|550px]] || [[File:Mesh Converge Direct Rainfall 50ft 002.png|500px]]
+
| '''50ft (15.2m) cell size<br>232,957 cell count<br> 0.5hr simulation run time''' ||[[File:Mesh_Converge_Direct_Rainfall_50ft_HIST.png|550px]] || [[File:Mesh Converge Direct Rainfall 50ft 002.png|500px]]
 
|}
 
|}
  
 
== Test Case 2 - Discussion==
 
== Test Case 2 - Discussion==

Revision as of 16:39, 17 August 2018

This page is currently under construction.

Introduction

This page of the TUFLOW Wiki discusses 2D cell size convergence. Cell size convergence refers to the tendency for model results to trend towards a common answer as cell size decreases. This behaviour occurs due to topographic features that influence the hydraulic flow behaviour better approximating reality as resolution increases. The series of creek cross-section images below demonstrate this. As model resolution increases from 20m to 5m the modelled topography progressively matches the real-world geometry more closely.
Mesh Converge XS 20m.pngMesh Converge XS 10m.pngMesh Converge XS 05m.png

Unfortunately it isn't practical for all models to be designed at an infinitely fine resolution due to the impact it has on simulation speed. Increasing a model resolution will make a simulation run slower. As a rule of thumb, halving the cell size in a model will typically increase the simulation run time by a factor 8. This is due to the number of cells increasing by a factor of (4) four and the necessity for a calculation timestep half that of the larger resolution, translating to (2) twice the number of calculations (4 x 2 = 8).

The challenge for modellers is, knowing what resolution is necessary to achieve results that are fit for purpose with sufficient accuracy and having a model that can run within a reasonable time (i.e. hours, not days).

Australian Rainfall and Runoff Guideline - Two Dimensional Modelling in Urban and Rural Floodplain provides some recommendations on this topic. It states:

The resolution of a 2D model grid/mesh determines the scale of physical features and flow behaviour that can be modelled for a given study area. Selection of an appropriate resolution is generally driven by a combination of the following factors:
* The scale of topographic and/or flow phenomena to be modelled
* The desired level of detail to be achieved in the model outputs
* The length of event time and consequent run time
* The size of the area of interest
Details of the model schematisation process including resolution aspects are described in Chapter 6. Chapter 7 also highlights the importance of grid/mesh resolutions in achieving manageable run times to maximise calibration outcomes. Table 10-2 (below) provides guidance on levels of model resolution that may be appropriate in certain typical situations.
Modelling Case Typical 2D Cell Resolution
Flow in Channel In order to adequately resolve flow in a channel it is desirable to provide at least 5 grid/mesh elements laterally across the channel
Urban Overland Most urban flood models employ grid/mesh resolutions of 2m to 5m.
Flow in Floodplain Rural floodplain models typically employ grid/mesh resolutions of 10m and 50m (although resolutions up to 200m have been used) depending on the size of the area to be analysed, the characteristics/dimensions of the floodplain and the desired level of output detail.
Lakes and Estuaries These situations often include areas of open water where less detail is required than along the water body boundary. Such situations are well suited to a flexible mesh rather than fixed grid based model as the mesh is able to incorporate a change of resolution across the model domain. Element resolutions for these models can span the full range as described above depending on project requirements.
Flow Over and Embankment Embankments effectively act as weirs in the floodplain context. Many 2D modelling packages have automatic or manually activated corrections that compensate for the error in head loss typically associated with modelling broad-crested weir flow with a 2D scheme. For practical purposes, a single 2D element is generally adequate to represent the impact of a levee, road or railway embankment. The resolution of these elements is generally not a significant limitation on the schematisation of most domains.

This Wiki page uses two test cases to discuss this topic. Quantitative results are presented demonstrating how and when resolution assumptions have a tangible impact on model results. TUFLOW HPC and it's GPU Module have been used for all simulations documented in the following sections. The computer used for the modelling has a NVIDIA GeForce GTX 1080 Ti GPU card.

Test Case 1 - Rural Dam Break

This test case has been sourced from the UK Environment Agency 2D Hydraulic Model Benchmark Test dataset. It is referred to as Test 5 in the Environment Agency (EA) dataset. The EA designed to simulate flood wave propagation down a river valley following the failure of a dam. The valley DEM is ~0.8 km by ~17 km and the valley slopes downstream on a slope of ~0.01 in its upper region, easing to ~0.001 at lower elevations. The model uses a single manning's n value of 0.04 across the entire domain. The model topography and EA reporting points are shown below.
Mesh Converge Model Description 001.png Mesh Converge Model Elevation 001.png

The model has a single inflow at the top of the catchment. The inflow hydrograph that has been used is shown below. Although the inflow only introduces water into the model for 100 minutes the model has been run for a simulation period of 30 hours. This was a requirement in the original EA model benchmark documentation.
Mesh Converge Model Inflow 001.png
Mesh Converge SMS 0.5hr.pngMesh Converge SMS 1.5hr.pngMesh Converge SMS 2.5hr.pngMesh Converge SMS 4hr.png

The EA benchmark testing originally assumed a 50m cell resolution. For the purpose of this assessment a range of cell sizes have been used to determine the impact changing grid resolution has on the model results. The following grid resolutions were used:

  • 10m (33ft) resolution - 188,240 cell count
  • 20m (66ft) resolution - 47,080 cell count
  • 50m (164ft) resolution - 7,540 cell count
  • 100m (328ft) resolution - 1,880 cell count
  • 150m (492ft) resolution - 840 cell count
  • 200m (656ft) resolution - 480 cell count
  • 250m (820ft) resolution - 300 cell count

Test Case 1 - Results

In the interest or keeping this page brief we have focused our result presentation on EA reporting points 4 and 5. Their location furthest downstream in the catchment makes them the most sensitive of all EA 7 reporting points. This is due to any divergence in result caused by poor representation of the upstream topography accumulating, amplifying the result difference associated with a change in cell resolution at these selected locations.

Results are presented below. Although the figures are shown in sequence (from fine to coarse resolution), the results are overlayed on one another moving through the dataset so it is obvious if poor convergence occurs.

Cell Size Location 4 Result Location 5 Result Mesh Resolution Figure
10m Mesh Converge Exg P4 010.png Mesh Converge Exg P5 010.png Mesh Converge Grid 010.png
20m Mesh Converge Exg P4 020.png Mesh Converge Exg P5 020.png Mesh Converge Grid 020.png
50m Mesh Converge Exg P4 050.png Mesh Converge Exg P5 050.png Mesh Converge Grid 050.png
100m Mesh Converge Exg P4 100.png Mesh Converge Exg P5 100.png Mesh Converge Grid 100.png
150m Mesh Converge Exg P4 150.png Mesh Converge Exg P5 150.png Mesh Converge Grid 150.png
200m Mesh Converge Exg P4 200.png Mesh Converge Exg P5 200.png Mesh Converge Grid 200.png
250m Mesh Converge Exg P4 250.png Mesh Converge Exg P5 250.png Mesh Converge Grid 250.png

Test Case 1 - Discussion

The graphed results indicate convergence is observed for all cases with a cell resolution equal to or less than 100m. The grid figures presented to the right of the graphs suggest the 100m cell resolution case has approximately (4) four cells laterally across the valley that the dam break flow is contained within. Although the 400-600m wide valley isn't a traditional creek or river channel, the scale of flow associated with the dam break means the valley is behaving like one. Minor topographic features within the valley are too small to have a significant impact on the flood behaviour for flow conditions of this large magnitude. This result trend is consistent with the Australian Rainfall and Runoff (ARR) cell size recommendation for the flow in a channel, "In order to adequately resolve flow in a channel it is desirable to provide at least 5 grid/mesh elements laterally across the channel".

Simulation time can influence model resolution selection. This is not the case in this situation. All models have run in under 5 minutes using TUFLOW HPC's GPU hardware module.

Cell Size Model Size
(Cell Count)
Simulation Run Time
(seconds)
Judgement of Convergence
(Yes / No)
10m (33ft) 188,240 284 Yes
20m (66ft) 47,080 98 Yes
50m (164ft) 7,540 32 Yes
100m (328ft) 1,880 15 Yes
150m (492ft) 840 10 No
200m (656ft) 480 9 No
250m (820ft) 300 7 No

Since simulation time is not a limiting factor in this case selection of cell size only needs to consider the result accuracy. What is appropriate in terms of accuracy is influenced by the intended use of the model. For example, if lot scale assessment of inundation and structural damage risk is required, selection of the 10m cell size may be appropriate. Alternatively, if the model is only intended to inform broad-scale risk, the 50m or 100m cell size may be sufficient.

Test Case 2 - Urbanised Catchment

This test case uses a hypothetical urban model. The model encompasses the entire catchment and covers an area of approximately 21miles2 (54km2). Development within the catchment ranges from rural undeveloped in the mountainous upper catchment and dense urban development in the lower catchment.
Mesh Converge Direct Rainfall Topo.pngMesh Converge Direct Rainfall Manning n.png
A direct rainfall approach has been used, applying rainfall directly to every cell within the model. The event hyetograph is a hypothetical 24 hour extreme event. The simulation duration has also been set to 24 hours.
Note, if you are unfamiliar with the direct rainfall modelling approach, this Hydrology and Water Symposium paper introduces the concept.
Image of Rainfall Hyetograph
The following grid resolutions were used to test the impact of cell size on the assessment results and simulation time:

  • 10ft (3.0m) resolution - 5,821,533 cell count
  • 12.5ft (3.7m) resolution – 3,725,781 cell count
  • 15ft (4.6m) resolution – 2,587,629 cell count
  • 20ft (6.1m) resolution – 1,455,869 cell count
  • 50ft (15.2m) resolution – 232,957 cell count

Test Case 2 - Results

Cell Resolution, Model Size and Simulation Run Time Simulation Run Time
(hrs)
Difference in Water Level Result
(Relative to 10ft Resolution Model)
Sample Peak Water Level Result
10ft (3.0m) cell size
20.3hr run time
N/A

The histogram graphs below are calculated by subtracting
their peak (maximum) flood level result from the 10ft cell
resolution model results shown to the right
Mesh Converge Direct Rainfall 10ft 002.png
12.5ft (3.8m) cell size
5,821,533 cell count
13.9hr simulation run time
Mesh Converge Direct Rainfall 12ft HIST.png Mesh Converge Direct Rainfall 12ft 002.png
15ft (4.6m) cell size
3,725,781 cell count
9.2hr simulation run time
Mesh Converge Direct Rainfall 15ft HIST.png Mesh Converge Direct Rainfall 15ft 002.png
20ft (6.1m) cell size
2,587,629 cell count
3.8hr simulation run time
Mesh Converge Direct Rainfall 20ft HIST.png Mesh Converge Direct Rainfall 20ft 002.png
30ft (9.1m) cell size
1,455,869 cell count
1.4hr simulation run time
Mesh Converge Direct Rainfall 30ft HIST.png Mesh Converge Direct Rainfall 30ft 002.png
50ft (15.2m) cell size
232,957 cell count
0.5hr simulation run time
Mesh Converge Direct Rainfall 50ft HIST.png Mesh Converge Direct Rainfall 50ft 002.png

Test Case 2 - Discussion