-
Notifications
You must be signed in to change notification settings - Fork 131
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
Instructions to use pre-installed versions on HPC clusters #2197
Conversation
Might it actually make sense to move/remove the documentation from the ESMValCore, since this is really targeted to end-users? I think it is a bit unfortunate to have the same information in two places, so perhaps we can keep it here, with the tool and just put a link to this page into the ESMValCore documentation? |
That is a good point. I have done that in the ESMValCore PR #1186. Note that #1186 will only work once this PR is merged. |
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.
nice one @remi-kazeroni - I think we should probably leave the doc in ESMValCore too just so people that want to use only Core functionality can do that, but it's becoming a nuisance to make sure that the two sets of doc are in sync so if you decide to remove it from Core docs as @zklaus suggests, I won't make a fuss of it 😁 EDIT: just saw your last comment about the link in Core docs - good stuff! 👍
Is that even technically an option? Can you do |
no, but you can import esmvalcore modules and use them in your work |
Thanks for your input @valeriupredoi and @zklaus! I suggest to get this merged since approved and discuss the core documentation in the other PR. I'll transfer your comments there. |
Description
The information about how to use the pre-installed ESMValTool on HPC clusters (Mistral, Jasmin) is currently only available in the ESMValCore documentation. This PR adds the information to the list of possible ways to install/use the ESMValTool.
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
- [ ] 🛠 Tests run successfully- [ ] 🛠 The list of authors is up to date- [ ] 🛠 Any changed dependencies have been added or removed correctlyNew or updated recipe/diagnostic
- [ ] 🧪 Recipe runs successfully- [ ] 🧪 Recipe is well documented- [ ] 🧪 Figure(s) and data look as expected from literature- [ ] 🛠 Provenance information has been addedNew or updated data reformatting script
- [ ] 🛠 Documentation is available- [ ] 🛠 The dataset has been added to the CMOR check recipe- [ ] 🧪 Numbers and units of the data look physically meaningfulTo help with the number of pull requests: