Felipe Marques de Almeida

I have no idea on such error. How are you calling the pipeline? Using docker, conda or singularity profile? Using the test dataset or your own? could you try, e.g....

Hi @rob-p , Pinging you to check if you have any idea on what this error experienced by @Khajidu may be related to?

Very funny that i did not work. I just tried again and it worked until the error commented here https://github.com/nf-core/scrnaseq/pull/139#issuecomment-1258005319 ```bash gitpod /workspace/scrnaseq/test (alevin-fry) $ nextflow run ../main.nf -profile test,docker...

Bakta outputs are extremely similar to Prokka, however, their annotation is more reliable. Therefore, the addition seems to be very straightforward: * Create a module for bakta so users can...

Now that pipeline has been restructured, this issue can become a reality. Since bakta database is huge, instead of downloading and formatting with the pipeline users will have to download...

Finally, after very much time, workflow is now properly running from top to bottom when using `bakta`. For release, it is now required to: - [x] Update the docs to...

Almost ready.

* requires running at least two annotations to evaluate how final results look like, so changes can be merged * And make sure docs are up to date > try...

Something is wrong with bakta docker image. When running it, it is complaining about diamond. With some -9 exit code.

Execution tests were finished. Now building new docker images, to check whether scripts and reports are properly updated so release can be made.