Getting Started

BUSCO runs on the command line, using a Terminal or Console application. You should have some familiarity with the basics of working with the command line.

BUSCO is a software package that requires a number of third-party tools. To simplify installation, BUSCO is available as a Conda package and a Docker image with all dependencies pre-installed. It can also be installed manually though in this case care must be taken to ensure all dependencies are installed and configured correctly.

Installation with Conda

Conda is an open-source package management and environment management system that simplifies the installation and management of software packages and their dependencies across diverse computing environments.

  1. Ensure sure you have conda version 4.8.4 or higher. Enter conda -V to check. If necessary, update conda by entering conda update -n base conda.

  2. To install BUSCO in the current environment, enter

    conda install -c conda-forge -c bioconda busco=5.6.1
  3. Alternatively you can create a new environment with BUSCO installed

    conda create -n <your_env_name> -c conda-forge -c bioconda busco=5.6.1
    conda activate <your_env_name>

If conda takes a long time to solve the environment, you can try using mamba instead of conda. Mamba is a reimplementation of the conda package manager in C++.

conda install -c conda-forge mamba
mamba install -c conda-forge -c bioconda busco=5.6.1

Installation with Docker

Docker is a tool for packaging and running applications and their dependencies in isolated containers, streamlining the deployment and management of software across diverse environments. Some familiarity with Docker is required to use the BUSCO Docker image. See the Docker userguide for details.

In short

docker pull ezlabgva/busco:v5.6.1_cv1
docker run -u $(id -u) -v $(pwd):/busco_wd ezlabgva/busco:v5.6.1_cv1

Avoid running containers in root, specify your user uid

docker run -u $(id -u) ezlabgva/busco:v5.6.1_cv1

Use mounts (-v) to exchange files between the host filesystem and the container filesystem. In the following example your current working directory ($(pwd)) is mounted as /busco_wd in the container. This allows you to access files in the current directory from within the container and to write files to the current directory from within the container.

docker run -u $(id -u) -v $(pwd):/busco_wd ezlabgva/busco:v5.6.1_cv1

The default working directory in the container is /busco_wd. With your non-root uid, attempts to write in the container virtual filesystem will fail if it is not a mount point. You can redefine the working directory using -w to match another mounted folder as current working directory. For example, if your BUSCO input filepath on your file system is /home/name/genome.fna

docker run -u $(id -u) -v /home/name/:/busco_wd ezlabgva/busco:v5.6.1_cv1 busco -i genome.fna

is equivalent to

docker run -u $(id -u) -v /home/name:/host_mount -w /host_mount ezlabgva/busco:v5.6.1_cv1 busco -i genome.fna

Be careful not to specify a host folder that does not exist when using -v /hostfolder/:/dockermount. Docker will create it with the root account, which is useless and annoying. It is safer to use the current directory -v $(pwd):/dockermount

Manual installation

To do a manual installation you will need to install the BUSCO code and all of its third-party dependencies separately. This is not recommended unless you have a specific reason to do so.

Installing BUSCO code

The following steps should be performed in a dedicated environment. See here for more on virtual environments.

  1. Clone the repository.
    git clone https://gitlab.com/ezlab/busco.git
    cd busco/
  2. Install using setuptools.
    sudo python3 setup.py
    python3 setup.py install --user

    NB: If you are running BUSCO in a Python virtual environment, the following should suffice:

    python3 setup.py install

Third-party components

A full installation of BUSCO requires

Please make sure that each software package listed above works INDEPENDENTLY of BUSCO before attempting to run any BUSCO assessments.

Relevant parameters given to BUSCO are propagated to third-party tools (e.g. number of cpus). Their default configuration should not be changed for BUSCO runs.

For Augustus, the option --augustus_parameters (see below) allows advanced users to freely pass parameters. Use it only to fix biologically relevant parameters such as the translation table and mention these when reporting the result. Do not use it for selecting the Augustus species, as there is a dedicated BUSCO parameter, and do not use it to specify the number of cpus.


Augustus uses several executables and PERL scripts. Please refer to Augustus documentation for PERL requirements.

Augustus requires environment variables to be declared as follows:

export PATH="/path/to/AUGUSTUS/augustus-3.2.3/bin:$PATH"
export PATH="/path/to/AUGUSTUS/augustus-3.2.3/scripts:$PATH"
export AUGUSTUS_CONFIG_PATH="/path/to/AUGUSTUS/augustus-3.2.3/config/"

