Tuflow

1D-2D Flood Modeller-TUFLOW: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1:
<ol>
=THIS PAGE IS CURRENTLY UNDER CONSTRUCTION=
 
=Introduction=
TUFLOW models can be configured to dynamically link to Flood Modeller by utilising a water level boundary to the 2D cells along the 1D/2D interface. In the 2D boundary condition (2d_bc) GIS layer, the location at which this link occurs is defined. The 2D water level applied at the 2D boundary cells is calculated by the Flood Modeller 1D model. The terminology used in TUFLOW is a '''HX''' type boundary on the 2D cells, with the '''H''' indicating that a '''H'''ead (water level) boundary is used and the '''X''' indicating the value is coming from an e'''X'''ternal model (in this case Flood Modeller).
Line 25 ⟶ 23:
<br>
 
The digitised direction of the HX and CN lines is not important. The CN lines however should be digitised approximately perpendicular to the direction of flow. Two CN lines are digitised for each node and snapped to the HX boundary lines along the left and right banks at vertices. Both CN and HX lines are digitised within the same 2d_bc file, on a basic approach, you only need to input the '''type''' attribute (either '''CN''' or '''HX'''). It is also recommended to input an '''f''' attribute value of '''1''' for CN lines for clarity, however if left at zero TUFLOW will by default change this value to 1. There are a range of Flags that can be used within the 2d_bc file, also D values to change elevations of the link cells and also A values to change the storage across the cells. Further information on these can be found within the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW manualManual]</u>.
<br>
The HX boundary lines should be digitised along the top of each bank such that the width between the lines approximately correlates to the width of the 1D channel. This is important so as not to either over/under compensate flow area between the two solvers.
Line 42 ⟶ 40:
<br>
 
The image below shows the representation within Flood Modeller and TUFLOW of a simple flume model. As you can see in Flood Modeller, the end open channel section '''FMT_003''' links directly to a spill unit, housing the same cross-section data, which then links to a dummy HT boundary unit. This dummy unit is left empty and works as a link between Flood Modeller and TUFLOW. TakingTo connect the Flood Modeller schematisation1D acrossnetwork to TUFLOW, assimilar we saw into the section above, the open channel section is linked via a 1D node and 2d_bc CN/HX connection. The SX link comes into play by having another 1D node (which, for clarity, it is recommended having a separate file to the Flood Modeller Nodes) which has the same ID as the dummy HT boundary. Remember that Flood Modeller is case sensitive so name exactly as is in Flood Modeller. As the connection between the open channel section '''FMT_003''' and the dummy boundary happens in Flood Modeller, no literal link is needed between these in the TUFLOW GIS files. All that is needed otherwise is a 2d_bc file with a CN/SX link snapped to the dummy boundary node, this again can be in a separate file to the CN/HX links for clarity or can be in the same file.
<br>
[[File:FMT LINK SX.png|900px]]
Line 53 ⟶ 51:
 
=Summary=
1D Flood Modeller and 2D TUFLOW models can be dynamically coupled to enable a bi-directional connection between the two software using either HX or SX links. The linkage take place when an Flood Modeller node is snapped to a HX or SX boundary, this can be via a CN connection link. The dynamic coupling allows full integration between Flood Modeller 1D networks and full floodplain modelling in TUFLOW 2D to capture complex overland flows.
Retrieved from "https://wiki.tuflow.com/1D-2D_Flood_Modeller-TUFLOW"