Skip to content
Snippets Groups Projects
Commit e1ecceac authored by Stefan Kesselheim's avatar Stefan Kesselheim
Browse files

Merge commit '1ebe261e' as 'spark_env'

parents 957fdc77 1ebe261e
No related branches found
No related tags found
No related merge requests found
venv
#!/bin/bash
# See https://stackoverflow.com/a/28336473
SOURCE_PATH="${BASH_SOURCE[0]:-${(%):-%x}}"
RELATIVE_PATH="$(dirname "$SOURCE_PATH")"
ABSOLUTE_PATH="$(realpath "${RELATIVE_PATH}")"
[[ "$0" != "${SOURCE_PATH}" ]] && echo "The activation script must be sourced, otherwise the virtual environment will not work." || ( echo "Vars script must be sourced." && exit 1) ;
source "${ABSOLUTE_PATH}"/config.sh
source "${ABSOLUTE_PATH}"/modules.sh
export PYTHONPATH="$(echo "${ENV_DIR}"/lib/python*/site-packages):${PYTHONPATH}"
source "${ENV_DIR}"/bin/activate
SOURCE_PATH="${BASH_SOURCE[0]:-${(%):-%x}}"
## Check if this script is sourced
[[ "$0" != "${SOURCE_PATH}" ]] && echo "Setting vars" || ( echo "Vars script must be sourced." && exit 1) ;
## Determine location of this file
RELATIVE_PATH="$(dirname "$SOURCE_PATH")"
ABSOLUTE_PATH="$(realpath "${RELATIVE_PATH}")"
####################################
### User Configuration
export ENV_NAME="$(basename "$ABSOLUTE_PATH")" # Default Name of the venv is the directory that contains this file
export ENV_DIR="${ABSOLUTE_PATH}"/venv # Default location of this VENV is "./venv"
#!/bin/bash
SOURCE_PATH="${BASH_SOURCE[0]:-${(%):-%x}}"
RELATIVE_PATH="$(dirname "$SOURCE_PATH")"
ABSOLUTE_PATH="$(realpath "${RELATIVE_PATH}")"
source "${ABSOLUTE_PATH}"/config.sh
KERNELFILE="${ENV_DIR}"/kernel.sh
echo the name is "$ENV_NAME"
echo "Setting up the kernel script in the following dir: " "${KERNELFILE}"
echo '#!/bin/bash
source "'"${ABSOLUTE_PATH}"'"/activate.sh
exec python -m ipykernel "$@"' > "${KERNELFILE}"
chmod a+x "${KERNELFILE}"
mkdir -p ~/.local/share/jupyter/kernels/"${ENV_NAME}"
echo '{
"argv": [
"'"${KERNELFILE}"'",
"-f",
"{connection_file}"
],
"display_name": "'"${ENV_NAME}"'",
"language": "python"
}' > ~/.local/share/jupyter/kernels/"${ENV_NAME}"/kernel.json
module purge
module load Stages/2022 GCC OpenMPI TensorFlow Horovod mpi4py PyTorch scikit-learn
Supercomputing Environment Template using Python Virtual Environments
=================
# Idea
This project contains a lightweight set of scripts to easily create Python working environments on
typical supercomputer setups, including creating Jupyter Kernels.
On Supercomputers, typically a basic environment based on **Environment Modules**. This setup is carefully
curated and optimized, including compilers, MPI version etc. Extra Python packages can be installed
with pip into user space. This, however, does not create a reproducible environment that can be used
by other users as well.
Conceptually, with Virtual Environments, it is easily possible to create project-based virtual environments.
These scripts streamline the creation and usage of such environments and make it easy for a users to share a setup
and to put it under version control with the main code.
Furthermore, in typical compute setup of scientific projects, one or more packages possibly are in active
development. In the context of these setups, it is intended to include them as submodules and add integrate
them into the workflow. This can e.g. mean that a compilation step is added in the setup step and
setting appropriate environment variables is included in the activation step.
# Details
The setup is configured in the bash script `config.sh`. The user can define a name for the venv and directory
where the venv files are stored. This defaults to the directory name of the containing folder and the "." folder
of the scripts. Please **edit** this file if you want a custom name and location for the venv.
The modules on top of which the the venv should be built are defined in `modules.sh`. Please **edit** the file
to your needs.
The file `requirements.txt` contains a list of packages to be installed during the setup process. Add required
packages to this file to reproducibly add them to the venv.
The script `setup.sh` creates the venv according to the config given in `config.sh`. Please **edit** this
file to add a setup step for submodules (e.g. compilation of libraries). If only plain venvs are used, this file
can remain unchanged. Note that the script *must* be ran at least once after the above configurations to actually create the environment.
The script `activate.sh` sets the environment variables such that the venv can be used. Please **edit** this file
to add environment variables for submodules. Note that the script must be *sourced* to take effect. Example:
```bash
source <path_to_venv>/activate.sh
```
The script `create_kernel.sh` will create a kernel json file in the user's home directory that can be found
by Jupyter and a helper script in the virtual environment folder.
# Intended Workflow
1. Edit `config.sh` to change name an location of the venv if required.
2. Edit `modules.sh` to change the modules loaded prior to the creation of the venv.
3. Edit `requirements.txt` to change the packages to be installed during setup.
4. Edit `setup.sh` and `activate.sh` to add extra steps for custom modules.
5. Create the environment with `bash setup.sh`.
6. Create a kernel with `bash create_kernel.sh`.
opencv-python
ipykernel
#!/bin/bash
SOURCE_PATH="${BASH_SOURCE[0]:-${(%):-%x}}"
RELATIVE_PATH="$(dirname "$SOURCE_PATH")"
ABSOLUTE_PATH="$(realpath "${RELATIVE_PATH}")"
source "${ABSOLUTE_PATH}"/config.sh
source "${ABSOLUTE_PATH}"/modules.sh
python -m venv --prompt "$ENV_NAME" --system-site-packages "${ENV_DIR}"
source "${ABSOLUTE_PATH}"/activate.sh
python -m pip install -r "${ABSOLUTE_PATH}"/requirements.txt
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment