Hot answers tagged


From the README, it looks like the command-line entry point is not busco but This seems to agree with the bioconda recipe, where and run_busco are listed among the commands.


You are correct, it is the score of the candidate protein against the BUSCO profile hmm assessed by hmmer. If it passes a threshold, it is validated as being that BUSCO gene. The threshold is defined for each profile based on the score of the species used to produce the profile. It can be found in name_odb10/scores_cutoff. And yes, the higher the better.


Most likely your Augustus installation is not functioning properly. Did you install Augustus from source or using conda? I believe the conda version of Augustus is known to have some issues. Something worth trying: Running a complete busco install in a VM. This image has all dependencies installed and properly configured.


The core idea behind BUSCO is that there are a number of genes that are Unique Single-Copy Orthologues (USCOs) that should be present in most genomes and should only appear once in the genome. This is only a guess, however, and not a universal rule. Sometimes genomes can have multiple copies of these USCOs, and these duplicated genes reduce the overall score ...


It's hard to say for sure without seeing the exact commands you used. However, Orthofinder identifies/defines single-copy orthologues as those genes present in a single copy in all species being compared in the analysis. If a BUSCO orthologue is present in more than one copy in one of the species being compared (could be multi-copy, could be fragmented etc.),...


The new version of busco (v4) has the user entry point called busco (it's still a python script). BUSCO v4 is available at conda, note it's a very fresh update.

Only top voted, non community-wiki answers of a minimum length are eligible