Check Files 2d dom: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
Line 1:
Contains a rectangle for each 2D domain showing the location, orientation and size of the domain based on commands located within the
Certain model input must appear within the model domain. For example a boundary location must be within the model domain (if not a <u>[[TUFLOW_Message_2001 | ERROR 2001]]</u> is generated).<br>▼
The geometry elevation and material datasets can extent outside the model domain, and are simply ignored. Therefore, it is not necessary to trim a DEM to the model domain.<br>▼
▲Certain model
For a <u>[https://www.tuflow.com/Modules.aspx?M2DModule multiple domain model]</u>, there will be multiple rectangles - one for each 2D domain. <br>▼
▲
<br>▼
▲For a <u>[https://www.tuflow.com/Modules.aspx?M2DModule multiple domain model]</u>, there will be multiple rectangles - one for each 2D domain. For a Quadtree model, there will be two rectangles: one for the model extent and one for the 1st nesting level (all active cells). <br>
'''Attributes of
{| align="center" class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;"| Attribute Name
Line 18 ⟶ 17:
|}
In the image below, a _dom_check file is shown. The 2d_code layer has also been included to show the active cells. <br>
▲<br>
[[File:2d_dom_check_01a.png]]<br>
<br>
{{Tips Navigation
| |||