-
Notifications
You must be signed in to change notification settings - Fork 99
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 in rule run_checkm2: No DIAMOND annotation was generated #747
Comments
It worked. So, to be precise, I removed my sample from samples.tsv file and I also moved the following files somewhere else (just in case I was wrong): Sample/ 51 directories, 166 files. I am not closing the Issue just in case @SilasK would like to say this is completely wrong or not 😆 |
Hello there,
I was running atlas binning and got to a good 94% of the job done when, while running CheckM2, I got stuck.
Print out is the following:
[] INFO: Running CheckM2 version 1.0.2
[] INFO: Running quality prediction workflow with 70 threads.
[] INFO: Calling genes in 1 bins with 70 threads:
Finished processing 1 of 1 (100.00%) bins.
[] INFO: Calculating metadata for 1 bins with 70 threads:
Finished processing 1 of 1 (100.00%) bin metadata.
[] INFO: Annotating input genomes with DIAMOND using 70 threads
[] INFO: Processing DIAMOND output
[] ERROR: No DIAMOND annotation was generated.
As far as I can see, it performed this twice, both on the same sample, and got stuck.
Hope anyone can help or to update here with solution I could find.
UPDATE1: I checked my samples, and realised that the one generating the error was the only one presenting 1 fasta file alone in the /binning/vamb/bins folder. As it would make sense that that only bin is as well low quality and diamond cannot classify it, I (made a copy somewhere else and) removed the sample. Tried then to rerun the analysis. Will update.
Update2: Analysis got stuck again because marvellous Atlas was able to regenerate out-of-dont-know-where the "removed" sample. Pretty smart, but creating me an issue in this case. Will try to remove the sample from samples.tsv file, let's see if I can trick Atlas this way.
NOTE: Atlas get stuck even though I tried to add the --keep-going flag. It is about 96% done, 299 of 311 steps.
@SilasK if anytime you have a moment to jump in would be great! It's starting to be a pretty fun adventure.
The text was updated successfully, but these errors were encountered: