Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deactivate Conda Env In HPC Init Script #388

Merged
merged 2 commits into from
Nov 8, 2024

Commits on Nov 7, 2024

  1. Conditional deactivate env, then activate new env

    This is to address a bug where a currently active env would cause the
    hpc init script to load the flepimop env not cleanly. Determine the
    currently active env if there is one and if it is not the flepimop env
    deactivate it with message to the user.
    TimothyWillard committed Nov 7, 2024
    Configuration menu
    Copy the full SHA
    d4c3c7f View commit details
    Browse the repository at this point in the history
  2. Split conda activate into three cases

    1) No env active, just activate the flepiMoP env.
    2) The flepiMoP env is active, go ahead and refresh it because
       `module load anaconda` modifies the paths.
    3) Another conda env is active, deactivate it with a message.
    TimothyWillard committed Nov 7, 2024
    Configuration menu
    Copy the full SHA
    c4264ba View commit details
    Browse the repository at this point in the history