-
Notifications
You must be signed in to change notification settings - Fork 0
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
spack.yaml
Environment Configuration
#5
Conversation
@harshula Would we be using a similar |
Hi @CodeGat , I think we will need to do the same for access-om3. |
0d60115
to
3838a4b
Compare
The model version in the
|
1 similar comment
The model version in the
|
This
It will be deployed using:
If this is not what was expected, commit changes to |
This
It will be deployed using:
If this is not what was expected, commit changes to |
Note for tomorrow: it is deploying to |
…definitions into spack.packages
7a08951
to
3ba8b83
Compare
This
It will be deployed using:
If this is not what was expected, commit changes to |
I did a
i.e. it works now So I think this change needs to be made. Can I push it? How do you want to name the versions of these modules ? Most of the default names seem ok?
|
Hey @anton-seaice I've seen the above checks fail. |
🚀 Deploying access-om3 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om3/pr5-27 where the binaries shall be on your 🛠️ Using: spack-packages DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
🚀 Deploying access-om3 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om3/pr5-28 where the binaries shall be on your DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
🚀 Deploying access-om3 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om3/pr5-29 where the binaries shall be on your DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me.
I have tested the pr5-29 build using ACCESS-NRI/access-om3-configs@a5fd61b and it starts and runs. This build points to the latest commit in COSIMA/access-om3@96f9159 and will work with the head of the current configurations under test.
We can continue to refine and improve this, but this gives us a starting point for using for Repro-CI testing
🚀 Deploying access-om3 Details and usage instructionsThis
This Prerelease is accessible on Gadi using: module use /g/data/vk83/prerelease/modules
module load access-om3/pr5-30 where the binaries shall be on your DetailsIt will be deployed using:
If this is not what was expected, commit changes to |
Initial changes to the
spack.yaml
to support theaccess-om3
SBD.Closes #3