TUFLOW 2D2D BC Advice: Difference between revisions

<li> Multiple 2D domain models use the 2d_bc “2D” link type as the boundary cells which transfer flow between the neighbouring domains.

*<li> The file containing the GIS layer must be read into the TBC files of both 2D domains. For example, the command below would be read into both TBC files listed in the TCF file: <font color="blue"><tt> Read GIS BC </tt></font> <font color="red"><tt>== </tt></font> <tt> mi\2d_bc_2D_Link_001_L.mif </tt><br>

*<li> The 2d_bc “2D” link line should be snapped to the polygon defining the active/inactive area mentioned in bullet point 1.<br>

*<li> Flow is transferred between both domains via a series of hidden 1D nodes. The location of the hidden 1D nodes requires consideration. TUFLOW creates these at each vertex along the 2D link line and also at a regular interval, as defined by the “d” attribute. The hidden 1D nodes act as storage that convey the water from one 2D domain to the other. The water levels along the 2d_bc 2D link line are linearly interpolated using the water levels in the hidden 1D nodes. If in reality the water level profile is not close to linear between vertices, strange flow patterns may occur which can lead to model instability. As such, appropriate resolution of the hidden 1D nodes is an important feature of multiple 2D domain models. The TCF command <font color="blue"><tt>Reveal 1D Nodes</tt></font><font color="red"><tt>== </tt></font> <tt> ON </tt> can be used to view the hidden 1D nodes. The hidden nodes will be written to the nwk_N check layer. The 2D link can then be checked by viewing the _2d_to_2d_check layer which displays the 2D cells used to link the two domains together. <br>

Some 2d_bc “2D” link line definition advice is provided below:<br><br>