NB: you can use the printenv command to view all your environment settings.

Known bugs and unsupported versions

tBLASTn 2.4+

During development we recognised an issue with tBLASTn versions 2.4-2.10.0 when using more than one CPU. NCBI issued a fix for the problem in version 2.10.1+. Make sure you have at least version 2.10.1+ installed.

Supported OS

BUSCO is being developed and tested on multiple distributions of Linux (e.g. Arch Linux, CentOS, Ubuntu). We do not support MacOS but BUSCO should work on it, although Augustus seems to cause troubles on some BSD-derived systems, including MacOS. Consider the Docker container if you work on incompatible environments.

Running BUSCO

Mandatory parameters


-i or --in defines the input file to analyse which is either a nucleotide fasta file or a protein fasta file, depending on the BUSCO mode. As of v5.1.0 the input argument can now also be a directory containing fasta files to run in batch mode.

-m or --mode sets the assessment MODE: genome, proteins, transcriptome

-l or --lineage_dataset Specify the name of the BUSCO lineage dataset to be used, e.g. hymenoptera_odb10. A full list of available datasets can be viewed by entering busco --list-datasets. You should always select the dataset that is most closely related to the assembly or gene set you are assessing. If you are unsure, you can use the --auto-lineage option to automatically select the most appropriate dataset. BUSCO will automatically download the requested dataset if it is not already present in the download folder. You can optionally provide a path to a local dataset instead of a name, e.g. -l /path/to/my/dataset.

-c or --cpu Specify the number of threads/cores to use. Unless this is specified BUSCO will only use one CPU, which could cause a long run time.

-o or --out Give your analysis run a recognisable short name. Output folders and files will be labelled with this name. If not specified the output will take the form "BUSCO_<input_filename>"

Optional parameters

--augustus Use augustus gene predictor for eukaryote runs.

--augustus_parameters "--PARAM1=VALUE1,--PARAM2=VALUE2" Pass additional parameters to Augustus. See Augustus documentation for parameter options. All parameters should be contained within a single string with no white space, with each parameter separated by a comma.

--augustus_species AUGUSTUS_SPECIES Specify a species for Augustus training.

--auto-lineage Run auto-lineage pipeline to find optimum lineage path.

--auto-lineage-euk Run auto-placement just on eukaryota tree to find optimal lineage path.

--auto-lineage-prok Run auto-lineage just on prokaryota trees to find optimum lineage path.

--config /path/to/config.ini Provide a config file as an alternative to command line parameters.

--contig_break n Number of contiguous Ns to signify a break between contigs in BBTools analysis. Default is n=10.

--datasets_version DATASETS_VERSION Specify the version of BUSCO datasets, e.g. odb10.

--download [dataset ...] Download dataset. Possible values are a specific dataset name, "all", "prokaryota", "eukaryota", or "virus". If used together with other command line arguments, make sure to place this last.

--download_base_url DOWNLOAD_BASE_URL Set the url to the remote BUSCO dataset location.

--download_path DOWNLOAD_PATH Specify local filepath for storing BUSCO dataset downloads. The default is a busco_downloads subdirectory in the current working directory.

-e N, --evalue N E-value cutoff for BLAST searches. Allowed formats, 0.001 or 1e-03 (Default: 1e-03).

-f, --force Force rewriting of existing files. Must be used when output files with the provided name already exist.

-h, --help Show this help message and exit.

--limit N How many candidate regions (contig or transcript) from the BLAST output to consider per BUSCO (default: 3). This option is only effective in pipelines using BLAST, i.e. the --augustus genome pipeline and the prokaryota transcriptome pipeline.

--list-datasets Print the list of available BUSCO datasets.

--long Optimize Augustus self-training mode. This adds considerably to the run time, but can improve results for some non-model organisms.

--metaeuk_parameters "--PARAM1=VALUE1,--PARAM2=VALUE2" Pass additional arguments to Metaeuk for the first run. See Metaeuk documentation for parameter options. All parameters should be contained within a single string with no white space, with each parameter separated by a comma, e.g. --metaeuk_parameters="--max-overlap=15,--min-exon-aa=15"

