TUFLOW 2D2D BC Advice - Revision history

Anne.Kolega: e.g.

2026-04-01T04:37:45Z

e.g.

← Older revision		Revision as of 14:37, 1 April 2026
Line 9:		Line 9:
	<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>		<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 <font color="blue"><tt>INVERT </tt></font> is specified (eg. <font color="blue"><tt>Read GIS CODE INVERT</tt></font> or <font color="blue"><tt>Read GIS Code BC INVERT</tt></font>), 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>		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 <font color="blue"><tt>INVERT </tt></font> is specified (e.g. <font color="blue"><tt>Read GIS CODE INVERT</tt></font> or <font color="blue"><tt>Read GIS Code BC INVERT</tt></font>), 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>

	Correct deactivation of active cells in areas of overlap can be reviewed via the [[TUFLOW_Check_Files \| grd_check file]], shown below.<br>		Correct deactivation of active cells in areas of overlap can be reviewed via the [[TUFLOW_Check_Files \| grd_check file]], shown below.<br>
Line 18:		Line 18:
	\| Correct Configuration \|\| Incorrect Configuration		\| Correct Configuration \|\| Incorrect Configuration
	\|}		\|}

Anne.Kolega at 02:09, 27 February 2026

2026-02-27T02:09:28Z

← Older revision		Revision as of 12:09, 27 February 2026
Line 59:		Line 59:
	</li>		</li>
	</ol>		</ol>
	<li> Example 2D/2D models are available for download from the [[https://wiki.tuflow.com/TUFLOW_Example_Models Example Models]] page of the Wiki.		<li> Example 2D/2D models are available for download from the <u>[https://wiki.tuflow.com/TUFLOW_Example_Models Example Models]</u> page of the Wiki.
	</li>		</li>
	</ol>		</ol>

Anne.Kolega at 01:57, 27 February 2026

2026-02-27T01:57:30Z

← Older revision		Revision as of 11:57, 27 February 2026
Line 59:		Line 59:
	</li>		</li>
	</ol>		</ol>
	<li> Example 2D/2D models are available for download from the [[~~Example_Models_Home_page \|~~ Example Models]] page of the Wiki.		<li> Example 2D/2D models are available for download from the [[https://wiki.tuflow.com/TUFLOW_Example_Models Example Models]] page of the Wiki.
	</li>		</li>
	</ol>		</ol>

Anne.Kolega at 01:50, 27 February 2026

2026-02-27T01:50:21Z

← Older revision		Revision as of 11:50, 27 February 2026
Line 27:		Line 27:

	<li> Flow is transferred between both domains via a series of hidden 1D nodes. The location of the hidden 1D nodes requires consideration. 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. The hidden 1D nodes act as storage that convey the water from one 2D domain to the other. The water levels along the 2d_bc 2D link line are linearly interpolated using the water levels in the hidden 1D nodes. If in reality the water level profile is not close to linear between vertices, strange flow patterns may occur which can lead to model instability. As such, appropriate resolution of the hidden 1D nodes is an important feature of multiple 2D domain models. <br><br>		<li> Flow is transferred between both domains via a series of hidden 1D nodes. The location of the hidden 1D nodes requires consideration. 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. The hidden 1D nodes act as storage that convey the water from one 2D domain to the other. The water levels along the 2d_bc 2D link line are linearly interpolated using the water levels in the hidden 1D nodes. If in reality the water level profile is not close to linear between vertices, strange flow patterns may occur which can lead to model instability. As such, appropriate resolution of the hidden 1D nodes is an important feature of multiple 2D domain models. <br><br>
	The TCF command <font color="blue"><tt>Reveal 1D Nodes </tt></font><font color="red"><tt>== </tt></font> <tt> ON </tt> can be used to view the hidden 1D nodes. The hidden nodes will be written to the [[TUFLOW_Check_Files \| nwk_N_check]] layer. The 2D link can also be reviewed using the [[TUFLOW_Check_Files \| 2d_to_2d_check ]] layer. ~~Both~~ are shown below. <br>		The TCF command <font color="blue"><tt>Reveal 1D Nodes </tt></font><font color="red"><tt>== </tt></font> <tt> ON </tt> can be used to view the hidden 1D nodes. The hidden nodes will be written to the [[TUFLOW_Check_Files \| nwk_N_check]] layer. The 2D link can also be reviewed using the [[TUFLOW_Check_Files \| 2d_to_2d_check ]] layer; both are shown below. <br>
	[[File: 2D2D_Guidance_003.JPG \|400px]] <br><br>		[[File: 2D2D_Guidance_003.JPG \|400px]] <br><br>

Line 35:		Line 35:

	[[File: 2D2D_Guidance_004.JPG \|400px]]<br>		[[File: 2D2D_Guidance_004.JPG \|400px]]<br>

	* The 2d_bc “2D” link line can be orientated in any direction within floodplain areas with low velocity (<0.5m/s). The 2d_bc “2D” link line “d” attribute should be used in this situation. This is discussed in the following section. <br>		* The 2d_bc “2D” link line can be orientated in any direction within floodplain areas with low velocity (<0.5m/s). The 2d_bc “2D” link line “d” attribute should be used in this situation. This is discussed in the following section. <br>

Line 44:		Line 43:

	2d_bc “2D” link line vertices are best located on ridges or embankments, including features that become inundated and drowned out during a simulation.<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.<br>

	* In regions of moderate to high velocity (>0.5m/s), manual vertex placement on the river banks and natural ridges in addition to a “d” value of 0 is common. Using a “d” value of 0 will create a hidden 1D node at each vertex along the 2d_bc “2D” link line. No intermediate hidden 1D nodes will be created.<br>		* In regions of moderate to high velocity (>0.5m/s), manual vertex placement on the river banks and natural ridges in addition to a “d” value of 0 is common. Using a “d” value of 0 will create a hidden 1D node at each vertex along the 2d_bc “2D” link line. No intermediate hidden 1D nodes will be created.<br>
	[[File: 2D2D_Guidance_007.JPG \|400px]]<br>		[[File: 2D2D_Guidance_007.JPG \|400px]]<br>

	* Model results are less sensitive to the hidden 1D node placement in regions of low velocity (<0.5m/s). Automated placement by using a “d” values greater than 0 is common in this situation. The selected value should be no less than three times the size of the larger cell resolution associated with the 2D/2D boundary. For example, if the model uses a 2.5m and 5m resolution, the “d” attribute should be set no smaller than 15m.<br>		* Model results are less sensitive to the hidden 1D node placement in regions of low velocity (<0.5m/s). Automated placement by using a “d” values greater than 0 is common in this situation. The selected value should be no less than three times the size of the larger cell resolution associated with the 2D/2D boundary. For example, if the model uses a 2.5m and 5m resolution, the “d” attribute should be set no smaller than 15m.<br>
	[[File: 2D2D_Guidance_006.JPG \|400px]]<br>		[[File: 2D2D_Guidance_006.JPG \|400px]]<br>

Chris Huxley at 03:01, 12 October 2016

2016-10-12T03:01:10Z

← Older revision		Revision as of 13:01, 12 October 2016
Line 62:		Line 62:
	</li>		</li>
	</ol>		</ol>
	<li> Example 2D/2D models are available for download from the [[Example_Models_Home_page \| Example Models]] page of the Wiki:		<li> Example 2D/2D models are available for download from the [[Example_Models_Home_page \| Example Models]] page of the Wiki.
	</li>		</li>
	</ol>		</ol>

Chris Huxley at 03:00, 12 October 2016

2016-10-12T03:00:51Z

← Older revision		Revision as of 13:00, 12 October 2016
Line 61:		Line 61:
	[[File: 2D2D_Guidance_008.JPG \|400px]]<br>		[[File: 2D2D_Guidance_008.JPG \|400px]]<br>
	</li>		</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>

Chris Huxley at 02:57, 12 October 2016

2016-10-12T02:57:09Z

← Older revision		Revision as of 12:57, 12 October 2016
Line 5:		Line 5:
	[[File: 2D2D_Guidance_000.JPG \|450px]]<br>		[[File: 2D2D_Guidance_000.JPG \|450px]]<br>

	Some useful tips are ~~listed~~ below:<br>		Some useful tips are provided below:<br>
	<ol>		<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>		<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>

Chris Huxley at 02:49, 12 October 2016

2016-10-12T02:49:24Z

← Older revision		Revision as of 12:49, 12 October 2016
Line 5:		Line 5:
	[[File: 2D2D_Guidance_000.JPG \|450px]]<br>		[[File: 2D2D_Guidance_000.JPG \|450px]]<br>

	Some ~~best~~ ~~practise~~ ~~advice for configuring a 2D / 2D boundary is~~ listed below:<br>		Some useful tips are listed below:<br>
	<ol>		<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>		<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>

Chris Huxley at 02:48, 12 October 2016

2016-10-12T02:48:45Z

← Older revision		Revision as of 12:48, 12 October 2016
Line 1:		Line 1:
	This section provides best practise advice for configuring TUFLOW 2D/2D boundaries. <br>		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, ~~Estry~~ control file and simulation time and map output commands) are defined outside the above mentioned 2D domain blocks. An example TCF file is shown below. Line 8 to 13 represents the first 2D domain. Line 15 to 20 contain the second 2D domain block. <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, estry control file and simulation time and map output commands) are defined outside the above mentioned 2D domain blocks. An example TCF file is shown below. Line 8 to 13 represents the first 2D domain. Line 15 to 20 contain the second 2D domain block. <br>

	[[File: 2D2D_Guidance_000.JPG \|450px]]<br>		[[File: 2D2D_Guidance_000.JPG \|450px]]<br>

Chris Huxley at 02:46, 12 October 2016

2016-10-12T02:46:01Z

← Older revision		Revision as of 12:46, 12 October 2016
Line 41:		Line 41:

	'''<u>2D BC "2D" Line Vertex Location and Hidden 1D Node Options'''</u>'''<br>		'''<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. 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 vertex location.<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.<br>
⚫	* In regions of moderate to high velocity (>0.5m/s), manual vertex placement on the river banks and natural ridges in addition to a “d” value of 0 is common. Using a “d” value of 0 will create a hidden 1D node at each vertex along the 2d_bc “2D” link line.<br>

		⚫	* In regions of moderate to high velocity (>0.5m/s), manual vertex placement on the river banks and natural ridges in addition to a “d” value of 0 is common. Using a “d” value of 0 will create a hidden 1D node at each vertex along the 2d_bc “2D” link line. No intermediate hidden 1D nodes will be created.<br>
	[[File: 2D2D_Guidance_007.JPG \|400px]]<br>		[[File: 2D2D_Guidance_007.JPG \|400px]]<br>