...
it is not designed for parallel use,
it will very likely lead to quota issues (HOME is limited to 5GB20 GB), and
it causes unnecessary backups of reproducible data.
...
| Code Block |
|---|
which python # load module ml lang ml Anaconda3Miniforge3 which python conda create --name myenv python=3.9.5 conda activate myenv # won't work if shell integration hasn't been set up already # shell integration conda init . $HOME/.bashrc # update shell # or `source $(conda info --base)/etc/profile.d/conda.sh` for immediate + non-permanent conda activate myenv # works now which python conda list conda install numpy # so far so good, but where is our environment (and the packages etc.) located? conda env list # it shouldn't live in $HOME but on the parallel FS # how to resolve this? # 1) provide `--prefix <path>` to `conda create` (and then full path to `conda activate`) # 2) conda config --add envs_dirs /scratch/<group>/<username>/.conda/envs # conda config --add pkgs_dirs /scratch/<group>/<username>/.conda/pkgs # let's recreate it properly... conda deactivate myenv # conda env remove --name myenv .... but let's just rm -rf $HOME/.conda conda config --add envs_dirs /scratch/pc2-mitarbeiter/bauerc/.conda/envs conda config --add pkgs_dirs /scratch/pc2-mitarbeiter/bauerc/.conda/pkgs cat $HOME/.condarc # (potentially) redo the above.... # then `which python` |
...
| Code Block |
|---|
which python
pip # command not found
# load module
ml lang
ml Python/3.9.5
which python
which pip
# note that the default path for global packages etc. is $HOME/.local/lib/python<ver>/site-packages
# to change it we can put the following into our .bashrc
# export PYTHONUSERBASE=/scratch/<group>/<username>/.local
export PYTHONUSERBASE=/scratch/pc2-mitarbeiter/bauerc/.local
# you might also want to add
export PATH=/scratch/pc2-mitarbeiter/bauerc/.local/bin:$PATH
pip install numpy
ls /scratch/pc2-mitarbeiter/bauerc/lib/python3.9/site-packages |
...