-
Notifications
You must be signed in to change notification settings - Fork 47
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
Final updates (documentation, site configs, ...) for spack-stack-1.4.1 #669
Final updates (documentation, site configs, ...) for spack-stack-1.4.1 #669
Conversation
…redSites.rst for spack-stack-1.4.1
@ulmononian I will need your help filling in the missing bits for AWS Parallel Works (in the preconfigured sites section). @AlexanderRichert-NOAA I will need your help filling in the missing bits for Acorn (in the preconfigured sites section). Thanks! |
@@ -31,7 +31,7 @@ unsetenv SLURM_EXPORT_ENV | |||
setenv PSM2_PATH_SELECTION "static_base" | |||
setenv SLURM_CPU_BIND "none" | |||
|
|||
# Settings specific for Cheyenne | |||
# Settings specific for Cheyenne and Hercules |
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.
just wanted to check: why are these settings only needed for cheyenne and hercules?
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.
Because every HPC has its own settings, depending on the interconnect, the scheduler settings etc.
The Acorn section is still current (and the installation path is correct). |
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.
Looks good! Thanks for making all of these updates
@ulmononian @AlexanderRichert-NOAA Ready for your final blessings and then we can tag and send out the release! |
doc/source/PreConfiguredSites.rst
Outdated
@@ -402,7 +395,7 @@ The following is required for building new spack environments and for using spac | |||
module load ecflow/5.8.4 | |||
|
|||
.. note:: | |||
Support for spack-stack-1.4.0 will be added later on develop. The instructions below are for an older release. | |||
Support for spack-stack-1.4.1 will be added later on develop. The instructions below are for an older release. |
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.
Lines 398-417 could be removed and replaced with:
For ``spack-stack-1.4.1`` with Intel, load the following modules after loading miniconda and ecflow:
module use /contrib/EPIC/spack-stack/spack-stack-1.4.1/envs/unified-dev/install/modulefiles/Core
module load stack-intel/2021.3.0
module load stack-intel-oneapi-mpi/2021.3.0
module load stack-python/3.9.12
module available
1.4.1 is installed on AWS, Azure, and GCP (by @mark-a-potts)
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.
Please re-review 51ba4b8
Summary
Final updates for spack-stack-1.4.1:
Testing
Installed on all platforms that are updated in the documentation, tested on about half of them
Applications affected
Primarily UFS WM; JEDI will use spack-stack-1.4.1 mainly for testing of
bufr@12
.Systems affected
All systems updated in the documentation (but existing spack-stack-1.4.0 installs remain in place).
Dependencies
n/a
Issue(s) addressed
Resolves #637 (requires all boxes in the issue to be ticked or crossed out)
Checklist