This topic is to collate meeting notes around the ongoing development of ACCESS-AM3 with a focus on role of CABLE.
Key individuals: @clairecarouge @MartinDix @ben @Jhan @inh599
This topic is to collate meeting notes around the ongoing development of ACCESS-AM3 with a focus on role of CABLE.
Key individuals: @clairecarouge @MartinDix @ben @Jhan @inh599
Meeting 16/1/2025
Status of developments:
%fes_cor
being the key and necessary example) so this is not fully resolvable.Additional open topics:
Other notes:
To do:
Next meeting: we will continue with fortnightly meetings for the moment (i.e. 30th January), but may relax to less frequently given focus on ESM1.6.
I am loathe to add an issue when I am trying to get rid of them BUT if this is deemed as an (reproducibility) important part of AM3 then I will add it to the STASH. My hesitation is that this alone will not give us reproducibility?
@Jhan It maybe better to go through the effort of adding this to STASH/restart (though whether to do that for AM3 only or both is a different question). Remember this %fes_cor
issue is only a small effect acting on the first time step of each restart. I can’t guarantee that this is the only cause of the current failure of restart reproducibility, but was noting that this particular cause is known.
I’m still hoping that we can find time to rethink/assess the whole correction terms topic and see if we can find a way past them (without breaking conservation). This would simplify the syncing between offline and coupled, conceivably allow us to investigate the use of SLI, and/or allow for our soil&snow time stepping to moved out from implicit into extras (to align better with JULES).
Meeting notes 30/1/2025
updates
cbm()
routine which may be the cause.%fes_cor
, %gammzz
, %osnowd
, and %rtsoil
. This should resolve restart reproducibilty in AM3 (with current configuration - at least %ga
[Penman-Monteith] would be needed to be added to ensure reproducibility across all configurations).Other notes
To do
cbm()
bug fix to be formally lodged as an AM3 issue (@Jhan @MartinDix)cbm()
bug fix also to be implemented in ESM1.6cbm()
fix to determine whether oscillations/spikes have been resolved (@MartinDix)snow_Aging()
routine which could avoid the need for osnowd
to be in the restart.