Meeting minutes 02/12/2025
Participants: @Jhan @clairecarouge @pearseb @dhb599 @dougiesquire @inh599 @lachlanswhyborn @manodeep @MartinDix @paulleopardi @RachelLaw @sofarrell @anton @Aidan
Chair: @clairecarouge
Minutes: @cbull
Off-topic but @Jhan thinks he doesn’t have write privileges to the am3 repo.
bgc update
@Jhan we have the two sinking rates tests going that have 130 and 150 years run so far (high and standard). @pearseb let’s go with the “standard” value.
ozone forcing
@MartinDix should be able to get it out in the next few days (pi control).
@paulleopardi pre-industrial ozone is currently being worked on
@paulleopardi: working on the preindustrial ozone forcing, but am not sure if the UK Met Office code will work in our context. @paulleopardi has a fallback that calculates the ozone in a different way, but not yet sure if that calculation is valid.
optimisation update
gadi’s problems have slowed work down
With the latest version we’re still getting 25 years per day with 5 nodes.
Manodeep is doing a load balancing analysis using oasis3mct, just started but this kind of work hasn’t been done in the past so maybe there is some scope for performance improvements.
Re: Amip performance. Last week there was a request to see if performance would be improved from increasing from 2 nodes to say 5 nodes. @MartinDix won’t be running amip runs immediately so you’ve got some time.
@anton is amip part of fast track? yes.
misc configuration discussion
@clairecarouge: what’s next for planning on the configurations.
@RachelLaw. We want to run:
- pi control
- emissions driven pi-control
- any of the idealised run that branch off pi control (e.g. 1% CO2, 4xCO2)
@anton How long is @spencerwong away for? (tomorrow) – relevant as Spencer was working on keeping all the configs sync’d up. @MartinDix emissions driven is pretty simple to set up.
We would like to keep amip up to date too.
@MartinDix would like to do some configuration clean up. Getting rid of an unused namelist variable(s), configurations will need to be updated.
plan for a release?
@anton. Should we press on for multiple configurations releases. This year? Next year? Some of the things to do include: Creating a release branch / release tag / publicly, Final configuration, Forcing finalised?
@Jhan missing field in sea ice? Is this part of the release @anton?
@inh599 doesn’t think we can go to full. Haven’t checked the stash codes. Thinks a beta is realistic.
@cbull. What kind of release are we aiming for? Full, beta?
@Aidan does not have specific plans in terms of a release.
@clairecarouge thinks the documentation needs improvement before release. Some offline discussions have suggested that people don’t have time before January. Interested to hear best ways to coordinate this.
On config documentation, we have some notes here.
Perhaps sections could be assigned via sub-issues of this issue?
@anton project board could be used too.
Misc
@cbull will be stepping away from ESM1.6 coordination to work on OM3/CM3 evaluation. @anton will take on the role.