

For example, to create a Conda environment called env_ABC containing the packages AAA, BBB, and CCC, and install it in the directory /usr/local/usrapps/, do :Ĭonda create -prefix /usr/local/usrapps/$GROUP/$USER/env_ABC AAA BBB CCCĬonda activate /usr/local/usrapps/$GROUP/$USER/env_ABC Choose a descriptive name for the environment - Conda will create the directory, the directory should not already exist. To install Conda environments, specify a prefix, which will be the path to where the environment will be installed. Please use a YAML file to avoid package conflicts. The following is the general idea of how to use Conda. The path for that space is generally /usr/local/usrapps/groupname. Installing and activating a Conda environmentīefore installing any software, including a Conda environment, request a space for user maintained software to be used by all members of a Project. For example, the bioconda and conda-forge channels may be added by adding the following lines to ~/.condarc:

If these files contain information for old Conda environments, edit the files and delete this section: Log out and then back in again after using conda init.įor users who have already been using different Conda environments and would like to begin installing with the new recommended procedures, clean out the remnants of old Conda environments by doing the following. Normally using a login file to automatically set the environment is strongly discouraged, but in the case of Conda, many features cannot be used without setting this initialization file.

To load the system installed Conda, load the module and use init to add it to the path. This step is necessary only once for an HPC user, unless the initialization settings are removed. Use the tcsh shell (type "tcsh") for all conda related work - the default shell for the new Hazel cluster is bash, however conda environment activation is not working properly on compute nodes with bash we are working on fixing this.

