-
Notifications
You must be signed in to change notification settings - Fork 7
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
Environment for accessing intake python package #229
Comments
Yes we need to remove dependencies on This issue probably belongs on the https://github.com/ACCESS-NRI/access-om3-configs repo (or https://github.com/ACCESS-NRI/model-config-tests). If you agree move/copy/dupe and we can discuss. |
We typically collect our OM3 & config related issues here because its hard to know where (and possibly in multiple places) the fix will be applied and to make the issues easier to find. |
Related payu-org/payu#521 |
As an interim patch - I think we can generate the datastore in a postscript instead of a userscript. The postscript starts a new PBS job, so when that fails due to not finding the storage data, it won't impact the CI. |
Note that the archive script starts a seperate PBS job which uses hh5
Note that the archive script starts a seperate PBS job which uses hh5
Note that the archive script starts a seperate PBS job which uses hh5
Note that the archive script starts a seperate PBS job which uses hh5
om3-scripts was updated to move the intake datastore generation into a seperate PBS job in COSIMA/om3-scripts#37 these PRs removed the hh5 dependency from the main payu job:
and with WW3: |
Note that the archive script starts a seperate PBS job which uses hh5
Note that the archive script starts a seperate PBS job which uses hh5
Note that the archive script starts a seperate PBS job which uses hh5
Note that the archive script starts a seperate PBS job which uses hh5 Co-authored-by: anton-seaice <[email protected]>
Closed through linked PRs |
Progress :)
Thanks to a new build on vk83 we can now trigger model runs through the CI:
This fails as the service user doesn't access hh5. We currently module use hh5 for an environment to build the intake-esm datastore for model output:
We could:
Keen to hear your thoughts @aidanheerdegen , @jo-basevi, @CodeGat
The text was updated successfully, but these errors were encountered: