Check Files 2d dom - Revision history

Emilie Nielsen at 06:04, 16 February 2026

2026-02-16T06:04:07Z

← Older revision		Revision as of 16:04, 16 February 2026
Line 2:		Line 2:

	Certain model inputs 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>		Certain model inputs 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>
	Any geometry elevations and material datasets that extend outside the model domain~~, and~~ are simply ignored. Therefore, it is not necessary to trim a DEM to the model domain.<br>		Any geometry elevations and material datasets that extend outside the model domain are simply ignored. Therefore, it is not necessary to trim a DEM to the model domain.<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>		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>

Emilie Nielsen at 04:35, 5 August 2025

2025-08-05T04:35:38Z

← Older revision		Revision as of 14:35, 5 August 2025
Line 7:		Line 7:


	'''Attributes of ~~dom_check~~'''<br>		'''Attributes of _dom_check'''<br>
	{\| align="center" class="wikitable" width="75%"		{\| align="center" class="wikitable" width="75%"
	! style="background-color:#005581; font-weight:bold; color:white;"\| Attribute Name		! style="background-color:#005581; font-weight:bold; color:white;"\| Attribute Name

Emilie Nielsen at 04:25, 5 August 2025

2025-08-05T04:25:07Z

← Older revision		Revision as of 14:25, 5 August 2025
Line 1:		Line 1:
	Contains a rectangle for each 2D domain showing the location, orientation and size of the domain based on commands located within the ~~TGC~~ ~~file~~. Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>		Contains a rectangle for each 2D domain showing the location, orientation and size of the domain based on commands located within the TUFLOW Geometry Control File (.tgc). Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>
⚫	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 inputs 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>
⚫	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>
		⚫	Any geometry elevations and material datasets that extend outside the model domain, and are simply ignored. Therefore, it is not necessary to trim a DEM to the model 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>

	[[File:domcheck.png\|600px]]

	'''Attributes of dom_check'''<br>		'''Attributes of dom_check'''<br>
Line 18:		Line 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		{{Tips Navigation

Emilie Nielsen at 02:17, 30 July 2024

2024-07-30T02:17:21Z

← Older revision		Revision as of 12:17, 30 July 2024
Line 1:		Line 1:
	Contains a rectangle for each 2D domain showing the location, orientation and size of the domain based on commands located within the ~~.tgc~~ file. Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>		Contains a rectangle for each 2D domain showing the location, orientation and size of the domain based on commands located within the TGC file. Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>
	Certain model input must appear within the model domain. For example a boundary location must be within the model domain (if not a [[TUFLOW_Message_2001 \| ERROR 2001]] is generated).<br>		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>		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>

	For a [https://www.tuflow.com/Modules.aspx?M2DModule multiple domain model], there will be multiple rectangles - one for each 2D domain. <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. <br>
	<br>		<br>

Line 13:		Line 13:
	! style="background-color:#005581; font-weight:bold; color:white;" width=75%\| Attribute Description		! style="background-color:#005581; font-weight:bold; color:white;" width=75%\| Attribute Description
	\|-		\|-
	\| Domain_Index\|\|The index of the model domain. This is the order with <tt>Start 2D Domain == <Domain Name></tt> commands appears in the ~~.tcf~~ control file. For a single domain model this will be 1.		\| Domain_Index\|\|The index of the model domain. This is the order with <font color="blue"><tt>Start 2D Domain </font><font color="red">== </font><Domain Name></tt> commands appears in the TCF control file. For a single domain model this will be 1.
	\|-		\|-
	\| Domain_Name\|\|The name of the model domain, this is useful for multiple domain models. For single domain models this will be set to "Domain_001".		\| Domain_Name\|\|The name of the model domain, this is useful for multiple domain models. For single domain models this will be set to "Domain_001".
	\|}		\|}


			{{Tips Navigation
			\|uplink=[[TUFLOW_Check_Files \| TUFLOW Check Files]]
			}}

Emilie Nielsen at 04:57, 18 July 2024

2024-07-18T04:57:10Z

← Older revision		Revision as of 14:57, 18 July 2024
Line 3:		Line 3:
	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>		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>

	For a [~~http~~://www.tuflow.com/Modules.aspx?M2DModule multiple domain model], there will be multiple rectangles - one for each 2D domain. <br>		For a [https://www.tuflow.com/Modules.aspx?M2DModule multiple domain model], there will be multiple rectangles - one for each 2D domain. <br>
	<br>		<br>

Rachel at 11:18, 21 December 2015

2015-12-21T11:18:20Z

← Older revision		Revision as of 21:18, 21 December 2015
Line 5:		Line 5:
	For a [http://www.tuflow.com/Modules.aspx?M2DModule multiple domain model], there will be multiple rectangles - one for each 2D domain. <br>		For a [http://www.tuflow.com/Modules.aspx?M2DModule multiple domain model], there will be multiple rectangles - one for each 2D domain. <br>
	<br>		<br>

			[[File:domcheck.png\|600px]]

	'''Attributes of dom_check'''<br>		'''Attributes of dom_check'''<br>

Steph.dufour at 16:01, 25 September 2015

2015-09-25T16:01:14Z

← Older revision		Revision as of 02:01, 26 September 2015
Line 1:		Line 1:
	Contains a rectangle for each 2D domain showing the location, orientation and size of the domain. Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>		Contains a rectangle for each 2D domain showing the location, orientation and size of the domain based on commands located within the .tgc file. Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>
	Certain model input must appear within the model domain. For example a boundary location must be within the model domain (if not a [[TUFLOW_Message_2001 \| ERROR 2001]] is generated).<br>		Certain model input must appear within the model domain. For example a boundary location must be within the model domain (if not a [[TUFLOW_Message_2001 \| ERROR 2001]] 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>		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>

Par at 00:09, 10 September 2015

2015-09-10T00:09:25Z

← Older revision		Revision as of 10:09, 10 September 2015
Line 1:		Line 1:
			Contains a rectangle for each 2D domain showing the location, orientation and size of the domain. Within this domain, cells can be turned on or off, outside this domain no 2D calculations can be performed.<br>
	To be created
			Certain model input must appear within the model domain. For example a boundary location must be within the model domain (if not a [[TUFLOW_Message_2001 \| ERROR 2001]] 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>

			For a [http://www.tuflow.com/Modules.aspx?M2DModule multiple domain model], there will be multiple rectangles - one for each 2D domain. <br>
			<br>

			'''Attributes of dom_check'''<br>
			{\| align="center" class="wikitable" width="75%"
			! style="background-color:#005581; font-weight:bold; color:white;"\| Attribute Name
			! style="background-color:#005581; font-weight:bold; color:white;" width=75%\| Attribute Description
			\|-
			\| Domain_Index\|\|The index of the model domain. This is the order with <tt>Start 2D Domain == <Domain Name></tt> commands appears in the .tcf control file. For a single domain model this will be 1.
			\|-
			\| Domain_Name\|\|The name of the model domain, this is useful for multiple domain models. For single domain models this will be set to "Domain_001".
			\|}

Par: Created page with "To be created"

2015-06-11T02:31:14Z

Created page with "To be created"

New page

To be created