CONDA ENV LIST HOW TO
CONDA ENV LIST INSTALL
CONDA ENV LIST FULL
CONDA ENV LIST SOFTWARE

The command prompt will then change (e.g. Once you have created your sub-environment, you can activate it using conda activate for example: You can alternatively give it a different location using the option -p instead of -n. If you have followed these instruction, this location should be /home/users//miniconda3/envs/myenv. It will show the proposed installation location, and once you answer the prompt to proceed, will do the installation. To create a named environment (for example, called 'myenv'), ensure that the base environment is activated (the command prompt should start with '(base) '), and type:

CONDA ENV LIST INSTALL

Unless you install packages directly into the base environment, your sub-environments will work independently. You can have multiple sub-environments under a single base environment, and activate the one that is required at any one time. You can deactivate the environment by typing:Ĭonda deactivate Creating and activating a sub-environmentĪlthough once you have activated the base conda environment, you can in principle start to install packages immediately, your use of conda will generally be better organised if you do not install packages directly into the base environment, but instead use a named sub-environment. Your command prompt will then change to include '(base) ' at the start, in order to remind you that this environment is activated. (You may encounter documentation elsewhere which suggests 'conda activate' instead, but the above command is a workaround for the fact that you have not run 'conda init', the reasons for which are explained above.) Or add -h to see help on other available command-line options.) Activating the base environmentĪssuming that you made the choices recommended above when running the installer, you should type the following in order to activate the base environment: (Add the -b option at the end of the above command to run the installer in batch mode, which will also skip the 'conda init'. If you say no, you can still follow the instructions below when you wish to activate your base environment. Say no to the question about 'conda init', because saying yes will cause it to add lines to your ~/.bashrc file causing your base environment to be activated every time you log in, which may interfere with the use of Jaspy.If you need to change this, see the section 'Varying the installation location' near the end of this page for more info. Accept the default location (~/miniconda3).You will be asked to confirm the licence agreement, to choose an installation location, and to decide whether it should run 'conda init'. Module unload jaspy Creating a base environment

You cannot have your own conda environment activated at the same time as Jaspy, so it is recommended that if you have loaded the jaspy module, then you start by typing:

CONDA ENV LIST FULL

It is possible as an alternative to use the full Anaconda, but your initial base environment will be much bigger if you do that (at time of writing this installs 5GB, compared to 400MB with miniconda) so we suggest the use of miniconda.

In order to create your own conda environments, you will first need to download the miniconda installer.

CONDA ENV LIST SOFTWARE

To decide whether you should use a Python virtual enviro nment or a Conda environment, first see the page: overview of software environments.

CONDA ENV LIST HOW TO

This page gives detail on how to create and use your own personal Conda environments via the miniconda installer, as an alternative to the use of Jaspy.

On JASMIN, we provide a wide range of packages via the Jaspy environment (which is itself a Conda environment). Creating and using miniconda environments

Conda env list