<title>Background</title> <p><italic>Conserved synteny </italic>is the (local) maintenance of gene content and order in certain chromosomal regions of related species. Several studies on chromosome evolution [##REF##12529304##1##, ####REF##15153998##2##, ##REF##16983148##3##, ##REF##17009864##4##, ##REF##17387144##5####17387144##5##] demonstrated that conserved synteny exists not only between closely-related species but also over very long evolutionary timescales. Long-range conserved synteny is a particularly frequent feature around developmentally important genes [##REF##17387144##5##], demonstrating that rearrangements are not an unbiased random process in genome evolution.</p> <p>Conserved synteny is, however, not only of interest as a phenomenon in genome evolution, but provides valuable practical information for the analysis of families of homologous genes. It is a long-standing problem in comparative genomics to identify orthologs, i.e. pairs of genes from two organisms that are separated from each other by a speciation event. In general, the task to distinguish true orthologs from paralogs cannot be solved based on pairwise comparisons. Gene loss, differences in evolutionary rates [##REF##15983874##6##], and convergent evolution often distort the sequence similarities to an extent that makes it impossible to determine orthology from the gene tree. Genomic linkage with genes whose orthology relationships are clearer (i.e. which are more conserved across species and have fewer in-species paralogs) than others can be exploited because linked genes likely share their duplication history. Local/tandem duplications place new copies into a new genomic context, large-scale duplications coordinately duplicate the genomic context and gene loss becomes obvious if it leaves large parts of the genomic context intact while erasing the gene of interest. Therefore, conserved synteny information may demonstrate the loss of a particular copy of a gene and hence put a restriction on which extant gene copies are potential orthologs. If the genomic context of duplicated genes has sufficiently diverged prior to a speciation event, synteny can even provide direct evidence for or against orthology.</p> <p>There are three basic approaches towards automated orthology identification.</p> <p>1. Similarity-based clustering methods. This group includes the popular reciprocal pairwise best hit approach and refinements (such as <monospace>Inparanoid</monospace>[##REF##11743721##7##, ####REF##15608241##8##, ##REF##18055500##9####18055500##9##]), as well as more sophisticated methods that initially represent homology as many-to-many relations. In [##UREF##0##10##], for instance, the "homology graph" graph of initial <monospace>blast</monospace> hits is refined by iteratively removing sub-optimal edges.</p> <p>2. Phylogenomics-based methods (such as the tree-based <monospace>Ensembl Compara</monospace>[##REF##18000006##11##] pipeline). These approaches first cluster homologous genes, then construct a gene phylogeny, attempt to reconcile it with a prescribed species tree and use the resulting mapping between gene-tree and species tree to assign orthology and paralogy relations. An alternative use of phylogenetic information is made by <monospace>PhyOP</monospace>, synonymous rate estimates to distinguish between orthologous and paralogous segments in closely related genomes [##REF##17009864##12##].</p> <p>3. Methods utilizing conserved synteny to infer true orthology between relatively recently diverged species. Methods range from whole genome alignments to combinations with similarity- and phylogenomics-based approaches. Examples are the commercial "syntenic-anchor" approach from Celera [##REF##15458983##13##], the former <monospace>Ensembl Compara</monospace> pipeline (prior the June 2006 release). Algorithms that are primarily designed to determine syntenic regions and break points between them also fall into this category [##REF##12421767##14##, ####UREF##1##15##, ##REF##15247098##16##, ##REF##16951135##17##, ##UREF##2##18####2##18##].</p> <p>Despite substantial improvements in this area, the automatically generated results are still far from being perfect, and the annotation provided by databases such as <monospace>Ensembl Compara</monospace>[##REF##18000006##11##] or <monospace>OrthoDB</monospace>[##REF##17947323##19##] are neither sufficiently complete nor sufficiently accurate for many applications. For instance, an in-depth study of lineage-specific differences in a family of transcription factors requires not only the complete complement of family members in each species, but also a flawless gene phylogeny (which implies a correct orthology assignment).</p> <p>The <monospace>SynBlast</monospace> tool is designed to assist the manual curation of such data and to focus on individual loci of interest. In contrast to most approaches to genome-wide orthology annotation, it does not operate on pre-determined gene (proteome) sets but it searches the nucleotide sequence of the entire target genome. Hence it does not exclude possible homologs only because they are missing from annotation tracks. Instead of attempting to automatically extract an assignment of orthologs and paralogs, <monospace>SynBlast</monospace> instead provides the user with detailed information on all plausible homologs and their genomic context. To this end, web-based graphical overviews that can easily be compared with one another are generated. While heuristic rules are employed by the software to propose a plausible rank-ordering of the homologs with the aim of determining the correct orthologs, its primary purpose is to present conflicting information to the researcher in such way that it facilitates the decision of a human curator.</p>
<title>Methods</title> <p>The vertebrate genomes were taken from <monospace>Ensembl</monospace> (release 42, Dec 2006). In case of the <italic>ParaHox </italic>application and also the <italic>Danio Hox </italic>example the new assembly version for zebrafish (Zv7, Apr 2007 from <monospace>Ensembl</monospace> release 46, Aug 2007) was used. The new <italic>Danio </italic>assembly was scanned with local <monospace>WU-BLAST</monospace> (<monospace>tblastn</monospace>, version 2.0 MP-WashU, 04-May-2006). All other <monospace>blast</monospace> searches were performed with local <monospace>tblastn</monospace> (<monospace>blastall</monospace> version 2.2.15 of the NCBI <monospace>BLAST</monospace> suite). Genome databases were used in repeat-masked form, and the minimum <italic>E</italic>-value was set to <italic>E </italic>= 10<sup>-5 </sup>or <italic>E </italic>= 10<sup>-4</sup>. The maximal size of the target cluster was restricted to twice the size of the reference cluster for all applications (parameter <italic>L</italic>). The number of different proteins to be contained in a valid synteny region at minimum (parameter <italic>N</italic>) was set to 1 (Parahox application) or 4 (Hox application). The cutoff for the HSP chain score was set to 100. The cutoff for the maximal overlap (w.r.t. query coordinates) of neighboring consistent HSPs was set to 40 amino acid positions. The fraction of the score used for matches of loci with different orientation was set to 90 percent while the gap penalties were set to 10 (gap in reference sequence) and 2 (gap in target sequence). All scripts were written in <monospace>Perl</monospace> (v5.8.8) and executed on PC hardware running Linux.</p> <p>The <italic>intra-score </italic>is calculated once for each query protein <italic>s</italic>, and describes the relative difference of the best and the second-best hit onto the reference genome (i.e. for the closest-related paralogs). This is approximated by their bit-score differences, i.e.</p> <p></p> <p>where <italic>q</italic><sub><italic>s</italic>1 </sub>and <italic>q</italic><sub><italic>s</italic>2 </sub>are the two top-scoring target loci (i.e., HSP chains) within the reference genome. The more distant the closest paralogs in the reference, the more reliable is the assignment of orthologs from the target species.</p> <p>The <italic>inter-score </italic>is calculated for each assigned target locus <italic>t</italic><sub><italic>s </italic></sub>within a target genome, defined as its relative bit-score difference to the best reference hit locus <italic>q</italic><sub><italic>s</italic>1</sub>:</p> <p></p> <p>Hence, the inter-score expresses how "bad" a putative ortholog hit to the target genome is w.r.t. the maximally expected score <italic>b</italic>(<italic>s</italic>, <italic>q</italic><sub><italic>s</italic>1</sub>).</p> <p>The ratio of intra-score and inter-score, <italic>S</italic><sub>intra</sub>/<italic>S</italic><sub>inter</sub>, quantifies the quality of an inter-species (potentially orthologous) hit in relation to the similarity between paralogs in the reference genome. Therefore, it serves as a measure for the confidence in the orthology of the query and target locus.</p> <p>The <italic>(log)RatioSum </italic>score is defined as the sum of the (logarithms of the) intra-inter-score ratios of all target loci assigned within the gene order alignment.</p>
<title>Results</title> <title>Algorithms and Implementation</title> <title>Overview of the SynBlast pipeline</title> <p><monospace>SynBlast</monospace> is a "semi-automatic" pipeline that is implemented as a suite of <monospace>Perl</monospace> scripts (<monospace>SynBlast</monospace> package). In order to allow automatic retrieval of proteins from syntenic regions and comparison of assignments with existing annotations the <monospace>Ensembl</monospace> system and databases [##REF##18000006##11##] were chosen as standard reference sources. Therefore, the pipeline scripts make use of the <monospace>Ensembl Perl</monospace> API to retrieve reference annotation and sequences from the <monospace>Ensembl Core</monospace> databases as well as homology annotations (for comparison only) from the <monospace>Ensembl Compara</monospace> database.</p> <p>The workflow is summarized in Figure ##FIG##0##1##. It starts from a focal protein coding gene of interest whose homologs are to be detected.</p> <p>Step 1, in order to include synteny information, the adjacent protein coding genes within a certain genomic distance (flanking size, e.g. 1 Mb up- and downstream) are added to the reference set. The system requires both the sequences and positional information (orientation and (relative) start and end positions) of the reference genes. This information can be provided manually by the user in form of a text file containing tab-separated entries of gene identifiers and their genomic coordinates. Details are given in the <monospace>SynBlast</monospace> Tutorial, which is included in the Online Supplemental Material [##UREF##3##20##]. Alternatively, the corresponding files can be generated using the <monospace>getEnsemblProteins.pl</monospace> script which retrieves sequences and annotation information from <monospace>Ensembl</monospace> databases.</p> <p>Step 2 consists of translated-<monospace>blast</monospace> searches using all reference proteins as queries on a selection of genome databases as targets. Resulting <monospace>blast</monospace> hits are expected to be in tabular (<monospace>NCBI BLAST</monospace>) format for further processing. Again this step can be performed manually using any program that creates <monospace>blast</monospace>-like tabular output, including <monospace>NCBI BLAST</monospace>[##REF##9254694##21##], <monospace>WU-BLAST</monospace> (<ext-link ext-link-type="uri" xlink:href="http://blast.wustl.edu"/>), or <monospace>BLAT</monospace>[##REF##11932250##22##]. When the genome data is available locally in <monospace>NCBI BLAST</monospace> format, the script <monospace>doBlastJobs.pl</monospace> automatizes this step using local <monospace>NCBI BLAST</monospace>. It is needed to include the reference species as target genome as well in order to enable the subsequent normalization of <monospace>blast</monospace> scores and to detect possible paralogous clusters that the user should be aware of when interpreting final pipeline results. Those paralogous regions of the reference set should be used as reference in a subsequent pipeline run as well to avoid false positive orthology assignments.</p> <p>In step 3, we search for potential regions of conserved synteny (syntenic target blocks). To this end we collect <monospace>blast</monospace> hits that are located within regions of limited size on the target genome. The purpose of this filtering step is to extract candidate subsets of <monospace>blast</monospace> hits (or HSPs, high scoring pairs) that can be treated separately in the following. At this stage we do not consider gene order, but gene content information, i.e. a user-specified number of query-specific hits must be contained at minimum in each candidate subset. The procedure is implemented in the script <monospace>doSyntenyFilter.pl</monospace>, and is described in detail in the following section.</p> <p>In step 4, all detected candidate regions of conserved synteny from step 3 are evaluated w.r.t. their agreement with the reference gene order. The technical details of the <monospace>doSyntenyAlignment.pl</monospace> procedure are described below. The candidate syntenic regions are sorted according to a scoring scheme that combines sequence similarity, synteny information, and orthology versus paralogy information. The results are presented as HTML files in a web browser together with graphical representations of gene order alignment matrices and paths. Graphics such as those shown in Figure ##FIG##1##2## allow the user to readily identify small-scale rearrangements such as translocations or inversions.</p> <title>Extraction of syntenic target blocks – <monospace>doSyntenyFilter.pl</monospace></title> <p>A region of one of the target genomes is considered as a candidate for a syntenic target block if it contains blast hits from at least <italic>N </italic>different proteins of the query set within an interval of length at most <italic>L</italic>. The parameters <italic>N </italic>and <italic>L </italic>are set by the user, both either directly or indirectly (relative to the reference set). They reflect the expected rate of gene loss and the expected structural similarity. The maximal regions of contiguous <monospace>blast</monospace> hits fulfilling these criteria are extracted separately for each target sequence. Depending on the status of the genome assembly, the sequence can be on a chromosome, a scaffold, or a contig. Small scaffolds or contigs pose a problem for this step as a target block syntenic to the query region may be mapped to several different scaffolds. In this case, <monospace>SynBlast</monospace> reports two or more separate syntenic regions and/or misses parts of the regions if less than <italic>N </italic>query proteins map to some of the scaffold regions. Note that for some genomes allelic variants are assembled into different scaffolds. <monospace>SynBlast</monospace> then reports all these scaffolds and it is left to the user to recognize this.</p> <p>In its current implementation, the candidate subsets of <monospace>blast</monospace> hits are found by a sliding window approach. In addition to the number of query proteins ≥ <italic>N </italic>that have <monospace>blast</monospace> hits within a sequence window of size ≤ <italic>L </italic>also the sum of all maximal HSP bit-scores for these proteins is recorded. This yields a convenient measure to prefer the higher-scoring subsets when there are overlapping intervals (in particular if <italic>L </italic>and <italic>N </italic>are too small). We currently use a greedy approach that selects a specified number of target block intervals in decreasing order of the score sum and skips all intervals overlapping a previously selected interval by more than a specified threshold. For a detailed description of the various effects following changes to the parameter settings of <italic>L </italic>and <italic>N </italic>we refer to the <monospace>SynBlast</monospace> tutorial, which is provided as part of the Supplemental Material [##UREF##3##20##].</p> <title>Evaluation of syntenic target blocks via gene order alignment – <monospace>doSyntenyAlignment.pl</monospace></title> <p>In the fourth step of the pipeline, each of the syntenic target blocks (subsets of <monospace>blast</monospace> hits), resulting from step 3, is analyzed separately in comparison to the query region. This part of the pipeline consists of several sub-components, which we discuss separately, see also Figure ##FIG##2##3##.</p> <p>(i) The set of reference proteins is linearly ordered (by start/end or mean positions) into so-called "query loci". If the query region contains overlapping proteins, these are combined into a single query locus. Thus, a query locus may comprise more than one query protein (an example is the second query locus in Figure ##FIG##2##3A##).</p> <p>(ii) For each query protein we chain all corresponding HSPs into models of target loci. Each HSP consists of an interval <italic>α </italic>= [<italic>a</italic>', <italic>a</italic>"] on the query sequence and a corresponding interval <italic>β </italic>= [<italic>b</italic>', <italic>b</italic>"] on the target sequence. These intervals are linearly ordered for both query and target based on their coordinates.</p> <p>Intervals on the two strands of a target are treated separately. We furthermore take into account that HSPs must not be too far away from each other, i.e. the maximal genomic extension is restricted to either an absolute or query gene dependent length (locus size limit; see also Figure ##FIG##2##3-B1##). Again, groups of intervals that are too far apart from each other are treated separately.</p> <p>For each group of HSPs with common orientation we compute an optimal "alignment" of these lists of intervals using a variant of the Needleman-Wunsch algorithm, similar to Ref. [##REF##15032508##23##]. The query and target intervals of the HSPs, respectively, are considered as characters within the alignment in which a match occurs if both intervals belong to the same HSP. The score of the match is its bit-score. Pairs of (query/target) intervals that do not correspond to the same HSP are considered as mismatches with score -∞. Small negative scores are given to insertions and deletions, endgaps are treated as free. The resulting alignment then defines a consistent chaining of collinear HSPs, here called an "HSP chain" for short. It represents an overall hit for the respective query protein (approximate gene model) with a group score equal to the sum of bit-scores of all HSPs of the chain. A score threshold can be specified to eliminate spurious hits, which otherwise might lead to incorrect groupings of adjacent loci in the next sub step, see also Figure ##FIG##2##3-B5##. Each HSP chain is furthermore characterized by a start, end, and mean position.</p> <p>(iii) As in sub-step (i), we now define a linear order of HSP chains by grouping them according to start/end or mean positions into so-called target loci, see Figure ##FIG##2##3##. If there are HSP chains that reside within the same target locus, (i.e. have overlapping intervals with some HSP chain) while representing hits for the same query protein, only the top-scoring chain is kept, see Figure ##FIG##2##3-B6##. Thus, we finally end up with linearly ordered blocks of target loci each containing one or more (overlapping) query-specific HSP chains.</p> <p>(iv) As in sub-step (ii), we use a variant of the Needleman-Wunsch algorithm to obtain a maximum weight sequence of collinear pairs of query and target loci. As before, mismatches are prohibited. Matches are scored as the arithmetic mean of the scores of all matching individual query proteins that belong to the same query locus. Formally, for each pair (<italic>q</italic>, <italic>t</italic>) of query and target locus let <italic>ν</italic><sub><italic>qt </italic></sub>be the number of matching query proteins between the pair of loci. The corresponding similarity score is</p> <p></p> <p>where <italic>b</italic>(<italic>s</italic>, <italic>t</italic><sub><italic>s</italic></sub>) is the bit-score of query protein s with its match <italic>t</italic><sub><italic>s </italic></sub>on the target genome as determined in sub-step (ii). In contrast to step (ii), we do not exclude matches between items of different orientation. Instead, we use only a fraction of the score <italic>b</italic>(<italic>s</italic>, <italic>t</italic><sub><italic>s</italic></sub>) (adjustable parameter) to penalize those matches. Thus, swapped orientation of a target locus w.r.t. the orientation of its matching query locus within the reference set is generally allowed, but the match score of such a locus is reduced to a user-defined fraction (e.g. 90%). This parameter can also be set to 0, in which case matches with reversed direction are considered as not informative at all. The gene order alignment score is consequently calculated for both orientations of the target block relative to the reference set, and only the higher-scoring alignment is retained in subsequent steps.</p> <p>In addition to this absolute scoring we also compute relative weights <italic>b</italic>(<italic>s</italic>, <italic>t</italic><sub><italic>s</italic></sub>)/<italic>b</italic>(<italic>s</italic>, <italic>q</italic><sub><italic>s</italic></sub>) where the absolute bit-score is scaled by the score obtained by matching the query protein <italic>s </italic>back to its genomic locus <italic>q</italic><sub><italic>s </italic></sub>within the reference genome. The value <italic>b</italic>(<italic>s</italic>, <italic>q</italic><sub><italic>s</italic></sub>) is a good approximation for the maximal <monospace>tblastn</monospace> score of a given query protein. The relative score is then used as match score during the gene order alignment. This ensures that the matches to each reference locus are scored relative to the information content of the locus.</p> <p>Since match scores are defined directly between loci we can conveniently combine the visualization of the alignment path and the scoring matrix, see Figure ##FIG##1##2##.</p> <p>(v) Finally, all evaluated target regions are compiled in a ranked list in browsable HTML format including graphical overviews of loci scoring matrices (dotplot) and alignments as well as an alignment table displaying additional information for assigned loci. Swapped orientation of a single target locus is indicated in the dotplot by a shaded dot. In the alignment graphics, an arrow with reversed orientation w.r.t. the arrow of its assigned query locus is used.</p> <p>The ranking can be based on the gene order alignment score (roughly the sum of (weighted) bit-scores for assigned target loci) or the <italic>(log)RatioSum </italic>score, which is calculated as the sum of (the logarithms of) intra-inter-score ratios of assigned target loci. This score ratio, which is described in detail in the "Methods" section, measures the ambiguity of orthology between two loci based on the existence of close paralogs within the reference. It has proven useful in the process of identifying true orthologs. In combination with the gene order alignment score this score makes it easier to distinguish between putative orthologous and paralogous hits or clusters.</p> <p>If reference and genome data are taken from <monospace>Ensembl</monospace> databases, <monospace>SynBlast</monospace> optionally retrieves the <monospace>Ensembl</monospace><monospace>Compara</monospace> homology annotations and the <monospace>Ensembl Core</monospace> protein coding gene annotations overlapping the target locus interval of the matching HSP chain identified by <monospace>SynBlast</monospace>, for comparison.</p> <title>Applications</title> <p>As a real-life test of <monospace>SynBlast</monospace>, we consider here the genomic clusters of vertebrate <italic>Hox </italic>and <italic>ParaHox </italic>genes. These genes code for homeodomain transcription factors that regulate the anterior/posterior patterning in most bilaterian animals [##REF##2569969##24##,##REF##1346368##25##]. <italic>Hox </italic>and <italic>ParaHox </italic>genes arose early in metazoan history from a single ancestral "<italic>UrHox </italic>gene" [##REF##11253066##26##]. After a few tandem duplication events, a large scale duplication lead to ancestral <italic>Hox </italic>and <italic>ParaHox </italic>clusters. While the ancestral <italic>ParaHox </italic>cluster remained largely unchanged, the evolution of its <italic>Hox </italic>counterpart was dominated by a series of tandem duplications. As a consequence, most bilaterians share at least eight distinct paralogous groups (8 in arthropods, and 13 or 14 in chordates) which retained high sequence similarity at the homeobox. Both <italic>Hox </italic>and <italic>ParaHox </italic>genes are usually organized in tightly linked clusters [##UREF##4##27##], with syntenic conservation extending even beyond the core clusters themselves. For instance, an additional homeobox gene, <italic>Evx</italic>, located at the 5' end of the <italic>Hox </italic>cluster can be seen as part of an extended <italic>Hox </italic>cluster, see [##REF##16341069##28##] for more details.</p> <p>The modern vertebrate genome arose from an ancestral chordate by means of two rounds of whole genome duplication [##REF##9254922##29##,##REF##16162861##30##]. Teleost fishes have undergone an additional round of genome duplication [##REF##10597637##31##,##REF##12618368##32##].</p> <p>Substantial loss of duplicated genes was the consequence of these duplication events. In the case of <italic>Hox </italic>clusters there is little doubt about the orthology relationships among the <italic>Hox </italic>genes of tetrapoda. In teleost fishes, however, the relationships of the duplicated <italic>Hox </italic>clusters between zebrafish and fugu have long been controversial, see [##REF##18202881##33##] for a discussion, and have only recently been resolved using a dense taxon sampling [##REF##16162861##30##]. It is well known that the relative order and orientation of <italic>Hox </italic>genes in their clusters have been highly conserved in vertebrate evolution, albeit there is substantial gene loss. The <italic>Hox </italic>clusters thus are an excellent test case to demonstrate the gene order alignment functionality of <monospace>SynBlast</monospace>.</p> <title>Vertebrate <italic>Hox </italic>clusters</title> <p>We used the four human <italic>Hox </italic>clusters as reference and searched the vertebrate target species with <monospace>SynBlast</monospace>. We consider here a diverse set of vertebrate genomes which contains both tetrapods (with 4 paralogous <italic>Hox </italic>clusters) and teleosts (with 8 paralogons). The cluster locations, gene inventories, and <monospace>SynBlast</monospace> scores are listed in Figure ##FIG##3##4##. In case of genomes with complete assemblies, the correct assignment of cluster orthology and the correct assignment of <italic>Hox </italic>gene identity is straightforward by visual inspection of the <monospace>SynBlast</monospace> cluster alignments, see Table ##TAB##0##1## for an example. Here, both the gene order alignment score and the <italic>logRatioSum </italic>score is suitable to assign cluster identity to the target loci in the zebrafish genome. However, the <italic>logRatioSum </italic>score clearly out-performs the gene order alignment score in case of the <italic>Danio Bb </italic>cluster. In combination, the two scores provide the best means to rank orthologous loci at the top. The zebrafish Zv7 assembly contains two inparalog copies <italic>DrCa1 </italic>and <italic>DrCa2 </italic>of the zebrafish <italic>HoxCa </italic>cluster. This is, however, certainly an assembly artifact and contradicts all of the existing literature, see e.g. [##REF##14707165##34##] and the references therein. <monospace>SynBlast</monospace> correctly retrieves both copies with comparable scores.</p> <p>In the case of incomplete assemblies, only partial clusters can be obtained. For instance, individual <italic>Hox </italic>loci of oppossum and chicken are located on small separate scaffolds. For the duplicated genomes of the five teleosts in our data set, we obtained all 7 <italic>Hox </italic>genes-containing paralogous clusters in agreement with the literature, see [##REF##18202881##33##,##REF##15967537##35##, ####REF##16162861##36##, ##REF##17845724##37##, ##REF##17553908##38####17553908##38##]. Since our query consisted of the <italic>Hox </italic>cluster only, we could of course not retrieve the 8th zebrafish paralogon, which is completely devoid of homeobox genes [##REF##16736008##39##].</p> <p>Several artifacts of preliminary genome assemblies further complicate the analysis: In the fugu <italic>HoxAa </italic>cluster we readily detected the artifactual breakage of the cluster into two fragments on scaf.12 and scaf.346. In the older Zv6 assembly of the zebrafish genome, some <italic>Hox </italic>clusters contained local rearrangements and obviously duplicated gene loci, in particular the <italic>HoxBb </italic>and <italic>HoxCb </italic>clusters. Most of these problems have been resolved in the most recent Zv7 assembly, while the <italic>Ca </italic>artifact has been newly introduced. Table ##TAB##1##2## summarizes the discrepancies of the <monospace>Ensembl Compara</monospace> annotation for the orthology assignments obtained using <monospace>SynBlast</monospace>, the latter conforming to the recent literature [##REF##18202881##33##].</p> <p>The very well-understood example of the <italic>Hox </italic>gene cluster demonstrates that the true orthology and paralogy relationships can be determined rather quickly and easily by means of a manual analysis with the assistance of <monospace>SynBlast</monospace>. Automatic orthology annotation pipelines, on the other hand, still produce unsatisfactory results despite recent progress.</p> <title>Teleost ParaHox clusters</title> <p>The <italic>ParaHox </italic>clusters of teleost fishes have long been used to contradict the whole genome duplication scenario because of a mainly unduplicated repertoire of <italic>ParaHox </italic>genes compared to other vertebrates. Even after the teleost-specific genome duplication had been broadly accepted, the small number of <italic>ParaHox </italic>genes in each cluster and the large amount of gene loss at this locus complicated attempts to decipher their duplication history. Knowledge about the number of paralogous <italic>Cdx </italic>genes and their assignment to paralogous groups is a good starting point for such a reconstruction. Two studies based on publicly available genome sequences arrived at different scenarios for the history of this particular <italic>ParaHox </italic>gene in teleost fishes [##REF##16619246##40##,##REF##16801555##41##]. While Prohaska et al. [##REF##16619246##40##] proposed the existence of a <italic>Cdx2 </italic>gene copy (at least for fugu and tetraodon), Mulley et al. [##REF##16801555##41##] concluded that both copies of <italic>Cdx2 </italic>were lost and suggested that this loss was compensated by two copies of <italic>Cdx1</italic>. A more recent analysis that uses additional sequence data [##REF##17822543##42##] settles the discrepancy in favor of [##REF##16801555##41##], supporting the retention of two <italic>Cdx1 </italic>genes in cichlids. The analysis of [##REF##17822543##42##] in part excludes zebrafish because of problems with the available genome assemblies. Here we demonstrate how <monospace>SynBlast</monospace> can be used to facilitate retrieval of candidate <italic>Cdx </italic>loci and cluster assignments in the zebrafish genome.</p> <p>In an intact <italic>ParaHox </italic>cluster, the <italic>Cdx </italic>gene is flanked by two <italic>ParaHox </italic>genes, i.e. <italic>Gsh </italic>and <italic>Pdx</italic>, and a number of genes of other gene families. According to [##REF##17822543##42##], the ancestral gnathostome <italic>ParaHox </italic>genes are organized in four clusters, designated A, B, C, and D in analogy to the <italic>Hox </italic>clusters (see Figure ##FIG##4##5##). The <italic>Cdx </italic>gene of the C cluster has been lost soon after the 1R/2R duplications [##REF##16801555##41##]. No organism with a fourth <italic>Cdx </italic>paralog resulting from this duplication event has yet been found. Therefore, only three of the four ancestral clusters each retained a <italic>Cdx </italic>gene: <italic>Cdx2 </italic>(cluster A), <italic>Cdx4 </italic>(cluster B), and <italic>Cdx1 </italic>(cluster D). As a consequence of the teleost genome duplication we would expect to find 8 <italic>ParaHox </italic>clusters, two A clusters (A1, A2), two B clusters (B1, B2) etc. and up to 6 <italic>Cdx </italic>genes in the 6 clusters A1/2, B1/2, and D1/2. We start our <monospace>SynBlast</monospace> search in the zebrafish genome with the four human <italic>ParaHox </italic>cluster regions.</p> <p>Table ##TAB##2##3## shows the scores for all pairs of the four human query loci with the 11 high-scoring target loci of zebrafish. The assignment of true orthologs is more challenging than in the case of <italic>Hox </italic>clusters but still revealing.</p> <p>One copy of <italic>ParaHoxA </italic>retained 13 of 24 genes flanking the <italic>Cdx2 </italic>locus even though <italic>Cdx2 </italic>itself was obviously lost. This is a case where gene loss can reliably be distinguished from missing data based on well-conserved synteny information (see Figure ##FIG##5##6##). The second copy retained only 5 of the 24 flanking genes. In line with the analysis of [##REF##16801555##41##,##REF##17822543##42##], we observe that the <italic>Cdx2 </italic>gene has been lost from both copies. We also observe that one of the two <italic>ParaHoxA </italic>contains the only copy of <italic>Gsh1 </italic>which is located at <bold>DrA2 </bold>(Chr.5), while the only copy of <italic>Pdx1 </italic>is located at <bold>DrA1 </bold>(Chr.24). Note that this information independently confirms the assignment of the two zebrafish <italic>ParaHoxA </italic>paralogs to the ancestral A cluster. <monospace>SynBlast</monospace> reports additional syntenic regions in the zebrafish genome that contain homologs of some of the genes of the <italic>HsA </italic>query. These are located on chromosomes 7, 14, 20, and 21, and can be assumed to be orthologs of the <italic>ParaHox </italic>B, C, and D clusters. In order to confirm this assumption, we also consider the remaining three human <italic>ParaHox </italic>regions as queries.</p> <p>The query with human <italic>ParaHoxB </italic>yields only poorly conserved synteny information. This can be due to the reorganization of this locus when it got translocated to the mammalian sex chromosome X, see [##REF##16619246##40##,##REF##16778056##43##] for details. Nevertheless, we obtain sufficient information from the linkage of the <italic>Cdx </italic>loci with <italic>chic1 </italic>to see that zebrafish has one <italic>Cdx4 </italic>locus, <bold>DrB1 </bold>(Chr.14). With the human <italic>ParaHoxC </italic>cluster, which contains the <italic>Gsh-2 </italic>gene as a query, two paralogous regions in the zebrafish genome can be identified. <bold>DrC1 </bold>on Chr.20 containing the only surviving copy of <italic>Gsh2</italic>, while a putative <bold>DrC2 </bold>locus on Chr.1 contains three high-scoring reference loci (<italic>fip1l1</italic>, <italic>chic2</italic>, and <italic>clock</italic>) and both neighbors of <italic>Gsh2</italic>, i.e. <italic>chic2 </italic>and <italic>pdgfrA</italic>, but is devoid of homeobox genes.</p> <p>Note that "empty" parahox clusters are not exceptional. Teleost fishes have also lost all homeobox genes in one of the <italic>HoxD </italic>paralogs (zebrafish, [##REF##16736008##39##]) or one of the <italic>HoxC </italic>paralogs (pufferfish, [##REF##16619246##40##]), respectively. Loss of a gene of interest can nevertheless be identified due to the retention of neighboring genes given sufficient conserved synteny.</p> <p>The assignment of orthologs to cluster <italic>HsParaHoxD </italic>is difficult. Conserved synteny information is relatively rare and only locally given, i.e. the orthologous hits for those query regions are scattered more or less across the target chromosome or even genome, which is probably due to extensive rearrangements. Nevertheless, one <italic>Cdx </italic>locus is linked to <italic>pdgfrB</italic>, a D cluster gene. <monospace>SynBlast</monospace> detects multiple fragments that map to two distinct zebrafish chromosomes. A plausible hypothesis is to interpret the three hits of Chr.14 at 22 M, 25 M, and 53 M as remnants of one dissolving cluster <bold>DrD1</bold>, while the two fragments of Chr.21 at 36 M and 43 M constitute the other <bold>DrD2 </bold>paralog.</p> <p>In summary, we have located the three retained <italic>Cdx </italic>genes in the highly fragmented zebrafish genome assembly, and we conclude that three <italic>Cdx </italic>genes were lost in the aftermath of the fish-specific genome duplication. Due to synteny information, the three <italic>Cdx </italic>genes can unambiguously be assigned to the paralog groups <italic>Cdx4 </italic>(one copy, B cluster) and <italic>Cdx1 </italic>(two copies, D clusters).</p> <title>Further Examples</title> <p>In addition to the difficult <italic>Hox </italic>and <italic>Parahox </italic>loci we have investigated several examples of human loci with extensive synteny in other vertebrates, some of which are included in the Online Supplemental Material for comparison. In these rather straightforward cases we encountered a rather common annotation problem. Homology-based protein annotation sometimes produces two (or even more) disconnected annotated fragments, in particular when evidence from different sources is used. Since these fragments are not recognized as parts of the same protein, they are subsequently interpreted as distinct homologs of the same protein, resulting in an erroneous "within-species-paralog" assignment. We observed that <monospace>SynBlast</monospace> correctly recognizes such disconnected fragments as belonging to the same query item in the HSP chaining step, and hence avoids these spurious "paralogs".</p>
<title>Discussion and Conclusion</title> <p>The <monospace>SynBlast</monospace> tool was developed to assist in the interactive preparation of high-quality orthology annotations. It uses synteny in addition to sequence similarity. A major difference to most other tools is that it does not operate on a "proteome set". Instead, it uses <monospace>tblastn</monospace> and a two-level alignment procedure to retrieve the homologs of a set of reference proteins. As a consequence, it is independent of gene predictions and annotations of the target genomes. Known or predicted protein sequences are required only for the query genome. This avoids in particular many of the problems with misannotations in the target genome that may confuse automatic pipelines.</p> <p>A major advantage of the synteny-based approach is that we also find fairly diverged homologs in a conserved context that would otherwise be discarded due to insufficient sequence similarity, see also [##REF##17888146##44##]. This allows the user to find supporting information for highly diverged genes or gene loss and to distinguish it from the failure to detect sequence similarity. As a consequence, we find that <monospace>SynBlast</monospace> is particularly useful to retrieve homologous regions in the presence of high rates of gene loss, such as after the teleost-specific genome duplication. Syntenic regions are found and gene losses can be identified even when the focal genes are lost from one or more paralogons. As demonstrated in the <italic>ParaHox </italic>cluster example, information on such loci is readily accessible using <monospace>SynBlast</monospace> and can be instrumental in deciphering complex duplication/loss scenarios. This is the case in particular when homologous genes that arose through several distinct duplication events are of interest, as in the case of homeobox clusters. Of course, in cases where synteny is not preserved, <monospace>SynBlast</monospace> cannot do better than a simple <monospace>blast</monospace> search. In such a case, the output of the program at least makes it easy for the user to identify cases of disintegrated synteny. To distinguish orthologous and paralogous regions, <monospace>SynBlast</monospace> provides two scoring schemes: one that attempts to evaluate the overall similarity of two syntenic regions (gene order alignment score), and alternatively the relative similarity in comparison to the most similar within-reference paralog (<italic>(log)RatioSum </italic>score). However, the <monospace>SynBlast</monospace> system was designed to aid a careful manual evaluation rather than to provide an automatic pipeline. Hence, it produces extensive graphical and tabular output of all regions in the target genomes that are potentially syntenic to the query region in the form of HTML pages, which also integrates the existing <monospace>Ensembl Compara</monospace> homology annotation for comparison. This renders the tool most useful when orthology annotation is not obvious and expert knowledge is required to reach a definitive conclusion.</p>
<title>Discussion and Conclusion</title> <p>The <monospace>SynBlast</monospace> tool was developed to assist in the interactive preparation of high-quality orthology annotations. It uses synteny in addition to sequence similarity. A major difference to most other tools is that it does not operate on a "proteome set". Instead, it uses <monospace>tblastn</monospace> and a two-level alignment procedure to retrieve the homologs of a set of reference proteins. As a consequence, it is independent of gene predictions and annotations of the target genomes. Known or predicted protein sequences are required only for the query genome. This avoids in particular many of the problems with misannotations in the target genome that may confuse automatic pipelines.</p> <p>A major advantage of the synteny-based approach is that we also find fairly diverged homologs in a conserved context that would otherwise be discarded due to insufficient sequence similarity, see also [##REF##17888146##44##]. This allows the user to find supporting information for highly diverged genes or gene loss and to distinguish it from the failure to detect sequence similarity. As a consequence, we find that <monospace>SynBlast</monospace> is particularly useful to retrieve homologous regions in the presence of high rates of gene loss, such as after the teleost-specific genome duplication. Syntenic regions are found and gene losses can be identified even when the focal genes are lost from one or more paralogons. As demonstrated in the <italic>ParaHox </italic>cluster example, information on such loci is readily accessible using <monospace>SynBlast</monospace> and can be instrumental in deciphering complex duplication/loss scenarios. This is the case in particular when homologous genes that arose through several distinct duplication events are of interest, as in the case of homeobox clusters. Of course, in cases where synteny is not preserved, <monospace>SynBlast</monospace> cannot do better than a simple <monospace>blast</monospace> search. In such a case, the output of the program at least makes it easy for the user to identify cases of disintegrated synteny. To distinguish orthologous and paralogous regions, <monospace>SynBlast</monospace> provides two scoring schemes: one that attempts to evaluate the overall similarity of two syntenic regions (gene order alignment score), and alternatively the relative similarity in comparison to the most similar within-reference paralog (<italic>(log)RatioSum </italic>score). However, the <monospace>SynBlast</monospace> system was designed to aid a careful manual evaluation rather than to provide an automatic pipeline. Hence, it produces extensive graphical and tabular output of all regions in the target genomes that are potentially syntenic to the query region in the form of HTML pages, which also integrates the existing <monospace>Ensembl Compara</monospace> homology annotation for comparison. This renders the tool most useful when orthology annotation is not obvious and expert knowledge is required to reach a definitive conclusion.</p>
<p>This is an Open Access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/2.0"/>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</p> <title>Motivation</title> <p>In the last years more than 20 vertebrate genomes have been sequenced, and the rate at which genomic DNA information becomes available is rapidly accelerating. Gene duplication and gene loss events inherently limit the accuracy of orthology detection based on sequence similarity alone. Fully automated methods for orthology annotation do exist but often fail to identify individual members in cases of large gene families, or to distinguish missing data from traceable gene losses. This situation can be improved in many cases by including conserved synteny information.</p> <title>Results</title> <p>Here we present the <monospace>SynBlast</monospace> pipeline that is designed to construct and evaluate local synteny information. <monospace>SynBlast</monospace> uses the genomic region around a focal reference gene to retrieve candidates for homologous regions from a collection of target genomes and ranks them in accord with the available evidence for homology. The pipeline is intended as a tool to aid high quality manual annotation in particular in those cases where automatic procedures fail. We demonstrate how <monospace>SynBlast</monospace> is applied to retrieving orthologous and paralogous clusters using the vertebrate <italic>Hox </italic>and <italic>ParaHox </italic>clusters as examples.</p> <title>Software</title> <p>The <monospace>SynBlast</monospace> package written in <monospace>Perl</monospace> is available under the GNU General Public License at <ext-link ext-link-type="uri" xlink:href="http://www.bioinf.uni-leipzig.de/Software/SynBlast/"/>.</p>
<title>Availability and requirements</title> <p>The <monospace>SynBlast</monospace> package written in <monospace>Perl</monospace> is available under the GNU General Public License at <ext-link ext-link-type="uri" xlink:href="http://www.bioinf.uni-leipzig.de/Software/SynBlast/"/>. It requires a Unix-like environment and several add-on perl modules (<monospace>DBI, GD</monospace>) installed, as well as an installation of the <monospace>Ensembl Core</monospace> and <monospace>Ensembl Compara</monospace> APIs of the appropriate release version, see also the <monospace>SynBlast</monospace> tutorial [##UREF##3##20##] for installation issues. A local version of the NCBI BLAST suite, as well as the genome sequence databases of selected target species is needed to generate the genome-wide similarity search results as part of the pipeline.</p> <p><bold>Project name: </bold><monospace>SynBlast</monospace></p> <p><bold>Project home page: </bold><ext-link ext-link-type="uri" xlink:href="http://www.bioinf.uni-leipzig.de/Software/SynBlast/"/></p> <p><bold>Operating System: </bold>Unix/GNU Linux</p> <p><bold>Programming languages: </bold><monospace>Perl</monospace>, <monospace>bash</monospace></p> <p><bold>Other requirements: </bold>several add-on <monospace>perl</monospace> modules (<monospace>DBI, GD</monospace>), <monospace>Ensembl Core/Compara</monospace> API, <monospace>NCBI BLAST</monospace> (or similar).</p> <p><bold>License: </bold>GNU GPL version 2 or any later version</p> <title>Authors' contributions</title> <p>SJP and PFS designed the study, JL developed the <monospace>SynBlast</monospace> pipeline and tool, all authors closely collaborated in preparing the manuscript.</p>
<title>Acknowledgements</title> <p>We thank Jutta J. Roth, Sven Findeiß, and Stephan Bernhart for valuable comments and discussions. This work was supported in part by the <italic>Deutsche Forschungsgemeinschaft </italic>(DFG), Proj. No. STA850/6-1 and by the European Community FP-6 project "EMBIO" <ext-link ext-link-type="uri" xlink:href="http://www-embio.ch.cam.ac.uk/"/>.</p>
<fig position="float" id="F1"><label>Figure 1</label><caption><p><bold>SynBlast pipeline steps</bold>. (1) A focal protein coding gene of interest and its surrounding genes (within a certain flanking size) are selected as reference set. Protein sequences and genomic positional information are either compiled manually or retrieved from Ensembl using the tool getEnsemblProteins.pl. (2) tblastn searches of all reference proteins are performed against selected target genome databases. (3) The resulting blast hit tables are scanned for regions of possibly conserved gene content. These regions are stored in separate blast hit tables. (4) The resulting sets of possibly syntenically conserved blast hits are evaluated based on their sum of blast bit-scores obtained by means of a gene loci order alignment to the reference set. The final decision on orthology or paralogy of ranked syntenic blocks is left to the user.</p></caption></fig> <fig position="float" id="F2"><label>Figure 2</label><caption><p><bold>Dotplot graphic and detailed alignment graphic</bold>. The dotplot (top) visualizes the content of the alignment scoring matrix used to calculate the global alignment with free endgaps where the reference loci (p) and target loci (q) are arranged in rows and columns, respectively. Brightness of green color indicates the relative score value (rscore) of sequence similarity for a particular locus match. The dotted squares correspond to the optimal alignment path, which is shown in the alignment drawing (black box). Swapped orientation of a single target locus (w.r.t. a matching reference locus and the cluster orientation) is indicated by shaded boxes and opposite arrow orientation in the dotplot and alignment drawing, respectively. (Note that in this example the alignment path contains only aligned loci which share the same orientation.) The focal reference gene is highlighted by a light frame and orange color in the dotplot and alignment drawing, respectively.</p></caption></fig> <fig position="float" id="F3"><label>Figure 3</label><caption><p><bold>Evaluation of syntenic blocks</bold>. Panel <bold>(A) </bold>summarizes the mappings from query to target, panel <bold>(B) </bold>elaborates on particular cases. The query region (panel <bold>(A)</bold>, middle) contains a sequence of syntenic query loci (green), each representing one or more possibly overlapping query proteins <underline>(i)</underline>. Each candidate target region in the genomes of interest (panel <bold>(A) </bold>above and below the query locus), is identified by a set of blast hits, HSPs, (yellow). For each region, the following steps are performed: First, the set of query-specific HSPs is chained <underline>(ii)</underline>, resulting in one or more HSP chains that represent approximate protein models (small boxes). Filtering rules are applied that exclude individual HSPs from a chain for one of the following four reasons: <italic>(1) </italic>if the resulting chain exceeds the prescribed size limit for a locus (<bold>B1</bold>) [default: twice the length of the query locus]; <italic>(2) </italic>if it is inconsistent with a co-linear ordering of other HSPs in the chain (<bold>B2</bold>); <italic>(3) </italic>if it overlaps with another query interval by more than a specified threshold (<bold>B3</bold>) [default: 30aa]; and <italic>(4) </italic>if it lies on the opposite strand (<bold>B4</bold>). Chains of HSPs are excluded if they score below a threshold bit-score [default: 50] after filtering (<bold>B5</bold>). The retained HSP chains are grouped <underline>(iii)</underline> into target loci (big open boxes) that contain all HSP chains (irrespective of their orientation) with overlapping target intervals. For each target locus, only the highest scoring chain for each query protein is kept (<bold>B6</bold>). This results in a sequence of non-overlapping target loci (recall that one locus might represent one or more proteins) that can be aligned <underline>(iv)</underline> with the sequence of query loci in a gene order alignment (gray shading, optimal assignments are shown by darker shading). The score of this alignment is then used to rank the region relative to other syntenic target regions.</p></caption></fig> <fig position="float" id="F4"><label>Figure 4</label><caption><p><bold>Overview on pipeline results for vertebrate Hox clusters</bold>. SynBlast results and manually extracted orthologous cluster positions and identities for selected vertebrate species are listed. Unless otherwise indicated, positions correspond to assigned blast hits' intervals from <italic>Hox1 </italic>to <italic>Hox13</italic>/<italic>Evx </italic>hits in gene order alignment. Cluster orientation is w.r.t. the human reference clusters, which are HOXA9_ENSG00000078399_5e5; HOXB9_ENSG00000170689_2e5; HOXC9_ENSG00000180806_3e5; HOXD9_ENSG00000128709_5e5. Unassigned loci from the reference may be due to overlaps of chained HSPs. A '*' indicates loci that are absent in agreement with the literature [##REF##15972462##45##]. Data for Ensembl release 42 (Dec 2006).</p></caption></fig> <fig position="float" id="F5"><label>Figure 5</label><caption><p><bold>Schematic representation of genes flanking the Cdx gene locus in the human ParaHox clusters</bold>. Only linked genes relevant for the interpretation of the <italic>SynBlast </italic>output are shown.</p></caption></fig> <fig position="float" id="F6"><label>Figure 6</label><caption><p><bold>ParaHox example application</bold>. SynBlast was used to determine the four pairs of paralogous regions generated by the fish-specific genome duplication from the four gnathostome <italic>ParaHox </italic>regions. We show alignment dot-plots for the high-ranking hits (according to the gene order alignment score and <italic>logRatioSum </italic>score (in brackets)) of the four query regions against the zebrafish genome (Zv7, Ensembl release 46, Aug 2007). Parameters for the synteny filtering step were <italic>N </italic>= 1, <italic>L </italic>= 2. See text for more details.</p></caption></fig>
<table-wrap position="float" id="T1"><label>Table 1</label><caption><p><monospace>SynBlast</monospace> results for <italic>Danio rerio</italic>, <monospace>Ensembl</monospace> release 46 (Zv7), with the human <italic>Hox </italic>clusters as query.</p></caption><table frame="hsides" rules="groups"><thead><tr><td align="right">Reference</td><td align="right"><italic>DrAa </italic><break/>chr.19 <break/>10.5 M</td><td align="right"><italic>DrAb </italic><break/>chr.16 <break/>16 M</td><td align="right"><italic>DrBa </italic><break/>chr.3 <break/>23 M</td><td align="right"><italic>DrBb </italic><break/>chr.12 <break/>26.5 M</td><td align="right"><italic>DrCa1 </italic><break/>chr.23 <break/>33.7 M</td><td align="right"><italic>DrCa2 </italic><break/>chr.23 <break/>35.2 M</td><td align="right"><italic>DrCb </italic><break/>chr.11 <break/>0.6 M</td><td align="right"><italic>DrDa </italic><break/>chr.9 <break/>2 M</td></tr></thead><tbody><tr><td align="right"><italic>HsA</italic></td><td align="right"><bold>2.58</bold></td><td align="right"><bold>3.29</bold></td><td align="right">-0.76</td><td align="right">-0.39</td><td align="right">-1.98</td><td align="right">-1.98</td><td align="right">-0.4</td><td align="right">-0.74</td></tr><tr><td align="right"><italic>HOXA9</italic></td><td align="right"><bold>5581</bold></td><td align="right"><bold>4073</bold></td><td align="right">4690</td><td align="right">2119</td><td align="right">3322</td><td align="right">3318</td><td align="right">1490</td><td align="right">3269</td></tr><tr><td align="right">chr.7</td><td align="right"><bold>2/1</bold></td><td align="right"><bold>1/3</bold></td><td align="right">7/2</td><td align="right">3/7</td><td align="right">9/4</td><td align="right">10/5</td><td align="right">4/8</td><td align="right">6/6</td></tr><tr><td/><td/><td/><td/><td/><td/><td/><td/><td/></tr><tr><td align="right"><italic>HsB</italic></td><td align="right">-1.14</td><td align="right">-0.01</td><td align="right"><bold>3.13</bold></td><td align="right"><bold>0.42</bold></td><td align="right">-1.66</td><td align="right">-1.69</td><td align="right">-0.64</td><td align="right">-0.48</td></tr><tr><td align="right"><italic>HOXB9</italic></td><td align="right">2702</td><td align="right">1342</td><td align="right"><bold>6201</bold></td><td align="right"><bold>1647</bold></td><td align="right">3008</td><td align="right">2982</td><td align="right">1003</td><td align="right">1678</td></tr><tr><td align="right">chr.17</td><td align="right">6/4</td><td align="right">3/7</td><td align="right"><bold>1/1</bold></td><td align="right"><bold>2/6</bold></td><td align="right">7/2</td><td align="right">8/3</td><td align="right">5/8</td><td align="right">4/5</td></tr><tr><td/><td/><td/><td/><td/><td/><td/><td/><td/></tr><tr><td align="right"><italic>HsC</italic></td><td align="right">-0.89</td><td align="right">-1.51</td><td align="right">-0.26</td><td align="right">-0.34</td><td align="right"><bold>6.44</bold></td><td align="right"><bold>7.58</bold></td><td align="right"><bold>0.22</bold></td><td align="right">-2.51</td></tr><tr><td align="right"><italic>HOXC9</italic></td><td align="right">2361</td><td align="right">2323</td><td align="right">3108</td><td align="right">1346</td><td align="right"><bold>8687</bold></td><td align="right"><bold>6537</bold></td><td align="right"><bold>4150</bold></td><td align="right">3798</td></tr><tr><td align="right">chr.12</td><td align="right">7/6</td><td align="right">8/7</td><td align="right">5/5</td><td align="right">6/8</td><td align="right"><bold>2/1</bold></td><td align="right"><bold>1/2</bold></td><td align="right"><bold>3/3</bold></td><td align="right">9/4</td></tr><tr><td/><td/><td/><td/><td/><td/><td/><td/><td/></tr><tr><td align="right"><italic>HsD</italic></td><td align="right">-0.92</td><td align="right">-0.63</td><td align="right">-0.85</td><td align="right">-0.6</td><td align="right">-0.41</td><td align="right">-0.41</td><td align="right">-0.71</td><td align="right"><bold>1.76</bold></td></tr><tr><td align="right"><italic>HOXD9</italic></td><td align="right">2799</td><td align="right">1811</td><td align="right">2660</td><td align="right">871</td><td align="right">3017</td><td align="right">3013</td><td align="right">1303</td><td align="right"><bold>4326</bold></td></tr><tr><td align="right">chr.2</td><td align="right">8/4</td><td align="right">5/6</td><td align="right">7/5</td><td align="right">4/8</td><td align="right">3/2</td><td align="right">2/3</td><td align="right">6/7</td><td align="right"><bold>1/1</bold></td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T2"><label>Table 2</label><caption><p>Incomplete and erroneous <monospace>Ensembl Compara</monospace> orthology annotations for vertebrate <italic>Hox </italic>cluster loci.</p></caption><table frame="hsides" rules="groups"><thead><tr><td align="left">Ref. cluster</td><td align="center" colspan="3">Genes</td><td align="center" colspan="2">Clusters</td></tr><tr><td colspan="1"><hr/></td><td colspan="3"><hr/></td><td colspan="2"><hr/></td></tr><tr><td/><td align="right">Δ</td><td align="right"><italic>β</italic></td><td align="right"><italic>n</italic></td><td align="right"><italic>M</italic></td><td align="right"><italic>K</italic></td></tr></thead><tbody><tr><td align="left"><italic>HoxA</italic></td><td align="right">11</td><td align="right">2</td><td align="right">148</td><td align="right">5</td><td align="right">16</td></tr><tr><td align="left"><italic>HoxB</italic></td><td align="right">25</td><td align="right">2</td><td align="right">118</td><td align="right">12</td><td align="right">16</td></tr><tr><td align="left"><italic>HoxC</italic></td><td align="right">11</td><td align="right">2</td><td align="right">88</td><td align="right">6</td><td align="right">10</td></tr><tr><td align="left"><italic>HoxD</italic></td><td align="right">20</td><td align="right">7</td><td align="right">113</td><td align="right">13</td><td align="right">16</td></tr></tbody></table></table-wrap> <table-wrap position="float" id="T3"><label>Table 3</label><caption><p><monospace>SynBlast</monospace> results for <italic>Danio rerio</italic>, <monospace>Ensembl</monospace> release 46 (Aug 2007), Zv7 assembly with the human <italic>ParaHox </italic>clusters as query.</p></caption><table frame="hsides" rules="groups"><thead><tr><td align="right">Reference</td><td align="right"><italic>DrA1 </italic><break/>chr.24 <break/>20 M <break/><italic>pdx1</italic></td><td align="right"><italic>DrA2 </italic><break/>chr.5 <break/>60 M <break/><italic>gsh1</italic></td><td align="right"><italic>DrB </italic><break/>chr.7 <break/>50 M</td><td align="right"><italic>DrB1 </italic><break/>chr.14 <break/>37 M <break/><italic>cdx4</italic></td><td align="right"><italic>DrC1 </italic><break/>chr.20 <break/>20 M <break/><italic>gsh2</italic></td><td align="right"><italic>DrC2 </italic><break/>chr.1 <break/>10 M</td><td align="right"><italic>DrD1</italic>? <break/>chr.14 <break/>53 M</td><td align="right"><italic>DrD1</italic>? <break/>chr.14 <break/>22 M</td><td align="right"><italic>DrD1 </italic><break/>chr.14 <break/>25 M <break/><italic>cdx1a</italic></td><td align="right"><italic>DrD2 </italic><break/>chr.21 <break/>43 M <break/><italic>CDX1</italic></td><td align="right"><italic>DrD2</italic>? <break/>chr.21 <break/>36 M</td></tr></thead><tbody><tr><td align="right"><italic>HsA/C1</italic></td><td align="right"><bold>2.49</bold></td><td align="right"><bold>0.25</bold></td><td align="right">0.52</td><td align="right">0.05</td><td align="right">-0.65</td><td align="right">-</td><td align="right">-</td><td align="right">-</td><td align="right">1.3</td><td align="right">-</td><td align="right">(0.13)</td></tr><tr><td align="right"><italic>CDX2</italic></td><td align="right"><bold>8343</bold></td><td align="right"><bold>2291</bold></td><td align="right">1605</td><td align="right">1537</td><td align="right">1922</td><td align="right">-</td><td align="right">-</td><td align="right">-</td><td align="right">1757</td><td align="right">-</td><td align="right">(1112)</td></tr><tr><td align="right">chr.13</td><td align="right"><bold>2/1</bold></td><td align="right"><bold>7/2</bold></td><td align="right">5/5</td><td align="right">9/6</td><td align="right">40/3</td><td align="right">-</td><td align="right">-</td><td align="right">-</td><td align="right">3/4</td><td align="right">-</td><td align="right">(8/8)</td></tr><tr><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/></tr><tr><td align="right"><italic>HsB/C2</italic></td><td align="right">(-0.41)</td><td align="right">(-0.7)</td><td align="right"><bold>2.53</bold></td><td align="right"><bold>0.47</bold></td><td align="right">(-0.04)</td><td align="right">-0.02</td><td align="right">-</td><td align="right">-</td><td align="right">-0.75</td><td align="right">-0.14</td><td align="right">-</td></tr><tr><td align="right"><italic>CDX4</italic></td><td align="right">(237)</td><td align="right">(139)</td><td align="right"><bold>2934</bold></td><td align="right"><bold>1192</bold></td><td align="right">(114)</td><td align="right">669</td><td align="right">-</td><td align="right">-</td><td align="right">543</td><td align="right">183</td><td align="right">-</td></tr><tr><td align="right">chr.X</td><td align="right">(19/25)</td><td align="right">(31/38)</td><td align="right"><bold>1/1</bold></td><td align="right"><bold>3/2</bold></td><td align="right">(7/41)</td><td align="right">5/7</td><td align="right">-</td><td align="right">-</td><td align="right">34/10</td><td align="right">12/32</td><td align="right">-</td></tr><tr><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/></tr><tr><td align="right"><italic>HsC/C3</italic></td><td align="right">-1.47</td><td align="right">-1.56</td><td align="right">-0.33</td><td align="right">-2.52</td><td align="right"><bold>3.23</bold></td><td align="right"><bold>0.91</bold></td><td align="right">-</td><td align="right">-</td><td align="right">-0.46</td><td align="right">-</td><td align="right">(-0.37)</td></tr><tr><td align="right"><italic>GSH2</italic></td><td align="right">1478</td><td align="right">507</td><td align="right">1424</td><td align="right">1595</td><td align="right"><bold>4756</bold></td><td align="right"><bold>1880</bold></td><td align="right">-</td><td align="right">-</td><td align="right">469</td><td align="right">-</td><td align="right">(488)</td></tr><tr><td align="right">chr.4</td><td align="right">54/4</td><td align="right">55/7</td><td align="right">19/5</td><td align="right">56/3</td><td align="right"><bold>1/1</bold></td><td align="right"><bold>3/2</bold></td><td align="right">-</td><td align="right">-</td><td align="right">26/9</td><td align="right">-</td><td align="right">(23/8)</td></tr><tr><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/><td/></tr><tr><td align="right"><italic>HsD/C4</italic></td><td align="right">-0.6</td><td align="right">(-2.77)</td><td align="right">(-3.57)</td><td align="right">-3.44</td><td align="right">-3.31</td><td align="right">(-0.06)</td><td align="right"><bold>0.79</bold></td><td align="right"><bold>0.03</bold></td><td align="right"><bold>-0.41</bold></td><td align="right"><bold>0.18</bold></td><td align="right"><bold>5.27</bold></td></tr><tr><td align="right"><italic>CDX1</italic></td><td align="right">439</td><td align="right">(254)</td><td align="right">(2238)</td><td align="right">953</td><td align="right">940</td><td align="right">(991)</td><td align="right"><bold>1796</bold></td><td align="right"><bold>1514</bold></td><td align="right"><bold>846</bold></td><td align="right"><bold>1107</bold></td><td align="right"><bold>2550</bold></td></tr><tr><td align="right">chr.5</td><td align="right">13/41</td><td align="right">(24/57)</td><td align="right">(42/2)</td><td align="right">41/12</td><td align="right">37/13</td><td align="right">(7/11)</td><td align="right"><bold>2/4</bold></td><td align="right"><bold>6/5</bold></td><td align="right"><bold>11/16</bold></td><td align="right"><bold>4/9</bold></td><td align="right"><bold>1/1</bold></td></tr></tbody></table></table-wrap>
<disp-formula id="bmcM1"><label>(1)</label><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" id="M1" name="1471-2105-9-351-i1" overflow="scroll"><mml:semantics><mml:mrow><mml:mi>S</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>q</mml:mi><mml:mo>,</mml:mo><mml:mi>t</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mrow><mml:mo>{</mml:mo><mml:mrow><mml:mtable columnalign="left"><mml:mtr columnalign="left"><mml:mtd columnalign="left"><mml:mrow><mml:mfrac><mml:mn>1</mml:mn><mml:mrow><mml:msub><mml:mi>ν</mml:mi><mml:mrow><mml:mi>q</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:msub></mml:mrow></mml:mfrac><mml:mstyle displaystyle="true"><mml:munder><mml:mo>∑</mml:mo><mml:mrow><mml:mi>s</mml:mi><mml:mo>∈</mml:mo><mml:mi>q</mml:mi></mml:mrow></mml:munder><mml:mrow><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mi>s</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>,</mml:mo></mml:mrow></mml:mstyle></mml:mrow></mml:mtd><mml:mtd columnalign="left"><mml:mrow><mml:mtext>if </mml:mtext><mml:msub><mml:mi>ν</mml:mi><mml:mrow><mml:mi>q</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:msub><mml:mo>≥</mml:mo><mml:mn>1</mml:mn></mml:mrow></mml:mtd></mml:mtr><mml:mtr columnalign="left"><mml:mtd columnalign="left"><mml:mrow><mml:mo>−</mml:mo><mml:mi>∞</mml:mi></mml:mrow></mml:mtd><mml:mtd columnalign="left"><mml:mrow><mml:mtext>otherwise</mml:mtext></mml:mrow></mml:mtd></mml:mtr></mml:mtable></mml:mrow></mml:mrow></mml:mrow></mml:semantics></mml:math></disp-formula> <disp-formula id="bmcM2"><label>(2)</label><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" id="M2" name="1471-2105-9-351-i2" overflow="scroll"><mml:semantics><mml:mrow><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mtext>intra</mml:mtext></mml:mrow></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>q</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>−</mml:mo><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>q</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mrow><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>q</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula> <disp-formula id="bmcM3"><label>(3)</label><mml:math xmlns:mml="http://www.w3.org/1998/Math/MathML" id="M3" name="1471-2105-9-351-i3" overflow="scroll"><mml:semantics><mml:mrow><mml:msub><mml:mi>S</mml:mi><mml:mrow><mml:mtext>inter</mml:mtext></mml:mrow></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mi>s</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>q</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo><mml:mo>−</mml:mo><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>t</mml:mi><mml:mi>s</mml:mi></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow><mml:mrow><mml:mi>b</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:mi>s</mml:mi><mml:mo>,</mml:mo><mml:msub><mml:mi>q</mml:mi><mml:mrow><mml:mi>s</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:mrow></mml:semantics></mml:math></disp-formula>
<table-wrap-foot><p>The <italic>logRatioSum </italic>score, the gene order alignment score, and the corresponding ranks are given. Putative orthologs are depicted in bold. In combination, the two scores provide the best means to rank orthologous loci at the top. In most cases, identification of orthologous regions is unambiguous. For completeness we list both copies of the artifactually duplicated DrCa cluster of chr.23.</p></table-wrap-foot> <table-wrap-foot><p>We list the total number <italic>n </italic>of <italic>Hox </italic>and <italic>Evx </italic>genes in the dataset; the number Δ of <italic>Hox </italic>and <italic>Evx </italic>gene orthology assignments (see Figure 4 that are well-supported (query coverage &gt; 30%) by <monospace>SynBlast</monospace> but that are missing in the <monospace>Compara</monospace> annotation; the number <italic>β </italic>of well-supported assignments with incorrect annotations in <monospace>Compara</monospace> (paralog). We furthermore list the number <italic>M </italic>of the <italic>K Hox </italic>clusters in the dataset which contain apparently missing and/or erroneous <monospace>Compara</monospace> annotations. All data refer to <monospace>Ensembl</monospace> release 42 (Dec 2006).</p></table-wrap-foot> <table-wrap-foot><p>The <italic>logRatioSum </italic>score, the gene order alignment score, and the corresponding ranks are given. Putative orthologs are depicted in bold. In combination, the two scores provide the best means to rank orthologous loci at the top. Numbers in parentheses indicate that the target region (column) is only approximately matched, and/or that only a single query gene was found. See text for more detail.</p></table-wrap-foot>
<graphic xlink:href="1471-2105-9-351-1"/> <graphic xlink:href="1471-2105-9-351-2"/> <graphic xlink:href="1471-2105-9-351-3"/> <graphic xlink:href="1471-2105-9-351-4"/> <graphic xlink:href="1471-2105-9-351-5"/> <graphic xlink:href="1471-2105-9-351-6"/>
[{"surname": ["Kamvysselis", "Patterson", "Birren", "Berger", "Lander", "Vingron M, Istrail S, Pevzner P, Waterman WM, Miller"], "given-names": ["M", "N", "B", "B", "ES"], "article-title": ["Whole-genome comparative annotation and regulatory motif discovery in multiple yeast species"], "source": ["Proceedings of the seventh annual international conference on Research in computational molecular biology"], "year": ["2003"], "publisher-name": ["ACM"], "fpage": ["157"], "lpage": ["166"]}, {"surname": ["El-Mabrouk", "Sankoff"], "given-names": ["N", "D"], "article-title": ["The Reconstruction of Doubled Genomes"], "source": ["SIAM J Comput"], "year": ["2003"], "volume": ["32"], "fpage": ["754"], "lpage": ["792"]}, {"surname": ["Choi", "Zheng", "Zhu", "Sankoff"], "given-names": ["V", "C", "Q", "D"], "article-title": ["Algorithms for the Extraction of Synteny Blocks from Comparative Maps"], "source": ["WABI: Algorithms in Bioinformatics, 7th International Workshop, Volume 4645 of Lecture Notes in Computer Science"], "year": ["2007"], "publisher-name": ["Heidelberg: Springer"], "fpage": ["277"], "lpage": ["288"]}, {"article-title": ["Online Supplemental Material"]}, {"surname": ["Holland"], "given-names": ["PWH"], "article-title": ["Beyond the Hox: How widespread is homeobox gene clustering?"], "source": ["J Anatomy"], "year": ["2001"], "volume": ["199"], "fpage": ["13"], "lpage": ["23"]}]
BMC Bioinformatics. 2008 Aug 24; 9:351