Update to 0.3.0-alpha.1 #177
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This updates both jigsaw and jigsaw-python to v1.0.0
...in github actions
Only install JIGSAW and JIGSAW-Python from the submodule if * creating a new environment * --recreate flag is used * --update_jigsaw flag is used
Install cmake and cxx-compiler in the deployment environment (not the final polaris environment) and use that to build Jigsaw.
xylar
added
the
deployment
This allows the software to be build with spack using different compilers and/or MPI libraries than are used for the for the libraries and E3SM component builds.
...and improve acknowledgment of Jigsaw's use in Polaris.
This was referenced Jan 30, 2024
…nd-libs Split spack software and libs
Add `jigsaw-python` as a submodule
Add metis and parmetis to spack build
It doesn't make sense to add it to the user's guide yet. Similarly, it doesn't make sense to add pm-gpu yet because MPAS compoents don't support it (yet).
Add MOAB to the spack build
Update Perlmutter support
Shared conda environments for Polaris releases are not supported and will not be in the near future.
Update scorpio to v1.4.2
Add Frontier as a supported machine
xylar
force-pushed
the
update-to-0.3.0-alpha.1
branch
from
a0589e5
to
a46277c
Compare
Should apparently be 56 rather than 64 (though that's hard to find in the docs).
Some systems like Frontier have cores that aren't allocatable. These need to be excluded from the core count that Polaris determines from slurm.
…cores Fix slurm handling of allocatable cores
…-node Fix cores_per_node for Frontier
xylar
added
the
framework
This combination cannot build MOAB.
Remove `gnu` with `mvapich` on Anvil
xylar
force-pushed
the
update-to-0.3.0-alpha.1
branch
from
3ea88e7
to
46d07f4
Compare
This merge explicitly points to the libnetcdf that should be used in the Jigsaw build. It also breaks the jigsaw build into its own function.
Fix libnetcdf in jigsaw build
Compy doesn't think its nodes have any allocated cores (all idle) so we will use the total number of cores per node instead.
Fix `cores_per_node` calculation on Compy and Anvil
|
What a slog! I'm going to mere this |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deployed and Tested
MPAS-Ocean with
pr:Omega CTests:
mache.nvidiaonpm-cpu, can't build yaml-cpp from ekat Omega#54gnugpuon Perlmutter-GPU Omega#56nvidiagpuon Perlmutter-GPU Omega#55