-
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
Progressing despite individual binner failure #651
Comments
Can you tell me which binner you used? maxbin? Would you be ok to simply not bin this sample? You could still use it to be quantified.. |
I used initially wanted to use all 4 available and aggregate with DASTools. Maxbin however is the one where this most frequently occurs. I think the most convienent option would be to have the workflow continue without having to manually curate the config and samples (Currently I end up removing maxbin, then removing either vamb or Semibin if they cause issues, then switching the final binner to metabat, and finally dropping samples from samples.tsv). If there's a way to not bin but still quantify that would be great |
There was no activity since some time. I hope your issue is solved in the mean time. Thank you for your contributions. |
Here is the relevant log output:
My issue pertains to binning -> genome creation. I often have smaller datasets so I am interested in performing ensemble binning [metabat, maxbin, vamb, and semibin], however, many times there are 1,2, even 8 samples that don't recover bins. It seems if using das tool this should be ok. Instead I typically resort to attempting all 4 methods but almost always am required to stick to metabat as the final binner.
Perhaps touching a temp file (results header, just empty for example) when binning is complete is possible?
** Atlas version**
2.16.1
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: