# Difference between revisions of "HPC Adaptive Timestepping"

(→HPC Timestep Synchronisation) |
Chris Huxley (Talk | contribs) (→HPC Timestep Synchronisation) |
||

Line 52: | Line 52: | ||

=HPC Timestep Synchronisation= | =HPC Timestep Synchronisation= | ||

− | HPC | + | HPC uses an adaptive timestep derived from the hydraulic conditions during a simulation. This time stepping 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 reports the calculated 2D target timestep without any result output synchronisation applied. As such, 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_synchronising_graph.png]] [[File:dt_synchronising.png|200px]] | [[File:dt_synchronising_graph.png]] [[File:dt_synchronising.png|200px]] |

## Revision as of 12:40, 14 July 2020

# Introduction

The HPC solver, by default, uses adaptive timestepping to progress through the simulation. The timestep is adjusted so that it complies with the mathematical stability criteria of a 2D SWE explicit solution. In contrast, TUFLOW Classic, being an implicit solution, is not numerically bound by these criteria, and can progress through the simulation using a fixed timestep. Due to the underlying solution scheme, HPC typically uses a smaller timestep than Classic. the following sections outline how TUFLOW HPC automatically selects its adaptive timestep.

# HPC 2D Timestep

TUFLOW HPC uses adaptive timestepping to maintain stability. There are three primary processes that determine the maximum timestep that an explicit solution to the Shallow Water Equations can use:

- Courant Number, Nu
- Wave Celerity Number, Nc
- Diffusion Number, Nd

The method TUFLOW HPC uses to calculate a timestep and achieve unconditional stability is as follows:

- The
`Timestep`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 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.
- Each timestep is also tested for the occurrence of NaNs. A NaN is “Not a Number” and occurs due to undefined mathematical calculations such as a divide by zero or square root of a negative number. The occurrence of a NaN is also indicative of a sudden instability. Should a NaN occur, the repeat timestep feature is implemented.
- Should a timestep need to be repeated more than ten times consecutively, the solution stops.
- The simulation will also stop if the default minimum permissible timestep of 0.1 seconds has been reached. This value can be manually adjusted using
`Timestep Minimum`.

Repeated timesteps are displayed to the Console Window and the number of them for a time interval are provided in the nRS_NaNs and nRS_HCNs columns in the _HPC.csv file output in the results folder. They are also reported to the _messages layer.

Repeated timesteps are an indication the 2D HPC solution is numerically “on-the-edge”. Models that have a high number of repeated timesteps should be sensitivity tested by reducing the control number limits using `Control Number Factor`. For example, repeat the simulation using `Control Number Factor``==`` 0.8 ` and compare the results. If there are acceptably immeasurable changes in the results, then running at the default control number limits can be considered satisfactory.

*NOTE: Models that require an excessively small 2D timestep to remain stable are symptomatic of models with input topography or boundary condition errors. Please refer to [Tutorial_Module03 | Tutorial Module 03] for discussion on this topic.*

# HPC 1D Timestep

HPC links with the 1D solver, ESTRY. When run with HPC (instead of Classic) ESTRY has been reconfigured to automatically act as an adaptive/varying timestep solution, and can step at different multiples of steps to the HPC 2D solver. The ESTRY 1D `Timestep ` command for a HPC 1D/2D linked model is the maximum limiting timestep the 1D solver can use, and the 1D and 2D solutions are synchronised based on the size of the "maximum 1D timestep" and the "target 2D timestep":

- If target 2D timestep = maximum 1D timestep: No adjustment is made.
- If target 2D timestep > maximum 1D timestep: the 1D proceeds in two or more steps eventually synchronising with the target 2D timestep.
- If target 2D timestep < Maximum 1D timestep: the 2D timestep is reduced below the target value to synchronise with 1D at a multiple of the 2D timesteps.

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.

# HPC Timestep Synchronisation

HPC uses an adaptive timestep derived from the hydraulic conditions during a simulation. This time stepping 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 reports the calculated 2D target timestep without any result output synchronisation applied. As such, 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".

File:Dt synchronising graph.png 200px