Skip to content

Commit 821652e

Browse files
committed
refine spack introductory section
1 parent c9c6f20 commit 821652e

File tree

1 file changed

+10
-17
lines changed

1 file changed

+10
-17
lines changed

docs/environment/spack.md

Lines changed: 10 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@
77
[Spack](https://spack.io/about/) is an open-source package manager designed for installing, building, and managing scientific software across a wide range of system including from personal computers to super computers. It supports multiple versions, compilers, and configurations of software packages, all coexisting in a single system without conflict. Spack provides with [over 8,500 ](https://packages.spack.io/)official software packages available since the `v1.0.0` release.Additionally users can also create [custom packages](https://spack-tutorial.readthedocs.io/en/latest/tutorial_packaging.html) via `package.py` files for software not yet available in the Spack pre-defined [packages](https://spack.readthedocs.io/en/latest/package_fundamentals.html).
88

99

10-
Similar to [EasyBuild](https://docs.easybuild.io/), [Spack](https://spack.io/about/) is also available on the UL HPC platform for managing and installing scientific software in more flexible and customizable way.
11-
At present, the UL HPC environment includes a pre-installed version of Spack,namely `devel/Spack/0.21.2` which can be accessed via the module system.
10+
<!-- Similar to [EasyBuild](https://docs.easybuild.io/), [Spack](https://spack.io/about/) is also available on the UL HPC platform for managing and installing scientific software in more flexible and customizable way.
11+
At present, the UL HPC environment includes a pre-installed version of Spack,namely `devel/Spack/0.21.2` which can be accessed via the module system. -->
1212

1313
??? question "Why use automatic building tools like [Easybuild](https://docs.easybuild.io) or [Spack](https://spack.io/) on HPC environments?"
1414

@@ -34,18 +34,9 @@ At present, the UL HPC environment includes a pre-installed version of Spack,nam
3434

3535
## Setting up Spack.
3636

37-
For all tests and compilation with Spack, it is essential to run on a **compute node**, not in the login/access node.
38-
39-
??? note "Connection to a compute node"
40-
41-
Here's an example of how to allocate an [interactive session](../jobs/interactive.md) in **Aion cluster**.
42-
43-
```{.sh .copy}
44-
si -N 1 -n 16 -c 1 -t 0-02:00:00
45-
```
46-
47-
This command requests a [job](../jobs/submit.md) with 1 node, 16 MPI processes (-n 16), and 1 CPU core per process (-c 1).The -n 16 option allows running up to 16 parallel processes, which can accelerate builds spack.However, these values are only examples and are not mandatory. Users may adjust the resource allocation according to their requirements or omit certain options entirely for simpler use cases.
37+
!!! warning "Connect to a compute node"
4838

39+
For all tests and compilation with Spack, it is essential to run on a [**compute node**](../systems/iris/compute.md), not in the [**login/access**](../connect/access.md). For detailed information on resource allocation and job submission, visit the [**Slurm Job Management System**](../slurm/index.md).
4940

5041

5142
### Clone & Setup Spack
@@ -59,7 +50,7 @@ cd $HOME
5950
git clone -c feature.manyFiles=true https://github.com/spack/spack.git
6051
```
6152

62-
Cloning the Spack repository creates a directory named spack, and by default, it uses the develop branch. However for improved stability switching to the latest official [release](https://github.com/spack/spack/releases) is recommended. The current release tags at that time `v1.0.0`. and to checkout the most recnet release `v1.0.0` :
53+
Cloning the Spack repository creates a directory named spack, and by default, it uses the develop branch. However for improved stability switching to the latest official [release](https://github.com/spack/spack/releases) is recommended. The current release tags at that time `v1.0.0`. and to checkout the most recent release `v1.0.0` :
6354

6455
``` { .sh .copy }
6556
cd spack
@@ -242,12 +233,14 @@ Then, add the following contents, which instructs Spack to use system-provided v
242233
```
243234

244235

245-
## Software installtion with Spack
236+
## Installing softwares with Spack
246237
!!! Note
247238
This section will include examples and detailed instructions on how to install software using Spack. Relevant official documentation will also be linked to guide users through advanced usage and best practices.
248239

240+
### Spack Binary Cache
241+
249242

250-
### Useful Spack Commands.
243+
<!-- ### Useful Spack Commands.
251244
252245
253246
The following tables summarizes the basic commands for managing software packages with Spack, from searching and installation to managing the software environment.
@@ -283,7 +276,7 @@ Below is a list of commonly used Spack environment commands:
283276
284277
285278
??? info "Further Reference"
286-
For more technical details, see the official Spack documentation:<a href="https://spack.readthedocs.io/en/latest/environments.html" target="_blank"><strong>Spack Environments</strong></a>
279+
For more technical details, see the official Spack documentation:<a href="https://spack.readthedocs.io/en/latest/environments.html" target="_blank"><strong>Spack Environments</strong></a> -->
287280

288281

289282

0 commit comments

Comments
 (0)