Skip to content

Conversation

@manodeep
Copy link
Collaborator

@manodeep manodeep commented Dec 23, 2025

1. Summary:

What has changed?
Swapping over to the latest ESM 1.6 release with upstream oasis3-mct v5.2

Why was this done?
Changing over to a later version of oasis3-mct (our current version is v2.x)

2. Issues Addressed:

3. Dependencies (e.g. on payu, or model)

This change requires changes to (note pull request(s) where relevant):

4. Ad-hoc Testing

What ad-hoc testing was done? How are you convinced this change is correct (plots are good)?

5. CI Testing

  • !test repro has been run

6. Reproducibility

Is this reproducible with the previous commit? (If not, why not?)

  • Yes
  • No - !test repro commit has been run.

7. Performance

Has the model performance (say, throughput of model-years/wall-day) changed?

  • Yes
  • No
  • N/A (if selected, please add a brief explanation why performance testing is not necessary for this PR)

If yes, provide the numbers from your testing. Is the performance better or worse?

8. Manifests

Have you changed the executable, the input files and/or the restart files?

  • Yes
  • No

If yes, have you updated the manifests?

  • Yes
  • No

To update the manifests, run payu setup (in a cloned copy of your feature branch) with reproducibility tests turned off:

manifest:
  reproduce:
    exe: false
    input: false
    restart: false
runlog:
  enable: false

Then commit the newly created manifest files (under manifests/) only to the branch for this PR.

9. Documentation

Is the documentation updated?

  • Yes
  • N/A

10. Merge Strategy

  • Merge commit
  • Rebase and merge
  • Squash

@manodeep
Copy link
Collaborator Author

!test repro

@manodeep manodeep requested a review from blimlim December 23, 2025 05:02
@github-actions
Copy link

✅ The Bitwise Reproducibility Check Succeeded ✅

When comparing:

  • update-to-upstream-oasis3-mct (checksums created using commit 0fe6cec), against
  • dev-preindustrial+concentrations (checksums in commit a99602d)
Further information

The experiment can be found on Gadi at /scratch/tm70/repro-ci/experiments/access-esm1.6-configs/0fe6cec823704f9058b2123ee2cb15da7a82f3b7, and the test results at https://github.com/ACCESS-NRI/access-esm1.6-configs/runs/58767198104.

The checksums generated by this !test command are found in the testing/checksum directory of https://github.com/ACCESS-NRI/access-esm1.6-configs/actions/runs/20451799654/artifacts/4950060882.

The checksums compared against are found here https://github.com/ACCESS-NRI/access-esm1.6-configs/tree/a99602d85a5704c748ff578da601ebb85834c9c0/testing/checksum

Test summary:
test_repro_historical
test_repro_determinism

Copy link
Collaborator

@blimlim blimlim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @manodeep, changes look good to me!

# oa3-mct v5.0 has multiple options for this
# $NLOGPRT: The first, second and third numbers on the line below this keyword refer to (i) the
# debug verbosity, (ii) internal timing statistics and (iii) component load balancing analysis. The
# information is written by OASIS3-MCT for each component and (optionnally) for each process.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# information is written by OASIS3-MCT for each component and (optionnally) for each process.
# information is written by OASIS3-MCT for each component and (optionally) for each process.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just realised this is copied directly from the docs, so maybe just leave it as it is.

@manodeep manodeep mentioned this pull request Feb 9, 2026
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants