Skip to content

Commit f469001

Browse files
committed
updating readme
1 parent 0e82e45 commit f469001

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed

README.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,16 @@
11
# DeepHyper Spack Packages
22

3+
## Overview
4+
35
This repository contains a collection of [Spack](https://spack.io) packages to manage the building of DeepHyper from source. Start by installing Spack on your system:
46

57
```bash
68
git clone -c feature.manyFiles=true https://github.com/spack/spack.git
79
. ./spack/share/spack/setup-env.sh
810
```
911

12+
Spack is quite recent and evolving quickly. Many packages are regularly updated. Therefore it can sometimes be useful to checkout the `develop` branch of Spack (`git checkout develop`) in case of issue to see if a fix has already been provided but not yet released.
13+
1014
Now should have access to the `spack` command. If you need spack to be loaded for any new session of your shell then you can add `. $PATH_TO_SPACK/spack/share/spack/setup-env.sh` to your `~/.bashrc` (or any other shell configuration). Once Spack is installed and loaded. Download the DeepHyper Spack packages and add them to your Spack installer:
1115

1216

@@ -57,3 +61,29 @@ The `info` command can help retrieve more information about the possible variant
5761
```bash
5862
spack info py-deephyper
5963
```
64+
65+
## Accessing Shared Site Packages
66+
67+
Sometimes the HPC facility can provide already compiled/installed packages. Spack can reuse these packages by defining a new `upstream` configuration. After cloning the Spack repository and activating the Spack environment (the command `spack` should now be available in your shell) add a new upstream configuration in the YAML file `$SPACK_ROOT/etc/spack/upstream.yaml` (`$SPACK_ROOT` should be available in your environment after activation of Spack).
68+
69+
At the Argonne Leadership Computing Facility (ALCF), Spack packages are provided at the `/soft/spack/root/opt/spack` location. Therefore we can edit the `upstream.yaml` file such as:
70+
71+
72+
```yaml
73+
upstreams:
74+
alcf-spack:
75+
install_tree: /soft/spack/root/opt/spack
76+
```
77+
78+
More information about [Chaining Spack Installations](https://spack.readthedocs.io/en/latest/chain.html#using-multiple-upstream-spack-instances).
79+
80+
## Spack and Conda
81+
82+
```
83+
spack add miniconda3
84+
```
85+
86+
for mac with arm64 use the `conda-forge` channel!
87+
```
88+
conda install -c conda-forge ...
89+
```

packages/py-deephyper/package.py

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,7 @@ class PyDeephyper(PythonPackage):
5353
depends_on("[email protected]:", type=("build", "run"))
5454

5555
with when("+nas"):
56+
#! Building tensorflow currently fails on "darwin-ventura-m1"
5657
depends_on("py-tensorflow@2:", type=("build", "run"))
5758
depends_on("py-networkx", type=("build", "run"))
5859
depends_on("py-pydot", type=("build", "run"))

0 commit comments

Comments
 (0)