Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create default deployment PR for esm1.6 #14

Open
ccarouge opened this issue Dec 1, 2024 · 2 comments
Open

create default deployment PR for esm1.6 #14

ccarouge opened this issue Dec 1, 2024 · 2 comments

Comments

@ccarouge
Copy link

ccarouge commented Dec 1, 2024

PR #10 shows a working version of UM7 + CABLE3 in an ESM build. Once this UM code is merged in UM7 repository, we should create a default deployment PR for ESM1.6. Ideally this should also include the generic tracers from the ocean side and updates to CICE.

@ccarouge
Copy link
Author

ccarouge commented Dec 2, 2024

Looking into this, it seems the spack package for esm1.6 could do with a refresh as well. See issue for the UM repo and issue for CICE5. I don't think we need to wait on the update to the spack package before getting a default deployment.

@ccarouge ccarouge changed the title create default spack package once Jhan's UM7 branch is merged in create default deployment PR for esm1.6 Dec 2, 2024
@ccarouge ccarouge transferred this issue from ACCESS-NRI/spack-packages Dec 2, 2024
@ccarouge
Copy link
Author

ccarouge commented Dec 2, 2024

Before we can test a deployment with the generic tracers, we need a config for these (ACCESS-NRI/access-esm1.6-configs#4) because it requires different inputs.

Maybe it is worth updating what is in main now so that it doesn't point to feature branches once the merge happens in the UM7 repo and then look at the generic tracers later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant