"will edit your `.bashrc` and that is not nice, especially when you might move to another module. \n",
"**Therefore this is not recommended to do.**\n",
"\n",
"In order to use your environment in a shell script or on a slurm job, try the following:\n",
"This script is used by `conda init bash` to set the configuration, we simply source (load) it and get the same functionality as we would be using `conda init bash`. **(Do not use `conda init bash`)**\n",
"\n",
"Load the shell setup script located in the conda source tree (`${CONDA_ROOT}/etc/profile.d/conda.sh`) and activate your environment:\n",
"```bash\n",
"# Load from the current conda module the BASH functionality (as in activate)\n",
Installed kernelspec MYENV in /jetfs/home/mblaschek/.local/share/jupyter/kernels/myenv
%% Cell type:markdown id: tags:
### Activate your conda environment
Conda Environments need to be added to the `PATH` to work well. So there is an `activate` function for these conda environments.
However, running
```bash
conda init bash
```
will edit your `.bashrc` and that is not nice, especially when you might move to another module.
**Therefore this is not recommended to do.**
In order to use your environment in a shell script or on a slurm job, try the following:
This script is used by `conda init bash` to set the configuration, we simply source (load) it and get the same functionality as we would be using `conda init bash`. **(Do not use `conda init bash`)**
Load the shell setup script located in the conda source tree (`${CONDA_ROOT}/etc/profile.d/conda.sh`) and activate your environment:
```bash
# Load from the current conda module the BASH functionality (as in activate)
"Hint: Checkout the guides on [Gitlab](https://gitlab.phaidra.org/imgw/computer-resources/-/blob/master/Python/QA-003-Conda-Environment.ipynb#Activate-your-conda-environment)\n",
"\n",
"### Load from the current conda module the BASH functionality (as in activate)\n",
"### Load bash conda configuration\n",
"This script is used by `conda init bash` to set the configuration, we simply source (load) it and get the same functionality as we would be using `conda init bash`. **(Do not use `conda init bash`)**\n",
You have done it! Your Notebook Server is running on the Jet Cluster.
Welcome, please skip this, if your know where you are, as this is meant as an introduction. However, not complete as it is.
If you need more infos about Notebooks have a look at [my Homepage](https://homepage.univie.ac.at/michael.blaschek/#python) and there are numerous Tutorials on the Internet for any advice, but feel free to ask me and give me feedback.
It is not recommended to use `conda init bash`, because it will write that specific version into your `.bashrc` file and will result in errors when you move to another module or newer version.
Hint: Checkout the guides on [Gitlab](https://gitlab.phaidra.org/imgw/computer-resources/-/blob/master/Python/QA-003-Conda-Environment.ipynb#Activate-your-conda-environment)
### Load from the current conda module the BASH functionality (as in activate)
### Load bash conda configuration
This script is used by `conda init bash` to set the configuration, we simply source (load) it and get the same functionality as we would be using `conda init bash`. **(Do not use `conda init bash`)**