Lmod hierarchical view under modern Cray environments
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
The issue names no repository files or tests, so first clarify whether the deliverable is an example or a full tutorial and validate the behavior in a modern Cray PrgEnv with Lmod. Done should document a hierarchical view that leaves the Cray environment unchanged, exposes mutually exclusive products, and switches or reloads the selected product when the custom module is loaded.
Written by the indexing model from the issue text.
Description
I'm looking for either an example or a full blown tutorial showing how to use the Cray PrgEnv to compile products and then expose the products through a hierarchical view.
I wish for the Cray environment to be left untouched. The user should only have to load some modules with a custom name to navigate the hierarchical view. the module exposing the hierarchy, should only change the module path, and not modify the environment in any other way unless exceptional.
i.e:
Hypre was compiled with the PrgEnv-[cray|amd|gcc], this will produce 3 products which I which to expose, never at the same time (mutual exclusion) and only when a particular module is loaded.
$ ml products-cce
$ ml load hypre
$ module li
------------------------- /cce/15.0.0/Core --------------------------
hypre/2.25.0
-------------------------------------- /Core ---------------------------------------
products-cce/xxx products-gcc/xxx products-rocmcc/xxx
$ ml products-gcc
<swap modules and automatically reload hypre (under the gcc Core, typical lmod stuff>
- Dominant language
- Python
- Stars
- 52
- Forks
- 38
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from spack/spack-tutorial
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
spack/spack-tutorial#190 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
spack/spack-tutorial#511 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
spack/spack-tutorial#486 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
spack/spack-tutorial#386 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
spack/spack-tutorial#186 ·
All issues in spack/spack-tutorial
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
john-kurkowski/tldextract#382 ·
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
feder-cr/invisible_playwright_mcp#1408 ·
Maintainers usually reply within 1 day