TUFLOW 2D2D BC Advice: Difference between revisions
Content deleted Content added
Chris Huxley (talk | contribs) No edit summary |
Chris Huxley (talk | contribs) No edit summary |
||
Line 6:
Some best practise advice for configuring a 2D /2D boundary is listed below:<br>
<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>
Line 21:
<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>
Line 54:
'''<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>
</li>
| |||