-
Notifications
You must be signed in to change notification settings - Fork 41
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
Bakta running only for one sample #171
Comments
Hi @SchwarzMarek , I have ran nextflow run main.nf -profile test,docker --annotation_tool bakta --baktadb_download true --outdir results |
Hi, |
It seems something went wrong with the assembly step in sample ERR044595. Was the FASTA file generated correctly? There is no value under the |
I can't see anything wrong with the assembly step. I noticed this issue when I wanted more precise annotation than those provided by prokka and did rerun with bakta. With prokka, I had annotations for every sample. One thing to note is that I was using full bakta db then (and also for this test data here). I'm uploading the full multiqc report. multiqc.zip Best |
Got it! Thanks for testing it out. If possible, please review it here: #178 |
Description of the bug
When running
bacass
for multiple samples,bakta
output is produced only for one of them.Execution trace and sw version are included in zip. (no
.nextflow.log
for this one, sorry)Command used and terminal output
No response
Relevant files
pipeline_info.zip
System information
No response
The text was updated successfully, but these errors were encountered: