View source for TUFLOW 1D2D Boundary Configuration Guidance

= Stability of 1D/2D SX Configurations =
With the release of TUFLOW HPC (in 2017) and the continuous improvement of GPU hardware compute capability, there is an industry trend for models of higher resolution. As such, the 2D cell size in flood models is becoming smaller and smaller. Testing has shown in some instances reducing the 2D cell size may lead to model instability at 1D/2D SX locations. This page discusses this observation, the cause and available methods to  correct the instability. Topics of discussion include: <br>
* 1D timestep selection <br>
* Use of a 1D Node to assign 1D/2D boundary condition cells <br>
* Use of SX 1D/2D boundary condition lines <br>
* Application of a SX Storage Factor <br>
* Use of SX 1D/2D boundary condition polygons <br>
These methods can be applied to both TUFLOW Classic and HPC using the 2017 release or newer. For the purpose of this demonstration TUFLOW HPC has been used.

==Base Case==
A simple 1D/2D model has been constructed based on <u>[[Tutorial_M03 | Tutorial Module 3]]</u>. SX points have been used to connect a 1D culvert (FC01.2) with the 2D domain. The culvert details are: <br>
* Type = R (Rectangular)
* Number of barrels = 5
* Width per culvert = 2.4m (i.e. the total width of the bank of culverts is 12m)
* Height = 1.2m
Three 2D cell resolutions have been tested: 5m, 2m and 1m. The figure below shows the 1D/2D linking cells of the culvert.<br> 
[[File:1D2D_Model_Stability_001.png|500px]]<br>
 
This figure highlights the variation in 2D storage volume associated with the 1D/2D SX connections. The storage associated with a single 1D/2D linking cell for each cell size is:
* 5m 2D cell size = 25m<sup>2</sup>/m
* 2m 2D cell size = 4m<sup>2</sup>/m
* 1m 2D cell size = 1m<sup>2</sup>/m <br>
The modelled flow rates in the culvert are presented in the figure below.<br>
[[File:1D2D_Model_Stability_002.png|500px]]<br>
Two key observations can be made:<br>
* The 1D/2D link associated with the 1m 2D cell size is not stable.
* The flow rate results through the 1D culvert decrease with cell size. This is an issue. It indicates cell size convergence (i.e. consistent results independent of cell size) was not achieved. This is caused by the 2D storage volume associated with the 1D/2D connection being insufficient compared to the flow area associated with the 1D channel (12m width). As a result, the 2D boundary cell is the model feature limiting flow exchange between the 1D and 2D, rather than the dimension and hydraulics associated with the 1D structure.
''Please note that a culvert connection to a single 2D cell is provided here as an example. Connections with a 2D cell width less than the structure face width is not recommended. For example, a 12m wide set of culverts should be connected to at least 12 x 1m cells, 6 x 2m cells and 3 x 5m cells respectively. Examples how this can be done are shown in the following sections.'' <br>

==1D Timestep==
Selection of a 1D timestep that is too large can cause instability. The <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> includes some discussion on 1D timestep selection and courant number criterion. Conceptually a 1D timestep should be chosen to ensure a volume of water does not travel a distance longer than the shortest 1D channel within a model. For example, if the flow velocity and celerity is 5m/s and the 1D channel length is 10 metres, the 1D timestep should be less than 2 seconds. To provide some tolerance for faster flows associated with different flood events, a timestep of 1 second may be appropriate. 

During real world studies it is good practice to check the 1D timestep sensitivity: <br>
* Select a 1D timestep based on the smallest channel length and the expected flow velocity within your model. <br>
* Trial using a smaller 1D timestep to establish whether the problem is timestep related. <br>
If the instability is not timestep related, reducing the timestep should have a negligible change in results. <br>

A 1s 1D timestep has been used for this testing. It is appropriate for the 1D features being modelled.<br>

''Note: The 1D timestep for a HPC 1D/2D linked model is the 'limiting' timestep the 1D solver can use. The 1D solver has been reconfigured to act as an adaptive/varying timestep solution, and the 1D timesteps are set at different multiple of 2D timesteps. <br>''

==1D/2D SX Links Defined Using 1D Nodes (1d_nwk) ==
As of the 2017 release of TUFLOW, nodes within a 1d_nwk file can be used to specify the location of 1D/2D boundary cells and also automatically assign an estimate of the appropriate number of 2D cells for the connection. 

For a culvert, this is done by snapping a 1d_nwk point feature to the end of the 1d_nwk line feature and setting the 1d_nwk point attributes:
* Type =  Node
* UCS = T
* CONN_1D_2D = SX 
2D cells will be automatically selected as a 1D/2D SX links. The number of cells that are associated with the 1D/2D SX link will be defined by the nodal storage of the 1D channel. The figure below shows the 1D/2D linking cells in the 5m, 2m and 1m cell size models using this method.<br>

[[File:1D2D Model Stability 004.png|500px]]<br>


The modelled flow rates are shown in the figure below. The figure demonstrates, comparable peak flow rates are obtained regardless of the cell size (i.e. cell size convergence is demonstrated). The stability in the 1m cell size case has been improved markedly, though there are still some oscillations at low flows. <br>

[[File:1D2D Model Stability 005.png|500px]]<br>

==SX Boundary Lines (2d_bc)==
2d_bc SX line features are often used to connect 1D structure to the 2D domain if the structure width is greater than one 2D cell wide (e.g. <u>[[Tutorial_M02 |Tutorial Module 02]]</u>). This configuration not only increases the number of 1D/2D linking cells, it also has the added benefit of defining the 1D/2D boundary cells at the approximate location of the inlet/outlet of the 1D culvert. An additional benefit of this approach is that the "width" of the linking cells remains similar in length and location irrespective of 2D cell size.  <br>

The 1D/2D linking cells in the 5m, 2m and 1m cell size models are shown in the the figure below.<br>

[[File:1D2D_Model_Stability_006.png|500px]]<br>

The result below indicates cell size convergence is achieved, the flow oscillations have also been reduced (compared to the model using the 1d_nwk Node 1D/2D link method).<br>

[[File:1D2D Model Stability 007.png|500px]]<br>

===SX Storage Factor (2d_bc)===
A new "SX Storage Factor" feature was been added to TUFLOW in the 2017 release. As the name suggests, this feature adds additional storage to the 1D/2D linking (SX) cells. The storage factor is specified by adjusting the 2d_bc "a" attribute value. "a" is treated as a storage multiplier. For example, specifying an "a" value of 2.0 doubles the storage associated with the 1D/2D boundary. Note that an "a" value of 0.0 assumes a multiplier of 1.0.<br>

The modelling result with an "a" value of 2.0 are presented in the figure below. The flow rate is now very smooth and the difference in peak flow rates is negligible.<br>
[[File:1D2D Model Stability 008.png|500px]]<br>
  
Testing has shown small increases in storage usually has immeasurable effect on results, however, sensitivity testing is recommended to confirm this assumption in different models. For example, if specifying an "a" value of 2 stabilises the link, sensitivity test by increasing "a" further to 3. If there is no appreciable or unacceptable change in results, increasing the storage by a factor within these bounds can be considered to have negligible effect on results.

==SX Boundary Regions/Polygons (2d_bc)==
SX boundary regions/polygons are another feature that was added for the 2017 TUFLOW release. Polygons can now be used as a 2d_bc SX input. All cells with a cell centre within the polygon are set as SX cells. A CN line is required to connect the 1D feature to the SX polygon, snapped to any vertex on the perimeter of the polygon. An example of this configuration and the 1D/2D linking cells produced in the 5m, 2m and 1m cell size models are shown in the figure below.<br>

[[File:1D2D_Model_Stability_009.png|500px]]<br>

The modelling results are presented in the figure below. Again, cell size convergence is demonstrated and the oscillations at low flow is removed.<br>

[[File:1D2D Model Stability 010.png|500px]]<br>

