HPC Model Review - Revision history

ElizaCollison: /* HPC TUFLOW Log File (hpc.tlf) /

2024-07-12T12:17:04Z

HPC TUFLOW Log File (*hpc.tlf)

← Older revision		Revision as of 22:17, 12 July 2024
Line 18:		Line 18:

	The last column of the *hpc.tlf file records the timesteping efficiency output. A value of 100% indicates that the HPC timesteps are perfectly aligned with the minimum stability timestep for complying with the three control numbers representing the Courant, Wave Celerity and Diffusion criteria.<br>		The last column of the *hpc.tlf file records the timesteping efficiency output. A value of 100% indicates that the HPC timesteps are perfectly aligned with the minimum stability timestep for complying with the three control numbers representing the Courant, Wave Celerity and Diffusion criteria.<br>

			If virtual pipes are used in the model, the following information will also be reported in the hpc.tlf and console window:
			* qInlet: flow extracted from the 2D domain.
			* qSurcharge: flow surcharging out of inlets, due to the outlet flow being limited.
			* qOutput: flow entering the 2D domain.

	= HPC dt Time Series Output (*.hpc.dt.csv) =		= HPC dt Time Series Output (*.hpc.dt.csv) =

Abigail.lillo: /* HPC TUFLOW Log File (hpc.tlf) /

2023-08-10T00:27:39Z

HPC TUFLOW Log File (*hpc.tlf)

← Older revision		Revision as of 10:27, 10 August 2023
Line 15:		Line 15:
	[[File: HPC_repeating_timestep.png]]		[[File: HPC_repeating_timestep.png]]

	The new *hpc.tlf file can be also used to review the dt, controlling number values and the water volume in the model. However, this may be easier to review using the hpc.dt.csv output.~~<br>~~		The new *hpc.tlf file can be also used to review the dt, controlling number values and the water volume in the model. However, this may be easier to review using the hpc.dt.csv output.

			The last column of the *hpc.tlf file records the timesteping efficiency output. A value of 100% indicates that the HPC timesteps are perfectly aligned with the minimum stability timestep for complying with the three control numbers representing the Courant, Wave Celerity and Diffusion criteria.<br>

	= HPC dt Time Series Output (*.hpc.dt.csv) =		= HPC dt Time Series Output (*.hpc.dt.csv) =

ElizaCollison: /* dt Map Output */

2022-11-23T23:24:30Z

dt Map Output

← Older revision		Revision as of 09:24, 24 November 2022
Line 42:		Line 42:

	= dt Map Output =		= dt Map Output =
	The dt map output is a grid map output that displays the calculated minimum timestep at each grid cell, and does not necessarily align with the timestep adopted in the model (the timestep in the model could be less if the previous timesteps were smaller). This helps identify which cells in the model are controlling the model timestep.br>		The dt map output is a grid map output that displays the calculated minimum timestep at each grid cell, and does not necessarily align with the timestep adopted in the model (the timestep in the model could be less if the previous timesteps were smaller). This helps identify which cells in the model are controlling the model timestep.<br>
	<font color="blue"><tt>Map Output Data Types </tt></font><font color="red"><tt>==</tt></font><tt> dt </tt> writes the minimum dt (timestep) calculated for each cell in the model to the specified Map Output Format (XMDF, DAT, ASC, FLT etc.). Reviewing this output helps modellers identify which cells in the model have the lowest timestep and thereby control the model timestep. These locations are likely to have the greatest depth, velocity or turbulence in the model, forcing TUFLOW to lower the timestep to satisfy the conditions of the controlling numbers mentioned in the <u>[[HPC_Adaptive_Timestepping \| HPC Adaptive Timestepping]]</u> page. If the timestep is extremely low the HPC model might be “hiding” poor data or model setup in this location. The simulation timestep will always be limited by the minimum occurring timestep anywhere in the model, hence it is important to ensure timestepping isn’t being unnecessarily restricted due to poor model configuration in one spot, even only in one cell. <br>		<font color="blue"><tt>Map Output Data Types </tt></font><font color="red"><tt>==</tt></font><tt> dt </tt> writes the minimum dt (timestep) calculated for each cell in the model to the specified Map Output Format (XMDF, DAT, ASC, FLT etc.). Reviewing this output helps modellers identify which cells in the model have the lowest timestep and thereby control the model timestep. These locations are likely to have the greatest depth, velocity or turbulence in the model, forcing TUFLOW to lower the timestep to satisfy the conditions of the controlling numbers mentioned in the <u>[[HPC_Adaptive_Timestepping \| HPC Adaptive Timestepping]]</u> page. If the timestep is extremely low the HPC model might be “hiding” poor data or model setup in this location. The simulation timestep will always be limited by the minimum occurring timestep anywhere in the model, hence it is important to ensure timestepping isn’t being unnecessarily restricted due to poor model configuration in one spot, even only in one cell. <br>
	<br>		<br>

