Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
H
HCC docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Monitor
Service Desk
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Holland Computing Center
HCC docs
Commits
484c8915
Commit
484c8915
authored
3 years ago
by
Adam Caprez
Browse files
Options
Downloads
Patches
Plain Diff
Commochameleon
parent
28233e96
No related branches found
No related tags found
1 merge request
!289
Commochameleon
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
content/applications/user_software/using_anaconda_package_manager.md
+28
-7
28 additions, 7 deletions
...lications/user_software/using_anaconda_package_manager.md
with
28 additions
and
7 deletions
content/applications/user_software/using_anaconda_package_manager.md
+
28
−
7
View file @
484c8915
...
...
@@ -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`
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment