Skip to content
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

BUSCO bug, solved in latest BUSCO version #56

Open
nikostr opened this issue Sep 24, 2024 · 3 comments
Open

BUSCO bug, solved in latest BUSCO version #56

nikostr opened this issue Sep 24, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@nikostr
Copy link

nikostr commented Sep 24, 2024

Description of the bug

I run into this bug https://gitlab.com/ezlab/busco/-/issues/721 when SANGERTOL_GENOMEASSEMBLY:GENOMEASSEMBLY:GENOME_STATISTICS_PURGED:BUSCO is being executed. This seems to be resolved in the latest version of BUSCO.

Command used and terminal output

nextflow run sanger-tol/genomeassembly \
        -resume \
        -c custom.config \
        -profile singularity,pdc_kth \
        --input assets/dataset.yaml \
        --outdir output-dir \
        -r 0.10.0 \
        --project <project-id>

Relevant files

No response

System information

No response

@nikostr nikostr added the bug Something isn't working label Sep 24, 2024
@nikostr
Copy link
Author

nikostr commented Oct 2, 2024

I just tried running the pipeline with the busco:5.7.1--pyhdfd78af_1 container, and it fixes the issue.

@nikostr
Copy link
Author

nikostr commented Oct 10, 2024

Well, it fixes that issue, but instead I get this issue: https://gitlab.com/ezlab/busco/-/issues/767

@nikostr
Copy link
Author

nikostr commented Oct 15, 2024

And that issue is in turn resolved by using the busco:5.8.0--pyhdfd78af_0 container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant