Skip to content

Bug in install script with non-standard environment location #284

@multimeric

Description

@multimeric

The install script assumes that the environment is located within $CONDA_BASE, which is not necessarily true. For example on my institute's HPC, CONDA_BASE=$(conda info --base) is the location of the global shared conda module, whereas the BindCraft env is located in the user's home directory.

source ${CONDA_BASE}/bin/activate ${CONDA_BASE}/envs/BindCraft || { echo -e "Error: Failed to activate the BindCraft environment."; exit 1; }

I found this to work fine for our use-case:

conda activate BindCraft || { echo -e "Error: Failed to activate the BindCraft environment."; exit 1; 

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions