TUFLOW Message 3022 - Revision history

Emilie Nielsen at 05:55, 18 July 2024

2024-07-18T05:55:32Z

← Older revision		Revision as of 15:55, 18 July 2024
Line 10:		Line 10:
	For HT boundary:		For HT boundary:
	* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.		* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.
	* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line ~~- please contact [mailto:support@tuflow.com support@tuflow.com] if you need assistance in doing this~~.		* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line.
	For HQ boundary:		For HQ boundary:
	* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).		* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).

Melissa.Moghanloo at 00:14, 3 March 2023

2023-03-03T00:14:20Z

← Older revision		Revision as of 10:14, 3 March 2023
Line 16:		Line 16:
	* Check total number of GT boundaries in the 2d_bc layer isn't more than 255.		* Check total number of GT boundaries in the 2d_bc layer isn't more than 255.

	\|prelink=[[TUFLOW_Message_3021\|Message 3021]]
	\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]		\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]
	\|nextlink=[[TUFLOW_Message_3023\|Message 3023]]
	}}		}}

Emilie Nielsen at 05:58, 2 March 2023

2023-03-02T05:58:10Z

← Older revision		Revision as of 15:58, 2 March 2023
Line 1:		Line 1:
	{{TUFLOW_Message		{{TUFLOW_Message
	\|tuflow_message=ERROR 3022: Number of Boundary Level Graphs exceeded. Maximum is 253.		\|tuflow_message=ERROR 3022 - Number of Boundary Level Graphs exceeded. Maximum is 253.
	<br>		<br>
			\|alt_msg=ERROR 3022 - Maximum number of Boundary tracer graphs exceeded.<br>
	\|alt_msg=None
			ERROR 3022 - Number of groundwater boundary Level Graphs exceeded. Maximum is 255.
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=~~TUFLOW~~ HPC has a limit of 253 unique HT or HQ boundaries.		\|message_desc=HPC has a limit of 253 for unique HT plus HQ boundaries, and 255 for GT boundaries.
	\|suggestions=		\|suggestions=
	~~Both~~, HT and HQ boundaries should only be digitised in the location where water is exiting the model, e.g. not along the whole code perimeter.<br>		HT, HQ, and GT boundaries should only be digitised in the location where water is entering/exiting the model, i.e. not along the whole code perimeter.<br>
	HT boundary:		For HT boundary:
	* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.		* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.
	* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line - contact support@tuflow.com if you need assistance in doing this.		* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line - please contact [mailto:support@tuflow.com support@tuflow.com] if you need assistance in doing this.
	HQ boundary:		For HQ boundary:
	* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).		* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).
			For GT boundary:
			* Check total number of GT boundaries in the 2d_bc layer isn't more than 255.

	\|prelink=[[TUFLOW_Message_3021\|Message 3021]]		\|prelink=[[TUFLOW_Message_3021\|Message 3021]]

Melissa.Moghanloo at 05:18, 13 July 2022

2022-07-13T05:18:45Z

← Older revision		Revision as of 15:18, 13 July 2022
Line 12:		Line 12:
	HQ boundary:		HQ boundary:
	* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).		* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).

	\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_3021\|Message 3021]]		\|prelink=[[TUFLOW_Message_3021\|Message 3021]]
	\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]		\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]

Pavlina Monhartova at 04:56, 10 March 2021

2021-03-10T04:56:49Z

← Older revision		Revision as of 14:56, 10 March 2021
Line 3:		Line 3:
	<br>		<br>
	\|alt_msg=None		\|alt_msg=None

	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=TUFLOW HPC has a limit of 253 unique HT or HQ boundaries.		\|message_desc=TUFLOW HPC has a limit of 253 unique HT or HQ boundaries.
	\|suggestions=		\|suggestions=
	Both, HT and HQ boundaries should only be digitised in the location where water is exiting the model, e.g. not along the whole code perimeter.		Both, HT and HQ boundaries should only be digitised in the location where water is exiting the model, e.g. not along the whole code perimeter.<br>
	HT boundary:		HT boundary:
	* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.		* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.

Pavlina Monhartova at 04:56, 10 March 2021

2021-03-10T04:56:20Z

← Older revision		Revision as of 14:56, 10 March 2021
Line 7:		Line 7:
	\|message_desc=TUFLOW HPC has a limit of 253 unique HT or HQ boundaries.		\|message_desc=TUFLOW HPC has a limit of 253 unique HT or HQ boundaries.
	\|suggestions=		\|suggestions=
	Both,HT and HQ boundaries should only be digitised in the location where ~~model~~ is exiting the model, e.g. not along the whole code perimeter.		Both, HT and HQ boundaries should only be digitised in the location where water is exiting the model, e.g. not along the whole code perimeter.
	HT boundary:		HT boundary:
	* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.		* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.

Pavlina Monhartova at 04:55, 10 March 2021

