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

potential BUG: conda executable path #2

Open
fryzjergda opened this issue Mar 19, 2024 · 1 comment
Open

potential BUG: conda executable path #2

fryzjergda opened this issue Mar 19, 2024 · 1 comment

Comments

@fryzjergda
Copy link

Hi,
I was having trouble with running the fpocketR, and narrowed down the problem to posket.run_fpocket().

the bash command there is (line 100):

    bash_command = f'conda run -n fpocketR fpocket -f {pdb} -k {chain} -l {state} -m {m} -M {M} -i {i} -D {D} -A {A} -p {p} -w p'

In my case the program was unable to invoke conda, so I had to explicitly give it a path to my conda executable:

    conda_executable = "/home/user/miniconda3/bin/conda"
    bash_command = f'{conda_executable} run -n fpocketR fpocket -f {pdb} -k {chain} -l {state} -m {m} -M {M} -i {i} -D {D} -A {A} -p {p} -w p'

I don't know if this was specific to my case, but wanted to let you know about the potential bug.

Best,
Tomasz

@VonBoss
Copy link
Contributor

VonBoss commented Apr 1, 2024

I haven't found a better way to implement the fpocket subprocess yet, hopefully, this isn't a widespread issue. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants