OrthoFinder: solving fundamental biases in whole genome comparisons dramatically improves orthogroup inference accuracy — TEI-tagged view

David M. Emms, Steven Kelly · 2015 · bioinformatics · doi:10.1186/s13059-015-0721-2 · TEI xml · tagged edition · index · concepts · authors
Where this record's text came from. 2026-08-30 schema-0.3 pass: every quote verified as an exact substring of the staged text and anchored at merge time; concept terms verified present; every edge endpoint an existing node.
22 quotations on this page contain a reference number where the paper printed a superscript. This journal style prints citations as raised numerals — parameters12,13 — and the extraction flattened them into the line, so the sentence reads parameters 12 , 13 . The digits are citation markers and not part of what the author wrote. The quotes keep them for the same reason they keep every other extraction fault: a quote is reproduced exactly or it proves nothing.
Other fields define these differently the same word, defined another way in another discipline
memory 23 fields · precision 10 fields · algorithm 5 fields · transcription factors 3 fields · recall 2 fields · linear model 2 fields
Tags on this paper every tag the record carries, whether or not the words occur in the text below — a number is how many papers in the corpus carry that tag; a tag with no number is unique to this paper
homology relationships orthology inference genome and transcriptome annotation pairwise relationships gene duplications orthology3 orthogroup set of genes derived from a single gene in the last common ancestor orthologues paralogues OrthoMCL BLAST MCL clustering algorithm gene synteny OrthoFinder gene length bias BLAST scores bit scores e-values OrthoBench recall8 precision27 novel score transform normalised scores reciprocal best BLAST hit RBNH inclusion threshold orthogroup graph F-score2 harmonic mean2 incomplete datasets sparse matrices matrix operations transcription factors4 whole genome duplication events gene-tree/species-tree reconciliation type IVc bHLH transcription factors algorithm9 protein sequence FASTA file OrthoXML putative cognate gene-pairs gene length and phylogenetic distance normalisation phylogenetic distance similarity measure top 5 % of hits most dissimilar RBNH MCL inflation parameter sparse matrix operations true negative orthologue assignments transcription factor orthogroups shared ancestry functional conservation single command system-or-tool-building173
Method, as described: all-versus-all BLAST, species-pair gene-length and phylogenetic-distance normalisation, RBNH-delimited graph construction, MCL clustering, OrthoBench evaluation, and gene-tree/species-tree reconciliation

Colour legend

Genome Biology<title level="j">A work — the journal / venue title.
2015<date>A year or date.

David M. EmmspersName, Steven KellypersName (2015date). “OrthoFinder: solving fundamental biases in whole genome comparisons dramatically improves orthogroup inference accuracy.” Genome Biologytitle·j.

Object of study — accurate and scalable inference of multi-species orthogroupsterm from protein sequences despite gene-length and phylogenetic-distance biases

Research question — whether normalised similarity scores and query-specific cognate thresholds improve complete orthogroupterm recovery over existing pairwise and clustering approaches

Contribution — OrthoFinderterm, a five-phase orthogroupterm inference algorithmterm that normalises BLAST scoresterm, builds a cognate-gene graph, clusters it with MCL, and is benchmarked for accuracy, missing-data robustness, scale, and plant transcription-factor discovery

Cross-disciplinary analysis
content-tags & facets: phenomenon · claim-type · cross-domain-transfer · mechanism · claim-relation · replication-status · limitation — grounded in the full text
phenomenonbias, precision, recall, F-score, robustness, and computational scaling in homology and orthogroup inference — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”
claim-typemethod — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”
method — evidence — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”
object of study — evidence — “Here we present OrthoFinder, a novel method that infers orthogroups of protein coding genes. It is fast, easy to use and scalable to thousands of genomes. In tests using real benchmark datasets OrthoFinder outperforms all other commonly used orthogroup inference methods by between 8 % and 33 %. We further demonstrate the utility of OrthoFinder through the inference and analysis of plant transcription factor orthogroups. Here we use phylogenetic methods to validate the orthogroups and show that using OrthoFinder to infer orthogroups identifies millions of previously unobserved relationships. Further information about the algorithm can be found at [ 19 ] and a standalone implementation of the algorithm is available under the GPLv3 licence at [ 20 ].”
research question — evidence — “Given that we had reduced gene length bias and that precision was high but recall was low, we assessed whether a method that could identify a higher proportion of cognate gene-pairs prior to clustering could produce an overall increase in clustering accuracy. Many orthology assignment methods make use of reciprocal best BLAST hit (RBH) as it is widely regarded as a high precision method for the identification of orthologues gene-pairs [ 25 – 27 ]. Therefore we also sought to use reciprocal best BLAST hits using our new length-normalised score to assist in construction of the orthogroup graph. Henceforth, we refer to a reciprocal best hit that is obtained using the length-normalised score as an RBNH (reciprocal best normalised hit).”
contribution — evidence — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”
mechanismall-versus-all BLAST Every sequence is compared against every sequence to generate candidate similarities. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”mechanisms[0]
mechanismequal sized bins Hits are stratified by the product of query and hit lengths. — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”mechanisms[1]
mechanismtop 5 % of hits High-quality hits in each bin define the expected length-score trend. — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”mechanisms[2]
mechanismlinear model Least-squares fitting in log-log space estimates the species-pair length dependency. — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”mechanisms[3]
mechanismnormalised scores Bit scores are divided by expected best-hit scores to remove length and distance effects. — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”mechanisms[4]
mechanismRBNHs Reciprocal best normalised hits delimit query-specific orthogroup similarity. — “Once scores are normalised OrthoFinder exploits RBNHs to identify putative cognate gene-pairs. RBHs are a high precision method to identify putative orthologues [ 25 – 27 ] and OrthoFinder uses the reciprocal requirement exploiting its length and phylogenetic distance normalised BLAST scores. For each gene the scores for its RBNHs are used to delimit the extent of sequence similarity of that gene’s orthogroup. Specifically, for each query sequence, q, any hit, h, with a normalised score, B ' qh , greater than or equal to the score for the lowest scoring RBNH of q is selected as a putative cognate gene-pair of q and therefore is connected to q in the orthogroup graph that is subsequently subjected to MCL clustering.”mechanisms[5]
mechanisminclusion threshold Hits above a query gene's weakest RBNH enter the cognate-gene graph. — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”mechanisms[6]
mechanismorthogroup graph Genes are nodes and normalised scores weight putative cognate edges. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”mechanisms[7]
mechanismMCL Markov clustering partitions the graph into discrete orthogroups. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”mechanisms[8]
mechanismspecies-wise normalisation Independent pairwise models prevent distant orthologues from being preferentially disconnected. — “The aim of this normalisation procedure is to remove gene length bias from BLAST bit scores and to normalise for phylogenetic distance between species. MCL converts sets of similarity scores into clusters by breaking apart clusters of genes that have low similarity scores (and therefore are unlikely to be orthogroups) and preserving clusters of sequences that have high similarity scores. If the similarity scores between long sequences are inherently larger than the similarity scores between short sequences then the clustering will preferentially break apart clusters of short sequences while preserving clusters of long sequences. This effect can be clearly seen in the results of a typical OrthoMCL cluster. Here, long sequences are placed in overly large clusters leading to low precision, and short sequences remain un-clustered leading to low recall (Fig. 3a ). The species-wise normalisation implemented by OrthoFinder similarly ensures that orthologues from more distant species (that have inherently lower similarity scores due to phylogenetic distance) are not preferentially discarded and is similar to a step that is performed in OrthoMCL wherein all scores are divided by the average score between a given species pair [ 13 ].”mechanisms[9]
mechanismsparse matrices Sparse hit storage makes the implementation memory efficient and enables optimized operations. — “OrthoFinder is written in python. It requires python together with the numpy and scipy libraries [ 35 ] to be installed. OrthoFinder requires the standalone BLAST+ and MCL algorithms that are freely available. These standalone applications must be installed separately to OrthoFinder and are not included in the OrthoFinder package. The implementation makes use of sparse matrices to store hits between sequences. This provides a memory efficient method of storing the data and allows key parts of the algorithm to be expressed using scipy’s highly optimised C++ implementations of sparse matrix operations. OrthoFinder can either run the BLAST searches for you or can be run on pre-computed BLAST searches. If you chose to run BLAST searches independently then instructions are provided in the documentation for how to process your sequence names in the pre-computed BLAST output. Similarly OrthoFinder will also automatically run MCL for you. However if you wish to run MCL separately using different parameter settings then the MCL input files are stored for this purpose in a working directory.”mechanisms[10]
mechanismmatrix operations Central sparse-matrix operations support scaling across genomes. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”mechanisms[11]
mechanismgene-tree/species-tree reconciliation Pre-ancestor duplications diagnose falsely merged orthogroups. — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”mechanisms[12]
mechanismprecision and recall The two observable assignment measures evaluate accuracy when true negatives are unknown. — “OrthoBench [ 5 ] is the only manually curated dataset of orthogroups for the assessment of orthogroup prediction algorithms. It was used in this work for assessing OrthoFinder as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinder was designed to solve. Criteria such as functional similarity within orthogroups, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroup and members of the same orthogroup do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignments is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroup inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precision and recall. precision = T P T P + F P recall = T P T P + F N”mechanisms[13]
mechanismsingle command Minimal-input orchestration runs BLAST, MCL, and output generation for independent users. — “Inferring orthologues underpins much of modern biological research and is among the first steps in the annotation and analysis of genome and transcriptome sequencing projects. As sequencing technologies are now within the budgets of most research groups these data resources are increasing in number rapidly. Thus there is a requirement for an orthogroup inference method that is accurate, robust, scalable, and that can be run easily by independent research groups on conventional computing resources. Many orthogroup inference methods are not available for general use but are provided as static databases (for example, EggNog and TreeFam). Thus the most widely used methods are those that enable researchers to analyse their own data resources. With this in mind OrthoFinder has been developed with the aim of being easy to use. The method is executed as a single command, has minimal dependencies and requires as input just the individual protein sequence FASTA files for each species that is being clustered. The algorithm carries out all calculations (including BLAST searches and MCL clustering) and outputs the orthogroups in both a plain tab delimited text file and in the OrthoXML community format. The algorithm itself is small, fast and memory efficient, making it suitable for use on linux desktop computers. Further information about the algorithm can be found at [ 19 ] and a standalone implementation of the algorithm is available under the GPLv3 licence at [ 20 ].”mechanisms[14]
contrasts-with pairwise orthology inference — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”claim_relations[0]
builds-on BLAST and MCL — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”claim_relations[1]
contrasts-with OrthoMCL — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”claim_relations[2]
extends reciprocal best hit orthology — “The rationale for this approach is that the level of normalised similarity of a query gene and its RBNHs can be used to estimate the extent of similarity of other genes within the same orthogroup. All genes more similar to a query gene than any of the query gene’s RBNHs (irrespective of species) are likely members of the same orthogroup. Therefore, the normalised similarity score for the most dissimilar RBNH of a gene is used as a cutoff for inclusion of additional cognate gene-pairs from all species. That is q is connected to h in the orthogroup graph if B ' qh > B ' qR where R is an RBNH of q. This provides a simple and robust method for recovering cognate gene-pairs that may otherwise be difficult to detect due to duplication events that can cause the RBNH method to fail. Further details, explanation and worked examples are provided in Additional file 8 : Figure S5.”claim_relations[3]
senseorthology as a non-transitive relation after gene duplication — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”senses[0]
senseorthogroup as complete descent from one ancestral gene across all species considered — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”senses[1]
senseorthogroup membership as including both orthologues and paralogues — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”senses[2]
sensegene-length bias as both short-gene omission and long-gene false inclusion — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”senses[3]
senseRBNH as reciprocal best hit after length normalisation — “Given that we had reduced gene length bias and that precision was high but recall was low, we assessed whether a method that could identify a higher proportion of cognate gene-pairs prior to clustering could produce an overall increase in clustering accuracy. Many orthology assignment methods make use of reciprocal best BLAST hit (RBH) as it is widely regarded as a high precision method for the identification of orthologues gene-pairs [ 25 – 27 ]. Therefore we also sought to use reciprocal best BLAST hits using our new length-normalised score to assist in construction of the orthogroup graph. Henceforth, we refer to a reciprocal best hit that is obtained using the length-normalised score as an RBNH (reciprocal best normalised hit).”senses[4]
sensecognate threshold as query-specific rather than globally fixed — “The rationale for this approach is that the level of normalised similarity of a query gene and its RBNHs can be used to estimate the extent of similarity of other genes within the same orthogroup. All genes more similar to a query gene than any of the query gene’s RBNHs (irrespective of species) are likely members of the same orthogroup. Therefore, the normalised similarity score for the most dissimilar RBNH of a gene is used as a cutoff for inclusion of additional cognate gene-pairs from all species. That is q is connected to h in the orthogroup graph if B ' qh > B ' qR where R is an RBNH of q. This provides a simple and robust method for recovering cognate gene-pairs that may otherwise be difficult to detect due to duplication events that can cause the RBNH method to fail. Further details, explanation and worked examples are provided in Additional file 8 : Figure S5.”senses[5]
senseprecision as false-positive-sensitive assignment correctness — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”senses[6]
senserecall as false-negative-sensitive assignment completeness — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”senses[7]
senseF-score as a harmonic balance weighted toward the weaker measure — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”senses[8]
sensephylogenetic-distance normalisation as equalizing best orthologue scores across species pairs — “OrthoFinder also normalises for phylogenetic distance, this is done so that the similarity scores between orthologues will be independent of phylogenetic distance (that is, the true orthologues in distantly related species will obtain similar scores to the true orthologues in closely related species). If this step is not done then true orthologues in distantly related species will always obtain lower scores than true orthologues in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologues (and cognates) will become disconnected from each other more easily than closely related true orthologues (and cognates) in the orthogroup graph. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene length information this means that short genes will always be penalised more than long genes.”senses[9]
sensetrue orthogroup as excluding pre-last-common-ancestor duplication splits — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”senses[10]
senseOrthoFinder scope as group inference rather than within-group pair classification — “In this work we have presented OrthoFinder, a novel method for inference of orthogroups. Our method is focused on a clear definition of an orthogroup, that is, that an orthogroup contains all genes descended from a single gene in the last common ancestor of the species whose genes are being analysed. This definition avoids conflating shared ancestry with other criteria that are not equivalent, such as functional conservation. Our method is designed to address the problem of orthogroup inference rather than categorise the disparate relationships that occur between individual genes within an orthogroup. These relationships are best resolved by first inferring orthogroups using OrthoFinder and then using multiple sequence alignment and phylogenetic methods on these orthogroups.”senses[11]
controlmanually curated OrthoBench orthogroups — held — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].” — rules out evaluation against unverified inferred group labels — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”controls[0]
controlprecision, recall, and F-score stratified by gene length — held — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths” — rules out aggregate accuracy hiding opposite short- and long-gene biases — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”controls[1]
controlnormalised scores inserted into the OrthoMCL clustering workflow — held — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths” — rules out attributing the score-transform effect to a different clustering algorithm — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”controls[2]
controlrandom deletion of 5 to 60 percent of genes — held — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.” — rules out dependence on complete genome inputs — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”controls[3]
controlsame CPU and precomputed BLAST inputs for OrthoFinder and OrthoMCL — held — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources. Fig. 4 Memory and time requirements of OrthoFinder. Sub-samples of between two and 41 plant genomes from Phytozome version 9.0 given pre-calculated BLAST results. The average number of genes per species was 30,731. a Maximum RAM requirements. b Time requirements. c The number of BLAST hits that must be processed for a given number of species (provided to place the time and RAM requirements into context)” — rules out hardware and shared-search cost from the runtime comparison — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”controls[4]
controlgene-tree/species-tree reconciliation of inferred transcription-factor groups — held — “As OrthoFinder clustered the transcription factors together into far fewer orthogroups than OrthoMCL (897 versus 3024) we sought to demonstrate that it was correct in doing so. To do this we used gene-tree/species-tree reconciliation to determine if the orthogroups were true orthogroups if they incorrectly clustered sequences that are separated by a gene duplication event that occurred before the last common ancestor of the species in the analysis. Overall, 858 of the 897 OrthoFinder orthogroups (96 %) consisted entirely of genes that were correctly clustered together and only 39 contained some genes that were separated by a duplication prior to the last common ancestor (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of the 897 OrthoFinder orthogroups, 210 were identical to ones from OrthoMCL and 471 OrthoFinder orthogroups were strict supersets of 2,271 OrthoMCL orthogroups (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of these, 90 % (425) were true orthogroups that each encompassed on average four OrthoMCL orthogroups (1,709 in total).” — rules out assuming that fewer, larger groups are correct from recall alone — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”controls[5]
controlalternative functions of query and hit gene length — held — “Though there is precedent for the use of L qh = L q L h to quantify the lengths of a pair of sequences that are being compared [ 14 ], different functions for gene length normalisation were also assessed. All other functions, including for example the use of the variable L ˜ q h = L q + L h in place of L qh , gave a lower overall clustering accuracy.” — rules out arbitrary choice of the multiplicative length measure — “Though there is precedent for the use of L qh = L q L h to quantify the lengths of a pair of sequences that are being compared [ 14 ], different functions for gene length normalisation were also assessed. All other functions, including for example the use of the variable L ˜ q h = L q + L h in place of L qh , gave a lower overall clustering accuracy.”controls[6]
notepairwise orthology inference — OrthoFinder adopts complete orthogroups rather than pairwise transitive sets. — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”claim_relations[0]
weightpairwise orthology inference — 0.95 — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”claim_relations[0]
evidence status noteBLAST and MCL — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”claim_relations[1]
noteBLAST and MCL — The pipeline transforms BLAST hits and clusters the resulting graph with MCL. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”claim_relations[1]
weightBLAST and MCL — 0.95 — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”claim_relations[1]
noteOrthoMCL — The benchmark and plant analysis directly compare the methods. — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”claim_relations[2]
weightOrthoMCL — 0.95 — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”claim_relations[2]
notereciprocal best hit orthology — RBNHs become query-specific thresholds that recover additional cognate pairs. — “The rationale for this approach is that the level of normalised similarity of a query gene and its RBNHs can be used to estimate the extent of similarity of other genes within the same orthogroup. All genes more similar to a query gene than any of the query gene’s RBNHs (irrespective of species) are likely members of the same orthogroup. Therefore, the normalised similarity score for the most dissimilar RBNH of a gene is used as a cutoff for inclusion of additional cognate gene-pairs from all species. That is q is connected to h in the orthogroup graph if B ' qh > B ' qR where R is an RBNH of q. This provides a simple and robust method for recovering cognate gene-pairs that may otherwise be difficult to detect due to duplication events that can cause the RBNH method to fail. Further details, explanation and worked examples are provided in Additional file 8 : Figure S5.”claim_relations[3]
weightreciprocal best hit orthology — 0.95 — “The rationale for this approach is that the level of normalised similarity of a query gene and its RBNHs can be used to estimate the extent of similarity of other genes within the same orthogroup. All genes more similar to a query gene than any of the query gene’s RBNHs (irrespective of species) are likely members of the same orthogroup. Therefore, the normalised similarity score for the most dissimilar RBNH of a gene is used as a cutoff for inclusion of additional cognate gene-pairs from all species. That is q is connected to h in the orthogroup graph if B ' qh > B ' qR where R is an RBNH of q. This provides a simple and robust method for recovering cognate gene-pairs that may otherwise be difficult to detect due to duplication events that can cause the RBNH method to fail. Further details, explanation and worked examples are provided in Additional file 8 : Figure S5.”claim_relations[3]
noteOrthoFinder —is-a→ algorithm — Direct categorical statement. — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”concept_edges[0]
relationOrthoFinder —is-a→ algorithm — OrthoFinder is an algorithm that infers orthogroups across multiple species. — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”concept_edges[0]
noteorthogroup —is-a→ set of genes derived from a single gene in the last common ancestor — Direct categorical definition. — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”concept_edges[1]
relationorthogroup —is-a→ set of genes derived from a single gene in the last common ancestor — An orthogroup is the set of genes derived from one ancestral gene. — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”concept_edges[1]
noteOrthoFinder —contrasted-with→ OrthoMCL — Direct benchmark comparison. — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”concept_edges[2]
relationOrthoFinder —contrasted-with→ OrthoMCL — OrthoFinder has a 25 percent higher F-score than OrthoMCL on OrthoBench. — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”concept_edges[2]
weightOrthoFinder —contrasted-with→ OrthoMCL — 0.95 — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”concept_edges[2]
notebit scores —contrasted-with→ e-values — Explicit replacement contrast. — “Given that orthogroup inference shows a clear gene length dependency, we sought to develop a transform of the BLAST scores that would reduce the impact of gene length on clustering accuracy. To do this we developed a novel method that determines the gene length dependency of a given pairwise species comparison from an analysis of the bit scores from an all-versus-all BLAST search between the two species. Bit scores were used in place of e-values as the e-value calculation enforces a limit of 1×10 −180 and thus all scores below this floor are given the same value (that is, 0) (Fig. 1b ) and thus length bias in e-values is non-uniform and irreversible. As bit scores do not have a threshold value, and they have been previously shown to be capable of facilitating accurate inference of phylogenetic trees [ 24 ], they were selected as the raw data for the development of a novel score transform.”concept_edges[3]
relationbit scores —contrasted-with→ e-values — Bit scores were used in place of floored e-values for the transform. — “Given that orthogroup inference shows a clear gene length dependency, we sought to develop a transform of the BLAST scores that would reduce the impact of gene length on clustering accuracy. To do this we developed a novel method that determines the gene length dependency of a given pairwise species comparison from an analysis of the bit scores from an all-versus-all BLAST search between the two species. Bit scores were used in place of e-values as the e-value calculation enforces a limit of 1×10 −180 and thus all scores below this floor are given the same value (that is, 0) (Fig. 1b ) and thus length bias in e-values is non-uniform and irreversible. As bit scores do not have a threshold value, and they have been previously shown to be capable of facilitating accurate inference of phylogenetic trees [ 24 ], they were selected as the raw data for the development of a novel score transform.”concept_edges[3]
weightbit scores —contrasted-with→ e-values — 0.95 — “Given that orthogroup inference shows a clear gene length dependency, we sought to develop a transform of the BLAST scores that would reduce the impact of gene length on clustering accuracy. To do this we developed a novel method that determines the gene length dependency of a given pairwise species comparison from an analysis of the bit scores from an all-versus-all BLAST search between the two species. Bit scores were used in place of e-values as the e-value calculation enforces a limit of 1×10 −180 and thus all scores below this floor are given the same value (that is, 0) (Fig. 1b ) and thus length bias in e-values is non-uniform and irreversible. As bit scores do not have a threshold value, and they have been previously shown to be capable of facilitating accurate inference of phylogenetic trees [ 24 ], they were selected as the raw data for the development of a novel score transform.”concept_edges[3]
noteF-score —operationalised-as→ harmonic mean — Exact operational definition. — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”concept_edges[4]
relationF-score —operationalised-as→ harmonic mean — The F-score is the harmonic mean of precision and recall. — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”concept_edges[4]
noteshared ancestry —distinct-from→ functional conservation — Explicit non-equivalence. — “In this work we have presented OrthoFinder, a novel method for inference of orthogroups. Our method is focused on a clear definition of an orthogroup, that is, that an orthogroup contains all genes descended from a single gene in the last common ancestor of the species whose genes are being analysed. This definition avoids conflating shared ancestry with other criteria that are not equivalent, such as functional conservation. Our method is designed to address the problem of orthogroup inference rather than categorise the disparate relationships that occur between individual genes within an orthogroup. These relationships are best resolved by first inferring orthogroups using OrthoFinder and then using multiple sequence alignment and phylogenetic methods on these orthogroups.”concept_edges[5]
relationshared ancestry —distinct-from→ functional conservation — Shared ancestry is not equivalent to functional conservation. — “In this work we have presented OrthoFinder, a novel method for inference of orthogroups. Our method is focused on a clear definition of an orthogroup, that is, that an orthogroup contains all genes descended from a single gene in the last common ancestor of the species whose genes are being analysed. This definition avoids conflating shared ancestry with other criteria that are not equivalent, such as functional conservation. Our method is designed to address the problem of orthogroup inference rather than categorise the disparate relationships that occur between individual genes within an orthogroup. These relationships are best resolved by first inferring orthogroups using OrthoFinder and then using multiple sequence alignment and phylogenetic methods on these orthogroups.”concept_edges[5]
evidence status noteconcept — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”concepts[40]
evidence status noteconcept — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”concepts[41]
outcomecontrol — held — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .” — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”controls[0]
evidence status notecontrol — A FIGURE/TABLE CAPTION IS JOINED INTO THE outcome evidence QUOTE, beginning at character 403: 'Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”controls[1]
outcomecontrol — held — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .” — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”controls[1]
evidence status notecontrol — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 403: 'Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. A FIGURE/TABLE CAPTION IS JOINED INTO THE outcome evidence QUOTE, beginning at character 403: 'Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”controls[2]
outcomecontrol — held — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”controls[2]
outcomecontrol — held — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”controls[3]
evidence status notecontrol — A FIGURE/TABLE CAPTION IS JOINED INTO THE outcome evidence QUOTE, beginning at character 2651: 'Fig. 4 Memory and time requirements of OrthoFinder. Sub-samples of bet…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”controls[4]
outcomecontrol — held — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.” — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources. Fig. 4 Memory and time requirements of OrthoFinder. Sub-samples of between two and 41 plant genomes from Phytozome version 9.0 given pre-calculated BLAST results. The average number of genes per species was 30,731. a Maximum RAM requirements. b Time requirements. c The number of BLAST hits that must be processed for a given number of species (provided to place the time and RAM requirements into context)”controls[4]
outcomecontrol — held — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.” — “As OrthoFinder clustered the transcription factors together into far fewer orthogroups than OrthoMCL (897 versus 3024) we sought to demonstrate that it was correct in doing so. To do this we used gene-tree/species-tree reconciliation to determine if the orthogroups were true orthogroups if they incorrectly clustered sequences that are separated by a gene duplication event that occurred before the last common ancestor of the species in the analysis. Overall, 858 of the 897 OrthoFinder orthogroups (96 %) consisted entirely of genes that were correctly clustered together and only 39 contained some genes that were separated by a duplication prior to the last common ancestor (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of the 897 OrthoFinder orthogroups, 210 were identical to ones from OrthoMCL and 471 OrthoFinder orthogroups were strict supersets of 2,271 OrthoMCL orthogroups (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of these, 90 % (425) were true orthogroups that each encompassed on average four OrthoMCL orthogroups (1,709 in total).”controls[5]
outcomecontrol — held — “Though there is precedent for the use of L qh = L q L h to quantify the lengths of a pair of sequences that are being compared [ 14 ], different functions for gene length normalisation were also assessed. All other functions, including for example the use of the variable L ˜ q h = L q + L h in place of L qh , gave a lower overall clustering accuracy.”controls[6]
evidence status notemechanism — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”mechanisms[0]
evidence status notemechanism — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”mechanisms[7]
evidence status notemechanism — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”mechanisms[8]
evidence status notesense — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 1171: 'Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST lo…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”senses[3]
relationgene duplications → orthology — Gene duplications make orthology non-transitive and not one-to-one. — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”unhoused_relations[0]
relationgene synteny → orthogroup — Synteny assists inference only for organisms where co-linearity is conserved. — “In addition to the approaches discussed above, several methods have also been developed that incorporate gene synteny/co-linearity information to assist in the inference of orthogroups [ 16 , 17 ]. For groups of organisms such as the Kinetoplastids, where gene synteny/co-linearity is well conserved [ 18 ] it can provide valuable additional information. However, synteny is not conserved over large evolutionary distances and thus can provide little assistance to the identification of related genes between distantly related groups such as plants and metazoa. Moreover, synteny is unavailable for de novo assembled transcriptomes and for fragmented, low-coverage genome assemblies. Thus there is a need to have accurate methods of orthogroup inference that do not require gene synteny information.”unhoused_relations[1]
weightgene synteny → orthogroup — 0.7 — “In addition to the approaches discussed above, several methods have also been developed that incorporate gene synteny/co-linearity information to assist in the inference of orthogroups [ 16 , 17 ]. For groups of organisms such as the Kinetoplastids, where gene synteny/co-linearity is well conserved [ 18 ] it can provide valuable additional information. However, synteny is not conserved over large evolutionary distances and thus can provide little assistance to the identification of related genes between distantly related groups such as plants and metazoa. Moreover, synteny is unavailable for de novo assembled transcriptomes and for fragmented, low-coverage genome assemblies. Thus there is a need to have accurate methods of orthogroup inference that do not require gene synteny information.”unhoused_relations[1]
evidence status notegene length bias → recall — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 1171: 'Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST lo…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. The row's relation quote (the separate quote for the relation) repeats this quote word for word and carries the same caption at the same place. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[2]
relationgene length bias → recall — Length-biased scores reduce recovery of short genes. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[2]
weightgene length bias → recall — 0.95 — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[2]
evidence status notegene length bias → precision — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 1171: 'Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST lo…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. The row's relation quote (the separate quote for the relation) repeats this quote word for word and carries the same caption at the same place. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[3]
relationgene length bias → precision — Length-biased scores increase incorrect clustering of long genes. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[3]
weightgene length bias → precision — 0.95 — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[3]
evidence status notenovel score transform → gene length bias — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 403: 'Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption. The row's relation quote (the separate quote for the relation) repeats this quote word for word and carries the same caption at the same place. — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”unhoused_relations[4]
relationnovel score transform → gene length bias — The score transform removes gene-length dependence before clustering. — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”unhoused_relations[4]
weightnovel score transform → gene length bias — 0.95 — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”unhoused_relations[4]
relationRBNH → inclusion threshold — RBNH scores delimit a query-specific inclusion threshold. — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”unhoused_relations[5]
weightRBNH → inclusion threshold — 0.95 — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”unhoused_relations[5]
relationsparse matrices → memory — Sparse storage yields linear memory scaling across the tested species counts. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”unhoused_relations[6]
weightsparse matrices → memory — 0.95 — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”unhoused_relations[6]
relationMCL inflation parameter → precision — Changing MCL inflation trades precision against recall. — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”unhoused_relations[7]
weightMCL inflation parameter → precision — 0.95 — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”unhoused_relations[7]
relationMCL inflation parameter → recall — Changing MCL inflation trades recall against precision. — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”unhoused_relations[8]
weightMCL inflation parameter → recall — 0.95 — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”unhoused_relations[8]
relationphylogenetic distance → normalised scores — Normalisation prevents distant true orthologues from receiving systematically lower scores. — “OrthoFinder also normalises for phylogenetic distance, this is done so that the similarity scores between orthologues will be independent of phylogenetic distance (that is, the true orthologues in distantly related species will obtain similar scores to the true orthologues in closely related species). If this step is not done then true orthologues in distantly related species will always obtain lower scores than true orthologues in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologues (and cognates) will become disconnected from each other more easily than closely related true orthologues (and cognates) in the orthogroup graph. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene length information this means that short genes will always be penalised more than long genes.”unhoused_relations[9]
weightphylogenetic distance → normalised scores — 0.95 — “OrthoFinder also normalises for phylogenetic distance, this is done so that the similarity scores between orthologues will be independent of phylogenetic distance (that is, the true orthologues in distantly related species will obtain similar scores to the true orthologues in closely related species). If this step is not done then true orthologues in distantly related species will always obtain lower scores than true orthologues in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologues (and cognates) will become disconnected from each other more easily than closely related true orthologues (and cognates) in the orthogroup graph. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene length information this means that short genes will always be penalised more than long genes.”unhoused_relations[9]
relationgene-tree/species-tree reconciliation → true orthogroup — Reconciliation tests whether an inferred group crosses a pre-ancestor duplication. — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”unhoused_relations[10]
weightgene-tree/species-tree reconciliation → true orthogroup — 0.95 — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”unhoused_relations[10]
relationsingle command → OrthoFinder — Single-command execution and minimal inputs make OrthoFinder usable by independent groups. — “Inferring orthologues underpins much of modern biological research and is among the first steps in the annotation and analysis of genome and transcriptome sequencing projects. As sequencing technologies are now within the budgets of most research groups these data resources are increasing in number rapidly. Thus there is a requirement for an orthogroup inference method that is accurate, robust, scalable, and that can be run easily by independent research groups on conventional computing resources. Many orthogroup inference methods are not available for general use but are provided as static databases (for example, EggNog and TreeFam). Thus the most widely used methods are those that enable researchers to analyse their own data resources. With this in mind OrthoFinder has been developed with the aim of being easy to use. The method is executed as a single command, has minimal dependencies and requires as input just the individual protein sequence FASTA files for each species that is being clustered. The algorithm carries out all calculations (including BLAST searches and MCL clustering) and outputs the orthogroups in both a plain tab delimited text file and in the OrthoXML community format. The algorithm itself is small, fast and memory efficient, making it suitable for use on linux desktop computers. Further information about the algorithm can be found at [ 19 ] and a standalone implementation of the algorithm is available under the GPLv3 licence at [ 20 ].”unhoused_relations[11]
weightsingle command → OrthoFinder — 0.95 — “Inferring orthologues underpins much of modern biological research and is among the first steps in the annotation and analysis of genome and transcriptome sequencing projects. As sequencing technologies are now within the budgets of most research groups these data resources are increasing in number rapidly. Thus there is a requirement for an orthogroup inference method that is accurate, robust, scalable, and that can be run easily by independent research groups on conventional computing resources. Many orthogroup inference methods are not available for general use but are provided as static databases (for example, EggNog and TreeFam). Thus the most widely used methods are those that enable researchers to analyse their own data resources. With this in mind OrthoFinder has been developed with the aim of being easy to use. The method is executed as a single command, has minimal dependencies and requires as input just the individual protein sequence FASTA files for each species that is being clustered. The algorithm carries out all calculations (including BLAST searches and MCL clustering) and outputs the orthogroups in both a plain tab delimited text file and in the OrthoXML community format. The algorithm itself is small, fast and memory efficient, making it suitable for use on linux desktop computers. Further information about the algorithm can be found at [ 19 ] and a standalone implementation of the algorithm is available under the GPLv3 licence at [ 20 ].”unhoused_relations[11]
evidence status notephenomenon — A FIGURE/TABLE CAPTION IS JOINED INTO THE phenomenon evidence QUOTE, beginning at character 1171: 'Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST lo…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption.
evidence status notemethod — A FIGURE/TABLE CAPTION IS JOINED INTO THE method evidence QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption.
evidence status notecontribution — A FIGURE/TABLE CAPTION IS JOINED INTO THE contribution evidence QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption.
no type for thisgene duplications → orthology — Gene duplications make orthology non-transitive and not one-to-one. — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”unhoused_relations[0]
no type for thisgene synteny → orthogroup — Synteny assists inference only for organisms where co-linearity is conserved. — “In addition to the approaches discussed above, several methods have also been developed that incorporate gene synteny/co-linearity information to assist in the inference of orthogroups [ 16 , 17 ]. For groups of organisms such as the Kinetoplastids, where gene synteny/co-linearity is well conserved [ 18 ] it can provide valuable additional information. However, synteny is not conserved over large evolutionary distances and thus can provide little assistance to the identification of related genes between distantly related groups such as plants and metazoa. Moreover, synteny is unavailable for de novo assembled transcriptomes and for fragmented, low-coverage genome assemblies. Thus there is a need to have accurate methods of orthogroup inference that do not require gene synteny information.”unhoused_relations[1]
no type for thisgene length bias → recall — Length-biased scores reduce recovery of short genes. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[2]
no type for thisgene length bias → precision — Length-biased scores increase incorrect clustering of long genes. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes. Fig. 1 Analysis of gene length dependency of BLASTp scores. a BLAST log 10 (bit score) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-value) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scores of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-score (red), recall (blue) and precision (green) of orthogroup inference using OrthoMCL plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-score, recall and precision were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengths in Homo sapiens is provided for reference”unhoused_relations[3]
no type for thisnovel score transform → gene length bias — The score transform removes gene-length dependence before clustering. — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinder to other orthogroup inference methods. a The length dependency of OrthoMCL. b The length dependency of OrthoMCL using our normalised similarity scores. c The length dependency of the complete OrthoFinder algorithm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinder F-score with all other methods tested in OrthoBench. e As in (d) but for recall. f As in (d) but for precision. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths”unhoused_relations[4]
no type for thisRBNH → inclusion threshold — RBNH scores delimit a query-specific inclusion threshold. — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”unhoused_relations[5]
no type for thissparse matrices → memory — Sparse storage yields linear memory scaling across the tested species counts. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”unhoused_relations[6]
no type for thisMCL inflation parameter → precision — Changing MCL inflation trades precision against recall. — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”unhoused_relations[7]
no type for thisMCL inflation parameter → recall — Changing MCL inflation trades recall against precision. — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”unhoused_relations[8]
no type for thisphylogenetic distance → normalised scores — Normalisation prevents distant true orthologues from receiving systematically lower scores. — “OrthoFinder also normalises for phylogenetic distance, this is done so that the similarity scores between orthologues will be independent of phylogenetic distance (that is, the true orthologues in distantly related species will obtain similar scores to the true orthologues in closely related species). If this step is not done then true orthologues in distantly related species will always obtain lower scores than true orthologues in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologues (and cognates) will become disconnected from each other more easily than closely related true orthologues (and cognates) in the orthogroup graph. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene length information this means that short genes will always be penalised more than long genes.”unhoused_relations[9]
no type for thisgene-tree/species-tree reconciliation → true orthogroup — Reconciliation tests whether an inferred group crosses a pre-ancestor duplication. — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”unhoused_relations[10]
no type for thissingle command → OrthoFinder — Single-command execution and minimal inputs make OrthoFinder usable by independent groups. — “Inferring orthologues underpins much of modern biological research and is among the first steps in the annotation and analysis of genome and transcriptome sequencing projects. As sequencing technologies are now within the budgets of most research groups these data resources are increasing in number rapidly. Thus there is a requirement for an orthogroup inference method that is accurate, robust, scalable, and that can be run easily by independent research groups on conventional computing resources. Many orthogroup inference methods are not available for general use but are provided as static databases (for example, EggNog and TreeFam). Thus the most widely used methods are those that enable researchers to analyse their own data resources. With this in mind OrthoFinder has been developed with the aim of being easy to use. The method is executed as a single command, has minimal dependencies and requires as input just the individual protein sequence FASTA files for each species that is being clustered. The algorithm carries out all calculations (including BLAST searches and MCL clustering) and outputs the orthogroups in both a plain tab delimited text file and in the OrthoXML community format. The algorithm itself is small, fast and memory efficient, making it suitable for use on linux desktop computers. Further information about the algorithm can be found at [ 19 ] and a standalone implementation of the algorithm is available under the GPLv3 licence at [ 20 ].”unhoused_relations[11]
limitationPairwise orthology is non-transitive after gene duplication and therefore loses complete-group recall. — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”limitations[0]
limitationSynteny is unavailable for transcriptomes and fragmented assemblies and is not conserved across large evolutionary distances. — “In addition to the approaches discussed above, several methods have also been developed that incorporate gene synteny/co-linearity information to assist in the inference of orthogroups [ 16 , 17 ]. For groups of organisms such as the Kinetoplastids, where gene synteny/co-linearity is well conserved [ 18 ] it can provide valuable additional information. However, synteny is not conserved over large evolutionary distances and thus can provide little assistance to the identification of related genes between distantly related groups such as plants and metazoa. Moreover, synteny is unavailable for de novo assembled transcriptomes and for fragmented, low-coverage genome assemblies. Thus there is a need to have accurate methods of orthogroup inference that do not require gene synteny information.”limitations[1]
limitationUncorrected BLAST scores systematically disadvantage short genes and over-cluster long genes. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes.”limitations[2]
limitationBLAST e-values have an irreversible floor that makes many strong similarities indistinguishable. — “Previous methods have exploited BLAST e-values (rather than bit scores) as a measure of similarity between sequences. However, as can be seen in Fig. 1b the use of e-values for assessment of similarity between sequences is flawed. Here, the minimum e-value that can be obtained for a given query sequence decreases with increasing sequence length until, at a certain length, the lower bound for e-values is reached and BLAST returns an e-value of 0. This creates two problems: (1) long sequences will frequently have low quality hits with better e-values than the best possible hits of short sequences; and (2) the floor value for the e-value calculation means that length bias is non-uniform and thus irreversible. Specifically, beyond the floor-value e-values cannot be used to distinguish between the qualities of hits as they are all assigned the same e-value. As can be seen in the heat map shown in Fig. 1b , many hits obtain this floor-value for a given pairwise species comparison and thus their similarities are indistinguishable. This length-bias must be removed to prevent biasing downstream clustering applications.”limitations[3]
limitationOMA's low OrthoBench recall partly reflects its different target of orthologues rather than complete orthogroups. — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”limitations[4]
limitationProcessing time from precomputed BLAST results grows quadratically with the number of species. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”limitations[5]
limitationBLAST searches remain the largest computational cost and are outside the algorithmic speed comparison. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”limitations[6]
limitationOrthoFinder does not classify the individual pairwise relationships inside inferred orthogroups. — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”limitations[7]
limitationTrue negative assignments are unknown in OrthoBench, preventing use of Matthews correlation coefficient. — “OrthoBench [ 5 ] is the only manually curated dataset of orthogroups for the assessment of orthogroup prediction algorithms. It was used in this work for assessing OrthoFinder as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinder was designed to solve. Criteria such as functional similarity within orthogroups, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroup and members of the same orthogroup do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignments is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroup inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precision and recall. precision = T P T P + F P recall = T P T P + F N”limitations[8]
limitationThe real benchmark assigns only a subset of sequences to curated true families. — “OrthoBench [ 5 ] is the only manually curated dataset of orthogroups for the assessment of orthogroup prediction algorithms. It was used in this work for assessing OrthoFinder as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinder was designed to solve. Criteria such as functional similarity within orthogroups, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroup and members of the same orthogroup do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignments is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroup inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precision and recall. precision = T P T P + F P recall = T P T P + F N”limitations[9]
limitationMCL inflation changes the balance between precision and recall. — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”limitations[10]
limitationSeparate installations of BLAST+ and MCL are required. — “OrthoFinder is written in python. It requires python together with the numpy and scipy libraries [ 35 ] to be installed. OrthoFinder requires the standalone BLAST+ and MCL algorithms that are freely available. These standalone applications must be installed separately to OrthoFinder and are not included in the OrthoFinder package. The implementation makes use of sparse matrices to store hits between sequences. This provides a memory efficient method of storing the data and allows key parts of the algorithm to be expressed using scipy’s highly optimised C++ implementations of sparse matrix operations. OrthoFinder can either run the BLAST searches for you or can be run on pre-computed BLAST searches. If you chose to run BLAST searches independently then instructions are provided in the documentation for how to process your sequence names in the pre-computed BLAST output. Similarly OrthoFinder will also automatically run MCL for you. However if you wish to run MCL separately using different parameter settings then the MCL input files are stored for this purpose in a working directory.”limitations[11]
Content tags
content-observations: finding · quantity · variable · definition · key-term — grounded in the full text
findingBLAST similarity scores contain a strong gene-length dependency that biases orthogroup recovery. — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes.”content_tags.findings[0]
findingShort sequences show low recall and long sequences show low precision under uncorrected OrthoMCL clustering. — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”content_tags.findings[1]
findingThe species-pair bit-score transform removed measurable length dependence from precision, recall, and F-score. — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ).”content_tags.findings[2]
findingQuery-specific RBNH thresholds raised overall clustering accuracy while preserving gene-length independence. — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”content_tags.findings[3]
findingOrthoFinder achieved precision 0.85, recall 0.81, and F-score 0.83 on OrthoBench. — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”content_tags.findings[4]
findingOrthoFinder outperformed TreeFam, OrthoMCL, and OMA by 8, 25, and 33 percent in F-score, respectively. — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”content_tags.findings[5]
findingBalanced precision and recall indicated neither systematic over-clustering nor under-clustering. — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”content_tags.findings[6]
findingOrthoFinder outperformed comparators for both difficult and randomly selected OrthoBench groups. — “In addition to accuracy, a number of other criteria were used to compare the performance of the different inference methods in the OrthoBench paper. These criteria included the percentage of orthogroups predicted without any errors, the number of erroneously assigned genes (that is, false positives, and thus also captured by the precision) and missing genes (that is, false negatives, and thus also captured by recall) in the assignment of genes to orthogroups and the proportion of orthogroups affected by these false positive and false negatives. The results for OrthoFinder according to these criteria are reported in Additional file 3 : Figure S2 and are consistent with the increased accuracy of OrthoFinder compared to other methods. Additionally, the 70 orthogroups that make up the OrthoBench dataset comprise 40 that represent particular biological or technical challenges and 30 randomly chosen orthogroups. Additional file 4 : Figure S3 shows the F-scores for these two categories separately to illustrate the difference in performance of the method for ‘randomly selected’ and ‘difficult’ orthogroups. OrthoFinder outperformed all other methods in both categories and achieved an F-score of 81 % and 90 % on the difficult and randomly selected orthogroups, respectively.”content_tags.findings[7]
findingF-score stayed above 0.75 after random deletion of 60 percent of input genes. — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”content_tags.findings[8]
findingOrthoFinder processed 12 species and 235,033 sequences in 14 minutes 20 seconds versus 20 hours 12 minutes for OrthoMCL. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.findings[9]
findingMemory scaled linearly and processing time quadratically with species count when starting from BLAST scores. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.findings[10]
findingForty-one plant genomes required about 4 GB of RAM and three hours on one CPU core. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.findings[11]
findingExtrapolation suggested roughly 450 plant-sized genomes could be clustered with 64 GB of RAM. — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources. Fig. 4 Memory and time requirements of OrthoFinder. Sub-samples of between two and 41 plant genomes from Phytozome version 9.0 given pre-calculated BLAST results. The average number of genes per species was 30,731. a Maximum RAM requirements. b Time requirements. c The number of BLAST hits that must be processed for a given number of species (provided to place the time and RAM requirements into context)”content_tags.findings[12]
evidence status notefinding — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 2651: 'Fig. 4 Memory and time requirements of OrthoFinder. Sub-samples of bet…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption.content_tags.findings[12]
findingOrthoFinder placed 97.6 percent of plant transcription factors in orthogroups versus 89.1 percent for OrthoMCL. — “Using established rules for the identification and classification of transcription factors [ 31 ] we identified and typed all of the transcription factors present in the 41 genomes present in Phytozome v9. The complete predicted proteomes from these 41 genomes were then subject to clustering using OrthoFinder and OrthoMCL and the distribution of transcription factors in the resultant orthogroups were analysed. OrthoMCL was used here as it is the method by which all transcription factor families are currently classified [ 31 ]. Consistent with the increased recall rate for OrthoFinder, analysis of the resulting orthogroups revealed that 8.5 % more transcription factors were placed in orthogroups using OrthoFinder than OrthoMCL (Fig. 5a , 97.6 % and 89.1 %, respectively, n = 52,744). Also consistent with the increased recall rate is that these orthogroups were less fragmented than those that were produced by OrthoMCL (Fig. 5b , 897 and 3,024 orthogroups, respectively). Importantly, the orthogroups inferred using OrthoFinder were missing fewer RBHs (Fig. 5c , 2.15 % and 5.77 %, respectively) and clustered more of the same type of transcription factor together (Fig. 5d and e ). A major difference between those orthogroups inferred using OrthoFinder and OrthoMCL is that those produced by OrthoFinder encompass a larger number of species than those recovered by OrthoMCL (Fig. 5f ), thus orthogroups produced by OrthoFinder encompass greater phylogenetic distances.”content_tags.findings[13]
findingOrthoFinder produced 897 less-fragmented transcription-factor orthogroups versus 3,024 from OrthoMCL. — “Using established rules for the identification and classification of transcription factors [ 31 ] we identified and typed all of the transcription factors present in the 41 genomes present in Phytozome v9. The complete predicted proteomes from these 41 genomes were then subject to clustering using OrthoFinder and OrthoMCL and the distribution of transcription factors in the resultant orthogroups were analysed. OrthoMCL was used here as it is the method by which all transcription factor families are currently classified [ 31 ]. Consistent with the increased recall rate for OrthoFinder, analysis of the resulting orthogroups revealed that 8.5 % more transcription factors were placed in orthogroups using OrthoFinder than OrthoMCL (Fig. 5a , 97.6 % and 89.1 %, respectively, n = 52,744). Also consistent with the increased recall rate is that these orthogroups were less fragmented than those that were produced by OrthoMCL (Fig. 5b , 897 and 3,024 orthogroups, respectively). Importantly, the orthogroups inferred using OrthoFinder were missing fewer RBHs (Fig. 5c , 2.15 % and 5.77 %, respectively) and clustered more of the same type of transcription factor together (Fig. 5d and e ). A major difference between those orthogroups inferred using OrthoFinder and OrthoMCL is that those produced by OrthoFinder encompass a larger number of species than those recovered by OrthoMCL (Fig. 5f ), thus orthogroups produced by OrthoFinder encompass greater phylogenetic distances.”content_tags.findings[14]
findingGene-tree/species-tree reconciliation found 96 percent of the OrthoFinder transcription-factor groups entirely correct. — “As OrthoFinder clustered the transcription factors together into far fewer orthogroups than OrthoMCL (897 versus 3024) we sought to demonstrate that it was correct in doing so. To do this we used gene-tree/species-tree reconciliation to determine if the orthogroups were true orthogroups if they incorrectly clustered sequences that are separated by a gene duplication event that occurred before the last common ancestor of the species in the analysis. Overall, 858 of the 897 OrthoFinder orthogroups (96 %) consisted entirely of genes that were correctly clustered together and only 39 contained some genes that were separated by a duplication prior to the last common ancestor (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of the 897 OrthoFinder orthogroups, 210 were identical to ones from OrthoMCL and 471 OrthoFinder orthogroups were strict supersets of 2,271 OrthoMCL orthogroups (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of these, 90 % (425) were true orthogroups that each encompassed on average four OrthoMCL orthogroups (1,709 in total).”content_tags.findings[15]
findingOrthoFinder united eight paraphyletic OrthoMCL groups for the type IVc bHLH family and recovered 36 previously unclustered genes. — “An illustrated example showing an OrthoFinder orthogroup and its constituent OrthoMCL orthogroups is provided in Fig. 6 . Here the OrthoFinder orthogroup (labelled bHLH 8 in Additional file 6 : Table S2) contains all known type IVc bHLH transcription factors [ 32 ]. Type IVc bHLH transcription factors have previously been shown to be conserved from green algae to land plants and thus span the complete taxonomic range contained in this analysis [ 32 ]. The OrthoFinder orthogroup correctly united eight paraphyletic OrthoMCL orthogroups and included 36 transcription factors (highlighted in grey) that were not clustered into any orthogroups by OrthoMCL (Fig. 6 ). The phylogenetic tree shows that there are no genes present in this OrthoFinder orthogroup that were the product of a gene duplication event prior to the divergence of the last common ancestor of all species in the analysis. This is only one example and the complete set of phylogenetic trees for each OrthoFinder transcription factor orthogroup are provided in Additional file 6 : Table S2 along with the OrthoMCL subsets that comprise these groups where appropriate. Also contained in this table are the results of the gene-tree/species-tree reconciliation for each tree inferred from an OrthoFinder orthogroup.”content_tags.findings[16]
findingThe plant analysis yielded 687 novel orthogroups and 6.9 million relationships not detected by OrthoMCL. — “Taken together, using OrthoFinder to cluster transcription factor genes resulted in the identification 687 (897 less the 210 that were the same) novel orthogroups of transcription factors across 41 different species comprising 7.7 million pairwise relationships (of which 6.9 million are not detected by OrthoMCL). Thus using OrthoFinder to cluster transcription factors has provided significant new insight into the relationship of transcription factor genes across plants. The number of orthogroups for each transcription factor type is provided in Fig. 5g and the full classification including all constituent accession numbers is provided in Additional file 6 : Table S2.”content_tags.findings[17]
findingF-score was relatively stable across MCL inflation settings, while the setting could trade precision against recall. — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”content_tags.findings[18]
findingThe method is scalable and robust to missing genes typical of incomplete genomes and de novo transcriptomes. — “The two key novel features of our method are: (1) a method to automatically remove gene length bias and phylogenetic distance from sequence similarity scores; and (2) a novel method to define the sequence similarity limits of an orthogroup. In the tests performed on the only publicly available orthogroup benchmark dataset (OrthoBench) OrthoFinder outperformed all of the commonly used orthogroup assignment methods by between 8 % and 33 %. Moreover we have shown OrthoFinder to be scalable and robust to missing genes typical of incomplete genomes and de novo transcriptome assemblies. The software is freely available and can take pre-computed BLAST scores as input making it easy to test on any newly developed benchmarks for which pre-computed BLAST scores are available.”content_tags.findings[19]
quantity8 % to 33 % — OrthoFinder accuracy advantage over other inference methods — “Identifying homology relationships between sequences is fundamental to biological research. Here we provide a novel orthogroup inference algorithm called OrthoFinder that solves a previously undetected gene length bias in orthogroup inference, resulting in significant improvements in accuracy. Using real benchmark datasets we demonstrate that OrthoFinder is more accurate than other orthogroup inference methods by between 8 % and 33 %. Furthermore, we demonstrate the utility of OrthoFinder by providing a complete classification of transcription factor gene families in plants revealing 6.9 million previously unobserved relationships.”content_tags.quantities[0]
quantity6.9 million — previously unobserved plant transcription-factor relationships — “Identifying homology relationships between sequences is fundamental to biological research. Here we provide a novel orthogroup inference algorithm called OrthoFinder that solves a previously undetected gene length bias in orthogroup inference, resulting in significant improvements in accuracy. Using real benchmark datasets we demonstrate that OrthoFinder is more accurate than other orthogroup inference methods by between 8 % and 33 %. Furthermore, we demonstrate the utility of OrthoFinder by providing a complete classification of transcription factor gene families in plants revealing 6.9 million previously unobserved relationships.”content_tags.quantities[1]
quantity70 orthogroups — manually curated groups in OrthoBench — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”content_tags.quantities[2]
quantity12 species — Metazoan breadth of OrthoBench — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”content_tags.quantities[3]
quantitytop 5 % — best hits retained per length bin for score-model fitting — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”content_tags.quantities[4]
quantity0.85 — OrthoFinder precision on OrthoBench — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”content_tags.quantities[5]
quantity0.81 — OrthoFinder recall on OrthoBench — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”content_tags.quantities[6]
quantity0.83 — OrthoFinder F-score on OrthoBench — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”content_tags.quantities[7]
quantity60 % — largest random gene deletion fraction in the incomplete-data test — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”content_tags.quantities[8]
quantityover 0.75 — F-score retained with 60 percent missing genes — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”content_tags.quantities[9]
quantity235,033 sequences — OrthoBench scale in the runtime comparison — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.quantities[10]
quantity14 min 20 s — OrthoFinder runtime for precomputed OrthoBench scores — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.quantities[11]
quantity20 h 12 min — OrthoMCL runtime for the same operation and CPU — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.quantities[12]
quantity41 — plant genomes in the scalability and transcription-factor analyses — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.quantities[13]
quantity52,744 — putative transcription factors compared — “Using established rules for the identification and classification of transcription factors [ 31 ] we identified and typed all of the transcription factors present in the 41 genomes present in Phytozome v9. The complete predicted proteomes from these 41 genomes were then subject to clustering using OrthoFinder and OrthoMCL and the distribution of transcription factors in the resultant orthogroups were analysed. OrthoMCL was used here as it is the method by which all transcription factor families are currently classified [ 31 ]. Consistent with the increased recall rate for OrthoFinder, analysis of the resulting orthogroups revealed that 8.5 % more transcription factors were placed in orthogroups using OrthoFinder than OrthoMCL (Fig. 5a , 97.6 % and 89.1 %, respectively, n = 52,744). Also consistent with the increased recall rate is that these orthogroups were less fragmented than those that were produced by OrthoMCL (Fig. 5b , 897 and 3,024 orthogroups, respectively). Importantly, the orthogroups inferred using OrthoFinder were missing fewer RBHs (Fig. 5c , 2.15 % and 5.77 %, respectively) and clustered more of the same type of transcription factor together (Fig. 5d and e ). A major difference between those orthogroups inferred using OrthoFinder and OrthoMCL is that those produced by OrthoFinder encompass a larger number of species than those recovered by OrthoMCL (Fig. 5f ), thus orthogroups produced by OrthoFinder encompass greater phylogenetic distances.”content_tags.quantities[14]
quantity96 % — OrthoFinder transcription-factor groups entirely correct by reconciliation — “As OrthoFinder clustered the transcription factors together into far fewer orthogroups than OrthoMCL (897 versus 3024) we sought to demonstrate that it was correct in doing so. To do this we used gene-tree/species-tree reconciliation to determine if the orthogroups were true orthogroups if they incorrectly clustered sequences that are separated by a gene duplication event that occurred before the last common ancestor of the species in the analysis. Overall, 858 of the 897 OrthoFinder orthogroups (96 %) consisted entirely of genes that were correctly clustered together and only 39 contained some genes that were separated by a duplication prior to the last common ancestor (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of the 897 OrthoFinder orthogroups, 210 were identical to ones from OrthoMCL and 471 OrthoFinder orthogroups were strict supersets of 2,271 OrthoMCL orthogroups (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of these, 90 % (425) were true orthogroups that each encompassed on average four OrthoMCL orthogroups (1,709 in total).”content_tags.quantities[15]
quantity1.5 — default MCL inflation parameter — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”content_tags.quantities[16]
variablegene length (bias dimension and normalisation input) — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes.”content_tags.variables[0]
variableBLAST bit score (raw and transformed sequence similarity measure) — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”content_tags.variables[1]
variablephylogenetic distance (between-species similarity confound normalised out) — “OrthoFinder also normalises for phylogenetic distance, this is done so that the similarity scores between orthologues will be independent of phylogenetic distance (that is, the true orthologues in distantly related species will obtain similar scores to the true orthologues in closely related species). If this step is not done then true orthologues in distantly related species will always obtain lower scores than true orthologues in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologues (and cognates) will become disconnected from each other more easily than closely related true orthologues (and cognates) in the orthogroup graph. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene length information this means that short genes will always be penalised more than long genes.”content_tags.variables[2]
variableprecision (incorrect-inclusion performance outcome) — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”content_tags.variables[3]
variablerecall (missing-member performance outcome) — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”content_tags.variables[4]
variableF-score (balanced primary benchmark outcome) — “Given that OrthoFinder exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroup inference. OrthoFinder outperformed all other methods that have been applied to OrthoBench [ 5 ] as measured by F-score (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCL (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precision and recall of OrthoFinder were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recall in this test as its goal is to identify orthologues instead of complete orthogroups and thus paralogues will be absent from the orthologue groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBench analysis [ 5 ].”content_tags.variables[5]
variablemissing genes (incomplete-dataset robustness manipulation) — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”content_tags.variables[6]
variablenumber of species (computational scaling input) — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.variables[7]
variablememory (linear computational resource outcome) — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.variables[8]
variabletime requirements (quadratic processing outcome after BLAST) — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”content_tags.variables[9]
variableMCL inflation parameter (precision-recall tradeoff setting) — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”content_tags.variables[10]
definitionorthogroup — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”content_tags.definitions[0]
definitionorthologues — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”content_tags.definitions[1]
definitionwithin-species paralogues — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”content_tags.definitions[2]
definitionRBNH — “Given that we had reduced gene length bias and that precision was high but recall was low, we assessed whether a method that could identify a higher proportion of cognate gene-pairs prior to clustering could produce an overall increase in clustering accuracy. Many orthology assignment methods make use of reciprocal best BLAST hit (RBH) as it is widely regarded as a high precision method for the identification of orthologues gene-pairs [ 25 – 27 ]. Therefore we also sought to use reciprocal best BLAST hits using our new length-normalised score to assist in construction of the orthogroup graph. Henceforth, we refer to a reciprocal best hit that is obtained using the length-normalised score as an RBNH (reciprocal best normalised hit).”content_tags.definitions[3]
definitionputative cognate gene-pair — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”content_tags.definitions[4]
evidence status notedefinition — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption.content_tags.definitions[4]
definitionorthogroup graph — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”content_tags.definitions[5]
evidence status notedefinition — A FIGURE/TABLE CAPTION IS JOINED INTO THE 'evidence' QUOTE, beginning at character 122: 'Fig. 7 Overview of the steps in the OrthoFinder algorithm for two exam…'. The page prints the caption apart from the paragraph; read the quote as the paragraph, then the caption.content_tags.definitions[5]
definitionprecision — “OrthoBench [ 5 ] is the only manually curated dataset of orthogroups for the assessment of orthogroup prediction algorithms. It was used in this work for assessing OrthoFinder as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinder was designed to solve. Criteria such as functional similarity within orthogroups, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroup and members of the same orthogroup do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignments is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroup inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precision and recall. precision = T P T P + F P recall = T P T P + F N”content_tags.definitions[6]
definitionrecall — “OrthoBench [ 5 ] is the only manually curated dataset of orthogroups for the assessment of orthogroup prediction algorithms. It was used in this work for assessing OrthoFinder as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinder was designed to solve. Criteria such as functional similarity within orthogroups, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroup and members of the same orthogroup do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignments is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroup inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precision and recall. precision = T P T P + F P recall = T P T P + F N”content_tags.definitions[7]
definitionF-score — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”content_tags.definitions[8]
definitiontranscription factor orthogroup — “To infer transcription factor orthogroups we first identified the set of transcription factors present in all genomes present in Phytozome V9. This identification was performed using the same rules for the presence and absence of PFAM domains as has been previously described [ 31 ]. The full set of protein coding genes from these genomes (including all the transcription factors) was then clustered using OrthoFinder and OrthoMCL and the distribution of the transcription factors within these orthogroups was analysed. OrthoMCL was selected for comparison here as it is the method by which all orthogroups of transcription factors are currently defined [ 31 ]. An orthogroup of transcription factors was defined as an orthogroup whose constituent genes comprised ≥50 % transcription factors of the same domain classification.”content_tags.definitions[9]
definitiontrue orthogroup — “To determine if OrthoFinder was correct in combining multiple separate OrthoMCL orthogroups each orthogroup was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinder had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroup by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroup was considered not to be a true orthogroup as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.”content_tags.definitions[10]
Concepts
terms this paper carries, each with the sentence it was cut from — the layer that joins one paper to another. Terms with no quote yet are on CONCEPTS.html.
concepthomology relationships — not defined in this paper's own words; shared evolutionary relationships among sequences — “Identifying homology relationships between sequences is fundamental to all aspects of biological research. In addition to the pivotal role these inferences play in furthering our understanding of the evolution and diversity of life, they also provide a coherent framework for the extrapolation of biological knowledge between organisms. In this context, orthology inference underpins genome and transcriptome annotation and provides the foundation on which synthetic and systems biology is built. Given the importance of this process to biological research there has been a rich heritage of methodology development in this area with the production of several effective orthology databases and algorithms.”concepts[0]
conceptorthology inference — not defined in this paper's own words; identification of cross-species gene relationships — “Identifying homology relationships between sequences is fundamental to all aspects of biological research. In addition to the pivotal role these inferences play in furthering our understanding of the evolution and diversity of life, they also provide a coherent framework for the extrapolation of biological knowledge between organisms. In this context, orthology inference underpins genome and transcriptome annotation and provides the foundation on which synthetic and systems biology is built. Given the importance of this process to biological research there has been a rich heritage of methodology development in this area with the production of several effective orthology databases and algorithms.”concepts[1]
conceptgenome and transcriptome annotation — not defined in this paper's own words; downstream use of inferred orthology — “Identifying homology relationships between sequences is fundamental to all aspects of biological research. In addition to the pivotal role these inferences play in furthering our understanding of the evolution and diversity of life, they also provide a coherent framework for the extrapolation of biological knowledge between organisms. In this context, orthology inference underpins genome and transcriptome annotation and provides the foundation on which synthetic and systems biology is built. Given the importance of this process to biological research there has been a rich heritage of methodology development in this area with the production of several effective orthology databases and algorithms.”concepts[2]
conceptpairwise relationships — not defined in this paper's own words; gene-to-gene relationships inferred across two species — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”concepts[3]
conceptgene duplications — not defined in this paper's own words; events that create non-one-to-one orthology — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”concepts[4]
conceptorthology — not defined in this paper's own words; descent relation between genes across species — “The most widely used methods for orthology inference can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationships between genes in two species, and then extending orthology to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologue. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplications cause orthology relationships that are not one-to-one [ 3 ] and so orthology is not a transitive relationship (for example, if gene A is an orthologue of gene B, and gene B is an orthologue of gene C, it is not necessarily true that gene A is an orthologue of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthology relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precision in recovering orthologues, however, they suffer from low rates of recall in discovering the complete orthogroup due to these complications arising from gene duplications.”concepts[5]
conceptorthogroup — not defined in this paper's own words; all descendants of one ancestral gene across the species considered — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”concepts[6]
conceptset of genes derived from a single gene in the last common ancestor — not defined in this paper's own words; categorical extension of an orthogroup — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”concepts[7]
conceptorthologues — not defined in this paper's own words; cross-species descendants of one ancestral gene — “There are two common problem definitions used by the majority of homology inference algorithms. One is to predict pairs of orthologues (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paralogues (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinder, is to predict orthogroups. An orthogroup is the set of genes derived from a single gene in the last common ancestor of all the species under consideration. This is the approach used by OrthoMCL [ 13 ] and eggNOG [ 34 ]. OrthoFinder follows this second approach to produce orthogroups of protein coding genes as this is a logical extension of orthology to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.”concepts[8]
conceptparalogues — not defined in this paper's own words; within-lineage descendants separated by duplication — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”concepts[9]
conceptOrthoMCL — not defined in this paper's own words; BLAST plus MCL orthogroup comparator — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”concepts[10]
conceptBLAST — not defined in this paper's own words; pairwise sequence search and scoring — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”concepts[11]
conceptMCL clustering algorithm — not defined in this paper's own words; graph clustering used for orthogroups — “The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroups; an orthogroup is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroup by definition contains both orthologues and paralogues, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthology to multiple species. The most widely used orthogroup inference method is OrthoMCL [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCL uses BLAST [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.”concepts[12]
conceptgene synteny — not defined in this paper's own words; co-linear genomic context used by some methods — “In addition to the approaches discussed above, several methods have also been developed that incorporate gene synteny/co-linearity information to assist in the inference of orthogroups [ 16 , 17 ]. For groups of organisms such as the Kinetoplastids, where gene synteny/co-linearity is well conserved [ 18 ] it can provide valuable additional information. However, synteny is not conserved over large evolutionary distances and thus can provide little assistance to the identification of related genes between distantly related groups such as plants and metazoa. Moreover, synteny is unavailable for de novo assembled transcriptomes and for fragmented, low-coverage genome assemblies. Thus there is a need to have accurate methods of orthogroup inference that do not require gene synteny information.”concepts[13]
conceptOrthoFinder — not defined in this paper's own words; normalised-score graph algorithm for orthogroups — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”concepts[14]
conceptgene length bias — not defined in this paper's own words; score and clustering dependency on sequence length — “Identifying homology relationships between sequences is fundamental to biological research. Here we provide a novel orthogroup inference algorithm called OrthoFinder that solves a previously undetected gene length bias in orthogroup inference, resulting in significant improvements in accuracy. Using real benchmark datasets we demonstrate that OrthoFinder is more accurate than other orthogroup inference methods by between 8 % and 33 %. Furthermore, we demonstrate the utility of OrthoFinder by providing a complete classification of transcription factor gene families in plants revealing 6.9 million previously unobserved relationships.”concepts[15]
conceptBLAST scores — not defined in this paper's own words; raw similarity scores with length dependence — “The inference of orthogroups across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLAST [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologue identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scores that are produced when the full set of protein sequences from one species is BLAST searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scores or low e-values (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroups by evaluation of BLAST scores in the absence of gene length information should result in a large number of missing genes (low recall) from orthogroups that contain short genes and a large number of incorrectly clustered genes (low precision) in orthogroups that contain long genes.”concepts[16]
conceptbit scores — not defined in this paper's own words; unfloored BLAST similarity values — “Given that orthogroup inference shows a clear gene length dependency, we sought to develop a transform of the BLAST scores that would reduce the impact of gene length on clustering accuracy. To do this we developed a novel method that determines the gene length dependency of a given pairwise species comparison from an analysis of the bit scores from an all-versus-all BLAST search between the two species. Bit scores were used in place of e-values as the e-value calculation enforces a limit of 1×10 −180 and thus all scores below this floor are given the same value (that is, 0) (Fig. 1b ) and thus length bias in e-values is non-uniform and irreversible. As bit scores do not have a threshold value, and they have been previously shown to be capable of facilitating accurate inference of phylogenetic trees [ 24 ], they were selected as the raw data for the development of a novel score transform.”concepts[17]
concepte-values — not defined in this paper's own words; thresholded BLAST significance values — “Given that orthogroup inference shows a clear gene length dependency, we sought to develop a transform of the BLAST scores that would reduce the impact of gene length on clustering accuracy. To do this we developed a novel method that determines the gene length dependency of a given pairwise species comparison from an analysis of the bit scores from an all-versus-all BLAST search between the two species. Bit scores were used in place of e-values as the e-value calculation enforces a limit of 1×10 −180 and thus all scores below this floor are given the same value (that is, 0) (Fig. 1b ) and thus length bias in e-values is non-uniform and irreversible. As bit scores do not have a threshold value, and they have been previously shown to be capable of facilitating accurate inference of phylogenetic trees [ 24 ], they were selected as the raw data for the development of a novel score transform.”concepts[18]
conceptOrthoBench — not defined in this paper's own words; manually curated orthogroup benchmark — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”concepts[19]
conceptrecall — not defined in this paper's own words; recovery of true orthogroup assignments — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”concepts[20]
conceptprecision — not defined in this paper's own words; correctness of included orthogroup assignments — “To determine if this was the case we assessed the performance of OrthoMCL using the OrthoBench dataset [ 5 ]. OrthoBench is the only publicly available benchmark dataset of manually curated orthogroups. The dataset consists of 70 orthogroups of protein coding genes covering 12 species within the Metazoa where each orthogroup contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroup see [ 5 ]. The recall and precision of OrthoMCL was assessed as a function of gene length in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCL and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recall rate (that is, many short sequences fail to be assigned to an orthogroup) and long sequences suffer from low precision (that is, many long sequences are assigned to the incorrect orthogroup) as predicted from the analysis of BLAST scores above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .”concepts[21]
conceptnovel score transform — not defined in this paper's own words; species-pair length and distance normalisation — “Application of this novel score transform prior to clustering of the OrthoBench dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCL (Fig. 3a ), neither precision, recall nor F-score displayed any dependency on gene length (Fig. 3b ). Moreover, precision was substantially increased over the entire range of sequence lengths (Fig. 3b ).”concepts[22]
conceptnormalised scores — not defined in this paper's own words; bias-corrected input to clustering — “In brief, for each species-pair in turn, the all-vs-all BLAST hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hits in each bin (ranked according to BLAST bit score) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scores that were obtained from each species-pair all-vs-all BLAST search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scores is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distance between species (See ‘ Gene length and phylogenetic distance normalisation ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distance normalised scores were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed.”concepts[23]
conceptreciprocal best BLAST hit — not defined in this paper's own words; high-precision pairwise orthologue signal — “Given that we had reduced gene length bias and that precision was high but recall was low, we assessed whether a method that could identify a higher proportion of cognate gene-pairs prior to clustering could produce an overall increase in clustering accuracy. Many orthology assignment methods make use of reciprocal best BLAST hit (RBH) as it is widely regarded as a high precision method for the identification of orthologues gene-pairs [ 25 – 27 ]. Therefore we also sought to use reciprocal best BLAST hits using our new length-normalised score to assist in construction of the orthogroup graph. Henceforth, we refer to a reciprocal best hit that is obtained using the length-normalised score as an RBNH (reciprocal best normalised hit).”concepts[24]
conceptRBNH — reciprocal best normalised hit — “Given that we had reduced gene length bias and that precision was high but recall was low, we assessed whether a method that could identify a higher proportion of cognate gene-pairs prior to clustering could produce an overall increase in clustering accuracy. Many orthology assignment methods make use of reciprocal best BLAST hit (RBH) as it is widely regarded as a high precision method for the identification of orthologues gene-pairs [ 25 – 27 ]. Therefore we also sought to use reciprocal best BLAST hits using our new length-normalised score to assist in construction of the orthogroup graph. Henceforth, we refer to a reciprocal best hit that is obtained using the length-normalised score as an RBNH (reciprocal best normalised hit).”concepts[25]
conceptinclusion threshold — not defined in this paper's own words; query-specific minimum cognate similarity — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”concepts[26]
conceptorthogroup graph — not defined in this paper's own words; weighted graph of genes and cognate pairs — “In brief, for each gene that had successfully identified one or more RBNHs, the scores for these RBNHs were used to delimit an inclusion threshold (see methods). As all scores are normalised for gene length and phylogenetic distance, hits to other genes (in any species) that had scores above this inclusion threshold were included as putative cognate gene-pairs and added to the orthogroup graph that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene length independence (Fig. 3c ). The overall results for OrthoFinder, were 0.85 precision, 0.81 recall and 0.83 F-score.”concepts[27]
conceptF-score — not defined in this paper's own words; harmonic balance of precision and recall — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”concepts[28]
conceptharmonic mean — not defined in this paper's own words; aggregation weighting the worse performance measure — “Where TP is the number of true positive orthogroup assignments (that is, correct assignments), FP is the number of false positive orthogroup assignments (that is, incorrect assignments) and FN is the number of false negative orthologue assignments (that is, missing assignments). The F-score is the harmonic mean of these two measures, where the harmonic mean weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBench analysis in Additional file 3 : Figure S2.”concepts[29]
conceptincomplete datasets — not defined in this paper's own words; inputs missing genes from assembly or prediction — “As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genes due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinder for analysing these incomplete datasets we assessed the performance of OrthoFinder with between 5 % and 60 % of genes deleted at random from the OrthoBench input sequences. This revealed that the accuracy of OrthoFinder is robust to missing data and that it achieved an F-score of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinder is suitable for orthogroup inference from partial and incomplete datasets.”concepts[30]
conceptsparse matrices — not defined in this paper's own words; central scalable hit-storage structure — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”concepts[31]
conceptmatrix operations — not defined in this paper's own words; optimized calculations on sparse hits — “The number of species for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroups using these datasets as they emerge. To keep pace with these increasing demands the algorithm utilises sparse matrices as the central data structure and performs many steps using matrix operations. For example, starting from pre-computed raw BLAST scores the identification of orthogroups for the OrthoBench dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinder on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCL takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinder, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinder. The memory (RAM) requirements increase linearly with the number of species clustered (Fig. 4a ). This is despite the fact that the number of BLAST hits increases quadratically with the number of species (Fig. 4c ). This linear scaling is achieved by processing the BLAST hits for each species sequentially and independently within OrthoFinder. Though the memory requirements increase linearly, the time requirements starting from pre-computed raw BLAST scores increases quadratically with the number of species (Fig. 4b ). This is to be expected as the number of BLAST hits that must be processed also increases quadratically. For example, identifying the orthogroups for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinder is capable of large analyses on conventional computing resources. It should be noted here that the BLAST searches incur the largest computational cost in any orthogroup inference analysis and that this cost is the same for all inference methods that use BLAST. In summary OrthoFinder is fast and scalable to hundreds of species on conventional computing resources.”concepts[32]
concepttranscription factors — not defined in this paper's own words; short duplication-rich plant regulatory genes — “Given that OrthoFinder has increased accuracy over other methods and that gene length bias has been eliminated from orthogroup inference, we sought to provide an additional demonstration of the utility of OrthoFinder for the inference of orthogroups. To do this we selected plant transcription factors as they are short genes and will thus suffer from low rates of recall in assignment to orthogroups in the absence of gene length bias correction. Moreover transcription factor genes are preferentially retained following whole genome duplication events [ 29 , 30 ] and thus transcription factor orthogroups are larger than average and contain multiple independent duplication events in multiple independent lineages that can cause some inference methods to fail. Finally, previous efforts to define transcription factor orthogroups have utilised OrthoMCL [ 31 ]. Thus current transcription factor orthogroups will have low recall resulting in fragmented orthogroups spanning few species.”concepts[33]
conceptwhole genome duplication events — not defined in this paper's own words; events preferentially retaining transcription factors — “Given that OrthoFinder has increased accuracy over other methods and that gene length bias has been eliminated from orthogroup inference, we sought to provide an additional demonstration of the utility of OrthoFinder for the inference of orthogroups. To do this we selected plant transcription factors as they are short genes and will thus suffer from low rates of recall in assignment to orthogroups in the absence of gene length bias correction. Moreover transcription factor genes are preferentially retained following whole genome duplication events [ 29 , 30 ] and thus transcription factor orthogroups are larger than average and contain multiple independent duplication events in multiple independent lineages that can cause some inference methods to fail. Finally, previous efforts to define transcription factor orthogroups have utilised OrthoMCL [ 31 ]. Thus current transcription factor orthogroups will have low recall resulting in fragmented orthogroups spanning few species.”concepts[34]
conceptgene-tree/species-tree reconciliation — not defined in this paper's own words; test of pre-ancestor duplications in groups — “As OrthoFinder clustered the transcription factors together into far fewer orthogroups than OrthoMCL (897 versus 3024) we sought to demonstrate that it was correct in doing so. To do this we used gene-tree/species-tree reconciliation to determine if the orthogroups were true orthogroups if they incorrectly clustered sequences that are separated by a gene duplication event that occurred before the last common ancestor of the species in the analysis. Overall, 858 of the 897 OrthoFinder orthogroups (96 %) consisted entirely of genes that were correctly clustered together and only 39 contained some genes that were separated by a duplication prior to the last common ancestor (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of the 897 OrthoFinder orthogroups, 210 were identical to ones from OrthoMCL and 471 OrthoFinder orthogroups were strict supersets of 2,271 OrthoMCL orthogroups (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of these, 90 % (425) were true orthogroups that each encompassed on average four OrthoMCL orthogroups (1,709 in total).”concepts[35]
concepttype IVc bHLH transcription factors — not defined in this paper's own words; plant regulator family used as an example — “An illustrated example showing an OrthoFinder orthogroup and its constituent OrthoMCL orthogroups is provided in Fig. 6 . Here the OrthoFinder orthogroup (labelled bHLH 8 in Additional file 6 : Table S2) contains all known type IVc bHLH transcription factors [ 32 ]. Type IVc bHLH transcription factors have previously been shown to be conserved from green algae to land plants and thus span the complete taxonomic range contained in this analysis [ 32 ]. The OrthoFinder orthogroup correctly united eight paraphyletic OrthoMCL orthogroups and included 36 transcription factors (highlighted in grey) that were not clustered into any orthogroups by OrthoMCL (Fig. 6 ). The phylogenetic tree shows that there are no genes present in this OrthoFinder orthogroup that were the product of a gene duplication event prior to the divergence of the last common ancestor of all species in the analysis. This is only one example and the complete set of phylogenetic trees for each OrthoFinder transcription factor orthogroup are provided in Additional file 6 : Table S2 along with the OrthoMCL subsets that comprise these groups where appropriate. Also contained in this table are the results of the gene-tree/species-tree reconciliation for each tree inferred from an OrthoFinder orthogroup.”concepts[36]
conceptalgorithm — not defined in this paper's own words; five-phase multi-species orthogroup procedure — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”concepts[37]
conceptprotein sequence FASTA file — not defined in this paper's own words; one-species input file — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”concepts[38]
conceptOrthoXML — not defined in this paper's own words; community-standard orthogroup output format — “OrthoFinder is an algorithm that infers orthogroups across multiple species. The method does not classify the pairwise relationships that exist between genes within these orthogroups. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinder is run with a single command and requires as input a directory containing one protein sequence FASTA file per species to be clustered. OrthoFinder does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroups in two file formats: the Quest for Orthologs community standard OrthoXML [ 33 ] and in plain text format with one orthogroup per line.”concepts[39]
conceptputative cognate gene-pairs — not defined in this paper's own words; candidate same-orthogroup sequence pairs — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”concepts[40]
conceptgene length and phylogenetic distance normalisation — not defined in this paper's own words; bias correction of BLAST bit scores — “An overview of the algorithm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinder algorithm for two example orthogroups of genes from three species. a The unknown orthogroups that the algorithm must recover, shown as a gene tree. b BLAST search of all genes against all genes. c Gene length and phylogenetic distance normalisation of BLAST bit scores to give the scores to be used for orthogroup inference. d Selection of putative cognate gene-pairs from normalised BLAST scores. e Construction of orthogroup graph, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit score. f Clustering of genes into discrete orthogroups using MCL BLAST all-versus-all search (Fig. 7b ). Protein BLAST (blastp) with an e-value threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisation of the BLAST bit scores (Fig. 7c ). This step models the all-vs-all BLAST hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene length and phylogenetic distance. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distance. Delimitation of orthogroup sequence similarity thresholds using RBNHs (Fig. 7d ). This step uses information from RBNHs (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graph a gene-pair must be an RBNH or produce a hit that is better scoring than the lowest scoring RBNH (irrespective of species) for either gene. Constructing an orthogroup graph for input into MCL (Fig. 7e ). Putative cognate gene-pairs are identified as above and are connected in the orthogroup graph with weights given by the normalised BLAST bit scores. Clustering of genes into orthogroups using MCL (Fig. 7f ) .”concepts[41]
conceptphylogenetic distance — not defined in this paper's own words; between-species divergence affecting scores — “OrthoFinder also normalises for phylogenetic distance, this is done so that the similarity scores between orthologues will be independent of phylogenetic distance (that is, the true orthologues in distantly related species will obtain similar scores to the true orthologues in closely related species). If this step is not done then true orthologues in distantly related species will always obtain lower scores than true orthologues in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologues (and cognates) will become disconnected from each other more easily than closely related true orthologues (and cognates) in the orthogroup graph. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene length information this means that short genes will always be penalised more than long genes.”concepts[42]
conceptsimilarity measure — not defined in this paper's own words; normalised bit-score comparison between sequences — “In this method we construct a similarity measure between sequences based on the bit-score normalised to take into account the query and hit sequences lengths and the phylogenetic distance between species. Unlike e-values, the bit-scores do not suffer from the presence of a threshold limit and thus different amounts of sequence similarity can be distinguished regardless of the lengths of the sequences involved. Let L q be the length of the query sequence and L h be the length of the hit sequence. In an analogous manner to the e-value calculation made by BLAST and other sequence comparison methods, we use the variable L qh = L q L h to quantify the lengths of a pair of sequences that are being compared.”concepts[43]
concepttop 5 % of hits — not defined in this paper's own words; high-scoring length-bin sample for fitting — “The top 5 % of hits are used rather than RBHs as selection of RBHs will be affected by the gene length-bias that we wish to correct. Moreover, gene duplication events can frequently cause RBHs to fail (Additional file 8 : Figure S5) and thus reduce the number of data points that are available for fitting. The normalisation procedure ensures that the best hits between a given species pair achieve (on average) the same scores irrespective of their gene length.”concepts[44]
conceptmost dissimilar RBNH — not defined in this paper's own words; query-specific cutoff-setting reciprocal hit — “The rationale for this approach is that the level of normalised similarity of a query gene and its RBNHs can be used to estimate the extent of similarity of other genes within the same orthogroup. All genes more similar to a query gene than any of the query gene’s RBNHs (irrespective of species) are likely members of the same orthogroup. Therefore, the normalised similarity score for the most dissimilar RBNH of a gene is used as a cutoff for inclusion of additional cognate gene-pairs from all species. That is q is connected to h in the orthogroup graph if B ' qh > B ' qR where R is an RBNH of q. This provides a simple and robust method for recovering cognate gene-pairs that may otherwise be difficult to detect due to duplication events that can cause the RBNH method to fail. Further details, explanation and worked examples are provided in Additional file 8 : Figure S5.”concepts[45]
conceptMCL inflation parameter — not defined in this paper's own words; clustering granularity and precision-recall control — “In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroup. This orthogroup graph is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameter on the OrthoFinder result is shown in Additional file 9 : Figure S6. The F-score of OrthoFinder is relatively stable to variation in MCL inflation parameter, however it is possible to trade precision against recall by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).”concepts[46]
conceptsparse matrix operations — not defined in this paper's own words; optimized implementation calculations — “OrthoFinder is written in python. It requires python together with the numpy and scipy libraries [ 35 ] to be installed. OrthoFinder requires the standalone BLAST+ and MCL algorithms that are freely available. These standalone applications must be installed separately to OrthoFinder and are not included in the OrthoFinder package. The implementation makes use of sparse matrices to store hits between sequences. This provides a memory efficient method of storing the data and allows key parts of the algorithm to be expressed using scipy’s highly optimised C++ implementations of sparse matrix operations. OrthoFinder can either run the BLAST searches for you or can be run on pre-computed BLAST searches. If you chose to run BLAST searches independently then instructions are provided in the documentation for how to process your sequence names in the pre-computed BLAST output. Similarly OrthoFinder will also automatically run MCL for you. However if you wish to run MCL separately using different parameter settings then the MCL input files are stored for this purpose in a working directory.”concepts[47]
concepttrue negative orthologue assignments — not defined in this paper's own words; unknown benchmark outcome needed for correlation coefficient — “OrthoBench [ 5 ] is the only manually curated dataset of orthogroups for the assessment of orthogroup prediction algorithms. It was used in this work for assessing OrthoFinder as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinder was designed to solve. Criteria such as functional similarity within orthogroups, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroup and members of the same orthogroup do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignments is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroup inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precision and recall. precision = T P T P + F P recall = T P T P + F N”concepts[48]
concepttranscription factor orthogroups — not defined in this paper's own words; groups dominated by one regulator domain class — “To infer transcription factor orthogroups we first identified the set of transcription factors present in all genomes present in Phytozome V9. This identification was performed using the same rules for the presence and absence of PFAM domains as has been previously described [ 31 ]. The full set of protein coding genes from these genomes (including all the transcription factors) was then clustered using OrthoFinder and OrthoMCL and the distribution of the transcription factors within these orthogroups was analysed. OrthoMCL was selected for comparison here as it is the method by which all orthogroups of transcription factors are currently defined [ 31 ]. An orthogroup of transcription factors was defined as an orthogroup whose constituent genes comprised ≥50 % transcription factors of the same domain classification.”concepts[49]
conceptshared ancestry — not defined in this paper's own words; ancestral descent basis of orthogroups — “In this work we have presented OrthoFinder, a novel method for inference of orthogroups. Our method is focused on a clear definition of an orthogroup, that is, that an orthogroup contains all genes descended from a single gene in the last common ancestor of the species whose genes are being analysed. This definition avoids conflating shared ancestry with other criteria that are not equivalent, such as functional conservation. Our method is designed to address the problem of orthogroup inference rather than categorise the disparate relationships that occur between individual genes within an orthogroup. These relationships are best resolved by first inferring orthogroups using OrthoFinder and then using multiple sequence alignment and phylogenetic methods on these orthogroups.”concepts[50]
conceptfunctional conservation — not defined in this paper's own words; function retention not equivalent to shared ancestry — “In this work we have presented OrthoFinder, a novel method for inference of orthogroups. Our method is focused on a clear definition of an orthogroup, that is, that an orthogroup contains all genes descended from a single gene in the last common ancestor of the species whose genes are being analysed. This definition avoids conflating shared ancestry with other criteria that are not equivalent, such as functional conservation. Our method is designed to address the problem of orthogroup inference rather than categorise the disparate relationships that occur between individual genes within an orthogroup. These relationships are best resolved by first inferring orthogroups using OrthoFinder and then using multiple sequence alignment and phylogenetic methods on these orthogroups.”concepts[51]
conceptsingle command — not defined in this paper's own words; minimal user-facing execution interface — “Inferring orthologues underpins much of modern biological research and is among the first steps in the annotation and analysis of genome and transcriptome sequencing projects. As sequencing technologies are now within the budgets of most research groups these data resources are increasing in number rapidly. Thus there is a requirement for an orthogroup inference method that is accurate, robust, scalable, and that can be run easily by independent research groups on conventional computing resources. Many orthogroup inference methods are not available for general use but are provided as static databases (for example, EggNog and TreeFam). Thus the most widely used methods are those that enable researchers to analyse their own data resources. With this in mind OrthoFinder has been developed with the aim of being easy to use. The method is executed as a single command, has minimal dependencies and requires as input just the individual protein sequence FASTA files for each species that is being clustered. The algorithm carries out all calculations (including BLAST searches and MCL clustering) and outputs the orthogroups in both a plain tab delimited text file and in the OrthoXML community format. The algorithm itself is small, fast and memory efficient, making it suitable for use on linux desktop computers. Further information about the algorithm can be found at [ 19 ] and a standalone implementation of the algorithm is available under the GPLv3 licence at [ 20 ].”concepts[52]

Full text — tagged

The reference list is not part of the text we hold for this paper. Our copy was extracted from the publisher's page and the bibliography did not survive that extraction, so the article below ends before its references. Nothing has been removed by us.

OrthoFinderterm: solving fundamental biases in whole genome comparisons dramatically improves orthogroupterm inference accuracy Abstract Identifying homology relationshipsterm between sequences is fundamental to biological research. Here we provide a novel orthogroupterm inference algorithmterm called OrthoFinderterm that solves a previously undetected gene length biasterm in orthogroupterm inference, resulting in significant improvements in accuracy. Using real benchmark datasets we demonstrate that OrthoFinderterm is more accurate than other orthogroupterm inference methods by between 8 % and 33 %. Furthermore, we demonstrate the utility of OrthoFinderterm by providing a complete classification of transcription factorterm gene families in plants revealing 6.9 million previously unobserved relationships.

The online version of this article (doi:10.1186/s13059-015-0721-2) contains supplementary material, which is available to authorized users.

Background and rationale Identifying homology relationshipsterm between sequences is fundamental to all aspects of biological research. In addition to the pivotal role these inferences play in furthering our understanding of the evolution and diversity of life, they also provide a coherent framework for the extrapolation of biological knowledge between organisms. In this context, orthology inferenceterm underpins genome and transcriptome annotationterm and provides the foundation on which synthetic and systems biology is built. Given the importance of this process to biological research there has been a rich heritage of methodology development in this area with the production of several effective orthologyterm databases and algorithmsterm.

The most widely used methods for orthology inferenceterm can be classified into two distinct groups. One group of methods approaches the problem by inferring pairwise relationshipsterm between genes in two species, and then extending orthologyterm to multiple species by identifying sets of genes spanning these species in which each gene-pair is an orthologueterm. Popular methods that adopt this approach include MultiParanoid [ 1 ] and OMA [ 2 ]. A confounding factor to these approaches is that gene duplicationsterm cause orthologyterm relationships that are not one-to-one [ 3 ] and so orthologyterm is not a transitive relationship (for example, if gene A is an orthologueterm of gene B, and gene B is an orthologueterm of gene C, it is not necessarily true that gene A is an orthologueterm of gene C) [ 4 ]. This lack of transitivity means that to capture all pairwise orthologyterm relationships individual genes must be allowed to be members of more than one set [ 2 ], or the gene sets must be restricted to subsets of species that share the same last common ancestor [ 1 ]. Methods that adopt these pairwise approaches have high levels of precisionterm in recovering orthologuesterm, however, they suffer from low rates of recallterm in discovering the complete orthogroupterm due to these complications arising from gene duplicationsterm.

The second group of methods do not adopt this pairwise strategy but rather attempt to identify complete orthogroupsterm; an orthogroupterm is the set of genes that are descended from a single gene in the last common ancestor of all the species being considered [ 2 , 5 – 9 ]. Here an orthogroupterm by definition contains both orthologuesterm and paraloguesterm, and in this context is frequently used as a unit of comparison for comparative genomics [ 10 – 12 ]. In this work we follow this latter approach as it is a logical extension of orthologyterm to multiple species. The most widely used orthogroupterm inference method is OrthoMCLterm [ 13 ] (usage assessed by citations n = 870 Scopus citations at the time of writing this article). OrthoMCLterm uses BLASTterm [ 14 ] to compute sequence similarity scores between sequences in multiple species and then uses the MCL clustering algorithmterm [ 15 ] to identify highly-connected clusters (groups of highly similar sequences) within this dataset.

In addition to the approaches discussed above, several methods have also been developed that incorporate gene syntenyterm/co-linearity information to assist in the inference of orthogroupsterm [ 16 , 17 ]. For groups of organisms such as the Kinetoplastids, where gene syntenyterm/co-linearity is well conserved [ 18 ] it can provide valuable additional information. However, synteny is not conserved over large evolutionary distances and thus can provide little assistance to the identification of related genes between distantly related groups such as plants and metazoa. Moreover, synteny is unavailable for de novo assembled transcriptomes and for fragmented, low-coverage genome assemblies. Thus there is a need to have accurate methods of orthogroupterm inference that do not require gene syntenyterm information.

Here we present OrthoFinderterm, a novel method that infers orthogroupsterm of protein coding genes. It is fast, easy to use and scalable to thousands of genomes. In tests using real benchmark datasets OrthoFinderterm outperforms all other commonly used orthogroupterm inference methods by between 8 % and 33 %. We further demonstrate the utility of OrthoFinderterm through the inference and analysis of plant transcription factor orthogroupsterm. Here we use phylogenetic methods to validate the orthogroupsterm and show that using OrthoFinderterm to infer orthogroupsterm identifies millions of previously unobserved relationships. Further information about the algorithmterm can be found at [ 19 ] and a standalone implementation of the algorithmterm is available under the GPLv3 licence at [ 20 ].

Problem definition, method evaluation and comparison to other approaches Gene length biasterm in BLAST scoresterm affects the accuracy of orthogroupterm detection The inference of orthogroupsterm across multiple species requires a fast method to measure pairwise sequence similarity between all sequences in the species being considered. BLASTterm [ 14 ] is the most widely used method to identify and measure similarity between sequences and thus it underpins the majority of orthologueterm identification methods [ 9 , 13 , 21 – 23 ]. Analysis of the pairwise BLAST scoresterm that are produced when the full set of protein sequences from one species is BLASTterm searched against those from another species revealed that there is a clear length dependency in the scores that are obtained (Fig. 1a and b ). Short sequences cannot produce large bit scoresterm or low e-valuesterm (Fig. 1a and b , respectively), whereas long sequences produce many hits with scores better than those for the best hits of short sequences (Fig. 1a and b ). Thus, methods that construct orthogroupsterm by evaluation of BLAST scoresterm in the absence of gene lengthterm·var information should result in a large number of missing genesterm·var (low recallterm) from orthogroupsterm that contain short genes and a large number of incorrectly clustered genes (low precisionterm) in orthogroupsterm that contain long genes. Fig. 1 Analysis of gene lengthterm·var dependency of BLASTp scores. a BLASTterm log 10 (bit scoreterm) for all hits between Homo sapiens (Homo_sapiens.GRCh37.60.pep.all, 21,841 sequences) and Mus musculus (Mus_musculus.NCBIM37.60.pep.all, 23,111 sequences) . b –log 10 (e-valueterm) for all hits between and Homo sapiens and Mus musculus . To avoid infinite values, BLAST scoresterm of zero have been replaced with the lowest obtainable value 10 −180 . The heat map in both cases goes from blue (lowest density of hits) to red (highest). c The F-scoreterm (red), recallterm (blue) and precisionterm (green) of orthogroupterm inference using OrthoMCLterm plotted as a function of sequence length. The sequences were sorted according to length and divided into four bins with the same number of sequences in each. The F-scoreterm, recallterm and precisionterm were calculated for each bin and the scores plotted against the geometric mean of the length of the sequences in each bin. The error bars show the lower and upper limits of sequence lengths for the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths. d Histogram of all protein-coding gene lengthsterm·var in Homo sapiens is provided for reference To determine if this was the case we assessed the performance of OrthoMCLterm using the OrthoBenchterm dataset [ 5 ]. OrthoBenchterm is the only publicly available benchmark dataset of manually curated orthogroupsterm. The dataset consists of 70 orthogroupsterm of protein coding genes covering 12 species within the Metazoa where each orthogroupterm contains all the genes derived from a single gene in the last common ancestor of the 12 species considered. For further details concerning the construction, species range and complexity of each orthogroupterm see [ 5 ]. The recallterm and precisionterm of OrthoMCLterm was assessed as a function of gene lengthterm·var in this dataset. This revealed that there were strong dependencies between the performance characteristics of OrthoMCLterm and the length of the gene that was being clustered (Fig. 1c , Additional file 1 : Table S1). Specifically, short sequences suffer from low recallterm rate (that is, many short sequences fail to be assigned to an orthogroupterm) and long sequences suffer from low precisionterm (that is, many long sequences are assigned to the incorrect orthogroupterm) as predicted from the analysis of BLAST scoresterm above. To put these results in perspective the distribution of protein lengths in Homo sapiens is provided in Fig. 1d .

A novel score transformterm eliminates gene length biasterm in orthogroupterm detection Given that orthogroupterm inference shows a clear gene lengthterm·var dependency, we sought to develop a transform of the BLAST scoresterm that would reduce the impact of gene lengthterm·var on clustering accuracy. To do this we developed a novel method that determines the gene lengthterm·var dependency of a given pairwise species comparison from an analysis of the bit scoresterm from an all-versus-all BLASTterm search between the two species. Bit scoresterm were used in place of e-valuesterm as the e-valueterm calculation enforces a limit of 1×10 −180 and thus all scores below this floor are given the same value (that is, 0) (Fig. 1b ) and thus length bias in e-valuesterm is non-uniform and irreversible. As bit scoresterm do not have a threshold value, and they have been previously shown to be capable of facilitating accurate inference of phylogenetic trees [ 24 ], they were selected as the raw data for the development of a novel score transformterm.

In brief, for each species-pair in turn, the all-vs-all BLASTterm hits (Fig. 2a ) were divided into equal sized bins of increasing sequence length according to the product of the query and hit sequence lengths. The top 5 % of hitsterm in each bin (ranked according to BLAST bit scoreterm·var) were used to represent ‘good’ hits for sequences of that length bin between the given species pair (Fig. 2b ). A linear model in log-log space was used to fit a line to these scores using least squares fitting (Fig. 2b ). All of the BLAST bit scoresterm·var that were obtained from each species-pair all-vs-all BLASTterm search are then transformed using this model so that the best hits between sequences in this species pair have equivalent scores that are independent of sequence length (Fig. 2c and d ). Following the transform the poor quality hits for longer sequences were no longer better than the best quality hits for short sequences (Fig. 2c ). This normalisation procedure is applied to each pairwise species comparison independently as the behaviour of the BLAST scoresterm is different for each pairwise species comparison (Additional file 2 : Figure S1). Importantly, this pairwise length normalisation between species also normalises for phylogenetic distanceterm between species (See ‘ Gene length and phylogenetic distance normalisationterm ’ & Additional file 2 : Figure S1). Specifically, the normalisation ensures that the best scoring hits between distantly related species achieve the same scores (on average) to the best scoring hits between closely related species (Additional file 2 : Figure S1). These length and phylogenetic distanceterm normalised scoresterm were then used as the measure of sequence similarity on which all subsequent analysis and clustering were performed. Fig. 2 The gene length and phylogenetic distance normalisationterm procedure for a single species pair. a BLAST bit scoresterm·var for all hits between Homo sapiens and Mus musculus . b BLAST bit scoresterm·var for the top 5 % of BLASTterm hits with least-squares fit of the equation log 10 B qh = a log 10 L qh + b ., where B qh is the bit scoreterm for the hit between sequence q and sequence h and L qh is the product of the gene lengthsterm·var (measured in amino acids). c Gene lengthterm·var and phylogenetic distanceterm normalised BLAST bit scoresterm·var. Note that there are a large number of poor scoring hits for long sequences due to these hits exceeding the BLASTterm search e-valueterm cutoff. d The same top 5 % of BLASTterm hits as shown in (b) after normalisation for reference Application of this novel score transformterm prior to clustering of the OrthoBenchterm dataset resulted in a dramatic reduction in the length dependency of the clustering results (Fig. 3 ). Unlike OrthoMCLterm (Fig. 3a ), neither precisionterm, recallterm nor F-scoreterm displayed any dependency on gene lengthterm·var (Fig. 3b ). Moreover, precisionterm was substantially increased over the entire range of sequence lengths (Fig. 3b ). Fig. 3 Comparison of OrthoFinderterm to other orthogroupterm inference methods. a The length dependency of OrthoMCLterm. b The length dependency of OrthoMCLterm using our normalised similarity scores. c The length dependency of the complete OrthoFinderterm algorithmterm. For A-C scores were calculated as in Fig. 1c . d Comparison of the results of OrthoFinderterm F-scoreterm with all other methods tested in OrthoBenchterm. e As in (d) but for recallterm. f As in (d) but for precisionterm. The error bars show the lower and upper limits of sequence lengths corresponding to the shortest and longest sequences in each bin and the dot shows the geometric mean of these lengths An improved method for orthogroupterm delimitation improves overall accuracy Given that we had reduced gene length biasterm and that precisionterm was high but recallterm was low, we assessed whether a method that could identify a higher proportion of cognate gene-pairs prior to clustering could produce an overall increase in clustering accuracy. Many orthologyterm assignment methods make use of reciprocal best BLAST hitterm (RBH) as it is widely regarded as a high precisionterm method for the identification of orthologuesterm gene-pairs [ 25 – 27 ]. Therefore we also sought to use reciprocal best BLAST hitsterm using our new length-normalised score to assist in construction of the orthogroup graphterm. Henceforth, we refer to a reciprocal best hit that is obtained using the length-normalised score as an RBNHterm (reciprocal best normalised hit).

In brief, for each gene that had successfully identified one or more RBNHsterm, the scores for these RBNHsterm were used to delimit an inclusion thresholdterm (see methods). As all scores are normalised for gene lengthterm·var and phylogenetic distanceterm, hits to other genes (in any species) that had scores above this inclusion thresholdterm were included as putative cognate gene-pairsterm and added to the orthogroup graphterm that was subjected to MCL clustering (for further details see methods). This novel data selection criterion resulted in a dramatic improvement in overall clustering accuracy while maintaining gene lengthterm·var independence (Fig. 3c ). The overall results for OrthoFinderterm, were 0.85 precisionterm, 0.81 recallterm and 0.83 F-scoreterm.

OrthoFinderterm outperforms all other methods from the OrthoBenchterm analysis Given that OrthoFinderterm exhibited high accuracy on the benchmark dataset we sought to determine the relative performance to other commonly used methods for orthogroupterm inference. OrthoFinderterm outperformed all other methods that have been applied to OrthoBenchterm [ 5 ] as measured by F-scoreterm (Fig. 3d ), performing 8 % better than TreeFam (the next best method) 25 % better than OrthoMCLterm (the most widely used method), and 33 % better than OMA (the lowest scoring method in this test). Importantly, the precisionterm and recallterm of OrthoFinderterm were balanced, demonstrating that the method is not biased towards over- or under-clustering of sequences. It should be noted that OMA exhibits a low recallterm in this test as its goal is to identify orthologuesterm instead of complete orthogroupsterm and thus paraloguesterm will be absent from the orthologueterm groups identified by this method. OMA is included here for completeness as it was included in the original OrthoBenchterm analysis [ 5 ].

In addition to accuracy, a number of other criteria were used to compare the performance of the different inference methods in the OrthoBenchterm paper. These criteria included the percentage of orthogroupsterm predicted without any errors, the number of erroneously assigned genes (that is, false positives, and thus also captured by the precisionterm) and missing genesterm·var (that is, false negatives, and thus also captured by recallterm) in the assignment of genes to orthogroupsterm and the proportion of orthogroupsterm affected by these false positive and false negatives. The results for OrthoFinderterm according to these criteria are reported in Additional file 3 : Figure S2 and are consistent with the increased accuracy of OrthoFinderterm compared to other methods. Additionally, the 70 orthogroupsterm that make up the OrthoBenchterm dataset comprise 40 that represent particular biological or technical challenges and 30 randomly chosen orthogroupsterm. Additional file 4 : Figure S3 shows the F-scoresterm for these two categories separately to illustrate the difference in performance of the method for ‘randomly selected’ and ‘difficult’ orthogroupsterm. OrthoFinderterm outperformed all other methods in both categories and achieved an F-scoreterm of 81 % and 90 % on the difficult and randomly selected orthogroupsterm, respectively.

OrthoFinderterm is suitable for the analysis of incomplete datasetsterm As many research groups are producing partial genome assemblies and transcriptome resources it is to be expected that sequence datasets will be missing genesterm·var due to incomplete assembly, low expression or errors in gene prediction. To demonstrate the suitability of OrthoFinderterm for analysing these incomplete datasetsterm we assessed the performance of OrthoFinderterm with between 5 % and 60 % of genes deleted at random from the OrthoBenchterm input sequences. This revealed that the accuracy of OrthoFinderterm is robust to missing data and that it achieved an F-scoreterm of over of 0.75 even when 60 % of the genes were missing from the input dataset (Additional file 5 : Figure S4). Thus OrthoFinderterm is suitable for orthogroupterm inference from partial and incomplete datasetsterm.

OrthoFinderterm is fast and scalable The number of speciesterm·var for which genome or transcriptome sequence resources are available is increasing rapidly and there is a corresponding need to be able to infer orthogroupsterm using these datasets as they emerge. To keep pace with these increasing demands the algorithmterm utilises sparse matricesterm as the central data structure and performs many steps using matrix operationsterm. For example, starting from pre-computed raw BLAST scoresterm the identification of orthogroupsterm for the OrthoBenchterm dataset (12 species, 235,033 sequences) takes 14 min 20 s using OrthoFinderterm on a single core of an Intel Core i7-4770 3.4GHz CPU. For comparison, OrthoMCLterm takes 20 h 12 min to perform the same operation using the same CPU and MySQL for its relational database management system. As the number of genomes that must be analysed increases, the scalability of the methods used becomes increasingly important. To demonstrate the scalability performance of OrthoFinderterm, the full set of sequenced plant genomes from Phytozome version 9.0 (n = 41 [ 28 ]) were clustered and the results are shown in Fig. 4 . Plant genomes were selected for this test as they are large with an average of 30,731 protein coding genes per species in Phytozome version 9.0 and thus they represent a stringent assessment of the scalability of OrthoFinderterm. The memoryterm·var (RAM) requirements increase linearly with the number of speciesterm·var clustered (Fig. 4a ). This is despite the fact that the number of BLASTterm hits increases quadratically with the number of speciesterm·var (Fig. 4c ). This linear scaling is achieved by processing the BLASTterm hits for each species sequentially and independently within OrthoFinderterm. Though the memoryterm·var requirements increase linearly, the time requirementsterm·var starting from pre-computed raw BLAST scoresterm increases quadratically with the number of speciesterm·var (Fig. 4b ). This is to be expected as the number of BLASTterm hits that must be processed also increases quadratically. For example, identifying the orthogroupsterm for all 41 plant species from Phytozome requires approximately 4 GB of RAM and took approximately 3 h on a single CPU core. Fitting the data to a line and extrapolating we estimate that approximately 450 plant sized genomes can be clustered on a linux computer with 64GB of RAM (Fig. 4a ). Thus OrthoFinderterm is capable of large analyses on conventional computing resources. It should be noted here that the BLASTterm searches incur the largest computational cost in any orthogroupterm inference analysis and that this cost is the same for all inference methods that use BLASTterm. In summary OrthoFinderterm is fast and scalable to hundreds of species on conventional computing resources. Fig. 4 Memoryterm·var and time requirementsterm·var of OrthoFinderterm. Sub-samples of between two and 41 plant genomes from Phytozome version 9.0 given pre-calculated BLASTterm results. The average number of genes per species was 30,731. a Maximum RAM requirements. b Time requirementsterm·var. c The number of BLASTterm hits that must be processed for a given number of speciesterm·var (provided to place the time and RAM requirements into context) Inference of high accuracy plant transcription factor orthogroupsterm Given that OrthoFinderterm has increased accuracy over other methods and that gene length biasterm has been eliminated from orthogroupterm inference, we sought to provide an additional demonstration of the utility of OrthoFinderterm for the inference of orthogroupsterm. To do this we selected plant transcription factorsterm as they are short genes and will thus suffer from low rates of recallterm in assignment to orthogroupsterm in the absence of gene length biasterm correction. Moreover transcription factorterm genes are preferentially retained following whole genome duplication eventsterm [ 29 , 30 ] and thus transcription factor orthogroupsterm are larger than average and contain multiple independent duplication events in multiple independent lineages that can cause some inference methods to fail. Finally, previous efforts to define transcription factor orthogroupsterm have utilised OrthoMCLterm [ 31 ]. Thus current transcription factor orthogroupsterm will have low recallterm resulting in fragmented orthogroupsterm spanning few species.

Using established rules for the identification and classification of transcription factorsterm [ 31 ] we identified and typed all of the transcription factorsterm present in the 41 genomes present in Phytozome v9. The complete predicted proteomes from these 41 genomes were then subject to clustering using OrthoFinderterm and OrthoMCLterm and the distribution of transcription factorsterm in the resultant orthogroupsterm were analysed. OrthoMCLterm was used here as it is the method by which all transcription factorterm families are currently classified [ 31 ]. Consistent with the increased recallterm rate for OrthoFinderterm, analysis of the resulting orthogroupsterm revealed that 8.5 % more transcription factorsterm were placed in orthogroupsterm using OrthoFinderterm than OrthoMCLterm (Fig. 5a , 97.6 % and 89.1 %, respectively, n = 52,744). Also consistent with the increased recallterm rate is that these orthogroupsterm were less fragmented than those that were produced by OrthoMCLterm (Fig. 5b , 897 and 3,024 orthogroupsterm, respectively). Importantly, the orthogroupsterm inferred using OrthoFinderterm were missing fewer RBHs (Fig. 5c , 2.15 % and 5.77 %, respectively) and clustered more of the same type of transcription factorterm together (Fig. 5d and e ). A major difference between those orthogroupsterm inferred using OrthoFinderterm and OrthoMCLterm is that those produced by OrthoFinderterm encompass a larger number of speciesterm·var than those recovered by OrthoMCLterm (Fig. 5f ), thus orthogroupsterm produced by OrthoFinderterm encompass greater phylogenetic distancesterm. Fig. 5 Inference of orthogroupsterm of plant transcription factorsterm. In all cases dark grey bars indicate the results for OrthoFinderterm and light grey bars indicate the results for OrthoMCLterm. a Comparison of the fraction of transcription factorsterm that are assigned to orthogroupsterm by OrthoFinderterm and by OrthoMCLterm. b Comparison of the number of transcription factor orthogroupsterm identified using each method. c The percentage of RBNHterm/RBH (for OrthoFinderterm/OrthoMCLterm) hits that are not contained in orthogroupsterm identified using each method. d The number of transcription factorsterm of the same type that each transcription factorterm is connected to in the orthogroupsterm produced by OrthoFinderterm. e as in (d) but for OrthoMCLterm. f Comparison of species coverage for transcription factor orthogroupsterm identified by each method. g The number of orthogroupsterm for each transcription factorterm type identified by OrthoFinderterm As OrthoFinderterm clustered the transcription factorsterm together into far fewer orthogroupsterm than OrthoMCLterm (897 versus 3024) we sought to demonstrate that it was correct in doing so. To do this we used gene-tree/species-tree reconciliationterm to determine if the orthogroupsterm were true orthogroupsterm·def if they incorrectly clustered sequences that are separated by a gene duplicationterm event that occurred before the last common ancestor of the species in the analysis. Overall, 858 of the 897 OrthoFinderterm orthogroupsterm (96 %) consisted entirely of genes that were correctly clustered together and only 39 contained some genes that were separated by a duplication prior to the last common ancestor (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of the 897 OrthoFinderterm orthogroupsterm, 210 were identical to ones from OrthoMCLterm and 471 OrthoFinderterm orthogroupsterm were strict supersets of 2,271 OrthoMCLterm orthogroupsterm (Additional file 6 : Table S2 and Additional file 7 : Table S3). Of these, 90 % (425) were true orthogroupsterm·def that each encompassed on average four OrthoMCLterm orthogroupsterm (1,709 in total).

An illustrated example showing an OrthoFinderterm orthogroupterm and its constituent OrthoMCLterm orthogroupsterm is provided in Fig. 6 . Here the OrthoFinderterm orthogroupterm (labelled bHLH 8 in Additional file 6 : Table S2) contains all known type IVc bHLH transcription factorsterm [ 32 ]. Type IVc bHLH transcription factorsterm have previously been shown to be conserved from green algae to land plants and thus span the complete taxonomic range contained in this analysis [ 32 ]. The OrthoFinderterm orthogroupterm correctly united eight paraphyletic OrthoMCLterm orthogroupsterm and included 36 transcription factorsterm (highlighted in grey) that were not clustered into any orthogroupsterm by OrthoMCLterm (Fig. 6 ). The phylogenetic tree shows that there are no genes present in this OrthoFinderterm orthogroupterm that were the product of a gene duplicationterm event prior to the divergence of the last common ancestor of all species in the analysis. This is only one example and the complete set of phylogenetic trees for each OrthoFinderterm transcription factor orthogroupterm·def are provided in Additional file 6 : Table S2 along with the OrthoMCLterm subsets that comprise these groups where appropriate. Also contained in this table are the results of the gene-tree/species-tree reconciliationterm for each tree inferred from an OrthoFinderterm orthogroupterm. Fig. 6 A bootstrapped maximum likelihood phylogenetic tree of the OrthoFinderterm orthogroupterm containing the type IVc bHLH transcription factorsterm (bHLH 8). The OrthoMCLterm orthogroupsterm that are subsets of the OrthoFinderterm orthogroupterm are indicated by different coloured fonts. Thirty-six of the OrthoFinderterm clustered genes (coloured grey) failed to be clustered in any OrthoMCLterm orthogroupterm. The tree was inferred using RAxML using the PROTGAMMAAUTO model (the JTT was model was selected as having the highest likelihood) with 100 bootstrap replicates. Scale bar indicates the number of substitutions per site. Percentage bootstrap support values are indicated by coloured circles shown at internal nodes Taken together, using OrthoFinderterm to cluster transcription factorterm genes resulted in the identification 687 (897 less the 210 that were the same) novel orthogroupsterm of transcription factorsterm across 41 different species comprising 7.7 million pairwise relationshipsterm (of which 6.9 million are not detected by OrthoMCLterm). Thus using OrthoFinderterm to cluster transcription factorsterm has provided significant new insight into the relationship of transcription factorterm genes across plants. The number of orthogroupsterm for each transcription factorterm type is provided in Fig. 5g and the full classification including all constituent accession numbers is provided in Additional file 6 : Table S2.

Algorithmterm implementation and evaluation criteria OrthoFinderterm is an algorithmterm that infers orthogroupsterm across multiple species. The method does not classify the pairwise relationshipsterm that exist between genes within these orthogroupsterm. The method does not require synteny information and is thus equally suitable for clustering protein sequences predicted from genome or transcriptome datasets. OrthoFinderterm is run with a single commandterm and requires as input a directory containing one protein sequence FASTA fileterm per species to be clustered. OrthoFinderterm does not require preprocessing of FASTA files (such as filtering of sequences) and does not require knowledge or use of any relational database management system such as MySQL. It outputs orthogroupsterm in two file formats: the Quest for Orthologs community standard OrthoXMLterm [ 33 ] and in plain text format with one orthogroupterm per line.

There are two common problem definitions used by the majority of homology inference algorithmsterm. One is to predict pairs of orthologuesterm (pairs of genes from two different species descendent from a single gene in the last common ancestor of the two species) and pairs of recent, within-species paraloguesterm·def (genes-pairs arising from a duplication event since the last speciation event for that species). The other approach, and the one used here for OrthoFinderterm, is to predict orthogroupsterm. An orthogroupterm is the set of genes derived from a single gene in the last common ancestorterm of all the species under consideration. This is the approach used by OrthoMCLterm [ 13 ] and eggNOG [ 34 ]. OrthoFinderterm follows this second approach to produce orthogroupsterm of protein coding genes as this is a logical extension of orthologyterm to multiple species as it groups all genes descended from a single gene in the last common ancestor of all species being considered.

Methodological overview of the OrthoFinderterm algorithmterm An overview of the algorithmterm in shown in Fig. 7 , it proceeds in five phases corresponding to sections b-f in the figure: Fig. 7 Overview of the steps in the OrthoFinderterm algorithmterm for two example orthogroupsterm of genes from three species. a The unknown orthogroupsterm that the algorithmterm must recover, shown as a gene tree. b BLASTterm search of all genes against all genes. c Gene length and phylogenetic distance normalisationterm of BLAST bit scoresterm·var to give the scores to be used for orthogroupterm inference. d Selection of putative cognate gene-pairsterm from normalised BLAST scoresterm. e Construction of orthogroup graphterm, genes are nodes in the graph and pairs of genes are connected by an edge with edge weights given by the normalised bit scoreterm. f Clustering of genes into discrete orthogroupsterm using MCL BLASTterm all-versus-all search (Fig. 7b ). Protein BLASTterm (blastp) with an e-valueterm threshold of 10 −3 is used so as to avoid discarding putative good hits for very short sequences. A relaxed threshold is used at this stage of the method as subsequent steps filter out false positive hits using stringent, orthogroup-specific criteria for inclusion (described below). Gene length and phylogenetic distance normalisationterm of the BLAST bit scoresterm·var (Fig. 7c ). This step models the all-vs-all BLASTterm hits for each pairwise comparison between species to identify and remove the gene similarity dependency on gene lengthterm·var and phylogenetic distanceterm. This is done so that the best hits between all species achieve the same scores regardless of sequence length or phylogenetic distanceterm. Delimitation of orthogroupterm sequence similarity thresholds using RBNHsterm (Fig. 7d ). This step uses information from RBNHsterm (Reciprocal Best length-Normalised hit) to define the lower limit of sequence similarity for putative cognate genes of each query gene. To be included in the orthogroup graphterm a gene-pair must be an RBNHterm or produce a hit that is better scoring than the lowest scoring RBNHterm (irrespective of species) for either gene. Constructing an orthogroup graphterm for input into MCL (Fig. 7e ). Putative cognate gene-pairsterm are identified as above and are connected in the orthogroup graphterm with weights given by the normalised BLAST bit scoresterm·var. Clustering of genes into orthogroupsterm using MCL (Fig. 7f ) .

The steps 2 to 4 are the novel parts of our algorithmterm and are described in detail below.

Gene length and phylogenetic distance normalisationterm The aim of this normalisation procedure is to remove gene length biasterm from BLAST bit scoresterm·var and to normalise for phylogenetic distanceterm between species. MCL converts sets of similarity scores into clusters by breaking apart clusters of genes that have low similarity scores (and therefore are unlikely to be orthogroupsterm) and preserving clusters of sequences that have high similarity scores. If the similarity scores between long sequences are inherently larger than the similarity scores between short sequences then the clustering will preferentially break apart clusters of short sequences while preserving clusters of long sequences. This effect can be clearly seen in the results of a typical OrthoMCLterm cluster. Here, long sequences are placed in overly large clusters leading to low precisionterm, and short sequences remain un-clustered leading to low recallterm (Fig. 3a ). The species-wise normalisation implemented by OrthoFinderterm similarly ensures that orthologuesterm from more distant species (that have inherently lower similarity scores due to phylogenetic distanceterm) are not preferentially discarded and is similar to a step that is performed in OrthoMCLterm wherein all scores are divided by the average score between a given species pair [ 13 ].

Previous methods have exploited BLASTterm e-valuesterm (rather than bit scoresterm) as a measure of similarity between sequences. However, as can be seen in Fig. 1b the use of e-valuesterm for assessment of similarity between sequences is flawed. Here, the minimum e-valueterm that can be obtained for a given query sequence decreases with increasing sequence length until, at a certain length, the lower bound for e-valuesterm is reached and BLASTterm returns an e-valueterm of 0. This creates two problems: (1) long sequences will frequently have low quality hits with better e-valuesterm than the best possible hits of short sequences; and (2) the floor value for the e-valueterm calculation means that length bias is non-uniform and thus irreversible. Specifically, beyond the floor-value e-valuesterm cannot be used to distinguish between the qualities of hits as they are all assigned the same e-valueterm. As can be seen in the heat map shown in Fig. 1b , many hits obtain this floor-value for a given pairwise species comparison and thus their similarities are indistinguishable. This length-bias must be removed to prevent biasing downstream clustering applications.

In this method we construct a similarity measureterm between sequences based on the bit-score normalised to take into account the query and hit sequences lengths and the phylogenetic distanceterm between species. Unlike e-valuesterm, the bit-scores do not suffer from the presence of a threshold limit and thus different amounts of sequence similarity can be distinguished regardless of the lengths of the sequences involved. Let L q be the length of the query sequence and L h be the length of the hit sequence. In an analogous manner to the e-valueterm calculation made by BLASTterm and other sequence comparison methods, we use the variable L qh = L q L h to quantify the lengths of a pair of sequences that are being compared.

The length normalisation procedure is shown in Fig. 2 . For each species pair, we: Sort all BLASTterm hits according to L qh = L q L h . Put the hits into equal sized bins of 1,000 hits (put the ‘shortest’ 1,000 hits according to L qh into one bin, the next 1,000 hits into the next bin and so on for all the hits). If there are fewer than 5,000 hits then we put the hits into bins of 200. Using fixed sized bins means that it is not necessary for the algorithmterm to specify the location of the bins in advance. Sort the hits in each bin according to BLAST bit scoreterm·var and select the top 5 % of hitsterm from each bin. Find the parameters a and b that best describe the fit between sequence similarity scores and gene lengthterm·var for the selected hits using the equation log 10 B qh = a log 10 L qh + b where B qh is the BLAST bit scoreterm·var between sequences q and h. Normalise all obtained BLAST bit scoresterm·var (not just the top 5 %) between the given species pair according to, B qh ' = B qh /10 b L qh a , so that B ' qh , (the normalised scoreterm) is the BLAST bit scoreterm·var for a hit divided by the BLAST bit scoreterm·var that would be expected for the best hits between sequences of that length for the species pair under consideration.

The top 5 % of hitsterm are used rather than RBHs as selection of RBHs will be affected by the gene length-bias that we wish to correct. Moreover, gene duplicationterm events can frequently cause RBHs to fail (Additional file 8 : Figure S5) and thus reduce the number of data points that are available for fitting. The normalisation procedure ensures that the best hits between a given species pair achieve (on average) the same scores irrespective of their gene lengthterm·var.

OrthoFinderterm also normalises for phylogenetic distanceterm, this is done so that the similarity scores between orthologuesterm will be independent of phylogenetic distanceterm (that is, the true orthologuesterm in distantly related species will obtain similar scores to the true orthologuesterm in closely related species). If this step is not done then true orthologuesterm in distantly related species will always obtain lower scores than true orthologuesterm in closely related species. Thus during graph clustering (which is unaware of phylogenetic relationship between species) distantly related true orthologuesterm (and cognates) will become disconnected from each other more easily than closely related true orthologuesterm (and cognates) in the orthogroup graphterm. Previous efforts to prevent this phylogenetic bias include dividing the observed similarity score for any given gene-pair by the mean similarity score observed for all reciprocal best hits between genes in that species pair [ 13 ]. However, in the absence of gene lengthterm·var information this means that short genes will always be penalised more than long genes.

Though there is precedent for the use of L qh = L q L h to quantify the lengths of a pair of sequences that are being compared [ 14 ], different functions for gene lengthterm·var normalisation were also assessed. All other functions, including for example the use of the variable \documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$ {\tilde{L}}_{qh}={L}_q+{L}_h $$\end{document} L ˜ q h = L q + L h in place of L qh , gave a lower overall clustering accuracy.

Identification of putative cognate gene-pairsterm for inclusion in the orthogroup graphterm Once scores are normalised OrthoFinderterm exploits RBNHsterm to identify putative cognate gene-pairsterm. RBHs are a high precisionterm method to identify putative orthologuesterm [ 25 – 27 ] and OrthoFinderterm uses the reciprocal requirement exploiting its length and phylogenetic distanceterm normalised BLAST scoresterm. For each gene the scores for its RBNHsterm are used to delimit the extent of sequence similarity of that gene’s orthogroupterm. Specifically, for each query sequence, q, any hit, h, with a normalised scoreterm, B ' qh , greater than or equal to the score for the lowest scoring RBNHterm of q is selected as a putative cognate gene-pairterm·def of q and therefore is connected to q in the orthogroup graphterm that is subsequently subjected to MCL clustering.

The rationale for this approach is that the level of normalised similarity of a query gene and its RBNHsterm can be used to estimate the extent of similarity of other genes within the same orthogroupterm. All genes more similar to a query gene than any of the query gene’s RBNHsterm (irrespective of species) are likely members of the same orthogroupterm. Therefore, the normalised similarity score for the most dissimilar RBNHterm of a gene is used as a cutoff for inclusion of additional cognate gene-pairs from all species. That is q is connected to h in the orthogroup graphterm if B ' qh > B ' qR where R is an RBNHterm of q. This provides a simple and robust method for recovering cognate gene-pairs that may otherwise be difficult to detect due to duplication events that can cause the RBNHterm method to fail. Further details, explanation and worked examples are provided in Additional file 8 : Figure S5.

In summary, the novel method presented here generates, for each query gene, an independent prediction of all the genes in its orthogroupterm. This orthogroup graphterm is then clustered using MCL with its default inflation parameter of 1.5. The effect of varying the MCL inflation parameterterm on the OrthoFinderterm result is shown in Additional file 9 : Figure S6. The F-scoreterm of OrthoFinderterm is relatively stable to variation in MCL inflation parameterterm, however it is possible to trade precisionterm against recallterm by varying this parameter (Additional file 9 : Figure S6). For comparison the analogous analysis is also presented for OrhtoMCL (Additional file 10 : Figure S7).

Implementation OrthoFinderterm is written in python. It requires python together with the numpy and scipy libraries [ 35 ] to be installed. OrthoFinderterm requires the standalone BLASTterm+ and MCL algorithmsterm that are freely available. These standalone applications must be installed separately to OrthoFinderterm and are not included in the OrthoFinderterm package. The implementation makes use of sparse matricesterm to store hits between sequences. This provides a memoryterm·var efficient method of storing the data and allows key parts of the algorithmterm to be expressed using scipy’s highly optimised C++ implementations of sparse matrix operationsterm. OrthoFinderterm can either run the BLASTterm searches for you or can be run on pre-computed BLASTterm searches. If you chose to run BLASTterm searches independently then instructions are provided in the documentation for how to process your sequence names in the pre-computed BLASTterm output. Similarly OrthoFinderterm will also automatically run MCL for you. However if you wish to run MCL separately using different parameter settings then the MCL input files are stored for this purpose in a working directory.

Evaluation OrthoBenchterm [ 5 ] is the only manually curated dataset of orthogroupsterm for the assessment of orthogroupterm prediction algorithmsterm. It was used in this work for assessing OrthoFinderterm as it has been independently evaluated, it underpins the testing of multiple different methods and it is a well-defined and stringent test of the problem that OrthoFinderterm was designed to solve. Criteria such as functional similarity within orthogroupsterm, expressed for example using enzyme classification numbers [ 36 ], were not used in this work since not all proteins with the same function are members of the same orthogroupterm and members of the same orthogroupterm do not necessarily all have the same function. As we are using real benchmark datasets for which only a subset of sequences have been assigned to ‘true’ gene families the extent of true negative orthologue assignmentsterm is unknown (as is the case for all methods tested on this dataset). Thus we cannot use the Matthews correlation coefficient to assess the performance of the orthogroupterm inference methods. In the absence of this information the simplest and most transparent evaluation of the accuracy of any prediction method is to measure its precisionterm and recallterm. \documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$ precisionterm=\frac{TP}{TP+FP} $$\end{document} precisionterm = T P T P + F P \documentclass[12pt]{minimal} \usepackage{amsmath} \usepackage{wasysym} \usepackage{amsfonts} \usepackage{amssymb} \usepackage{amsbsy} \usepackage{mathrsfs} \usepackage{upgreek} \setlength{\oddsidemargin}{-69pt} \begin{document}$$ recallterm=\frac{TP}{TP+FN} $$\end{document} recallterm = T P T P + F N Where TP is the number of true positive orthogroupterm assignments (that is, correct assignments), FP is the number of false positive orthogroupterm assignments (that is, incorrect assignments) and FN is the number of false negative orthologueterm assignments (that is, missing assignments). The F-scoreterm is the harmonic meanterm of these two measures, where the harmonic meanterm weights towards the worst performing measure. We also provide other evaluation measures from the original OrthoBenchterm analysis in Additional file 3 : Figure S2.

Inference of transcription factor orthogroupsterm To infer transcription factor orthogroupsterm we first identified the set of transcription factorsterm present in all genomes present in Phytozome V9. This identification was performed using the same rules for the presence and absence of PFAM domains as has been previously described [ 31 ]. The full set of protein coding genes from these genomes (including all the transcription factorsterm) was then clustered using OrthoFinderterm and OrthoMCLterm and the distribution of the transcription factorsterm within these orthogroupsterm was analysed. OrthoMCLterm was selected for comparison here as it is the method by which all orthogroupsterm of transcription factorsterm are currently defined [ 31 ]. An orthogroupterm of transcription factorsterm was defined as an orthogroupterm whose constituent genes comprised ≥50 % transcription factorsterm of the same domain classification.

To determine if OrthoFinderterm was correct in combining multiple separate OrthoMCLterm orthogroupsterm each orthogroupterm was subject to gene-tree—species-tree reconciliation. Using, gene-tree species-tree reconciliation it is possible to determine if OrthoFinderterm had incorrectly placed together genes that had diverged prior to the last common ancestor of the species being analysed. To do this, gene trees were inferred for each orthogroupterm by aligning the sequences using mafft-linsi [ 37 ] and inferring a maximum likelihood tree from this alignment using FastTree [ 38 ]. DLCpar [ 39 ] was used to reconcile these gene trees with the known species tree [ 28 ]. Using this method, each gene tree was assessed to determine if it contained bipartitions that occurred prior to the divergence of the last common ancestor of all the species being analysed. If such a bipartition was identified then the orthogroupterm was considered not to be a true orthogroupterm·def as it contained one or more genes that evolved by duplication prior to the last common ancestor of all species under consideration.

Discussion In this work we have presented OrthoFinderterm, a novel method for inference of orthogroupsterm. Our method is focused on a clear definition of an orthogroupterm, that is, that an orthogroupterm contains all genes descended from a single gene in the last common ancestor of the species whose genes are being analysed. This definition avoids conflating shared ancestryterm with other criteria that are not equivalent, such as functional conservationterm. Our method is designed to address the problem of orthogroupterm inference rather than categorise the disparate relationships that occur between individual genes within an orthogroupterm. These relationships are best resolved by first inferring orthogroupsterm using OrthoFinderterm and then using multiple sequence alignment and phylogenetic methods on these orthogroupsterm.

The two key novel features of our method are: (1) a method to automatically remove gene length biasterm and phylogenetic distanceterm from sequence similarity scores; and (2) a novel method to define the sequence similarity limits of an orthogroupterm. In the tests performed on the only publicly available orthogroupterm benchmark dataset (OrthoBenchterm) OrthoFinderterm outperformed all of the commonly used orthogroupterm assignment methods by between 8 % and 33 %. Moreover we have shown OrthoFinderterm to be scalable and robust to missing genesterm·var typical of incomplete genomes and de novo transcriptome assemblies. The software is freely available and can take pre-computed BLAST scoresterm as input making it easy to test on any newly developed benchmarks for which pre-computed BLAST scoresterm are available.

We further demonstrate the utility of OrthoFinderterm by providing a novel classification of all transcription factorsterm in the available, fully-sequenced plant genomes present in Phytozome V9. This analysis clusters 97.6 % of the 52,744 putative transcription factorsterm into orthogroupsterm. This novel analysis identifies millions of relationships that have not previously been reported providing new insight into the relationship and evolution of transcription factorterm gene families in plants.

Inferring orthologuesterm underpins much of modern biological research and is among the first steps in the annotation and analysis of genome and transcriptome sequencing projects. As sequencing technologies are now within the budgets of most research groups these data resources are increasing in number rapidly. Thus there is a requirement for an orthogroupterm inference method that is accurate, robust, scalable, and that can be run easily by independent research groups on conventional computing resources. Many orthogroupterm inference methods are not available for general use but are provided as static databases (for example, EggNog and TreeFam). Thus the most widely used methods are those that enable researchers to analyse their own data resources. With this in mind OrthoFinderterm has been developed with the aim of being easy to use. The method is executed as a single commandterm, has minimal dependencies and requires as input just the individual protein sequence FASTA filesterm for each species that is being clustered. The algorithmterm carries out all calculations (including BLASTterm searches and MCL clustering) and outputs the orthogroupsterm in both a plain tab delimited text file and in the OrthoXMLterm community format. The algorithmterm itself is small, fast and memoryterm·var efficient, making it suitable for use on linux desktop computers. Further information about the algorithmterm can be found at [ 19 ] and a standalone implementation of the algorithmterm is available under the GPLv3 licence at [ 20 ].

Interpretive notes.
• Highlighted spans are tagged entities: persName (author), title (venue), placeName (place), date (year), and term (a key concept: domain / ai / method).
• Eponymous or retrospective terms (e.g. “Nash equilibrium”, “segregation”) do not appear in the original source and so are not highlighted — a deliberate choice (see Report 4).
• Some entries begin with a word in capitals. EVIDENCE CORRECTED means the finding still stands and it was our quotation that was wrong — it has been replaced. RETRACTED means the entry itself was wrong; it stays on the page, marked, with its reason, rather than being deleted. WITHDRAWN AND REPLACED means a corrected version of it appears in the entries below. Each mark carries its own reason, because the reasons differ from one entry to the next. An entry we have WITHDRAWN is removed from this page and kept in the record, with its reason. A line reading Audit and a date is a later re-reading of the entry against its whole sentence: DOUBTFUL means it was kept, and the reason says what is loose about it.
• Quotation marks inside the tagger's sentence. Where a tag is the tagger's own sentence, a phrase in quotation marks inside it is borrowed from the paper — the tagger's wording around it is not. The paper's own sentence is the evidence quote shown on the same row, so the borrowing can be checked against the thing borrowed from without leaving this page. Nothing inside quotation marks anywhere on this page is ours: if it is quoted, it is the paper's. Whose words a concept carries. A concept entry records a term the paper itself uses, so the term, the sense given for it, and its evidence are the paper's own words, quoted where the paper fixes them. This is the opposite of a sense entry in the tag table, which is the tagger's sentence about how the paper uses a term. Where a concept entry could not be grounded in the paper's words, the entry says so on its own row.
• Counts: 1 work · 1 date.
Meta-Tagging Project · record emms2015-orthofinder-whole-genome-comparisons.
© 2026 Shir Sivroni