Remove makefile support from mom5 and use tag-based versions - #443
Conversation
4c9a302 to
4d07b33
Compare
be19aa5 to
8889c48
Compare
|
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: and that branch (https://github.com/ACCESS-NRI/MOM5/tree/access-esm1.5) does not contain a CMake build system. |
|
To unblock this PR, could we put a comment stating only use up to X (e.g. |
I'll wait for @aidanheerdegen to confirm he's fine with this before reviewing |
|
I am fine with this as long as it is still possible for a user to take the ACCESS-ESM1.5 deployment 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. |
|
This PR should be merged after Issue #446 is fixed and merged. |
c7a9a8a to
b3e085b
Compare
641ad99 to
604f274
Compare
* Add version 2026.02.000
* Add version 2025.08.000.
* 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.
cea2b28 to
bcd37cd
Compare
dougiesquire
left a comment
There was a problem hiding this comment.
Thanks @harshula, looking good!
* 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.
bcd37cd to
91c56c2
Compare
* Suggested by Aidan Heerdegen.
91c56c2 to
439f787
Compare
dougiesquire
left a comment
There was a problem hiding this comment.
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.
|
Hi @dougiesquire ,
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? |
|
Hi @dougiesquire ,
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
left a comment
There was a problem hiding this comment.
Roger. Thanks for all your work on this
Motivation
Caveat
If we need to backport a bug fix for
gcom4orum7forACCESS-ESM1.5, we could create a new branchapi-v2-esm1.5that branches off the commit just before the commit containing this PR's merge.Pre-merge actions
access-spack-packagestag 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