Merge branch 'conda_activate_common' into 'master'

Add activation and license note for conda

See merge request !381

content/applications/user_software/using_anaconda_package_manager.md

@@ -18,13 +18,13 @@ straightforward.
 
 - [Using Anaconda](#using-anaconda)
 - [Searching for Packages](#searching-for-packages)
-- [Creating custom Anaconda Environments](#creating-custom-anaconda-environments)
+- [Creating Custom Anaconda Environments](#creating-custom-anaconda-environments)
 - [Using /common for environments](#using-common-for-environments)
 - [Adding and Removing Packages from an Existing Environment](#adding-and-removing-packages-from-an-existing-environment)
 - [Moving and Recreating Existing Environment](#moving-and-recreating-existing-environment)
 - [Remove Unused Anaconda Packages and Caches](#remove-unused-anaconda-packages-and-caches)
-- [Creating custom GPU Anaconda Environment](#creating-custom-gpu-anaconda-environment)
-- [Creating custom MPI Anaconda Environment](#creating-custom-mpi-anaconda-environment)
+- [Creating Custom GPU Anaconda Environment](#creating-custom-gpu-anaconda-environment)
+- [Creating Custom MPI Anaconda Environment](#creating-custom-mpi-anaconda-environment)
 - [Using an Anaconda Environment in a Jupyter Notebook](#using-an-anaconda-environment-in-a-jupyter-notebook)
 - [Using Mamba](#using-mamba)
 
@@ -252,6 +252,18 @@ conda remove -n mynumpy --all
 {{< /highlight >}}
 {{% /panel %}}
 
+The migrated environment can then be activated with: 
+
+{{% panel theme="info" header="Activate new environment" %}}
+{{< 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`.
+
 ### Remove Unused Anaconda Packages and Caches
 
 By default, conda environments are installed in the user’s home directory at `~/.conda/envs`.