2021-03-10T04:55:37Z

← Older revision		Revision as of 14:55, 10 March 2021
Line 5:		Line 5:

	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=TUFLOW HPC has a limit of 253 unique HT boundaries.		\|message_desc=TUFLOW HPC has a limit of 253 unique HT or HQ boundaries.
	\|suggestions=		\|suggestions=
			Both,HT and HQ boundaries should only be digitised in the location where model is exiting the model, e.g. not along the whole code perimeter.
⚫	* Check total number of HT boundaries in the 2d_bc layer is more than 253.
			HT boundary:
⚫	* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line - ~~please~~ contact support@tuflow.com if you need assistance in doing this.
		⚫	* Check total number of HT boundaries in the 2d_bc layer isn't more than 253.
		⚫	* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line - contact support@tuflow.com if you need assistance in doing this.
			HQ boundary:
			* Check that the number of HQ boundary segments (vertex to vertex) isn't higher than 253. This usually happens when the boundary is generated from subcatchments layer processed from various software packages containing a large number of vertices close to each other. If so, simplify the boundary (and code polygon).
	\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]		\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]
	\|link3=''		\|link3=''

Bill Syme at 02:20, 15 August 2018

2018-08-15T02:20:41Z

← Older revision		Revision as of 12:20, 15 August 2018
Line 5:		Line 5:

	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=TUFLOW HPC has a limit of 253 unique ~~H (HS and~~ HT) boundaries.		\|message_desc=TUFLOW HPC has a limit of 253 unique HT boundaries.
	\|suggestions=		\|suggestions=
	* Check total number of ~~HS and~~ HT boundaries in the 2d_bc layer is more than 253.		* Check total number of HT boundaries in the 2d_bc layer is more than 253.
	* Check number of ~~HS and~~ HT boundaries read in the model by searching for ~~"nhs" and~~ "nht" in the .tlf file. If the number is higher than the number of ~~HS and~~ HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the ~~HS/~~HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries.		* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than the number of HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries. The use of "td", "a" and "b" to incrementally adjust HT boundary values was used in the past to vary the water levels along a boundary, for example, a tidal boundary where the tidal range and timing varies. The recommended approach today to vary water levels along a boundary is to snap 1d_bc HT (or HS) boundary points to a HX line - please contact support@tuflow.com if you need assistance in doing this.
	\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]		\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]
	\|link3=''		\|link3=''

Bill Syme at 02:10, 15 August 2018

2018-08-15T02:10:08Z

← Older revision		Revision as of 12:10, 15 August 2018
Line 5:		Line 5:

	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=HPC has a limit of 253 unique HT boundaries.		\|message_desc=TUFLOW HPC has a limit of 253 unique H (HS and HT) boundaries.
	\|suggestions=		\|suggestions=
	* Check number of HT boundaries in the 2d_bc layer if more than 253.		* Check total number of HS and HT boundaries in the 2d_bc layer is more than 253.
	* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than number of HT boundaries in the 2d_bc layer check if ~~attribute~~ "Td", "A" and/or "B" have any ~~value~~ specified. These attributes ~~will~~ ~~add~~ an ~~incremental~~ ~~amount~~ to each cell of the HT boundary ~~and~~ each cell ~~will~~ be ~~read~~ in ~~TUFLOW~~ as unique ~~HT boundary~~.		* Check number of HS and HT boundaries read in the model by searching for "nhs" and "nht" in the .tlf file. If the number is higher than the number of HS and HT boundaries in the 2d_bc layer then check if attributes "td", "a" and/or "b" have any (non-zero) values specified. These attributes adjust the boundary values incrementally along each cell of the HS/HT boundary, thereby creating a unique boundary time-series for each cell and can significantly increase the number of unique boundaries.
	\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]		\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]
	\|link3=''		\|link3=''

Pavlina Monhartova at 23:44, 10 July 2018

2018-07-10T23:44:06Z

← Older revision		Revision as of 09:44, 11 July 2018
Line 8:		Line 8:
	\|suggestions=		\|suggestions=
	* Check number of HT boundaries in the 2d_bc layer if more than 253.		* Check number of HT boundaries in the 2d_bc layer if more than 253.
	* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than number of HT boundaries in the 2d_bc layer check if attribute Td, A and/or B have any value specified. These attributes will add an incremental amount to each cell of the HT boundary and each cell will be read in TUFLOW as unique HT boundary.		* Check number of HT boundaries read in the model by searching for "nht" in the .tlf file. If the number is higher than number of HT boundaries in the 2d_bc layer check if attribute "Td", "A" and/or "B" have any value specified. These attributes will add an incremental amount to each cell of the HT boundary and each cell will be read in TUFLOW as unique HT boundary.
	\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]		\|discussion_page=* [[Talk:TUFLOW Message 3022\|Discuss Message 3022]]
	\|link3=''		\|link3=''