Skip to content

Remove makefile support from mom5 and use tag-based versions - #443

Merged
harshula merged 12 commits into
api-v2from
cleanup-before-esm1.6-release
Aug 6, 2026
Merged

Remove makefile support from mom5 and use tag-based versions#443
harshula merged 12 commits into
api-v2from
cleanup-before-esm1.6-release

Conversation

@harshula

@harshula harshula commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Motivation

Caveat

If we need to backport a bug fix for gcom4 or um7 for ACCESS-ESM1.5, we could create a new branch api-v2-esm1.5 that branches off the commit just before the commit containing this PR's merge.

Pre-merge actions

  • Update the access-spack-packages tag mentioned in the source files. e.g., "access-esm1.5 is only available in access-spack-packages tagged 2026.07.010 and older."

Component Repository CI manifest fixes.

Post-merge actions

@harshula harshula self-assigned this Jun 16, 2026
@github-project-automation github-project-automation Bot moved this to New Issues 🌅 in Model Release Jun 16, 2026
@harshula
harshula force-pushed the cleanup-before-esm1.6-release branch from 4c9a302 to 4d07b33 Compare June 18, 2026 07:09
@harshula harshula changed the title Remove makefile support from cice5 and mom5 Remove makefile support from access-mocsy and mom5 Jun 18, 2026
@harshula
harshula force-pushed the cleanup-before-esm1.6-release branch from be19aa5 to 8889c48 Compare June 22, 2026 07:58
@harshula harshula changed the title Remove makefile support from access-mocsy and mom5 Remove makefile support from mom5 Jun 22, 2026
@harshula

Copy link
Copy Markdown
Collaborator Author

The blocker for this PR is that https://github.com/ACCESS-NRI/ACCESS-ESM1.5 (https://github.com/ACCESS-NRI/ACCESS-ESM1.5/blob/f2572827861803b9a9165821d4a7e96d9566c515/spack.yaml#L17-L19) uses the following MOM5 branch:

version("access-esm1.5", branch="access-esm1.5")
and that branch (https://github.com/ACCESS-NRI/MOM5/tree/access-esm1.5) does not contain a CMake build system.

@harshula

Copy link
Copy Markdown
Collaborator Author

To unblock this PR, could we put a comment stating only use up to X (e.g. 2026.06.004) version of access-spack-packages above https://github.com/ACCESS-NRI/ACCESS-ESM1.5/blob/f2572827861803b9a9165821d4a7e96d9566c515/config/versions.json#L4 .

@harshula
harshula marked this pull request as ready for review June 23, 2026 10:53
@dougiesquire

Copy link
Copy Markdown
Contributor

To unblock this PR, could we put a comment stating only use up to X (e.g. 2026.06.004) version of access-spack-packages above https://github.com/ACCESS-NRI/ACCESS-ESM1.5/blob/f2572827861803b9a9165821d4a7e96d9566c515/config/versions.json#L4 .

I'll wait for @aidanheerdegen to confirm he's fine with this before reviewing

@aidanheerdegen

aidanheerdegen commented Jun 25, 2026

Copy link
Copy Markdown
Member

I am fine with this as long as it is still possible for a user to take the ACCESS-ESM1.5 deployment spack.yaml and build it on gadi and make minor code changes. This would necessarily be limited to the versions of dependencies pinned at the point of this change, but I think that is fine.

This gets a bit more complex when we move to a new HPC. At that point we'd need to decide if ESM1.5 was going to be supported on the new architecture, and if so we would need to look at the work required to do so. But I think it is fine wait and see and make a decision then.

@anton-seaice
anton-seaice removed their request for review June 25, 2026 03:19

@dougiesquire dougiesquire left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @harshula

Comment thread spack_repo/access/nri/packages/mom5/package.py Outdated
Comment thread spack_repo/access/nri/packages/mom5/package.py Outdated
@harshula

Copy link
Copy Markdown
Collaborator Author

This PR should be merged after Issue #446 is fixed and merged.

@harshula
harshula requested a review from dougiesquire June 29, 2026 06:25
Comment thread spack_repo/access/nri/packages/mom5/package.py
@harshula
harshula force-pushed the cleanup-before-esm1.6-release branch from c7a9a8a to b3e085b Compare July 6, 2026 03:05
@harshula
harshula force-pushed the cleanup-before-esm1.6-release branch 2 times, most recently from 641ad99 to 604f274 Compare July 7, 2026 04:15
* cice4 is a dependency of only access-esm1.5.
* access-esm1.5 will not be buildable after Makefile support
  is removed from the MOM5 SPR.
* Claude Opus 5 suggested the comment update.
* Dougie Squire suggested constraining versioning.

@dougiesquire dougiesquire left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @harshula, looking good!

Comment thread spack_repo/access/nri/packages/gcom4/package.py Outdated
Comment thread spack_repo/access/nri/packages/gcom4/package.py
* Dougie Squire suggested adding a msg to the conflicts().
* Add version stable and tag-based versions
* Add a version that corresponds to the um7 version used in ACCESS-ESM1.5.
* Tommy Gatti suggested adding a conflict() to prevent building
  access-esm1.5, instead of deleting the SBR from the repository.
@harshula
harshula force-pushed the cleanup-before-esm1.6-release branch from bcd37cd to 91c56c2 Compare August 5, 2026 05:29
@harshula
harshula requested a review from dougiesquire August 5, 2026 05:31
* Suggested by Aidan Heerdegen.
@harshula
harshula force-pushed the cleanup-before-esm1.6-release branch from 91c56c2 to 439f787 Compare August 5, 2026 06:12

@dougiesquire dougiesquire left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @harshula.

I think we need to replace the =access-esm1.5 with =stable in the gcom4 build-ci manifests?

Similarly for um7 build-ci manifests. Looks like the oasis3-mct version should be updated in these also.

@harshula

harshula commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator Author

Hi @dougiesquire ,

I think we need to replace the =access-esm1.5 with =stable in the gcom4 build-ci manifests?

Similarly for um7 build-ci manifests.

Already documented in the PR description.

@harshula
harshula requested a review from dougiesquire August 5, 2026 11:24
@dougiesquire

Copy link
Copy Markdown
Contributor

Already documented in the PR description.

Sorry, missed that. Is there a reason why these are to be done after merge but the equivalent in MOM5, libaccessom2 and oasis3-mct were done before?

@harshula

harshula commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator Author

Hi @dougiesquire ,

Sorry, missed that. Is there a reason why these are to be done after merge but the equivalent in MOM5, libaccessom2 and oasis3-mct were done before?

This PR is blocker for the ACCESS-ESM1.6 release and I would prefer not to keep completing tasks that should be completed by others.

@dougiesquire dougiesquire left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Roger. Thanks for all your work on this

@harshula
harshula merged commit e3330a8 into api-v2 Aug 6, 2026
46 of 50 checks passed
@github-project-automation github-project-automation Bot moved this from New Issues 🌅 to Done ✅ in Model Release Aug 6, 2026
@harshula
harshula deleted the cleanup-before-esm1.6-release branch August 6, 2026 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done
Status: Done ✅

Development

Successfully merging this pull request may close these issues.

7 participants