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.

Sign up for GitHub

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

Jump to bottom

Use conditional values for the MOM5 "type" variant. #183

Open
penguian opened this issue Jan 22, 2025 · 3 comments
Open

Use conditional values for the MOM5 "type" variant. #183

penguian opened this issue Jan 22, 2025 · 3 comments
Assignees
@penguian

Comments

@penguian
Copy link
Contributor

penguian commented Jan 22, 2025 •
edited
Loading

See #116

Each of access-esm1p5, access-esm1p6 and access-om2-bgc currently uses different type values with different versions of mom5,as follows.

Package mom5 version type
access-esm1p5 access-esm1.5 ACCESS-CM
access-esm1p6 access-esm1.5 ACCESS-CM
access-esm1p6 access-esm1.6 ACCESS-ESM
access-om2-bgc default ACCESS-OM-BGC

As per #116 , use conditional values for the type variant in mom5 to reflect this.
@penguian penguian self-assigned this Jan 22, 2025
@dougiesquire
Copy link
Contributor

@penguian, why are there two entries in the table for access-esm1p6?

@anton-seaice
Copy link
Contributor

Is the suggestion to use the type variant instead of version for building from the same codebase for different deployments ?

@harshula
Copy link
Collaborator

Note, The version determines what source code is used.

@aekiss aekiss removed this from ACCESS-OM3 025 Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@penguian penguian

Labels
None yet
Projects
ACCESS-ESM1.5 Spack
Status: No status
ACCESS-ESM1.6
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@penguian @harshula @dougiesquire @anton-seaice