You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue covers parameters related to THERMO_SPANS_COUPLING within the module MOM of the MOM input parameters.
In MOM6, tracer advection is stepped with the thermodynamic timestep, which can be much longer than the coupling timestep. This can be achieved by enabling THERMO_SPANS_COUPLING. In the following setup, it is set to 8100s, which is 6 times longer than the coupling timestep of 1350s. Similar tracer timesteps can be found in GFDL OM4 0.25deg, and GFDL OM5 0.25deg.
THERMO_SPANS_COUPLING = True ! [Boolean] default = False
! If true, the MOM will take thermodynamic and tracer timesteps that can be
! longer than the coupling timestep. The actual thermodynamic timestep that is
! used in this case is the largest integer multiple of the coupling timestep
DT_THERM = 8100.0 ! [s] default = 1350.0
! The thermodynamic and tracer advection time step. Ideally DT_THERM should be
! an integer multiple of DT and less than the forcing or coupling time-step,
! unless THERMO_SPANS_COUPLING is true, in which case DT_THERM can be an integer
! multiple of the coupling timestep. By default DT_THERM is set to DT.
DTBT_RESET_PERIOD = 8100.0 ! [s] default = 1350.0 - (DT_THERM)
! The period between recalculations of DTBT (if DTBT <= 0). If DTBT_RESET_PERIOD
! is negative, DTBT is set based only on information available at
! initialization. If 0, DTBT will be set every dynamics time step. The default
! is set by DT_THERM. This is only used if SPLIT is true.
A preliminary test compared two cases for a 10-day run using 1440 cpu cores with a PE layout of #ocn: 1344, #ice: 96, #cpl: 96, #atm: 48 and #rof: 48.
Case
dt_dyn
dt_therm_ice
dt_cpl
dt_therm
Run duration (ocn)
THERMO_SPANS_COUPLING = False
1350s
1350s
1350s
1350s
465.23s
THERMO_SPANS_COUPLING = True
1350s
1350s
1350s
8100s
221.97s
The results show a reduction in run duration from 465.23s to 221.97s, significantly improving performance.
However, further scientific testing for longer runs is necessary to confirm that the differences are negligible.
The text was updated successfully, but these errors were encountered:
Thanks @minghangli-uni. This looks like a duplicate of #138. Could you maybe move this to a comment there so we can close this issue and just have one?
Thank you @dougiesquire. I was thinking that submitting a PR linked to a comment within an issue rather than to the beginning of the issue, might cause some kind of confusion. But this definitely requires further evaluation and testing, such as altering dt_therm.
This issue covers parameters related to
THERMO_SPANS_COUPLING
within themodule MOM
of the MOM input parameters.In MOM6, tracer advection is stepped with the thermodynamic timestep, which can be much longer than the coupling timestep. This can be achieved by enabling
THERMO_SPANS_COUPLING
. In the following setup, it is set to 8100s, which is 6 times longer than the coupling timestep of 1350s. Similar tracer timesteps can be found in GFDL OM4 0.25deg, and GFDL OM5 0.25deg.A preliminary test compared two cases for a 10-day run using 1440 cpu cores with a PE layout of #ocn: 1344, #ice: 96, #cpl: 96, #atm: 48 and #rof: 48.
The results show a reduction in run duration from 465.23s to 221.97s, significantly improving performance.
However, further scientific testing for longer runs is necessary to confirm that the differences are negligible.
The text was updated successfully, but these errors were encountered: