# Coordinating development threads for next phase of control experiment

**URL:** <https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523>\
**Category:** CMIP7 development\
**Created:** [20 May 2025 01:51 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523 "2025-05-20T01:51:30Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![cbull](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/cbull/32/2203_2.png) [@cbull](https://forum.access-hive.org.au/u/cbull)\
**Post date:** [20 May 2025 01:51 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/1 "2025-05-20T01:51:31Z")

</div>

As discussed [here](https://forum.access-hive.org.au/t/csiro-access-nri-standup-minutes/3789/37) at the ESM1.6 standup 20/05/2025, this thread is to discuss and plan the upcoming combining of ESM 1.6 dev work to continue the existing Jhan simulation.

Please edit the below table with the name of the proposed update (this post is a wiki so anyone can edit it), it’s priority, target date and related github issue.

When making a contribution to the spin-up, refer to this [checklist](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/6)

| Proposed update | Priority | Coordinator | Order | GitHub Issue/PR | Status | Target Date (ready) |
| --- | --- | --- | --- | --- | --- | --- |
| Ozone | 0 | Paul | | CMIP7 official forcing. | Data ready, waiting on software update to allow download | |
| N dep | 0 | Paul | | CMIP7 official forcing. | Data ready, waiting on software update to allow download | |
| Iron dep | 0 | Dougie | | Outside CMIP7 official forcings. For the ocean only. | PR [here](https://github.com/ACCESS-NRI/access-esm1.6-configs/pull/209) | |
| Cooling in spin-up - possibly tweak ocean albedo in UM | | | | Revisit after other priority 0 changes are done | | |
| More STASH changes for data request | 0\* | | | [Additional stash outputs for data request · Issue #164 · ACCESS-NRI/access-esm1.6-configs](https://github.com/ACCESS-NRI/access-esm1.6-configs/issues/164) | Nice to have for spinup but essential for publication | |
| Any diag table changes needed for data request? | 0\* | | | | Nice to have for spinup but essential for publication | |
| code change: radiation / bgc only experiments | 0\* | | | | | |
| CABLE as a library | | | | | Still worth investigating | |
| Alternate vcmax feedback | 1 | | | | | |
| Reset sea-level? | 2 | | | | | |
| Canopy height | 2 | | | Test spatially and temporally varying canopy height · Issue #108 · ACCESS-NRI/access-esm1.6-configs | | |
| Root distribution | 2 | | | May be included with parameter changes for Australian pfts | | |
| EGNL productivity / seasonality | 2 | | | | | |
| Mediterranean ocean bathymetry change? / additional mixing | 0 | Chris | | Change bathymetry to address Mediterraean salinity increase · Issue #127 · ACCESS-NRI/access-esm1.6-configs · GitHub | Dropped | |
| | | | | | | |
| COMPLETED | | | | | | |
| Water balance fixes / adjust lprec | 0 | Spencer | 1 | A bit more work for a few days. But we’ll need to adjust lprec anyway. | Done. In access-esm1p6/2025.09.002 | |
| Switch to oneAPI compiler + use recent dependencies (MPI, NetCDF) | 0 | Manodeep | 1 | Added the known working version for oneapi by manodeep · Pull Request #126 · ACCESS-NRI/ACCESS-ESM1.6 · GitHub | PR [here](https://github.com/ACCESS-NRI/access-esm1.6-configs/pull/209). Done. In access-esm1p6/2025.09.002 | |
| cleaning up the vegetation distribution (so land use change is working) | 0 | Alex | 1b | TBD: Produce Land Use ancillaries for the ACCESS-ESM1.6 piControl experiments · Issue #54 · ACCESS-NRI/CMIP7-Input | Done. In access-esm1p6/2025.09.002 | |
| Australian PFTs | 0 | Alex | 1b | Add Australian PFTs · Issue #106 · ACCESS-NRI/access-esm1.6-configs.; [https://github.com/ACCESS-NRI/UM7/issues/129](https://github.com/ACCESS-NRI/UM7/issues/129). Summary of changes required here: [Updates required for land, including Australian pfts · Issue #191 · ACCESS-NRI/access-esm1.6-configs · GitHub](https://github.com/ACCESS-NRI/access-esm1.6-configs/issues/191) | Done. In access-esm1p6/2025.09.002 | |
| Tweaks to WOMBATlite | 1 | Pearse | | [Slight tweak to WOMBATlite default parameters for ESM1.6 · Issue #44 · ACCESS-NRI/GFDL-generic-tracers · GitHub](https://github.com/ACCESS-NRI/GFDL-generic-tracers/issues/44) | | No longer required |
| Atmosphere STASH changes | 0 | | | Pull requests · ACCESS-NRI/access-esm1.6-configs | | Added to branch 16/5/25 |
| Wombat parameter change (alkalinity gradient) | 0 | | | Dev preindustrial+concentrations pjb update1 by pearseb · Pull Request #126 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 4/6/25 |
| Wombat parameter change (disscal) | 0 | | | Update field\_table by pearseb · Pull Request #132 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 11/6/25 |
| GHG | 0 | | | Use CMIP7 GHG concentrations for PI control · Issue #110 · ACCESS-NRI/access-esm1.6-configs | | Added to branch 7/5/25 |
| Volcanic | 0 | | | Use CMIP7 volcanic forcing for PI control · Issue #114 · ACCESS-NRI/access-esm1.6-configs | | Added to branch 14/5/25 |
| Aerosols | 0 | | | Use CMIP7 aerosol emissions for PI control · Issue #123 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 6/6/25 |
| Wombat diagnostics to be output for assessing model | 1 | | | Update diag\_table\_wombatlite by dougiesquire · Pull Request #107 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 5/5/25 |
| Read number of phenology types from file | | | | Update phenology file by blimlim · Pull Request #133 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 11/6/25 |
| Wombat parameter change (alkalinity gradient) | 0 | | | Dev preindustrial+concentrations pjb update1 by pearseb · Pull Request #126 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 4/6/25 |
| Wombat parameter change (disscal) | 0 | | | Update field\_table by pearseb · Pull Request #132 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 11/6/25 |
| GHG | 0 | | | Use CMIP7 GHG concentrations for PI control · Issue #110 · ACCESS-NRI/access-esm1.6-configs | | Added to branch 7/5/25 |
| Volcanic | 0 | | | Use CMIP7 volcanic forcing for PI control · Issue #114 · ACCESS-NRI/access-esm1.6-configs | | Added to branch 14/5/25 |
| Aerosols | 0 | | | Use CMIP7 aerosol emissions for PI control · Issue #123 · ACCESS-NRI/access-esm1.6-configs · GitHub | | Added to branch 6/6/25 |
| deep\_cmt\_opt | | | | Deep CMT option · Issue #121 · ACCESS-NRI/access-esm1.6-configs | | Done / no change |
| Build system changes (see below) | 0 | Dougie | 1 | Update mom5 SPR for new CMake build system by dougiesquire · Pull Request #238 · ACCESS-NRI/spack-packages · GitHub | Done. | August spinup |
| MOM grid format update (area changes) | 0 | Dougie | 1 | Update ocean grid inputs to mosaic format · Issue #31 · ACCESS-NRI/access-esm1.6-configs · GitHub | Done. | August spinup |
| CICE5 | 0 | Anton | 1 | Create test config for cice5 integration · Issue #80 · ACCESS-NRI/access-esm1.6-configs · GitHub | Done | August spinup |

| Priority legend | |
| --- | --- |
| 0 | Absolutely essential for spinup |
| 0\* | Absolutely essential for production run |
| 1 | Would be great to have |
| 2 | In a perfect world |

If the feature you wish to add doesn’t have a GitHub issue please create one and add it to [the ESM1.6 project board](https://github.com/orgs/ACCESS-NRI/projects/14). Instructions for doing this are [here](https://github.com/orgs/ACCESS-NRI/projects/14/views/1?pane=info).

Got questions? Contentious things to discuss? Pop thoughts in this thread, below.

0\* Ice\_history.F90 Ice diagnostic edits for ice outputs in production runs parallel to STASHC and diag table changes.

---

<div class="post-metadata">

**Author:** ![micael](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/micael/32/93_2.png) [@micael](https://forum.access-hive.org.au/u/micael)\
**Post date:** [21 May 2025 22:42 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/2 "2025-05-21T22:42:27Z")

</div>

Shall we include the switch to OneAPI in that table?

---

<div class="post-metadata">

**Author:** ![cbull](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/cbull/32/2203_2.png) [@cbull](https://forum.access-hive.org.au/u/cbull)\
**Post date:** [21 May 2025 22:56 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/3 "2025-05-21T22:56:53Z")

</div>

Yes please. And any other known/planned optimisation changes.

---

<div class="post-metadata">

**Author:** ![RachelLaw](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RachelLaw](https://forum.access-hive.org.au/u/RachelLaw)\
**Post date:** [27 May 2025 23:57 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/4 "2025-05-27T23:57:18Z")

</div>

I’ve tried to group the table by changes that are more on the technical or I/O side, those that have a larger science component and those that are just on forcing. My thinking was that there is more potential to group some of the technical changes together when updating the configuration but the science changes may need to happen more incrementally.

---

<div class="post-metadata">

**Author:** ![RachelLaw](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RachelLaw](https://forum.access-hive.org.au/u/RachelLaw)\
**Post date:** [28 May 2025 23:25 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/5 "2025-05-28T23:25:06Z")

</div>

I suggest we use the first hour of our regular NESP project meeting next Wednesday (4/6, 10am) to discuss the ‘science changes’ in the table. The aim would be to prioritise which changes go in when, dependencies between changes etc. If you aren’t already on the meeting invitation but would be interested in attending, please let me know.

---

<div class="post-metadata">

**Author:** ![clairecarouge](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/clairecarouge/32/380_2.png) [@clairecarouge](https://forum.access-hive.org.au/u/clairecarouge)\
**Post date:** [4 August 2025 06:21 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/6 "2025-08-04T06:21:35Z")

</div>

Revision: 6

Here are checklists to guide contributors on updating the spin-up for ESM1.6:

### Worked example: contributor guidelines for ACCESS ESM1.6

If there is no issue for the proposed change, create an issue in [access-esm1.6-configs](https://github.com/ACCESS-NRI/access-esm1.6-configs/) to describe the change and any discussions/figures/justification/testing

Create config change as a new branch in [access-esm1.6-configs](https://github.com/ACCESS-NRI/access-esm1.6-configs/) where the branch is based on tip of `dev-preindustrial+concentrations` and named using an issue number , e.g. `99-dev-preindustrial+concentrations `for issue 99.

Makes changes to your branch and then open Pull Request (see screenshots)  
Note that changes to restart files may need to be specified for some config changes and this specifies the restart file used;

 ![Screenshot 2025-08-05 at 10.35.07 am](https://us1.discourse-cdn.com/flex020/uploads/access1/original/2X/1/1e81f373c9868c1ee15b57544ee3958cf5b5d8fc.png)

 ![Screenshot 2025-08-05 at 10.38.00 am](https://us1.discourse-cdn.com/flex020/uploads/access1/original/2X/b/b94561175a78f8a0b0e4ee842302a366c2840587.png)

Request for review;

Merge your changes into `dev-preindustrial+concentrations`.

### Worked example: How to update the spin up (inputs from reviewer, contributor and runner)

Reviewer/contributor decide if a tag is going to be needed on the merged version on the `dev-preindustrial+concentrations` branch (a tag is used when the spin up will be updated).

Ask runner to continue run based on tagged commit.

Update [experiment tables](https://forum.access-hive.org.au/t/esm1-6-spin-up-experiments/4219) on ACCESS-Hive forum.

### Worked example: runner (@Jhan) guidelines for ACCESS ESM1.6

Pull or clone fresh from the tagged commit of [GitHub - ACCESS-NRI/access-esm1.6-configs: Standard ACCESS-ESM1.6 configurations released and supported by ACCESS-NRI](https://github.com/ACCESS-NRI/access-esm1.6-configs/) (should be on `dev-preindustrial+concentrations` branch);

Continue run deciding to either use an older restart (to provide some overlapping years), parallel runs or an abrupt change;

Update [experiment tables](https://forum.access-hive.org.au/t/esm1-6-spin-up-experiments/4219) on ACCESS-Hive forum;

Update [coordination table](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523) on ACCESS-Hive forum.

Please reach out to @Jhan as the `runner` to coordinate getting changes added. And @anton and @spencerwong for any technical guidance on contributor steps. And @clairecarouge and @cbull are available to help too.

---

<div class="post-metadata">

**Author:** ![RachelLaw](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RachelLaw](https://forum.access-hive.org.au/u/RachelLaw)\
**Post date:** [23 September 2025 00:28 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/7 "2025-09-23T00:28:55Z")

</div>

**Spin-up options with (late-September) consolidated code**

This table describes alternate spin-up options for code base with ocean albedo scaling, CICE5, oneAPI etc, new vegetation distribution including Australian pfts, water balance fixes. Some forcings still to be updated. Some diagnostics still to be added.

| Name | Atmos restart | Ocean restart | Ocean BGC restart | CICE restart | Notes | Branch name |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | land-update 40 | April 500 | April 500 | 2025-08-01 | 0.92 albedo - Jhan. Use year number from April run | test-PIspinup-Sept-A |
| 2 | land-update 40 | April where June started | April where June started | 2025-08-01 | 0.92 albedo - Jhan. Use year number from April | test-PIspinup-Sept-B |
| 3 | | | | | 0.90 albedo - Martin to test | |
| 4 | | | | | Try a case with Mediterranean mixing? | |
| | | | | | | |
| | | | | | | |

---

<div class="post-metadata">

**Author:** ![cbull](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/cbull/32/2203_2.png) [@cbull](https://forum.access-hive.org.au/u/cbull)\
**Post date:** [23 September 2025 00:32 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/8 "2025-09-23T00:32:48Z")

</div>

Thanks for starting a table @RachelLaw, would it be better placed [here](https://forum.access-hive.org.au/t/esm1-6-spin-up-experiments/4219) do you think? (One can move posts by clicking on the wrench icon)

---

<div class="post-metadata">

**Author:** ![RachelLaw](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RachelLaw](https://forum.access-hive.org.au/u/RachelLaw)\
**Post date:** [23 September 2025 00:43 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/9 "2025-09-23T00:43:22Z")

</div>

@cbull - I was thinking discussion of options works here while the other post maintains the summary of the ones that form our spin-up chain - a ‘master list’. This will inevitably get more complicated now we are proposing to pull restarts for the different components from different runs, including some that may not be on the master list yet.

---

<div class="post-metadata">

**Author:** ![RachelLaw](https://avatars.discourse-cdn.com/v4/letter/r/da6949/32.png) [@RachelLaw](https://forum.access-hive.org.au/u/RachelLaw)\
**Post date:** [23 September 2025 00:46 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/10 "2025-09-23T00:46:31Z")

</div>

@anton - for filling out this spin-up table - what options do we have for CICE5 restarts and do we have to be careful about compatibility with other restarts?

---

<div class="post-metadata">

**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\
**Post date:** [23 September 2025 01:08 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/11 "2025-09-23T01:08:07Z")

</div>

The only cice5 restarts are

/g/data/vk83/prerelease/configurations/inputs/access-esm1p6/modern/pre-industrial/restart/2025.08.01

which is year 1843

and those from the August spin-up run (years 1843 to 20xx)

The retained cliamte memory in the sea ice is small - it will equalibriate with the ocean quickly. But the year in the cice restart needs to match the other components - [it can be changed](https://github.com/ACCESS-NRI/access-esm1.6-configs/pull/147#issuecomment-3138259417) using `nco`

---

<div class="post-metadata">

**Author:** ![sofarrell](https://avatars.discourse-cdn.com/v4/letter/s/ea5d25/32.png) [@sofarrell](https://forum.access-hive.org.au/u/sofarrell)\
**Post date:** [26 September 2025 06:59 UTC](https://forum.access-hive.org.au/t/coordinating-development-threads-for-next-phase-of-control-experiment/4523/12 "2025-09-26T06:59:09Z")

</div>

@RachelLaw Have we dropped the idea of starting from the beginning of the April run when the solar constant change but bring some of the BGC fields back to the start, are you baking in that first 500 years of excess cooling in the Southern Ocean in particular.
