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 |
||
| (8 intermediate revisions by the same user not shown) | |||
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 is defined using <font color="blue"><tt> Start 2D Domain </tt></font> <font color="red"><tt>== </tt></font> <tt> <name> </tt> and <font color="blue"><tt> End 2D Domain </tt></font> commands. Unique geometry control file, boundary condition file, initial water level, plot output and time step commands are defined within each domain block. All other commands (such as the boundary condition database, material file references,
[[File: 2D2D_Guidance_000.JPG |450px]]<br>
Some
<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>
Line 41:
'''<u>2D BC "2D" Line Vertex Location and Hidden 1D Node Options'''</u>'''<br>
As previously mentioned, flow is transferred between both domains via a series of hidden 1D nodes. TUFLOW creates these at each vertex along the 2d_bc "2D" link line and also at a regular interval, as defined by the “d” attribute.<br>
2d_bc “2D” link line vertices are best located on ridges or embankments, including features that become inundated and drowned out during a simulation. 2d_bc “2D” link line “d” attribute can be used to insert additional hidden 1D nodes between the manually specified vertices location.<br>▼
▲2d_bc “2D” link line vertices are best located on ridges or embankments, including features that become inundated and drowned out during a simulation
* In regions of low velocity (<0.5m/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>▼
[[File: 2D2D_Guidance_006.JPG |400px]]<br>▼
* In regions of moderate to high velocity (>0.5m/s),
[[File: 2D2D_Guidance_007.JPG |400px]]<br>
▲*
▲[[File: 2D2D_Guidance_006.JPG |400px]]<br>
'''<u>2D BC "2D" Line Storage Multiplier Options'''</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 (<0.5m/s): “a” <=3<br>▼
* Moderate to high velocity area (>0.5m/s): “a” <=6<br>
▲* Low velocity area (<0.5m/s): “a” <=3<br>
'''<u>Separate 2D BC “2D” Link Lines'''</u>'''<br>
Line 57 ⟶ 61:
[[File: 2D2D_Guidance_008.JPG |400px]]<br>
</li>
</ol>
<li> Example 2D/2D models are available for download from the [[Example_Models_Home_page | Example Models]] page of the Wiki.
</li>
</ol>
| |||