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
@har917 Can you check the issue above and make sure I understood the conversation here correctly? Is that so we need the L_REV_CORR option on in all ESM1.6 configurations.
From what I can see, I think Jhan added it to his running configuration but not to the shared configurations in this repository.
offline runs do NOT need the correction terms - l_rev_corr shouldn't make a difference because all usage should be inside a cable_runtime%um_implicit like condition [but this itself is confused]
ESM1.5 effectively has l_rev_corr = .FALSE.
all future coupled configurations should have l_rev_corr = .TRUE. by default [unless someone really wants to go backwards].
Whether the route to ensure the switch takes a TRUE value is via the standard configuration (namelist) or hard-wired into the code somehow is down to NRI preference.
In the longer term we should either
work to remove the switch from the code base entirely (it was only implemented this way to allow for backwards compatibility]
(my preference) remove the correction terms from the codebase entirely (they're a blocker for SLI)
To improve on the energy balance, we need to have the following option in
cable.nml
:This option was introduced for work on ACCESS-CM2 to improve the energy balance and should be in used for ACCESS models based on CABLE3.
The option should be set in all configurations.
The text was updated successfully, but these errors were encountered: