-
Notifications
You must be signed in to change notification settings - Fork 47
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
Error during "creating z y v clusters from the final set of bins" avamb workflow #297
Comments
It is possible that this command was not run with the shell Bash, but with another kind of shell. CC @Paupiera - perhaps this can be rewritten in Python? Since we know that the user certainly has a functioning Python install, but we do not necessarily know which shell they are using. |
Hi, thanks for your answer.
|
Hello, I am sorry that you are experiencing problems. For a better interpretation of the error, could you share a tarball with the |
Here are the files. I tried to re-run it one time, not sure if that altered something |
Hi, Everything looks normal regarding the workflow from the
Please let me know the error you get in case it does not run. |
Hi, thanks for checking it in detail. |
Great. The script executed should have created the final clusters |
I'm not sure. I have checked and I have a avamb_manual_drep_disjoint_clusters.tsv file under tmp, not under avamb folder. According to the file modification, the file was created before, not now... |
That should not happen, since the:
command should create the |
Hi, I am having the same issue. I tried to run the above but was given the error vamb/workflow_avamb/src/write_clusters_from_dereplicated_and_ripped_bins.sh: line 29: avamb_outdir/: Is a directory Is there a possible solve? |
Hello,
I'm running avamb snakemake workflow on my dataset and everything worked perfect when I specified "min_comp": "0.9" and "max_cont": "0.05" on the config file. However, I repeated the process to specify "min_comp": "0.7" and "max_cont": "0.1" (from the scratch as I couldn't find a way to run the workflow after just changing that) and I am getting the following error.
I have found the same error with two different datasets:
The text was updated successfully, but these errors were encountered: