You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: