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

Flood Modeller can also be dynamically linked to outflow directly to the 2D TUFLOW domain at the start or end of a floodFlood modellerModeller reach. This can relate to tributary channels, small draining channels, and also the main channel if exiting into a 2D estuarine environment for example.

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. Taking the Flood Modeller schematisation across to TUFLOW, as we saw in 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 recommendrecommended having in a separate file to the Flood Modeller Nodes) which has the same ID as the dummy HT boundary,. rememberRemember 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.