--metaeuk_rerun_parameters "--PARAM1=VALUE1,--PARAM2=VALUE2" Pass additional parameters to Metaeuk for the second run. See Metaeuk documentation for parameter options. All parameters should be contained within a single string with no white space, with each parameter separated by a comma.

--miniprot Use Miniprot gene predictor.

--offline In offline mode BUSCO will not attempt to download files. Ensure all required dataset files are already downloaded and available.

--opt-out-run-stats Opt out of data collection (from v5.6.0). Collected data is used to improve BUSCO. All collected data is anonymised and includes the pipelines used, the datasets selected, options used and runtime statistics.

--out_path OUTPUT_PATH Optional location for results folder, excluding results folder name. The default is the current working directory.

-q, --quiet Disable the info logs, displays only errors.

-r, --restart Continue a run that had already partially completed. Restarting skips calls to tools that have completed but performs all pre- and post-processing steps.

--scaffold_composition Writes ACGTN content per scaffold to a file scaffold_composition.txt. Used by BBTools.

--skip_bbtools Skip BBTools for assembly statistics.

--tar Compress some subdirectories with many files to save space.

-v, --version Show this version and exit.

Editing BUSCO Run Configuration

BUSCO will try to use the dependencies available in your environment. For the Conda and Docker distributions these are pre-installed. For the manual installation, it is up to the user to ensure the dependencies are available. An alternative to making the tool commands available in your local environment PATH is to point to the locations of the tools in a BUSCO configuration file, config.ini. A config file template is available here. This can also be used to override the PATH if you have a reason to use a specific version of a third-party tool. All command line options can also be specified in the config file instead of on the command line. Providing input parameters through the command line will override those defined in config.ini.

To activate this config file, either pass it as a command line option

busco --config /path/to/myconfig.ini

or set the environment variable BUSCO_CONFIG_FILE with the path to the file, as follows:

export BUSCO_CONFIG_FILE="/path/to/myconfig.ini"

Features and Tips for running BUSCO

  • Generally the lineage to select for your assessments should be the most specific lineage available, e.g. for assessing fish data one would select the actinopterygii lineage rather than the metazoa lineage.

A full list of available BUSCO datasets can be obtained by entering busco --list-datasets

  • If you are assessing a large number of species/strains/versions etc. then to minimise runtime (at the expense of resolution) one might select a less specific lineage set with fewer BUSCOs, e.g. for assessing 20 bird genomes each with a couple of different assembly versions one might select the vertebrata or the metazoa lineages rather than the aves lineage, at least for the initial rounds of assessments.
  • Assessments generally produce several folders with lots of files. These are for your benefit, so that you can examine individual cases in more detail and/or use the data for downstream analyses.
  • Please do take some time to check the log files, these are there for your benefit in order to highlight potential problems that may have occurred during your BUSCO run.
  • Compare the results from assessing your data with like-for-like assessments of corresponding publicly available data for other closely-related species. In this way, the BUSCO results can be used to claim that your dataset is as good as, or better than, existing publicly available datasets for similar species.
  • If manual curation of annotated gene sets was performed, report BUSCO results before and after curation to quantify improvements.

Automated lineage selection

For metagenomic analysis it is possible to let BUSCO selected automatically the datasets that is best suited to the input assembly, using the --auto-lineage option, e.g.

busco -m MODE -i INPUT -o OUTPUT --auto-lineage

or ignoring eukaryotes to save runtime, if compatible with your experimental goal.

busco -m MODE -i INPUT -o OUTPUT --auto-lineage-prok

or ignoring non-eukaryotes to save runtime, if compatible with your experimental goal.

busco -m MODE -i INPUT -o OUTPUT --auto-lineage-euk

The automated lineage selection process runs BUSCO on the generic lineage datasets for the domains archaea, bacteria and eukaryota. Once the optimal domain is selected, BUSCO automatically attempts to find the most appropriate BUSCO dataset to use based on phylogenetic placement. BUSCO evaluations are valid when an appropriate dataset is used, i.e., the dataset belongs to the lineage of the species to test. Because of overlapping markers/spurious matches among domains, BUSCO matches in another domain do not necessarily mean that your genome/proteome contains sequences from this domain. However, a high BUSCO score in multiple domains might help you identify possible contaminations.

Lineage datasets

