Tuflow

HPC Adaptive Timestepping: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
m Updated limits to reflect the expressions
Β 
(20 intermediate revisions by 2 users not shown)
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 (βˆ†π‘₯).
|[[FILE: Courant Number Equation.PNG |250px]]
|<1≀1.0
|-
|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.
|[[FILE: SWC Number Equation.PNG |250px]]
|<1≀1.0
|-
|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.
|[[FILE: Diffusion Number Equation.PNG |250px]]
|<0≀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.
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 <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 bulletpointsbullet points.
* 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.
Line 52 ⟢ 57:
 
=HPC Timestep Synchronisation=
HPC usinguses an adaptive timestep doesn'tderived necessarilyfrom synchronisethe 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 intervalintervals. InTo suchaccount case,for thethis minimumTUFLOW timestepHPC (dt)makes reporteda intimestep hpc.dt.csvadjustments willto showsynchronize reducedthe computational timestep towith allowoutput forreporting writingtimes. resultsWhen exactlythis atoccurs the mapminimum andtimestep time(dt) seriesreported outputin intervalhpc.dt.csv will report a reduced timestep. This adjustment doesn’t have any effect on the hydraulic calculationcalculations, itand as such, is not reported in the hpc.tlf, neitheror showsshown in the dt map output. The "dtStar" column in the hpc.dt.csv isfile 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>
[[File:dt_sync.png|500px]]<br>
<br>
 
=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.<br>
<br>
{{Tips Navigation
|uplink=[[ HPC_Modelling_Guidance | Back to HPC Modelling Guidance]]
}}
Retrieved from "https://wiki.tuflow.com/HPC_Adaptive_Timestepping"