Conda Workshop: Summary
- Simon Alexander
- Lisa Stafford
Goal: Summarize the concepts covered across the workshop.
Conda Commands Covered
Before you can use any of these you must have a version of Conda loaded: module load miniconda3/<version>
Calling conda on its own from the command-line will list all the available sub-commands.
Sub-Command | Description |
|---|---|
| List help on a particular <sub-command> |
| Create a Conda environment - this can be empty or pre-install packages. -n create in the configured default location. Typically ~/.conda/envs but can be configured using .condarc -p create in the current working directory. |
| Clone an existing environment. |
| If created using -n, then <env-name> can simply be the name of that environment. If created using -p then the absolute path must be defined. An environment must be activated to use it. |
| Deactivate an environment to finish using it. |
| Search for a By convention, R packages will be named |
| Conda install a package. If a |
| List the current configuration of your miniconda3 environment. This includes: |
| List known Conda environments. Displays what is defined within the |
| Add a channel to your |
| Export into a readable text file the current environment. |
| Create a new Conda environment importing from a previously exported |
Summary
Looked at:
What Conda is and the various distributions that provide it, basic terminology, and how to use miniconda3 on the cluster.
Creating various environments, based on languages, and application based.
Detailing how to configure conda to update where environments are created, packages are cached, and using channels.
Reproducing and sharing environments by cloning, exporting and importing.
Environments, packages and caches can take up Gs of storage, we looked at how we can clean our environments.
Best practices when using
sallocandsbatch.
Prev | Workshop Home |
|
Use the following link to provide feedback on this training: https://forms.gle/fuRnwt5rGUaDgzYB6 or use the QR code below.
