-
Notifications
You must be signed in to change notification settings - Fork 4
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
PermissionError in phold plot
#36
Comments
Hi @Ulthran , Thanks for raising this. I am not sure myself what could be the issue - I don't think it has anything to do with the output for phold compare. It looks like it can't force remove the output directory George |
Thanks @gbouras13, without
Unfortunately, that's because of snakemake making the output directory before running the command (which I don't think is behavior I can change). So I need to run with |
@Ulthran I've run into that with snakemake before too :( I'll implement phold into a snakemake pipeline when I get some time and see if I get the same error as well - otherwise, not quite sure how to go about fixing this! George |
Ok thanks George, this is at the end of our pipeline so it's not hugely important that it be automated. If you do come up with a fix though we'll be happy to implement it! |
Hi @Ulthran , We have implemented phold in a snakemake pipeline (https://github.com/linsalrob/sphae) and don't have such an error - maybe have a look at the rules in sphae? George |
Thanks @gbouras13 , it's only happening for |
Description
Trying to run
phold plot
and I'm getting this error:I'm running this locally on a computer where I'm the only user. Permissions for the output of
phold compare
:What I Did
Ran install, predict, compare with minimal options, just specifying inputs, outputs, db path, and
--force
. Plot command:Getting this using a conda install and a docker install. I suspect it's just a matter of earlier steps writing with overly restrictive permissions for what plot is trying to do. Let me know if there's any more information/help I can give.
Thanks,
Charlie
The text was updated successfully, but these errors were encountered: