You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered this twice, with larger bacterial datasets, but for whatever reason, whether quality of raw read data is bad or spades cannot produce a decent assembly, Bakta will then fail (not surprisingly) and after a few retries, the whole pipeline stops until I remove the samples in question.
Is there a way to proceed with the analysis, even if Spades, or Bakta fail for a small number of samples, making note of which samples couldn't go though the pipeline?
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered:
Spades failures will now be ignored and any downstream steps relying on the assembly should be ignored. Feel free to reopen if this is still a problem.
Description of the bug
I have encountered this twice, with larger bacterial datasets, but for whatever reason, whether quality of raw read data is bad or spades cannot produce a decent assembly, Bakta will then fail (not surprisingly) and after a few retries, the whole pipeline stops until I remove the samples in question.
Is there a way to proceed with the analysis, even if Spades, or Bakta fail for a small number of samples, making note of which samples couldn't go though the pipeline?
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: