HPC Adaptive Timestepping: Difference between revisions

Content deleted Content added
Line 43:
 
=HPC 1D Timesteping=
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 BothESTRY 1D and<font 2Dcolor="blue"><tt>Timestep solutions</tt></font> arecommand always synchronising at the 2D target timestep, orfor a multiple of theHPC 1D/2D targetlinked timestep if the 1D timestepmodel is sufficiently greater for the 2D to perform more than one step. If the 1Dmaximum limiting timestep is less than half the 2D target timestep, the 1D proceedssolver incan twouse, or more steps eventually synchronising with the 2D timestep. Where there is not a one to one synchronisation ofand the 1D and 2D timesteps,solutions aare usuallysynchronised negligible mass error may occur and can be checked by reviewing the CME% values shownbased on the Consolesize Window,of the .tlf"maximum file1D ortimestep" the _MB.csv file inand the same"target manner2D as Classic.timestep":
* If target 2D timestep = maximum 1D timestep: No adjustment is made.
The ESTRY 1D <font color="blue"><tt>Timestep </tt></font> for a HPC 1D/2D linked model is the maximum limiting timestep the 1D solver can use.<br>
* 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.
<br>
[[File:1d2ddt.png|800px]]