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 1:
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
▲[[File: 2D2D_Guidance_000.JPG |400px]]<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 INVERT option can be used with Read GIS CODE or Read GIS Code BC 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>
Line 16 ⟶ 15:
[[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:<br>
<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>
| |||