Setup.sh and source vs conda activate

[liamfriar]

I am setting up parahunter and get the following error:

setup.sh: line 31: activate: No such file or directory

I think the error is due to the environment having already been activated in line 20 of the same program. Is there a reason that the program uses source activate instead of conda activate ? source deactivate is depricated on my machine in favor of conda deactivate, and conda activate does not appear to push an error/warning when you run conda activate multiple times in a row (unlike source activate which gave the error above).

I am not familiar with source activate, so maybe there is some reason that I am just unaware of.

[Arkadiy-Garber]

Hey Liam,

Thanks for the heads up about this! I've seen this error before on my end and just solved it by swapping out 'source activate ...' for 'conda activate ...' I still am not clear on what the differences are and why one command works in some contexts and not in others.

In any case, if you ran the setup.sh script, it shoudl have created the conda env and you can activate it with conda activate parahunt. Let me know if that works!

Cheers,
Arkadiy

[liamfriar]

Hi, thank you for the quick answer! Yes, I ran setup.sh and am able to use conda activate parahunt . Just googling around, it looks like source activate may be needed for certain older versions of OS's (https://conda.io/projects/conda/en/latest/user-guide/getting-started.html)