BUSCO uses a set of evolutionarily-informed expectations of gene content of near-universal single-copy orthologs to assess the completeness of genome assemblies, gene sets, and transcriptomes. These expectations are derived from the analysis of a large number of evolutionarily diverse species, and are provided in the form of lineage-specific datasets. Marker genes are selected as those that are present in at least 90% of the species in a given lineage, and present in a single copy in 90% of those species. The marker genes are used to assess the completeness of the genome assembly or gene set being analysed. BUSCO scores are reported as the percentage of these marker genes that are found in the assembly or gene set.

BUSCO sampling space adapted from Waterhouse et al (2010)

BUSCO provides a set of pre-computed datasets for a wide range of organisms. Any use of these datasets for analyses in a publication or product must include the citation of the corresponding paper: https://doi.org/10.1093/molbev/msab199.

Specify a lineage dataset with the -l or --lineage_dataset option, for example

busco ... -l enterobacterales_odb10 ...

BUSCO will automatically download the requested dataset if it is not already present in the download folder. You can optionally provide a path to a local dataset instead of a name, e.g. -l /path/to/my/dataset. To print the full list of available datasets enter busco --list-datasets

For metagenomic analysis it is possible to let BUSCO selected automatically the datasets that is best suited to the input assembly, using the --auto-lineage, --auto-lineage-prok, or --auto-lineage-euk options.

The datasets are organised in folders that contain:

📁 hmms HMM file for each BUSCO
📁 info Files with lists of species, genes, ortho-groups, and annotations
📁 prfl Block profile file for each BUSCO
📎 ancestral FASTA file, consensus ancestral sequences for each BUSCO
📎 ancestral_variants FASTA file, consensus & variant sequences for each BUSCO
📎 dataset.cfg Configuration data including default Augustus species
📎 lengths_cutoff Length cut-offs for complete BUSCO matches
📎 scores_cutoff Score cut-offs for orthologous BUSCO matches
📎 links_to_ODB10.txt Annotations and links to OrthoDB for each gene
📎 missing_in_parasitic.txt List of genes present in lineages containing clades with reduced parasitic genomes (e.g. fungi_odb10)

Download and automated update

BUSCO can obtain the last version of the lineage datasets. If the name of a dataset is passed, e.g. -l bacteria_odb10, BUSCO will download it automatically. If a full path is given to BUSCO using -l /my/own/path/bacteria_odb10, this automated management will be disabled. Otherwise, files used during the automated lineage selection process are also automatically obtained by BUSCO.

By default, if a new version of a file is available, BUSCO will warn you. If you pass the argument --update-data, busco will replace the current file or folder with the up to date version and archive the previous one.

Individual datasets can also be downloaded using the busco download command, e.g. busco download bacteria_odb10. It is also possible to do a bulk download by using the following arguments in place of the dataset name: "all", "prokaryota", "eukaryota", or "virus".


If you are running BUSCO in an environment that does not have access to the Internet, you can pass the --offline argument to prevent BUSCO from attempting any download. You will have to download and unpack all files manually from https://busco-data.ezlab.org/v5/data/ and place them in the BUSCO download folder. The location of this folder should then be passed using the command line flag: --download_path /path/to/datasets.

A valid download folder looks as follows:

|-- information
|   `-- lineages_list.2019-11-27..txt
|-- lineages
|   |-- acidobacteria_odb10
|   |-- actinobacteria_class_odb10
|   |-- actinobacteria_phylum_odb10
|   |-- actinopterygii_odb10
|   |-- tissierellia_odb10
|   |-- tremellomycetes_odb10
|   |-- vibrionales_odb10
|   `-- xanthomonadales_odb10
`-- placement_files
    |-- list_of_reference_markers.archaea_odb10.2019-12-16..txt
    |-- mapping_taxid-lineage.archaea_odb10.2019-12-16..txt
    |-- mapping_taxids-busco_dataset_name.archaea_odb10.2019-12-16..txt
    |-- supermatrix.aln.archaea_odb10.2019-12-16..faa
    |-- tree.archaea_odb10.2019-12-16..nwk
    `-- tree_metadata.archaea_odb10.2019-12-16..txt

Interpreting the results

BUSCO provides a quantitative assessment of the completeness in terms of expected gene content of a genome assembly, transcriptome, or annotated gene set. The results are simplified into categories of Complete and single-copy, Complete and duplicated, Fragmented, or Missing BUSCOs, where "BUSCOs" is shorthand for "BUSCO marker genes".

BUSCO completeness results make sense only in the context of the biology of your organism. You have to understand whether missing or duplicated genes are of biological or technical origin. For instance, a high level of duplication may be explained by a recent whole duplication event (biological) or a chimeric assembly of haplotypes (technical). Transcriptomes and protein sets that are not filtered for isoforms will lead to a high proportion of duplicates. Therefore you should filter them before a BUSCO analysis. Finally, focusing on specific tissues or specific life stages and conditions in a transcriptomic experiment is unlikely to produce a BUSCO-complete transcriptome. In this case, consistency across your samples is what you will be aiming for.

If you need help or suggestions, use the BUSCO issues board to exchange with the BUSCO development team and other users.


If found to be complete, whether single-copy or duplicated, the BUSCO matches have scored within the expected range of scores and within the expected range of length alignments to the BUSCO profile. If in fact an ortholog is not present in the input dataset, or the ortholog is only partially present (highly fragmented), and a high-identity full-length homolog is present, it is possible that this homolog could be mistakenly identified as the complete BUSCO. The score thresholds are optimised to minimise this possibility, but it can still occur.


If found to be fragmented, the BUSCO matches have scored within the range of scores but not within the range of length alignments to the BUSCO profile. For transcriptomes or annotated gene sets this indicates incomplete transcripts or gene models. For genome assemblies this could indicate either that the gene is only partially present or that the sequence search and gene prediction steps failed to produce a full-length gene model even though the full gene could indeed be present in the assembly. When running eukaryotic datasets with the Metaeuk (default) or Augustus gene predictor, matches that produce such fragmented results are given a "second chance" with a second round of sequence searches and gene predictions with ancestral variants of the missing sequences and, in the case of Augustus, parameters trained on those BUSCOs that were found to be complete. However this can still fail to recover the whole gene. Some fragmented BUSCOs from genome assembly assessments could therefore be complete but are just too divergent or have very complex gene structures, making them very hard to locate and predict in full.


If found to be missing, there were either no significant matches at all, or the BUSCO matches scored below the range of scores for the BUSCO profile. For transcriptomes or annotated gene sets this indicates that these orthologs are indeed missing or the transcripts or gene models are so incomplete/fragmented that they could not even meet the criteria to be considered as fragmented. For genome assemblies this could indicate either that these orthologs are indeed missing, or that the sequence search step failed to identify any significant matches, or that the gene prediction step failed to produce even a partial gene model that might have been recognised as a fragmented BUSCO match. Like for fragments, when running eukaryotic datasets with the Metaeuk (default) or Augustus pipelines, BUSCOs missing after the first round are given a "second chance" with a second round of sequence searches and gene predictions with ancestral variants of the missing sequences and, in the case of Augustus, parameters trained on those BUSCOs that were found to be complete. However this can still fail to recover the whole gene. Some missing BUSCOs from genome assembly assessments could therefore be partially present, and even possibly (but unlikely) complete, but they are just too divergent or have very complex gene structures, making them very hard to locate and predict correctly or even partially.

Reporting BUSCO

  • Report results in simple BUSCO notation: C:89.0%[S:85.8%,D:3.2%],F:6.9%,M:4.1%,n:3023
  • Use the generate_plot.py (see below) script to produce simple graphical summaries (that are easily customisable) for your publication’s supporting online information.
  • Report the versions you used for all third party components. We highly recommand using the BUSCO container, whose version is sufficent to safely reproduce a run.
  • Report the BUSCO set(s) you used for your assessments. Mention the creation date of the dataset, not only the name, e.g. archaea_odb10 (2019-01-04).
  • Report the BUSCO options you used.
  • Report the version(s) of the genome assembly, annotated gene set, or transcriptome that you assessed.

Companion scripts