==Conclusion==
When the spatial resolution of a model is increased (i.e. cell size reduced) review of result sensitivity at 1D/2D SX link locations is recommended. This can be done quickly and easily by plotting 1D results and checking for unwanted oscillations. This page demonstrated some useful methods for stabilising 1D/2D boundary (SX) links, in particular where the 1D structure is large in comparison to the 2D cell size. Available options that were introduced included reviewing the 1D timestep, using 1D nodes to define the 1D/2D boundary link, SX boundary lines, SX storage factors and SX boundary polygons.
<br>
<br>

= Stability of 1D/2D HX Configurations in TUFLOW HPC =
TUFLOW HPC inflow boundaries may experience recirculation when a uniform elevation is defined along the length of the boundary. This problem may also occur along HX boundaries in 1D-2D linked models that outflow from the 1D to the 2D domain. This is not a common configuration, though may occur when using a 1D channel to convey the flow from a dam break or similar along a defined channel onto floodplains in the 2D domain.

Consider setting up the 1D-2D linking shown in the figure below; the HX boundary “HXb1” shown in red is connected at each end to the same 1D node, whereas the remaining HX boundaries shown in purple are connected at each end to different 1D nodes. In the case that the flow is leaving the 2D domain to enter the 1D channel, the boundary is usually stable without energy correction, however for the reverse case, under high flow velocity conditions, the boundary may display instability or recirculation. If this does occur the problem may be remedied via an energy correction, using the command 
<font color="blue"><tt>HPC Boundary Approach </font> <font color="red">==</font> Method B</tt>. Note that this will likely cause water level lines to display some discontinuity between the 1D and 2D domain across the boundary.

[[File:1D2DHXEnergyCorrection.png|500px]]<br>

=1D/2D Modelling Webinar=
Guidance on 1D channel / 2D domain external linking, nesting a 1D channel within a 2D domain, embedding a 1D culvert within a 2D embankment, underground pipe network modelling: <u>[https://www.youtube.com/watch?v=CNhj3PyLD-Q&feature=youtu.be Webinar Link:  1D/2D Linking Guidance]</u><br>


=Common Questions Answered (FAQ)=
==Are HX and SX boundaries treated the same as 2D domain cells?==
HX cells are treated the same computationally as other H boundaries (HT, HS, HQ).  Momentum preservation across a H boundary/link is approximated by assuming the 2D velocity field across the H line is preserved.  The flow across a HX line is transmitted to the 1D node/unit and is effectively a 1D Q boundary.<br>
SX cells are normal (active) cells that can receive/send a flow from a connected 1D element.  The water levels in the 2D SX cell(s) are sent to the 1D node/unit as a 1D H boundary.  1D H boundaries don’t contribute to storage so the storage of the connected 1D node is not used (head boundaries of all types, 1D or 2D of any software, do not contribute to storage as the water level is set rather than solve the mass balance equation as done for normal nodes).  There is no momentum assumed or transferred to SX cells.<br>
:*'''HX''' = Water level ('''H''') set by an e'''X'''ternal computation or data feed.
:*'''SX''' = Flow as a '''S'''ource (flow without a horizontal direction, e.g. rainfall) from an e'''X'''ternal computation or data feed.
==What are the differences between how HX and SX boundary cells treat volume and transfer flow?==
HX are effectively head boundaries and do not contribute to storage (head boundaries of all types, 1D or 2D of any software, do not contribute to storage as the water level is set rather than solve the mass balance equation as done for normal cells).  SX cell storage is used as per a normal cell.  <br>
No flow is transmitted across HX cell sides except for those sides adjoining a normal cell (i.e. active Code 1 cells).  SX cells are like normal cells and can transmit across all four sides, i.e.:
:*HX cells can transmit water to/from an adjoining SX cell.  
:*HX cells can’t transmit to an adjoining HX cell.  
:*SX cells can transmit to an adjoining SX cell.
<br>
{{Tips Navigation
|uplink=[[ HPC_Modelling_Guidance | Back to HPC Modelling Guidance]]
}}