From be1b4b7c2605359861c7eb898a07eeb341e09537 Mon Sep 17 00:00:00 2001 From: Helena Date: Fri, 23 Apr 2021 13:46:43 +0200 Subject: [PATCH] Create helper environment via mamba I was helping our two Avans students (Bob van Rijthoven, Diemo Perre) get Jovian setup and they'd been stuck on conda resolution. On a previous installation it'd gone very well, but, we needed to reconfigure and reinstall and it stuck for days at a time on creating the Jovian_helper_env. I didn't see anything obvious slowing down the resolution, but on running a manual `conda env create -f ...` with `-vvv` it was just stuck in the SAT solver. Creating this environment via mamba was instantaneous in comparison. It seems you're using mamba already in some of the per tool environments, I think it may make sense for the helper environment (and the main env possibly?) to be created via mamba as well. --- bin/includes/Databases | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bin/includes/Databases b/bin/includes/Databases index d75a6af..e44a921 100755 --- a/bin/includes/Databases +++ b/bin/includes/Databases @@ -11,7 +11,7 @@ if [[ $PATH != *${HELPER_NAME}* ]]; then # If helper env is not in your path (i. if ! conda activate "${HELPER_NAME}"; then # If exit statement is not 0, i.e. helper conda env hasn't been installed yet, do... echo -e "\tInstalling Jovian helper environment..." - conda env create -f ${PATH_JOVIAN_HELPER_YAML} # Create the env from the specified yaml file + mamba env create -f ${PATH_JOVIAN_HELPER_YAML} # Create the env from the specified yaml file set -o allexport conda activate "${HELPER_NAME}" set +o allexport @@ -24,4 +24,4 @@ bash bin/includes/Databases_installer # The rest of the code is performed in the helper env, not in the master env. conda deactivate # conda deactivate # if you need to go back to the master_env. N.B. Wrap this command with set +u and set -u when working in strict bash mode. -echo -e "DONE" \ No newline at end of file +echo -e "DONE"