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

Separate BUSCO pipeline ? #101

Open
muffato opened this issue Jun 17, 2024 · 1 comment
Open

Separate BUSCO pipeline ? #101

muffato opened this issue Jun 17, 2024 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@muffato
Copy link
Member

muffato commented Jun 17, 2024

Given that we need to run BUSCO in at least two places (genomenote and blobtoolkit) and that we may want to run just BUSCO on some assemblies, is it worth making a pipeline just for running BUSCO ? It would probably have a single extra step to fetch lineages.

The alternative is running blobtoolkit with a set of ext.when conditions that essentially limit it to BUSCO.

Regardless of which pipeline has BUSCO, the resulting gene annotations should be processed the same way ensemblgenedownload does.

@muffato muffato converted this from a draft issue Jun 17, 2024
@muffato muffato added the question Further information is requested label Jun 17, 2024
@muffato muffato moved this from Todo to Triage in Genome After Party Jun 17, 2024
@tkchafin
Copy link

Adding a link to the progress we made in the hackathon: https://github.com/tkchafin/busco/tree/dev

@tkchafin tkchafin self-assigned this Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: Triage
Development

No branches or pull requests

2 participants