The scripts/generate_plot.py script allows users to quickly view their BUSCO summary results in an easily-understandable bar chart. The scripts/generate_plot.py uses R (https://www.r-project.org/) and ggplot2 (http://ggplot2.org/) to summarise BUSCO runs for side-by-side comparisons. The script produces a PNG image (if both R and ggplot2 are available), as well as an R source code file that can be used to run on a different machine where both R and ggplot2 are available or which can be edited to fully customise the resulting bar chart (colours, labels, fonts, axes, etc.).

usage: python3 generate_plot.py -wd [WORKING_DIRECTORY] [OTHER OPTIONS]

BUSCO plot generation tool.
Place all BUSCO short summary files (short_summary.[generic|specific].dataset.label.txt) in a single folder. It will be your working directory, in which the generated plot files will be written
See also the user guide for additional information

required arguments:
  -wd PATH, --working_directory PATH
                        Define the location of your working directory

optional arguments:
  -rt RUN_TYPE, --run_type RUN_TYPE
                        type of summary to use, `generic` or `specific`
  --no_r                To avoid to run R. It will just create the R script file in the working directory
  -q, --quiet           Disable the info logs, displays only errors
  -h, --help            Show this help message and exit

To run scripts/generate_plot.py, first create a folder, e.g. mkdir BUSCO_summaries, and then copy the BUSCO short summary file from each of the runs you want to plot into this folder.

cp XX1/short_summary.*.lineage_odb10.XX1.txt BUSCO_summaries/.
cp XX2/short_summary.*.lineage_odb10.XX2.txt BUSCO_summaries/.
cp XX3/short_summary.*.lineage_odb10.XX3.txt BUSCO_summaries/.

Then simply run the script giving as argument the name (or full path if you are not in same working directory) of the folder you created containing the summaries you wish to plot.

python3 scripts/generate_plot.py –wd BUSCO_summaries
python3 scripts/generate_plot.py –wd /full/path/to/my/folder/BUSCO_summaries

The resulting PNG image and the corresponding R source code file will be produced in the same folder containing the BUSCO summaries. By default, the run name is used as the label for each plotted result, and this is automatically extracted from the short summary file name: so for short_summary.generic.lineage_odb10.XX1.txt the label would be XX1. You can modify this as long as you keep the naming convention: short_summary.generic.lineage_odb10.[edit_name_here].txt or you can simply edit the R source code file to change any plotting parameters and produce a personalised bar chart running the code manually in your R environment.

Example scripts/generate_plot.py bar chart:

mkdir my_summaries
cp SPEC1/short_summary.generic.lineage1_odb10.SPEC1.txt my_summaries/.
cp SPEC2/short_summary.generic.lineage2_odb10.SPEC2.txt my_summaries/.
cp SPEC3/short_summary.specific.lineage2_odb10.SPEC3.txt my_summaries/.
cp SPEC4/short_summary.generic.lineage3_odb10.SPEC4.txt my_summaries/.
cp SPEC5/short_summary.generic.lineage4_odb10.SPEC5.txt my_summaries/.
python3 scripts/generate_plot.py –wd my_summaries

BUSCO plot|5x5


The repository https://gitlab.com/ezlab/busco_usecases contains the script that was used to produce the phylogenomics portion of the BUSCO v3 (PMID: 29220515) paper. It has not been ported to BUSCO v4.


If you need help, please search the BUSCO issues board or open a new issue if your question has not previously been answered.



The novelties introduced in BUSCO v4 and v5 and the new BUSCO datasets (*_odb10) are described here.
If you've used these versions or datasets, the correct citation would be:

Mosè Manni, Matthew R Berkeley, Mathieu Seppey, Felipe A Simão, Evgeny M Zdobnov, BUSCO Update: Novel and Streamlined Workflows along with Broader and Deeper Phylogenetic Coverage for Scoring of Eukaryotic, Prokaryotic, and Viral Genomes. Molecular Biology and Evolution, Volume 38, Issue 10, October 2021, Pages 4647–4654

The following protocol covers the various BUSCO running modes and workflows, BUSCO setup, guidelines to interpret the results, and additional analyses, e.g., for building phylogenomic trees and visualizing syntenies using BUSCO results:

Manni, M., Berkeley, M. R., Seppey, M., & Zdobnov, E. M. (2021). BUSCO: Assessing genomic data quality and beyond. Current Protocols, 1, e323. doi: 10.1002/cpz1.323


The BUSCO software is licensed under the MIT License.

The BUSCO datasets are licensed under the Creative Commons Attribution-NoDerivatives 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nd/4.0/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.
Any use of these datasets for analyses in a publication or product must include the citation of the corresponding paper: https://doi.org/10.1093/molbev/msab199.