Closed tdivoll closed 3 months ago
SOLUTION:
.bashrc
was being sourced on bash_profile
! After I deleted this block from .bash_profile
, Cylc works.
# Get the aliases and functions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
I suspect it was the Conda init block on the .bashrc
that gets added by default when using Conda on Oscar. Essentially it would either activate the base environment inside the ift-env
or just switch to base
from ift-env
(I'm still not sure which case is true), which then didn't have Cylc.
@hollandjg, for context as you move into using Cylc on Oscar
I have been getting an error trying to use Cylc that suggests
cylc
is not found half way through thejob.sh
, specifically lines 130 and 164 of thejob.sh
.The workflow:
base
envift-env
Conda env that contains Cylc installcylc_hpc/flow.cylc
using the sample params csv file and theflow_generator.py
global_setup
Things I have tried:
cylc
wrapper script as suggested in the linked thread and set the env var for Cylc versionCYLC_HOME_ROOT="${CYLC_HOME_ROOT:-/users/tdivoll/.conda/envs/ift-cylc/bin/cylc}"
to.bash_profile
as a temp hack to see if it worksconda config --set auto_activate_base=true
in.bashrc
,.bash_profile
, or.zshrc
. See this thread for context.