...
Namely all names are removed (i.e. if you had an env made with '-n my_env' typing `conda activate my_env` would no longer activate the environment) as the conda binary is looking in /opt/conda and /home/$user${USER}/.conda/envs for environments.
To activate the environments you have created you’ll need to use the full path (i.e. `conda activate /home/$user${USER}/*conda/envs/my_env`).
This will also change where you create environments. When you use `conda create -n my_env` it will place it in a new folder located at /home/<username>/.conda/envs/ and you can activate it using the typical `conda activate my_env`.
If you want to install in the old location instead of using `conda create -n my_env` you will need to use the prefix option to point to your env folder: `conda create -p /home/<username>${USER}/*conda/envs/my_env`. All environments created with the prefix option will have to be activate with the full path instead of the name.
...
Note: If for some reason you want to switch back to your personal conda setup and loose the use of environment switching using Jupyter Notebooks/Lab on the HPC simply run:
/home/<username>${USER}/*conda/bin/conda init bash
...