Chris Huxley: /* Control Number Factor Sensitivity Testing */

2022-05-30T05:31:31Z

Control Number Factor Sensitivity Testing

← Older revision		Revision as of 15:31, 30 May 2022
Line 66:		Line 66:
	= Control Number Factor Sensitivity Testing =		= Control Number Factor Sensitivity Testing =
	Sensitivity run can be done by reducing timestepping interval using Control Number Factor == 0.8. This reduces the timestep (as dictated by the three control numbers) by the factor 0.8, making the simulation to take roughly 20% longer. If comparing the two results shows negligible differences it is a strong indicator the default control number limits may be considered satisfactory. If there are unacceptable measurable differences, the location of these impacts may also help to spatially identify where the solution may have been struggling at the default control numbers. These areas can then be inspected for input topography or boundary conditions errors. Models shouldn’t need to have the CNF lowered any more than this, as if they do, it would indicate there is more likely an underlying model configuration issue that needs attention.		Sensitivity run can be done by reducing timestepping interval using Control Number Factor == 0.8. This reduces the timestep (as dictated by the three control numbers) by the factor 0.8, making the simulation to take roughly 20% longer. If comparing the two results shows negligible differences it is a strong indicator the default control number limits may be considered satisfactory. If there are unacceptable measurable differences, the location of these impacts may also help to spatially identify where the solution may have been struggling at the default control numbers. These areas can then be inspected for input topography or boundary conditions errors. Models shouldn’t need to have the CNF lowered any more than this, as if they do, it would indicate there is more likely an underlying model configuration issue that needs attention.
			<br>
			<br>
			{{Tips Navigation
			\|uplink=[[ HPC_Modelling_Guidance \| Back to HPC Modelling Guidance]]
			}}

ElizaCollison: /* dt Map Output */

2022-05-03T04:28:45Z

dt Map Output

← Older revision		Revision as of 14:28, 3 May 2022
Line 45:		Line 45:
	<font color="blue"><tt>Map Output Data Types </tt></font><font color="red"><tt>==</tt></font><tt> dt </tt> writes the minimum dt (timestep) calculated for each cell in the model to the specified Map Output Format (XMDF, DAT, ASC, FLT etc.). Reviewing this output helps modellers identify which cells in the model have the lowest timestep and thereby control the model timestep. These locations are likely to have the greatest depth, velocity or turbulence in the model, forcing TUFLOW to lower the timestep to satisfy the conditions of the controlling numbers mentioned in the <u>[[HPC_Adaptive_Timestepping \| HPC Adaptive Timestepping]]</u> page. If the timestep is extremely low the HPC model might be “hiding” poor data or model setup in this location. The simulation timestep will always be limited by the minimum occurring timestep anywhere in the model, hence it is important to ensure timestepping isn’t being unnecessarily restricted due to poor model configuration in one spot, even only in one cell. <br>		<font color="blue"><tt>Map Output Data Types </tt></font><font color="red"><tt>==</tt></font><tt> dt </tt> writes the minimum dt (timestep) calculated for each cell in the model to the specified Map Output Format (XMDF, DAT, ASC, FLT etc.). Reviewing this output helps modellers identify which cells in the model have the lowest timestep and thereby control the model timestep. These locations are likely to have the greatest depth, velocity or turbulence in the model, forcing TUFLOW to lower the timestep to satisfy the conditions of the controlling numbers mentioned in the <u>[[HPC_Adaptive_Timestepping \| HPC Adaptive Timestepping]]</u> page. If the timestep is extremely low the HPC model might be “hiding” poor data or model setup in this location. The simulation timestep will always be limited by the minimum occurring timestep anywhere in the model, hence it is important to ensure timestepping isn’t being unnecessarily restricted due to poor model configuration in one spot, even only in one cell. <br>
	<br>		<br>
	[[FILE: Min dt raster.png ~~\| 600px~~]] <br>		[[FILE: Min dt raster 01.png]] <br>
	<br>		<br>
	The cause of the low timestep may become clearer when observing it geographically in the dt Map Output, as the low timestep may occur close to specific hydraulic features. This is seen in the example above, where an unusually low dt value is observed upstream, where the road intersects a local channel. It is helpful to review this in conjunction with the hpc.dt.csv to know which of the controlling numbers is causing the timestep to be lowered.<br>		The cause of the low timestep may become clearer when observing it geographically in the dt Map Output, as the low timestep may occur close to specific hydraulic features. This is seen in the example above, where an unusually low dt value is observed upstream, where the road intersects a local channel. It is helpful to review this in conjunction with the hpc.dt.csv to know which of the controlling numbers is causing the timestep to be lowered.<br>

Pavlina Monhartova: /* Introduction */

2021-12-30T00:24:45Z

Introduction

← Older revision		Revision as of 10:24, 30 December 2021
Line 1:		Line 1:
	= Introduction =		= Introduction =
	HPC is an unconditionally stable 2D solution scheme that is mass conservative. This can result in HPC “hiding” poor data or model setup. Modellers must take measures to ensure the quality of their HPC models for commercial uses, by taking all reasonable steps to correct or at the very least understand areas of poor representation in their models.<br>		TUFLOW HPC is an unconditionally stable 2D solution scheme that is mass conservative. This can result in HPC “hiding” poor data or model setup. Modellers must take measures to ensure the quality of their HPC models for commercial uses, by taking all reasonable steps to correct or at the very least understand areas of poor representation in their models.<br>

	= TUFLOW Log File (*.tlf) =		= TUFLOW Log File (*.tlf) =

Pavlina Monhartova: /* TUFLOW Log File (.tlf) /

2021-12-30T00:23:31Z

TUFLOW Log File (*.tlf)

← Older revision		Revision as of 10:23, 30 December 2021
Line 5:		Line 5:
	The first step of reviewing a HPC model is no different to reviewing a TUFLOW Classic model. Start by opening the TUFLOW log file (*.tlf) and confirm at the bottom of the file, that the model run finished successfully by observing "Simulation FINISHED" and that the final mass error reported is acceptable as shown below:<br>		The first step of reviewing a HPC model is no different to reviewing a TUFLOW Classic model. Start by opening the TUFLOW log file (*.tlf) and confirm at the bottom of the file, that the model run finished successfully by observing "Simulation FINISHED" and that the final mass error reported is acceptable as shown below:<br>

	[[~~FILE~~: ~~HPC~~ ~~TLF~~.~~JPG \| 700px~~]]<br>		[[File:Simulation Summary 02.PNG]]<br>
	Though HPC is volume conservative and shouldn't produce any mass error it is still important to review the Mass Error, as it can still occur when coupling HPC with 1D elements in either the 1D/2D linking, or in the 1D itself.<br>		Though HPC is volume conservative and shouldn't produce any mass error it is still important to review the Mass Error, as it can still occur when coupling HPC with 1D elements in either the 1D/2D linking, or in the 1D itself.<br>
	A 'healthy' model will usually report up to 1% mass error. Higher mass error is an indication the solution is not converging, usually in isolated locations. In nearly all cases it is because of poor data (e.g. cliff edge between data sets) or model schematisation (e.g. large pit connected to one tiny 2D cell or boundary poorly digitised so it is not roughly perpendicular to the flow). The total model mass error can also be observed in the TUFLOW Summary File (*.tsf) output as oppose to the tlf file. <br>		A 'healthy' model will usually report up to 1% mass error. Higher mass error is an indication the solution is not converging, usually in isolated locations. In nearly all cases it is because of poor data (e.g. cliff edge between data sets) or model schematisation (e.g. large pit connected to one tiny 2D cell or boundary poorly digitised so it is not roughly perpendicular to the flow). The total model mass error can also be observed in the TUFLOW Summary File (*.tsf) output as oppose to the tlf file. <br>

Pavlina Monhartova: /* TUFLOW Log File (.tlf) /

2021-02-26T00:06:13Z

TUFLOW Log File (*.tlf)

← Older revision		Revision as of 10:06, 26 February 2021
Line 7:		Line 7:
	[[FILE: HPC TLF.JPG \| 700px]]<br>		[[FILE: HPC TLF.JPG \| 700px]]<br>
	Though HPC is volume conservative and shouldn't produce any mass error it is still important to review the Mass Error, as it can still occur when coupling HPC with 1D elements in either the 1D/2D linking, or in the 1D itself.<br>		Though HPC is volume conservative and shouldn't produce any mass error it is still important to review the Mass Error, as it can still occur when coupling HPC with 1D elements in either the 1D/2D linking, or in the 1D itself.<br>
	A 'healthy' model will usually report up to ±1% mass error. The total model mass error can also be observed in the TUFLOW Summary File (*.tsf) output as oppose to the tlf file. <br>		A 'healthy' model will usually report up to 1% mass error. Higher mass error is an indication the solution is not converging, usually in isolated locations. In nearly all cases it is because of poor data (e.g. cliff edge between data sets) or model schematisation (e.g. large pit connected to one tiny 2D cell or boundary poorly digitised so it is not roughly perpendicular to the flow). The total model mass error can also be observed in the TUFLOW Summary File (*.tsf) output as oppose to the tlf file. <br>

	= HPC TUFLOW Log File (*hpc.tlf) =		= HPC TUFLOW Log File (*hpc.tlf) =

Pavlina Monhartova: /* HPC dt Time Series Output (.hpc.dt.csv) /

2021-02-03T04:32:13Z

HPC dt Time Series Output (*.hpc.dt.csv)

← Older revision		Revision as of 14:32, 3 February 2021
Line 35:		Line 35:
	This becomes valuable when trying to determine what is causing the low timestep and how to resolve it. For example:<br>		This becomes valuable when trying to determine what is causing the low timestep and how to resolve it. For example:<br>

⚫	*An Nd value of 0.3 or higher might suggest that there is poor boundary setup, or insufficient SX cells linked to a 1D structure.
⚫	*An Nc value of 1.0 or higher could be caused by an erroneously low cell elevation, resulting in an artificially large water depth.
	*An Nu value of 1.0 or greater may indicate that the velocity is unusually high.		*An Nu value of 1.0 or greater may indicate that the velocity is unusually high.
		⚫	*An Nc value of 1.0 or higher could be caused by an erroneously low cell elevation, resulting in an artificially large water depth.
		⚫	*An Nd value of 0.3 or higher might suggest that there is poor boundary setup, or insufficient SX cells linked to a 1D structure.

	Because each relates to a hydraulic condition, they provide insight into what might be causing an issue in the model.<br>		Because each relates to a hydraulic condition, they provide insight into what might be causing an issue in the model.<br>

Pavlina Monhartova at 04:31, 3 February 2021

2021-02-03T04:31:17Z

← Older revision		Revision as of 14:31, 3 February 2021
Line 10:		Line 10:

	= HPC TUFLOW Log File (*hpc.tlf) =		= HPC TUFLOW Log File (*hpc.tlf) =
	The .hpc.tlf log file records the model timestep, control numbers and volume of water in model at each timestep. It also shows repeated timesteps if the [[HPC_Adaptive_Timestepping \| control number limits]] were exceeded or there is a significant change in control numbers (more than 20%). It is inevitable to have repeated timesteps, if a model has a sudden change in rainfall input from one timestep to the next, or has a warmup period with small flow rate before a large inflow. However, if there is a high occurrence of repeating timesteps when the boundary inflows are smooth, this could be an indicator of model instability. The total number of repeated timesteps is also recorded in Simulation Summary of the .tlf file.<br>		The .hpc.tlf log file records the model timestep, control numbers and volume of water in model at each timestep. It also shows repeated timesteps if the <u>[[HPC_Adaptive_Timestepping \| control number limits]]</u> were exceeded or there is a significant change in control numbers (more than 20%). It is inevitable to have repeated timesteps, if a model has a sudden change in rainfall input from one timestep to the next, or has a warmup period with small flow rate before a large inflow. However, if there is a high occurrence of repeating timesteps when the boundary inflows are smooth, this could be an indicator of model instability. The total number of repeated timesteps is also recorded in Simulation Summary of the .tlf file.<br>
	'''Note:''' TUFLOW HPC allows the [[HPC_Adaptive_Timestepping \| control numbers]] to be breached by 20%. The timestep will not be repeated with Nc, Nu smaller than 1.2 and Nd smaller than 0.36. <br>		'''Note:''' TUFLOW HPC allows the <u>[[HPC_Adaptive_Timestepping \| control numbers]]</u> to be breached by 20%. The timestep will not be repeated with Nc, Nu smaller than 1.2 and Nd smaller than 0.36. <br>
	<br>		<br>
	[[File: HPC_repeating_timestep.png]]		[[File: HPC_repeating_timestep.png]]

HPC Model Review - Revision history

ElizaCollison: /* HPC TUFLOW Log File (*hpc.tlf) */

Abigail.lillo: /* HPC TUFLOW Log File (*hpc.tlf) */

ElizaCollison: /* dt Map Output */

Chris Huxley: /* Control Number Factor Sensitivity Testing */

ElizaCollison: /* dt Map Output */

Pavlina Monhartova: /* Introduction */

Pavlina Monhartova: /* TUFLOW Log File (*.tlf) */

Pavlina Monhartova: /* TUFLOW Log File (*.tlf) */

Pavlina Monhartova: /* HPC dt Time Series Output (*.hpc.dt.csv) */

Pavlina Monhartova at 04:31, 3 February 2021

ElizaCollison: /* HPC TUFLOW Log File (hpc.tlf) /

Abigail.lillo: /* HPC TUFLOW Log File (hpc.tlf) /

Pavlina Monhartova: /* TUFLOW Log File (.tlf) /

Pavlina Monhartova: /* TUFLOW Log File (.tlf) /

Pavlina Monhartova: /* HPC dt Time Series Output (.hpc.dt.csv) /