Skip to content
Snippets Groups Projects
Commit 2ecd7351 authored by Adam Caprez's avatar Adam Caprez
Browse files

Merge branch 'commochameleon' into 'master'

Commochameleon

See merge request !289
parents 28233e96 484c8915
Branches
Tags
1 merge request!289Commochameleon
......@@ -96,13 +96,6 @@ under.
### Creating Custom Anaconda Environments
{{% notice info %}}
**NOTE:** By default, conda packages are installed in the user's `home` directory.
Since Crane's `home` directories are not writeable from the worker nodes,
the commands for installing, adding and removing conda packages shown here
should be performed on the **login node**, and not as part of an interactive or SLURM job.
{{% /notice %}}
The `create` command is used to create a new environment. It requires
at a minimum a name for the environment, and at least one package to
install. For example, suppose we wish to create a new environment, and
......@@ -127,6 +120,34 @@ conda activate mynumpy
Our new environment is now active, and we can use it. The shell prompt will change to indicate this as well.
### Using /common for environments
By default, conda environments are installed in the user's `home` directory at `~/.conda/envs`.
This is fine for smaller environments, but larger environments (especially ML/AI-based ones) can quickly
exhaust the space in the `home` directory.
For larger environments, we recommend using the `$COMMON` folder instead. To do so, use the `-p` option
instead of `-n` for `conda create`. For example, creating the same environment as above but
placing it in the folder `$COMMON/mynumpy` instead.
{{% panel theme="info" header="Create environment in /common" %}}
{{< highlight bash >}}
conda create -p $COMMON/mynumpy numpy=1.17
{{< /highlight >}}
{{% /panel %}}
To activate the environment, you must use the full path.
{{% panel theme="info" header="Activate environment in /common" %}}
{{< highlight bash >}}
conda activate $COMMON/mynumpy
{{< /highlight >}}
{{% /panel %}}
**Please note** that you'll need to add the `#SBATCH --licenses=common` directive to your submit scripts
as described [here]({{< relref "using_the_common_file_system" >}}) in order to use environments
in `$COMMON`.
### Adding and Removing Packages from an Existing Environment
To install additional packages in an environment, use the `install`
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment