View source for TUFLOW 2D2D BC Advice

This section provides best practise advice for configuring TUFLOW 2D/2D boundaries. <br>

Multiple domain models are defined in TUFLOW using 2D Domain Blocks within the TCF file. Each Domain Block includes unique geometry control file, boundary condition file, initial water level and time step commands. All other commands (such as the boundary condition database, material file reference and simulation time commands) are defined outside the above mentioned 2D Domain Blocks. An example TCF file is shown below. Line 8 to 13 represents the first 2D domain. Line 15 to 20 is the second 2D domain block. <br>

[[File: 2D2D_Guidance_000.JPG |350px]]<br>

Some best practise advice for configuring a 2D /2D boundary is listed below:<br>
<ol>
<li>When one domain is nested within another, remember to deactivate the active cells in the parent domain (mesh) where the domains overlap. This is done in the parent domain TGC file.<br>

The <font color="blue"><tt>INVERT </tt></font> option can be used with <font color="blue"><tt>Read GIS CODE</tt></font> or <font color="blue"><tt>Read GIS Code BC</tt></font> to deactivate the active cells using the same GIS polygon that is used to define the active cells in the child domain. If INVERT is specified (eg. Read GIS Code Invert or Read GIS Code BC Invert), the active/inactive status of any Code polygon is reversed (i.e. a Code of 1 becomes 0, and a Code of -1 or 0 becomes 1).  This means that the same layer can be used by both TGC files when linking 2D domains.<br> <br>   

Correct deactivation of active cells in areas of overlap can be reviewed by viewing the [[TUFLOW_Check_Files | grd_check file]].<br> 
[[File: 2D2D_Guidance_001.JPG|400px]] 
[[File: 2D2D_Guidance_002.JPG|400px]]<br>

<li>Multiple 2D domain models use the 2d_bc “2D” link type as the boundary cells which transfer flow between the neighbouring domains.  
*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>  

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

* 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>
[[File: 2D2D_Guidance_003.JPG |400px]] <br>
Some 2d_bc “2D” link line definition advice is provided below:

'''<u>2D BC Line Orientation'''</u>'''<br>
The 2d_bc “2D” link line should be orientated perpendicular to the flow direction in areas of moderate to high velocity (>1m/s), such as across a river or creek.<br>

[[File: 2D2D_Guidance_004.JPG |400px]]<br>

[[File: 2D2D_Guidance_005.JPG |400px]]<br>

The 2d_bc “2D” link line can be orientated in any direction within floodplain areas with low velocity (<1m/s).  The 2d_bc “2D” link line “d” attribute should be used in this situation.<br>

'''<u>Line Vertex Location'''</u>'''<br>
2d_bc “2D” link line vertices are best located on ridges or embankments, particularly if the features become inundated and drowned out during a simulation.<br>
2d_bc “2D” link line “d” attribute can be used to insert additional “hidden” vertices (storage nodes) between the manually specified vertices location.<br>

In regions of low velocity (<1m/s), the “d” value should be no less than three times the distance of the larger cell resolution associated with the 2D/2D boundary.  For example, if the model adopts a 2.5m and 5m resolution, the “d” attribute should be set no smaller than 15m.<br>

In regions of high velocity (>1m/s), greater or no “d” value is common. Not specifying a “d” value will create a hidden 1D node at each vertex along the 2d_bc “2D” link line.<br>

'''<u>Storage Multiplier'''</u>'''<br>
2d_bc “2D” link line “a” attribute defines the storage allocation to each of the hidden 1D nodes. The default value is 2. Increasing the value may improve stability, though but may unacceptably attenuate results. Sensitivity testing has identified the following recommended maximum values:<br>
Low velocity area (<1m/s):   “a” <=3<br>
Low velocity area (>1m/s):   “a” <=6<br>

'''<u>Separate “2D” Link Lines'''</u>'''<br>
Consider using separate 2D boundary condition lines where there are unique flow paths separated by areas of dry land.<br>