Skip to content

Conversation

@minghangli-uni
Copy link
Collaborator

@minghangli-uni minghangli-uni commented Dec 9, 2025

1. Summary:

What has changed?
config.yaml, MOM_input, nuopc.runconfig, docs/MOM_parameter_doc.layout, and manifests/input.yaml.

Why was this done?
Remain consistency with #970

2. Issues Addressed:

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

This change requires changes to (note required version where true):

  • payu:
  • access-om3:
  • om3-scripts:

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. Documentation

The docs folder has been updated with output from running the model?

  • Yes
  • N/A

A PR has been created for updating the documentation?

  • Yes:
  • N/A

8. Formatting

Changes to MOM_input have been copied from model output in docs/MOM_parameter_docs.short?

  • Yes
  • N/A

9. Merge Strategy

  • Merge commit
  • Rebase and merge
  • Squash

minghangli-uni and others added 2 commits December 9, 2025 14:48
* Add mask_table.1038.63x56

* Replace AUTOMASKTABLE with offline generated masktable

Add layout and iolayout

* Change processor layout in nuopc.runconfig and ncpus/mem in config.yaml

* Add mask_table.1038.63x56 to manifests/input.yaml

* Updated checksums as part of https://github.com/ACCESS-NRI/access-om3-configs/actions/runs/20048855820

* Update docs/MOM_parameter_doc.layout

* Update MOM_input according to docs/MOM_parameter_doc.layout

---------

Co-authored-by: access-bot <[email protected]>
Co-authored-by: Andrew Kiss <[email protected]>
@minghangli-uni minghangli-uni self-assigned this Dec 9, 2025
@minghangli-uni
Copy link
Collaborator Author

!test repro commit

@minghangli-uni minghangli-uni marked this pull request as ready for review December 9, 2025 04:10
@github-actions
Copy link

github-actions bot commented Dec 9, 2025

❌ The Bitwise Reproducibility Check Failed ❌

When comparing:

  • cherry-pick-processor-layout-masktable-25km-ryf (checksums created using commit a9caa54), against
  • dev-MC_25km_jra_ryf (checksums in commit 2637f9a)

🔧 The new checksums will be committed to this PR, if they differ from what is on this branch.

Further information

The experiment can be found on Gadi at /scratch/tm70/repro-ci/experiments/access-om3-configs/a9caa54b41d7fcdf4edcdaae8a6526968837e1dd, and the test results at https://github.com/ACCESS-NRI/access-om3-configs/runs/57508967570.

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

The checksums compared against are found here https://github.com/ACCESS-NRI/access-om3-configs/tree/2637f9a45cc802958dbeac941cb5c7ca09ac6455/testing/checksum

Test summary:
test_repro_historical

@minghangli-uni minghangli-uni requested a review from aekiss December 9, 2025 04:20
@minghangli-uni
Copy link
Collaborator Author

Hi @aekiss , this is a companion PR cherry-picking #970, could you please have a look?

Copy link
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

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

Unsolicited review. Looks good, thanks @minghangli-uni

Copy link
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

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

Actually hang on one sec

@dougiesquire
Copy link
Collaborator

See #1004

@minghangli-uni
Copy link
Collaborator Author

@dougiesquire Should I update the "corrected" numbers here or align them with the 25km iaf configuration for consistency?

@dougiesquire
Copy link
Collaborator

If you have the updated layout ready to go, maybe just close this PR and open a new one to dev-MC_25km_jra_ryf. Then we can get that merged and can cherry-pick into dev-MC_25km_jra_iaf after we release tomorrow

@dougiesquire
Copy link
Collaborator

@minghangli-uni any updates here? Would be good to get this sorted and get things consistent again across our config branches

@minghangli-uni
Copy link
Collaborator Author

Now that 94b7eb3 has been merged, I’ll redo the processor layout - it should be much faster with this change in place.

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.

4 participants