In the past we recommended using the source activate, but with recent versions of our miniconda modules you can now use conda activate without having to run conda init. If you have run conda init previously, use the following command to clean out your .bashrc file (where conda adds some code specific to a single install location):
Thank you very much.
I processed as you suggested, but I now get this:
he following modules were not unloaded:
(Use “module --force purge” to unload all):
StdEnv
/usr/share/lmod/lmod/init/bash: line 70: conda: command not found
You may need to log out and back in? I was able to log in as you (because I’m YCRC staff, not a hacker) and successfully activate that environment in an interactive session and in a batch job with conda activate.
Hi, thank you very much. I am now using conda activate but I am still getting this message in my output files:
CommandNotFoundError: Your shell has not been properly configured to use 'conda deactivate'.
To initialize your shell, run
$ conda init <SHELL_NAME>
Currently supported shells are:
- bash
- fish
- tcsh
- xonsh
- zsh
- powershell
See 'conda init --help' for more information and options.
IMPORTANT: You may need to close and restart your shell after running 'conda init'.