That looks really useful, will check it out next week.

I think we should definitively incorporate this to our pipeline.

I was also thinking we should make genome.nf and genome_and_annotation.nf into workflows, as right now they are subworkflows.

We should also have a look at the BUSCO subworkflow from the MAG pipeline. See #85.

We should also have a look at the BUSCO subworkflow from the MAG pipeline. See #85.

My implementation does have a val_busco_lineages_path input. If this is provided, busco will download the data there once and will reuse it. If all the data is already downloaded, then busco will use that instead of redownloading it.

For cloud environments, this parameter needs to be optimised so that a tar ball can be passed similar to what mag is doing.

Hi @GallVp, I would like to incorporate your BUSCO subworkflow into our pipeline, at least for now. We can update it later once it's made into an nf-core subworkflow.

I'm not sure what's the etiquette to follow here, especially when it comes to giving you proper credit.

Thank you @FernandoDuarteF

It will be good to share the workflows across pipelines and maintain them jointly. I am happy to create a PR and that will put me as a contributor on the repo. That's enough credit for me. How about we do the following,

• I submit the sub-workflow to nf-core/modules and invite your review. Hopefully, it will be accepted now that there are two pipelines using it. If not, we will have to maintain it where it is, i.e. in my modules repo.
• I create a PR to genomeqc for adding the sub-workflow and again invite your review.

Thank you @GallVp! Awesome, let's do that then.