HPC Adaptive Timestepping - Revision history

Abrar.Alttahir: /* HPC 1D Timestep */

2025-11-10T05:45:12Z

HPC 1D Timestep

← Older revision		Revision as of 15:45, 10 November 2025
Line 54:		Line 54:
	Where there is not a one to one synchronisation of the 1D and 2D timesteps, a usually negligible mass error may occur and can be checked by reviewing the CME% values shown on the Console Window, the .tlf file or the _MB.csv file in the same manner as Classic.		Where there is not a one to one synchronisation of the 1D and 2D timesteps, a usually negligible mass error may occur and can be checked by reviewing the CME% values shown on the Console Window, the .tlf file or the _MB.csv file in the same manner as Classic.
	<br>		<br>
	[[File:~~1d2ddt~~.png~~\|800px~~]]		[[File:TUFLOWHPC1D2DTimestepSync2.png]]

	=HPC Timestep Synchronisation=		=HPC Timestep Synchronisation=

RobertWright: Updated limits to reflect the expressions

2025-04-22T13:27:07Z

Updated limits to reflect the expressions

← Older revision		Revision as of 23:27, 22 April 2025
Line 17:		Line 17:
	\|This condition ensures that water entering one side of a 2D cell does not pass through the other side within one timestep. For this to be satisfied, the product of the water velocity (𝑢) and model timestep (∆𝑡) must be less than the cell size (∆𝑥).		\|This condition ensures that water entering one side of a 2D cell does not pass through the other side within one timestep. For this to be satisfied, the product of the water velocity (𝑢) and model timestep (∆𝑡) must be less than the cell size (∆𝑥).
	\|[[FILE: Courant Number Equation.PNG \|250px]]		\|[[FILE: Courant Number Equation.PNG \|250px]]
	\|<1.0		\|≤1.0
	\|-		\|-
	\|style="height:110px;" \| The Shallow Wave Celerity <br> Number (Nc)		\|style="height:110px;" \| The Shallow Wave Celerity <br> Number (Nc)
	\|This numerical condition relates to the shallow water wave celerity (wave speed) and is derived from the fluid flow equations to represent long waves (i.e. wave length is substantially longer than the water depth). The product of the model timestep (∆𝑡) and the long wave speed (square root of the gravity (g) and water depth (h)) must be less than the cell size (∆𝑥), for the condition to be satisfied.		\|This numerical condition relates to the shallow water wave celerity (wave speed) and is derived from the fluid flow equations to represent long waves (i.e. wave length is substantially longer than the water depth). The product of the model timestep (∆𝑡) and the long wave speed (square root of the gravity (g) and water depth (h)) must be less than the cell size (∆𝑥), for the condition to be satisfied.
	\|[[FILE: SWC Number Equation.PNG \|250px]]		\|[[FILE: SWC Number Equation.PNG \|250px]]
	\|<1.0		\|≤1.0
	\|-		\|-
	\|style="height:80px;" \| Diffusion Number (Nd)		\|style="height:80px;" \| Diffusion Number (Nd)
	\|This numerical condition relates to the sub-grid scale eddy viscosity term which causes diffusion of momentum. To maintain stability the product of the eddy viscosity coefficient (ν_T) and the timestep (∆𝑡) divided by the square of the grid spacing (∆𝑥2) must remain below 0.3. Models controlled by the diffusion number tend to require a timestep significantly smaller than those controlled by the shallow wave celerity or courant numbers. If you find your model is predominantly diffusion controlled it may be that equivalent solution accuracy can be achieved by selecting a larger cell size. This is worth testing, as it will most likely increase the simulation speed with no loss of result fidelity.		\|This numerical condition relates to the sub-grid scale eddy viscosity term which causes diffusion of momentum. To maintain stability the product of the eddy viscosity coefficient (ν_T) and the timestep (∆𝑡) divided by the square of the grid spacing (∆𝑥2) must remain below 0.3. Models controlled by the diffusion number tend to require a timestep significantly smaller than those controlled by the shallow wave celerity or courant numbers. If you find your model is predominantly diffusion controlled it may be that equivalent solution accuracy can be achieved by selecting a larger cell size. This is worth testing, as it will most likely increase the simulation speed with no loss of result fidelity.
	\|[[FILE: Diffusion Number Equation.PNG \|250px]]		\|[[FILE: Diffusion Number Equation.PNG \|250px]]
	\|<0.3		\|≤0.3
	\|}		\|}

Chris Huxley: /* HPC Quadtree Adaptive Timestepping */

2022-05-30T05:31:15Z

HPC Quadtree Adaptive Timestepping

← Older revision		Revision as of 15:31, 30 May 2022
Line 63:		Line 63:

	=HPC Quadtree Adaptive Timestepping=		=HPC Quadtree Adaptive Timestepping=
	All the above is applicable to the HPC with Quadtree simulations. In addition the Quadtree solver uses a single adaptive timestep for the entire model at any instance in time. Different timesteps are not applied to the respective different resolution nest levels. If a small cell resolution is nested down in water that is deeper than the cell face length, the Diffusion control number would be the critical limiter that is setting the timestep and the model will run slower than expected. This can be confirmed by reviewing the <u>[[HPC_Model_Review#HPC_dt_Time_Series_Output_.28.2A.hpc.dt.csv.29 \| hpc.dt.csv file]]</u> information.		All the above is applicable to the HPC with Quadtree simulations. In addition the Quadtree solver uses a single adaptive timestep for the entire model at any instance in time. Different timesteps are not applied to the respective different resolution nest levels. If a small cell resolution is nested down in water that is deeper than the cell face length, the Diffusion control number would be the critical limiter that is setting the timestep and the model will run slower than expected. This can be confirmed by reviewing the <u>[[HPC_Model_Review#HPC_dt_Time_Series_Output_.28.2A.hpc.dt.csv.29 \| hpc.dt.csv file]]</u> information.<br>
			<br>
			{{Tips Navigation
			\|uplink=[[ HPC_Modelling_Guidance \| Back to HPC Modelling Guidance]]
			}}

Pavlina Monhartova: /* HPC 2D Timestep */

2021-07-16T03:38:47Z

HPC 2D Timestep

← Older revision		Revision as of 13:38, 16 July 2021
Line 34:		Line 34:
	* Celerity Control number relates to water depth relative to cell size. Energy can pass through deeper water faster than shallow water, as such deep water will trigger this control.		* Celerity Control number relates to water depth relative to cell size. Energy can pass through deeper water faster than shallow water, as such deep water will trigger this control.
	* Diffusion control relates diffusion of momentum relating to the sub grid viscosity. Small cells in deep water will trigger this one.		* Diffusion control relates diffusion of momentum relating to the sub grid viscosity. Small cells in deep water will trigger this one.
			TUFLOW will use the highest timestep possible without exceeding the limits associated with each of the control numbers.<br>

	The method TUFLOW HPC uses to calculate a timestep and achieve unconditional stability is as follows:		The method TUFLOW HPC uses to calculate a timestep and achieve unconditional stability is as follows:
	* The <font color="blue"><tt>Timestep </tt></font> command included in the TUFLOW Control File (TCF) is only used for the first calculation timestep. The specified value should be consistent with what would be appropriate for a TUFLOW Classic model (i.e. 1/2 to 1/5 the 2D cell size). Internally, TUFLOW HPC divides this value by 10 to apply a value that is suitable for an explicit solution scheme. All subsequent calculations are completed using the adaptive timestep approach outlined in the following bullet points.		* The <font color="blue"><tt>Timestep </tt></font> command included in the TUFLOW Control File (TCF) is only used for the first calculation timestep. The specified value should be consistent with what would be appropriate for a TUFLOW Classic model (i.e. 1/2 to 1/5 the 2D cell size). Internally, TUFLOW HPC divides this value by 10 to apply a value that is suitable for an explicit solution scheme. All subsequent calculations are completed using the adaptive timestep approach outlined in the following bullet points.

Pavlina Monhartova: /* HPC 2D Timestep */

2021-07-16T03:37:24Z

HPC 2D Timestep

← Older revision		Revision as of 13:37, 16 July 2021
Line 29:		Line 29:
	\|<0.3		\|<0.3
	\|}		\|}

			In general terms:
			* Courant number relates to velocity relative to the cell size. High velocities will trigger this as the control.
			* Celerity Control number relates to water depth relative to cell size. Energy can pass through deeper water faster than shallow water, as such deep water will trigger this control.
			* Diffusion control relates diffusion of momentum relating to the sub grid viscosity. Small cells in deep water will trigger this one.

	The method TUFLOW HPC uses to calculate a timestep and achieve unconditional stability is as follows:		The method TUFLOW HPC uses to calculate a timestep and achieve unconditional stability is as follows:
	* The <font color="blue"><tt>Timestep </tt></font> command included in the TUFLOW Control File (TCF) is only used for the first calculation timestep. The specified value should be consistent with what would be appropriate for a TUFLOW Classic model (i.e. 1/2 to 1/5 the 2D cell size). Internally, TUFLOW HPC divides this value by 10 to apply a value that is suitable for an explicit solution scheme. All subsequent calculations are completed using the adaptive timestep approach outlined in the following ~~bulletpoints~~.		* The <font color="blue"><tt>Timestep </tt></font> command included in the TUFLOW Control File (TCF) is only used for the first calculation timestep. The specified value should be consistent with what would be appropriate for a TUFLOW Classic model (i.e. 1/2 to 1/5 the 2D cell size). Internally, TUFLOW HPC divides this value by 10 to apply a value that is suitable for an explicit solution scheme. All subsequent calculations are completed using the adaptive timestep approach outlined in the following bullet points.
	* The HPC timestep is calculated using the hydraulic conditions from the end of the previous timestep.		* The HPC timestep is calculated using the hydraulic conditions from the end of the previous timestep.
	* If the hydraulic conditions have changed significantly it is possible for one or more of the Nu, Nc, Nd control number criteria to be violated at one or more locations within the model. For example, a sudden change in rainfall from one timestep to the next (which occurs with stepped rainfall boundaries) would potentially cause a violation. The HPC solver, by default, treats a 20% exceedance of a control number as a violation and will implement a repeat timestep feature. HPC uses a repeat timestep feature to maintain unconditional stability. The repeat timestep feature involves retaining the complete hydraulic solution from the previous (good) timestep. Should a control number anywhere within the model be exceeded by more than 20%, the solution reverts to the retained timestep, the timestep is reduced and then repeated.		* If the hydraulic conditions have changed significantly it is possible for one or more of the Nu, Nc, Nd control number criteria to be violated at one or more locations within the model. For example, a sudden change in rainfall from one timestep to the next (which occurs with stepped rainfall boundaries) would potentially cause a violation. The HPC solver, by default, treats a 20% exceedance of a control number as a violation and will implement a repeat timestep feature. HPC uses a repeat timestep feature to maintain unconditional stability. The repeat timestep feature involves retaining the complete hydraulic solution from the previous (good) timestep. Should a control number anywhere within the model be exceeded by more than 20%, the solution reverts to the retained timestep, the timestep is reduced and then repeated.

Pavlina Monhartova: /* HPC Quadtree Adaptive Timestepping */

2021-07-16T03:31:17Z

HPC Quadtree Adaptive Timestepping

← Older revision		Revision as of 13:31, 16 July 2021
Line 58:		Line 58:

	=HPC Quadtree Adaptive Timestepping=		=HPC Quadtree Adaptive Timestepping=
	~~The~~ Quadtree solver uses a single adaptive timestep for the entire model at any instance in time. Different timesteps are not applied to the respective different resolution nest levels. If a small cell resolution is nested down in water that is deeper than the cell face length, the Diffusion control number would be the critical limiter that is setting the timestep and the model will run slower than expected. This can be confirmed by reviewing the <u>[[HPC_Model_Review#HPC_dt_Time_Series_Output_.28.2A.hpc.dt.csv.29 \| hpc.dt.csv file]]</u> information.		All the above is applicable to the HPC with Quadtree simulations. In addition the Quadtree solver uses a single adaptive timestep for the entire model at any instance in time. Different timesteps are not applied to the respective different resolution nest levels. If a small cell resolution is nested down in water that is deeper than the cell face length, the Diffusion control number would be the critical limiter that is setting the timestep and the model will run slower than expected. This can be confirmed by reviewing the <u>[[HPC_Model_Review#HPC_dt_Time_Series_Output_.28.2A.hpc.dt.csv.29 \| hpc.dt.csv file]]</u> information.

Pavlina Monhartova: /* HPC Timestep Synchronisation */

2021-07-16T03:26:57Z

HPC Timestep Synchronisation

← Older revision		Revision as of 13:26, 16 July 2021
Line 54:		Line 54:
	HPC uses an adaptive timestep derived from the hydraulic conditions during a simulation. This timestepping approach creates a situation where the computational timestep does not always align exactly with the specified map and time series result output intervals. To account for this TUFLOW HPC makes a timestep adjustments to synchronize the computational timestep with output reporting times. When this occurs the minimum timestep (dt) reported in hpc.dt.csv will report a reduced timestep. This adjustment doesn’t have any effect on the hydraulic calculations, and as such, is not reported in the hpc.tlf or shown in the dt map output. The "dtStar" column in the hpc.dt.csv file also reports the calculated 2D target timestep without any result output synchronisation applied. If the hpc.dt.csv file is being used to quality check the health of a simulation, "dtStar" should be used for the analysis, not "dt".<br>		HPC uses an adaptive timestep derived from the hydraulic conditions during a simulation. This timestepping approach creates a situation where the computational timestep does not always align exactly with the specified map and time series result output intervals. To account for this TUFLOW HPC makes a timestep adjustments to synchronize the computational timestep with output reporting times. When this occurs the minimum timestep (dt) reported in hpc.dt.csv will report a reduced timestep. This adjustment doesn’t have any effect on the hydraulic calculations, and as such, is not reported in the hpc.tlf or shown in the dt map output. The "dtStar" column in the hpc.dt.csv file also reports the calculated 2D target timestep without any result output synchronisation applied. If the hpc.dt.csv file is being used to quality check the health of a simulation, "dtStar" should be used for the analysis, not "dt".<br>
	<br>		<br>
	[[File:dt_sync.png\|500px]]		[[File:dt_sync.png\|500px]]<br>
	<br>		<br>

Pavlina Monhartova: /* HPC Timestep Synchronisation */

2021-07-16T03:26:41Z

HPC Timestep Synchronisation

← Older revision		Revision as of 13:26, 16 July 2021
Line 55:		Line 55:
	<br>		<br>
	[[File:dt_sync.png\|500px]]		[[File:dt_sync.png\|500px]]
			<br>

			=HPC Quadtree Adaptive Timestepping=
			The Quadtree solver uses a single adaptive timestep for the entire model at any instance in time. Different timesteps are not applied to the respective different resolution nest levels. If a small cell resolution is nested down in water that is deeper than the cell face length, the Diffusion control number would be the critical limiter that is setting the timestep and the model will run slower than expected. This can be confirmed by reviewing the <u>[[HPC_Model_Review#HPC_dt_Time_Series_Output_.28.2A.hpc.dt.csv.29 \| hpc.dt.csv file]]</u> information.

Chris Huxley: /* HPC 2D Timestep */

2021-03-31T12:08:16Z

HPC 2D Timestep

← Older revision		Revision as of 22:08, 31 March 2021
Line 25:		Line 25:
	\|-		\|-
	\|style="height:80px;" \| Diffusion Number (Nd)		\|style="height:80px;" \| Diffusion Number (Nd)
	\|This numerical condition relates to the sub-grid scale eddy viscosity term which causes diffusion of momentum. To maintain stability the product of the eddy viscosity coefficient (ν_T) and the timestep (∆𝑡) divided by the square of the grid spacing (∆𝑥2) must remain below 0.3.		\|This numerical condition relates to the sub-grid scale eddy viscosity term which causes diffusion of momentum. To maintain stability the product of the eddy viscosity coefficient (ν_T) and the timestep (∆𝑡) divided by the square of the grid spacing (∆𝑥2) must remain below 0.3. Models controlled by the diffusion number tend to require a timestep significantly smaller than those controlled by the shallow wave celerity or courant numbers. If you find your model is predominantly diffusion controlled it may be that equivalent solution accuracy can be achieved by selecting a larger cell size. This is worth testing, as it will most likely increase the simulation speed with no loss of result fidelity.
	\|[[FILE: Diffusion Number Equation.PNG \|250px]]		\|[[FILE: Diffusion Number Equation.PNG \|250px]]
	\|<0.3		\|<0.3

Pavlina Monhartova: /* HPC Timestep Synchronisation */

2020-07-22T00:09:37Z

HPC Timestep Synchronisation

← Older revision		Revision as of 10:09, 22 July 2020
Line 52:		Line 52:

	=HPC Timestep Synchronisation=		=HPC Timestep Synchronisation=
	HPC uses an adaptive timestep derived from the hydraulic conditions during a simulation. This timestepping approach creates a situation where the computational timestep does not always align exactly with the specified map and time series result output intervals. To account for this TUFLOW HPC makes a timestep adjustments to synchronize the computational timestep with output reporting times. When this occurs the minimum timestep (dt) reported in hpc.dt.csv will report a reduced timestep. This adjustment doesn’t have any effect on the hydraulic calculations, and as such, is not reported in the hpc.tlf or shown in the dt map output. The "dtStar" column in the hpc.dt.csv file also reports the calculated 2D target timestep without any result output synchronisation applied. If the hpc.dt.csv file is being used to quality check the health of a simulation, "dtStar" should be used for the analysis not "dt".<br>		HPC uses an adaptive timestep derived from the hydraulic conditions during a simulation. This timestepping approach creates a situation where the computational timestep does not always align exactly with the specified map and time series result output intervals. To account for this TUFLOW HPC makes a timestep adjustments to synchronize the computational timestep with output reporting times. When this occurs the minimum timestep (dt) reported in hpc.dt.csv will report a reduced timestep. This adjustment doesn’t have any effect on the hydraulic calculations, and as such, is not reported in the hpc.tlf or shown in the dt map output. The "dtStar" column in the hpc.dt.csv file also reports the calculated 2D target timestep without any result output synchronisation applied. If the hpc.dt.csv file is being used to quality check the health of a simulation, "dtStar" should be used for the analysis, not "dt".<br>
	<br>		<br>
	[[File:dt_sync.png\|500px]]		[[File:dt_sync.png\|500px]]