SwissOrthology Interactive Guide

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>SwissOrthology Interactive Guide</title> <meta name="description" content="Interactive guide how to choose the most appropriate orthology resource"> <meta name="viewport" content="width=device-width, initial-scale=1"> <link rel='icon' href="/static/favicon.ico" type='image/x-icon'/> <link rel="stylesheet" href="//stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css" integrity="sha384-ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2MZw1T" crossorigin="anonymous"> <link href="//fonts.googleapis.com/icon?family=Material+Icons|Material+Icons+Outlined|Signika:300,400,600,700|Open+Sans:300,400,500,700" rel="stylesheet"> <link rel="stylesheet" href="/static/css/style.css"/>  <script> var _paq = window._paq = window._paq || []; /* tracker methods like "setCustomDimension" should be called before "trackPageView" */ _paq.push(['trackPageView']); _paq.push(['enableLinkTracking']); (function() { var u="https://matomo.sib.swiss/"; _paq.push(['setTrackerUrl', u+'matomo.php']); _paq.push(['setSiteId', '53']); var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0]; g.async=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s); })(); </script>  </head> <body> <nav class="navbar navbar-expand-md navbar-light bg-light bg-lightest"> <div class="container"> <a class="sib-logo" href="https://www.sib.swiss" target="_blank"> <img src="/static/image/logo-sib.png" alt="Logo SIB" /> </a> <a class="navbar-brand" href="/service/search"> <img alt="SwissOrthology" src="/static/image/logo-swiss-orthology.svg"> </a>  <div id="navbarNav"> <ul class="navbar-nav ml-auto"> <li class="nav-item"> <a class="nav-link" href="/service/search"> <img src="/static/image/home.svg"> Home <span class="sr-only">(current)</span> </a> </li> <li class="nav-item"> <a class="nav-link" href="/service/about"> <img src="/static/image/info.svg"> About </a> </li> <li class="nav-item"> <a class="nav-link" href="/service/guide"> <img src="/static/image/book-open.svg"> Guide </a> </li> <li class="nav-item"> <a class="nav-link" href="/service/events"> <img src="/static/image/calendar.svg"> Events </a> </li> </ul> </div> </div> </nav> <div id="guide" class="content-container"> <div class="container"> <h1>SwissOrthology Guide</h1> <p><a href="#" id="toggleAccordionShow">Expand all</a> / <a href="#" onclick="location.reload();">Reset</a> </p> <div id="accordion"> <div class="card" id="welcome"> <div class="card-header" id="guide_card_h1"> <h5 class="mb-0"> <button class="btn btn-link" data-toggle="collapse" data-target="#guide_card_b1" aria-expanded="true" aria-controls="guide_card_h1"> Welcome </button> </h5> </div> <div id="guide_card_b1" class="collapse show" aria-labelledby="guide_card_h1" data-parent="#accordion"> <div class="card-body"> <div class="card-title"> <h2>Welcome</h2> </div> <p class="card-text">Welcome to the SwissOrthology Flowchart. Here, you can interactively find information to help guide you to choose between different SwissOrthology tools. For some applications, either OMA or OrthoDB is better suited. For others, both orthology resources are fine. In the flowchart, you can interactively decide which resource to use based on one of the following criteria: </p> <ul> <li><a href="#species_types" data-toggle="collapse" data-target="#species_types .collapse" aria-expanded="false" aria-controls="species_types">Type of species</a></li> <li><a href="#analysis_type" data-toggle="collapse" data-target="#analysis_type .collapse" aria-expanded="false" aria-controls="analysis_type">Type of analysis</a></li>  <li><a a href="output_data_format" data-toggle="collapse" data-target="#output_data_format .collapse" aria-expanded="false" aria-controls="output_data_format">Format of data</a></li> </ul> <p>Click on one of the above to begin exploring how SwissOrthology can work for you.</p> </div> </div> </div> <div class="card" id="species_types"> <div class="card-header" id="guide_card_h2"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b2" aria-expanded="false" aria-controls="guide_card_b2"> Type of species </button> </h5> </div> <div id="guide_card_b2" class="collapse" aria-labelledby="guide_card_h2" data-parent="#accordion"> <div class="card-body"> <div class="card-title"> <h2>Type of species</h2> </div> <ul> <li><a href="#species_by_domain" data-toggle="collapse" data-target="#species_by_domain .collapse" aria-expanded="false" aria-controls="species_by_domain"> I'm interested in a certain domain of species.</a></li> <li><a href="#species_own_analysis" data-toggle="collapse" data-target="#species_own_analysis .collapse" aria-expanded="false" aria-controls="species_own_analysis"> I’m interested in using my own sequenced genomes.</a> </li> </ul> </div> </div> </div> <div class="card" id="analysis_type"> <div class="card-header" id="guide_card_h3"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b3" aria-expanded="false" aria-controls="guide_card_b3"> Type of analysis </button> </h5> </div> <div id="guide_card_b3" class="collapse" aria-labelledby="guide_card_h3" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title"> Type of analysis </h2> <ul> <li><a href="#orthologs_in_set_of_species" data-toggle="collapse" data-target="#orthologs_in_set_of_species .collapse" aria-expanded="false" aria-controls="orthologs_in_set_of_species"> Identify all orthologs of a gene in a given set of organisms</a></li> <li><a href="#markers_for_speciestree" data-toggle="collapse" data-target="#markers_for_speciestree .collapse" aria-expanded="false" aria-controls="markers_for_speciestree"> Identify orthologous marker genes to infer a species tree</a> </li> <li><a href="#build_a_gene_tree" data-toggle="collapse" data-target="#build_a_gene_tree .collapse" aria-expanded="false" aria-controls="build_a_gene_tree">Build a gene tree</a> </li> <li><a href="#history_of_gene_family" data-toggle="collapse" data-target="#history_of_gene_family .collapse" aria-expanded="false" aria-controls="history_of_gene_family"> Trace the evolutionary history of a gene family</a> </li> <li><a href="#synteny" data-toggle="collapse" data-target="#synteny .collapse" aria-expanded="false" aria-controls="synteny">Find the synteny between two genomes</a></li> <li><a href="#domain" data-toggle="collapse" data-target="#domain .collapse" aria-expanded="false" aria-controls="domain">Analysis on domains</a></li> <li><a href="#go" data-toggle="collapse" data-target="#go .collapse" aria-expanded="false" aria-controls="guide_card_b24">Gene Ontology</a></li> <li>Other</li> </ul> </div> </div> </div>  <div class="card" id="species_by_domain"> <div class="card-header" id="guide_card_h5"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b5" aria-expanded="false" aria-controls="guide_card_b5"> Species by domain </button> </h5> </div> <div id="guide_card_b5" class="collapse" aria-labelledby="guide_card_h5" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Species by domain</h2> <ul> <li><a href="#common_domains" data-toggle="collapse" data-target="#common_domains .collapse" aria-expanded="false" aria-controls="common_domains">Eukaryota</a></li> <li><a href="#common_domains" data-toggle="collapse" data-target="#common_domains .collapse" aria-expanded="false" aria-controls="common_domains">Archaea</a></li> <li><a href="#common_domains" data-toggle="collapse" data-target="#common_domains .collapse" aria-expanded="false" aria-controls="common_domains">Bacteria</a></li> <li><a href="#orthodb_species" data-toggle="collapse" data-target="#orthodb_species .collapse" aria-expanded="false" aria-controls="orthodb_species">Viruses</a></li> </ul> </div> </div> </div> <div class="card" id="common_domains"> <div class="card-header" id="guide_card_h6"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b6" aria-expanded="false" aria-controls="guide_card_b6"> Species in OMA and OrthoDB </button> </h5> </div> <div id="guide_card_b6" class="collapse" aria-labelledby="guide_card_h6" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Species in OMA and OrthoDB</h2> <p class="card-text"><strong>Both OMA and OrthoDB predict orthologs for a diversity of animal, plant, fungal, and bacterial genomes.</strong></p> <p class="card-text">OMA predicts orthologs over many species, including animal, fungal, plant, archaea, bacteria. The latest OMA release (Aug 2020) covers <strong>2326 species</strong>. OMA also infers orthologs across kingdoms. A full list of species and their update dates is available on the <a href="https://omabrowser.org/oma/release/">release information page</a>.</p> <p>OrthoDB’s latest release predicts orthologs among <strong>7275 species</strong> and <strong>6488 viruses</strong>: 448 metazoan, 117 plant, 549 fungal, 148 protist, 5609 bacterial, 404 archaeal genomes, and 6488 viruses, picking up the best sequenced and annotated representatives for each species or operational taxonomic unit. <a href="https://www.orthodb.org/?page=species_list">The latest species list can be found here.</a></p> <p class="card-text">Additional information:</p> <ul> <li>OrthoDB additionally infers orthologs among viral genomes.</li> <li>Don’t find your species? <a href="https://omabrowser.org/oma/suggestion/genome/">You can suggest it for the next OMA release</a>. </li> <li>OrthoDB offers the possibility to analyse your genome of interest online by mapping to existing orthologous groups. </li> </ul> </div> </div> </div> <div class="card" id="orthodb_species"> <div class="card-header" id="guide_card_h7"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b7" aria-expanded="true" aria-controls="guide_card_b7"> Species in OrthoDB </button> </h5> </div> <div id="guide_card_b7" class="collapse" aria-labelledby="guide_card_h7" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Species in OrthoDB</h2> <p class="card-text">In addition to the 7275 eukaryotic, bacteria, and archaea species, OrthoDB v10 covers <strong>6488 viruses</strong>. </p> </div> </div> </div> <div class="card" id="species_own_analysis"> <div class="card-header" id="guide_card_h8"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b8" aria-expanded="false" aria-controls="guide_card_b8"> Using your own species in analysis </button> </h5> </div> <div id="guide_card_b8" class="collapse" aria-labelledby="guide_card_h8" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Using your own species in analysis</h2> <p class="card-text"><strong>Both OMA and OrthoDB allow for using your own sequenced genomes as input data.</strong></p> <p class="card-text">The OMA pipeline can run on custom genomic/transcriptomic data using the <a href="https://omabrowser.org/standalone">OMA standalone software</a>, and it is even possible to combine precomputed data with custom data by <a href="https://omabrowser.org/export">exporting parts of the OMA database</a>, which saves time on the all-against-all step.</p> <p class="card-text">The OrthoDB software is also freely available from <a href="https://www.orthodb.org/software">https://www.orthodb.org/software</a>.</p> <p class="card-text">Additionally, in OrthoDB users can upload and analyze online their genome of interest. As many genomes are newly sequenced and analysis is needed for the first publication, OrthoDB has the possibility for users to create a registered account. After uploading the data, the analysis is performed automatically. The registered user can then see the OrthoDB interface with the new data and benefit from annotations of related orthologous groups in OrthoDB and other dababases.</p> </div> </div> </div> <div class="card" id="orthologs_in_set_of_species"> <div class="card-header" id="guide_card_h9"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b9" aria-expanded="false" aria-controls="guide_card_b9"> Identify all orthologs of a gene in a given set of organisms </button> </h5> </div> <div id="guide_card_b9" class="collapse" aria-labelledby="guide_card_h9" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Identify all orthologs of a gene in a given set of organisms</h2> <ul> <li><a href="#pairwise_orthologs" data-toggle="collapse" data-target="#pairwise_orthologs .collapse" aria-expanded="false" aria-controls="pairwise_orthologs">I want pairwise orthologs between my favorite gene and specific genomes of interest</a></li> <li><a href="#orthologous_groups" data-toggle="collapse" data-target="#orthologous_groups .collapse" aria-expanded="false" aria-controls="orthologous_groups">I want orthologous groups (clusters of genes from multiple genomes)</a></li> </ul> <p class="card-text">Additional information:</p> <ul> <li>Do you want to include <a href="#paralogs" data-toggle="collapse" data-target="#paralogs .collapse" aria-expanded="false" aria-controls="paralogs">paralogs</a>? </li> <li>Do you want to include <a href="#homoeologs" data-toggle="collapse" data-target="#homoeologs .collapse" aria-expanded="false" aria-controls="homoeologs">homoeologs</a>? </li> </ul> </div> </div> </div> <div class="card" id="pairwise_orthologs"> <div class="card-header" id="guide_card_h10"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b10" aria-expanded="false" aria-controls="guide_card_b10"> Pairwise orthologs </button> </h5> </div> <div id="guide_card_b10" class="collapse" aria-labelledby="guide_card_h10" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Pairwise orthologs</h2> <p class="card-text">The OMA Browser reports different subtypes of orthologous and paralogous relationships.</p> <p class="card-text">Evolutionary relationships are often described as pairwise relationships. <strong>Pairwise orthologs</strong> in OMA are those which are inferred at the base of the OMA algorithm. They are formed by looking for the evolutionarily closest protein sequences between two genomes within a confidence interval.</p> <p class="card-text">Users can find a list of all ortholog pairs for a given gene of interest by searching for their gene on the omabrowser. See the <a href="https://omabrowser.org/oma/uses/">OMA Manual: Orthologs of a Given Gene</a> on how to find pairwise orthologs, HOG-induced orthologs, and OMA-induced orthologs.</p> <p>Alternatively, users can download a list of <em>all</em> predicted ortholog pairs between <a href="https://omabrowser.org/oma/genomePW">genomes of interest</a>. The result is returned as a tab-separated text file.</p> https://omabrowser.org/oma/uses/ <p>Additional information:</p> <ul> <li><a href="#type_diff_oma" data-toggle="collapse" data-target="#type_diff_oma .collapse" aria-expanded="false" aria-controls="type_diff_oma"> How are pairwise orthologs related to hierarchical orthologous groups?</a></li> <li><a href="#One_to_one_vs_many_orthologs" data-toggle="collapse" data-target="#One_to_one_vs_many_orthologs .collapse" aria-expanded="false" aria-controls="One_to_one_vs_many_orthologs"> What is the difference between 1:1 and 1:many orthologs?</a></li> <li><a href="https://omabrowser.org/oma/type/">I want to distinguish between 1:1, 1:many, or many:many pairwise orthologs</a></li> </ul> </div> </div> </div> <div class="card" id="One_to_one_vs_many_orthologs"> <div class="card-header" id="guide_card_h10b"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b10b" aria-expanded="false" aria-controls="guide_card_b10b"> 1-to-1 vs. 1-to-many orthologs </button> </h5> </div> <div id="guide_card_b10b" class="collapse" aria-labelledby="guide_card_h10b" data-parent="#accordion"> <div class="card-body"> <p class="card-text">OMA reports the relationship cardinality of the pairwise orthologs, which reflects the level of co-orthology, or the degree of duplications which one or both of the orthologs has undergone. One-to-one (1:1) pairwise orthology means that both genes in the pair have only one ortholog in the other species. A one-to-many relationship (1:m) means that the gene of interest has more than one ortholog in the other species. This implies that the gene was duplicated in an ancestor of the other species, but after the speciation event. A many-to-many (m:m) relationship means both orthologs underwent lineage-specific duplications.</p> <p class="card-text">OrthoDB reports the phyletic profile for each ortholog group. It is a summary of the ortholog presence (from universal to species-specific) and copy-numbers (single/multi-copy counts). For example, orthologous Group 125711at40674 at Mammalia level (functionally annotated as Cellular tumor antigen p53) contains 116 genes in 109 species (out of 111). It is single copy in 102 species, and multi-copy in 7 species.</p> </div> </div> </div> <div class="card" id="orthologous_groups"> <div class="card-header" id="guide_card_h11"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b11" aria-expanded="false" aria-controls="guide_card_b11"> Orthologous groups </button> </h5> </div> <div id="guide_card_b11" class="collapse" aria-labelledby="guide_card_h11" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Orthologous groups</h2> <p class="card-text summary"> <strong>Both OMA and OrthoDB report groups of orthologous genes.</strong> </p> <p class="card-text">OrthoDB was the first database to introduce <strong>hierarchical orthologous groups</strong>. The concept of orthologous groups is inherently hierarchical, as each phylogenetic clade or subclade of species has a distinct common ancestor. The ortholog delineation procedure is applied at each major radiation of the species taxonomy to produce more finely resolved groups of closely related species and to allow users to select the most relevant level.</p> <p class="card-text">OMA also reports Hierarchical Orthologous Groups or <strong>HOGs</strong>. HOGs are sets of genes that are defined with respect to particular taxonomic ranges of interest. They group genes that have descended from a single common ancestral genes in that taxonomic range. Currently, HOGs can be accessed by searching for a specific HOG id or by a member gene of the group. To get to a HOG through one of its member gene pages, click on the “Groups” tab in the upper right-hand corner. </p> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Accessing HOGs and OMA Groups" src="/static/image/guide/access_the_data_groups-1.png"> <figcaption class="figure-caption">Example of a group being accessed by the gene-centric page of one of its member genes.</figcaption> </figure> <p class="card-text"> For more detailed information, see <a href="https://omabrowser.org/oma/uses/">Access the OMA Data: Group-centric pages</a>. Additionally, all the HOGs from the <a href="https://omabrowser.org/oma/current/">current release</a> can be downloaded in OrthoXML format and parsed and analysed with <a href="https://github.com/DessimozLab/pyham">pyham</a>.</p> <p class="card-text">Another type of orthologous group that OMA reports are called <strong>OMA Groups</strong>. OMA groups contain sets of genes which are all orthologous to one another within group. This implies that there is at most one entry from each species in a group. OMA Groups can equally be accessed by searching for an OMA Group id or through the Groups tab on any gene-centric page of the browser.</p> <p class="card-text">Additional information:</p> <ul> <li>What are HOGs <a href="https://www.youtube.com/watch?v=5p5x5gxzhZA">YouTube video</a> </li> <li><a href="#type_diff_oma" data-toggle="collapse" data-target="#type_diff_oma .collapse" aria-expanded="false" aria-controls="type_diff_oma">Difference between different types of orthologs in OMA</a> </li> </ul> </div> </div> </div> <div class="card" id="type_diff_oma"> <div class="card-header" id="guide_card_h12"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b12" aria-expanded="false" aria-controls="guide_card_b12"> Differences between different types of orthologs in OMA </button> </h5> </div> <div id="guide_card_b12" class="collapse" aria-labelledby="guide_card_h12" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Differences between different types of orthologs in OMA</h2> <p class="card-text">OMA reports three “types” of orthologs: pairwise-induced orthologs,Hierarchical Orthologous Groups (HOGs)-induced orthologs, and OMA Group-induced orthologs. These are three different methods, so they might not report identical orthologs. However, HOG and OMA Group orthologs are based on pairwise orthologs so they should be similar. For more information, see: <a href="https://omabrowser.org/oma/homologs/">Differents types of homologs in OMA</a>. </p> <table class="table table-hover comparison-table"> <caption>Differences between pairwise orthologs and HOGs</caption> <thead> <tr> <th></th> <th>Pairwise orthologs</th> <th>Hierarchical Orthologous Groups (HOGs)</th> <th>OMA Groups</th> </tr> </thead> <tbody> <tr> <td>Algorithm</td> <td>Built by mutually-closest protein sequences within a confidence interval</td> <td>Built by merging groups of pairwise orthologs at different taxonomic levels using a guide tree </td> <td>Built by searching for cliques of pairwise orthologs (i.e. all genes that are pairwise orthologs to all others in the group) </td> </tr> <tr> <td>Genomes included</td> <td>Compares 2 genomes at a time</td> <td>Compares all genomes at a time</td> <td>Compares all genomes at a time</td> </tr> <tr> <td>Types of homologs</td> <td>Strictly orthologs, but can be 1:m or n:m.</td> <td>Groups of orthologs and in-paralogs for a specific speciation event of reference. </td> <td>Strictly orthologs, at most 1 per species reported, although there may be more not reported. </td> </tr> </tbody> </table> <p class="card-text">Additional information:</p> <ul> <li>Introduction to HOGs <a href="https://www.youtube.com/watch?v=5p5x5gxzhZA">YouTube video</a> </li> <li><a href="https://genome.cshlp.org/content/29/7/1152.full">Altenhoff et al. 2015 </a> </li> <li><a href="https://genome.cshlp.org/content/29/7/1152.full"> Zahn-Zabal et al. 2020 </a> </li> </ul> </div> </div> </div> <div class="card" id="paralogs"> <div class="card-header" id="guide_card_h13"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b13" aria-expanded="false" aria-controls="guide_card_b13"> Paralogs </button> </h5> </div> <div id="guide_card_b13" class="collapse " aria-labelledby="guide_card_h13" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Paralogs</h2> <p class="card-text summary">Both OMA and OrthoDB report paralogs.</p> <p class="card-text">Paralogs are those genes which started diverging due to a duplication.</p> <p class="card-text">In OMA, paralogs are derived from the HOGs, inferred from duplication events. Thus, any pair of genes in the same species and the same HOG are <i>in-paralogs</i> with respect to the defined taxonomic level of the HOG.</p> <p class="card-text">Paralogs can be accessed in the OMA browser from the gene-centric pages by clicking on the Paralogs tab from the side-menu. They are defined in OMA by the taxonomic level at which the duplication occurred. The resulting table displays the duplication level, domain of life, taxon (species in which the paralog is found), protein ids, cross references, and domain architectures.</p> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Exporting the MSA of a specific HOG in OMA" src="/static/image/guide/oma_paralogs.png"> <figcaption class="figure-caption">Paralogs of a query gene in OMA with duplication level according to HOG inference</figcaption> </figure> <p class="card-text">OrthoDB reports in-paralogs with respect to a given taxonomic level. Users can see online or download paralogs in orthologous groups; the paralogs are genes from the same species in the same orthologous group.</p> <p>How do in-paralogs relate to <a href="#One_to_one_vs_many_orthologs" data-toggle="collapse" data-target="#One_to_one_vs_many_orthologs .collapse" aria-expanded="false" aria-controls="One_to_one_vs_many_orthologs">1:1, 1:many and many:many orthology relations?</a></p> </div> </div> </div> <div class="card" id="homoeologs"> <div class="card-header" id="guide_card_h14"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b14" aria-expanded="false" aria-controls="guide_card_b14"> Homoeologs </button> </h5> </div> <div id="guide_card_b14" class="collapse" aria-labelledby="guide_card_h14" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Homoeologs</h2> <p class="card-text summary">OMA reports homoeologs for allopolyploid species in the database.</p> <p class="card-text">Homoeologs are pairs of genes that originated by speciation and were brought back together in the same genome by allopolyploidization. Homoeologs can be thought of as orthologs between subgenomes.</p> <p class="card-text">OMA reports homoeologs for 4 species: <i>Triticum aestivum</i> (bread wheat), <i>Gossypium hirsutum</i> (upland cotton), <i>Brassica napus</i> (rapeseed), and <i>Xenopus laevis</i> (African clawed frog).</p> <p class="card-text">Additional information:</p> <ul> <li>Glover et al. 2016. <a href="http://doi.org/10.1016/j.tplants.2016.02.005">Homoeologs: What Are They and How Do We Infer Them?</a> Trends in Plant Science. </li> </ul> </div> </div> </div> <div class="card" id="markers_for_speciestree"> <div class="card-header" id="guide_card_h15"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b15" aria-expanded="false" aria-controls="guide_card_b15"> Identify orthologous marker genes to infer a species tree </button> </h5> </div> <div id="guide_card_b15" class="collapse" aria-labelledby="guide_card_h15" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Identify orthologous marker genes to infer a species tree</h2> <p class="card-text summary">Both OMA and OrthoDB provide orthologous marker genes.</p> <p class="card-text">Orthologous marker genes (also known as phylogenetic marker genes) are sets of genes which are all orthologous to one another within the group. These marker genes should be 1:1, implying that there is at most one entry from each species in a group, and thus these marker genes are especially useful when creating a phylogenetics tree-- the gene tree will should match the species tree.</p> <p class="card-text">OMA identifies cliques of orthologous pairs (“<a href="#orthologous_groups" data-toggle="collapse" data-target="#orthologous_groups .collapse" aria-expanded="false" aria-controls="orthologous_groups">OMA groups</a>”), which are especially useful as marker genes for phylogenetic reconstruction and tend to be very specific. Since many users are only interested in a small subset of genomes, there is a function to retrieve, for a given subset of species, the most complete OMA groups. This functionality, entitled ‘<a href="https://omabrowser.org/oma/export_markers">Export marker genes</a>’, is accessible under the ‘Download’ menu. Users can optionally choose a minimum proportion of species present in each group (‘occupancy’), and a maximum number of groups to export. From the choice of species and parameters, the OMA server identifies the most complete groups and produces a compressed archive file containing one fasta file per marker gene (i.e. per OMA group).</p> <p class="card-text">For a full description of the Export Marker Genes tool, see <a href="https://oma-stage.vital-it.ch/oma/tools/">Catalog of Tools: Phylogenetic Marker Gene Export.</a> </p> <p class="card-text">OrthoDB identifies single copy Orthologous Groups (OGs): groups with 1:1 representatives in all (or >90%, >80%) of species, as well as universal orthologous groups, meaning groups with members present in all (or >90%, >80%) of species at any selected taxonomic level. Using such filters, users can choose the numbers of OGs they want to build a species tree at the level of interest. </p> </div> </div> </div> <div class="card" id="build_a_gene_tree"> <div class="card-header" id="guide_card_h16"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b16" aria-expanded="false" aria-controls="guide_card_b16"> Build a gene tree </button> </h5> </div> <div id="guide_card_b16" class="collapse" aria-labelledby="guide_card_h16" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Build a gene tree</h2> <p class="card-text summary">It is possible to obtain gene families, or groups of orthologous genes, from both OMA and OrthoDB, which are necessary to build a gene tree.</p> <p class="card-text">In OMA, you can obtain the <a href="https://omabrowser.org/oma/homologs/">HOGs</a>, which are groups orthologs and paralogs which descended from a common ancestral gene at any given taxonomic level. To streamline the process of building a gene tree, you can:</p> <ul> <li>Search for your favorite gene on the OMA browser, then go to the HOG table view.</li> <li>Or, <a href="https://omabrowser.org/oma/hogs/">search for your HOG of interest directly</a> using the HOG id or one of its member genes.</li> <li>Download the fasta sequences directly from the HOG table.</li> <li>Or, export the Mafft multiple sequence alignment (accessible from the side menu).</li> <li>Use the MSA in an external tree-building software.</li> </ul> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Exporting the MSA of a specific HOG in OMA" src="/static/image/guide/oma_hog_msa.png" style="max-width:70%; height:auto;" > <figcaption class="figure-caption">Exporting the fasta file (A) or MSA (B) of a HOG in OMA.</figcaption> </figure> <p class="card-text">OrthoDB provides an “Advanced” search with a PhyloProfile option. There, one can select single copy groups for tree building. “PhyloProfile” allows the user to filter single-copy orthologous groups and their presence in most species (100%, 90% or 80%); this can be done at a selected taxonomic level, as well as coupled with specific annotations (i.e. certain functions). Afterwards, sequences for selected groups can be downloaded in an unaligned Fasta format and usedto build a MSA and a tree.</p> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="OrthoDB's advanced search with PhyloProfile option" src="/static/image/guide/orthodb_advance_search.png"> <figcaption class="figure-caption">OrthoDB's advanced search option</figcaption> </figure> <p class="card-text">Additional information:</p> <ul> <li><a href="#history_of_gene_family" data-toggle="collapse" data-target="#history_of_gene_family .collapse" aria-expanded="false" aria-controls="history_of_gene_family">Visualize evolutionary history of duplications, losses, and gains on the gene tree</a></li> </ul> </div> </div> </div> <div class="card" id="history_of_gene_family"> <div class="card-header" id="guide_card_h17"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b17" aria-expanded="false" aria-controls="guide_card_b17"> Trace the evolutionary history of a gene family </button> </h5> </div> <div id="guide_card_b17" class="collapse" aria-labelledby="guide_card_h17" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Trace the evolutionary history of a gene family</h2> <p class="card-text summary">OMA lets you trace the evolutionary history of a gene family in terms of gene duplications and losses.</p> <p class="card-text">The evolutionary history of gene families can be complex due to duplications and losses. As provided by several orthology databases, hierarchical orthologous groups (HOGs) are sets of genes that are inferred to have descended from a common ancestral gene within a species clade. By keeping track of HOG composition along the species tree, it is possible to infer the emergence, duplications and losses of genes within a gene family of interest.</p> <p class="card-text">The OMA browser allows for viewing HOGs with an interactive widget called iham to visualize and explore gene family history encoded in HOGs. Additionally, one can query the HOGs for evolutionary events programmatically using the python library called <a href="https://zoo.cs.ucl.ac.uk/doc/pyham/index.html">pyham</a>.</p> <p class="card-text">See the guide: <a href="http://lab.dessimoz.org/oma-howto/#h.d59l68yb10zz">How to Get the Evolutionary History of Your Favorite Gene in OMA</a> to find out how to get to and use iham. You can also learn more about iham by watching the <a href="https://www.youtube.com/watch?v=6eAoamP7NLo&t=302s">YouTube tutorial</a>. </p> <p class="card-text">OrthoDB for each orthologous group offers the following set of evolutionary descriptors: Phyletic Profile, Duplicability, Evolutionary Rate and Gene Architecture.</p> <ul> <li><strong>Phyletic profile</strong> that reflects gene universality, i.e. proportion of species with at least one ortholog in a particular ortholog group, </li> <li><strong>Duplicability</strong> that reflects the proportion of multi-copy versus single-copy orthologs in an ortholog group, </li> <li><strong>Evolutionary rate</strong> that reflects the relative conservation or divergence of protein sequence, </li> <li><strong>Gene architecture</strong> that reflects the observed variations of the protein lengths and exon counts of the member orthologs. </li> </ul> <p class="card-text">Additional information</p> <ul> <li>Train et al. 2018. <a href="http://doi.org/10.1093/bioinformatics/bty994">iHam and pyHam: visualizing and processing hierarchical orthologous groups.</a> Bioinformatics. </li> <li>Blog post: <a href="http://lab.dessimoz.org/blog/2017/06/29/pyham">pyHam: a python package to visualize and process hierarchical orthologous groups (HOGs)</a></li> </ul> </div> </div> </div> <div class="card" id="synteny"> <div class="card-header" id="guide_card_h18"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b18" aria-expanded="false" aria-controls="guide_card_b18"> Find the synteny between two genomes </button> </h5> </div> <div id="guide_card_b18" class="collapse" aria-labelledby="guide_card_h18" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Find the synteny between two genomes</h2> <p class="card-text">Synteny is the conservation of gene order and/or overall chromosomal location. Synteny can be viewed on a global or local level, where global synteny looks at the overall chromosomal conservation, and local synteny looks in a smaller neighborhood for conservation of gene homology and order.</p> <ul> <li><a href="#export_pairwise_orthologs_for_synteny" data-toggle="collapse" data-target="#export_pairwise_orthologs_for_synteny .collapse" aria-expanded="false" aria-controls="export_pairwise_orthologs_for_synteny">I want to export orthologs between 2 genomes to use in another synteny software</a></li> <li><a href="#global_synteny_between_two_chromosomes" data-toggle="collapse" data-target="#global_synteny_between_two_chromosomes .collapse" aria-expanded="false" aria-controls="global_synteny_between_two_chromosomes">I want to visualize the global synteny between two chromosomes </a></li> <li><a href="#local_synteny" data-toggle="collapse" data-target="#local_synteny .collapse" aria-expanded="false" aria-controls="local_synteny">I want to visualize the local synteny between several species </a></li> </ul> </div> </div> </div> <div class="card" id="export_pairwise_orthologs_for_synteny"> <div class="card-header" id="guide_card_h19"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b19" aria-expanded="false" aria-controls="guide_card_b19"> Export orthologs between two genomes to use in an external synteny software </button> </h5> </div> <div id="guide_card_b19" class="collapse" aria-labelledby="guide_card_h19" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Export orthologs between two genomes to use in an external synteny software</h2> <p class="card-text summary">Both OMA and OrthoDB let you export orthologs for external synteny packages.</p> <p class="card-text">Many synteny programs exist for computation and visualization of syntenic regions between two genomes, such as <a href="http://bioinformatics.psb.ugent.be/beg/tools/i-adhore30">i-ADHoRe</a>, <a href="http://chibba.pgml.uga.edu/mcscan2/">MCScanX</a>, <a href="http://circos.ca/">circos</a>, among others. Generally the input for these programs is a text file of pairwise orthologous relations or orthologous groups. </p> <p class="card-text">With OMA you can download <a href="#pairwise_orthologs" data-toggle="collapse" data-target="#pairwise_orthologs .collapse" aria-expanded="false" aria-controls="pairwise_orthologs">pairs of orthologs between two genomes</a> or <a href="#orthologous_groups" data-toggle="collapse" data-target="#orthologous_groups .collapse" aria-expanded="false" aria-controls="orthologous_groups">HOGs</a>. With OrthoDB you can download <a href="#orthologous_groups" data-toggle="collapse" data-target="#orthologous_groups .collapse" aria-expanded="false" aria-controls="orthologous_groups">HOGs.</a></p> </div> </div> </div> <div class="card" id="global_synteny_between_two_chromosomes"> <div class="card-header" id="guide_card_h20"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b20" aria-expanded="false" aria-controls="guide_card_b20"> Visualize global synteny between two chromosomes </button> </h5> </div> <div id="guide_card_b20" class="collapse" aria-labelledby="guide_card_h20" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Visualize global synteny between two chromosomes</h2> <p class="card-text summary">OMA lets you <a href="https://omabrowser.org/oma/dotplot/">visualize the global synteny</a> between two chromosomes of different or the same genomes.</p> <p class="card-text">These are the steps to use the OMA Synteny Dot Plot:</p> <ul> <li>Select the two genomes you want to compare. If comparing two different genomes, by default the dots on the plot represent orthologs, with paralogs being optional. If you compare the same genome, OMA will display <a href="#paralogs" data-toggle="collapse" data-target="#paralogs .collapse" aria-expanded="false" aria-controls="paralogs"> paralogs</a>. If the same genome is an allopolyploid (wheat, brassica napus, or cotton), you will display <a href="#homoeologs">homoeologs</a> and/or <a href="#paralogs" data-toggle="collapse" data-target="#paralogs .collapse" aria-expanded="false" aria-controls="paralogs"> paralogs</a> between subgenomes. <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Selecting the genome pair for synteny visualization in OMA" src="/static/image/guide/oma_synteny_genome_selection.png"> </figure> </li> <li>After choosing the genomes, a heatmap will appear below showing where the frequency of orthologous relations are between the two genomes. This is to get an overall idea which chromosomes are conserved, because the higher number the orthologs per chromosome pair indicates a higher synteny.<br/> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Heatmap showing orthologs among different chromosomes" src="/static/image/guide/oma_synteny_heatmap.png"> </figure> </li> <li>The Synteny Dotplot is then displayed, where each dot is a pairwise orthologous relation between the two chromosomes. There are several options here, with buttons in the upper right hand corner of the diagram. <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Synteny dotplot of selected chromosome pair" src="/static/image/guide/oma_synteny_dotplot.png"> </figure> </li> </ul> <p class="card-text">A wide range of operations can then be applied to the selected chromosome pair:</p> <ul> <li>You can export the file as an image</li> <li>You can filter which dots to display based on the type of homologous relationship (1:1,1:m, m:n, close paralogs, homoeologs). </li> <li>You can filter the dots by Evolutionary/Phylogenetic distance. This is computed as part of the normal OMA algorithm and based on sequence similarity. Click on the icon to display the histogram the bottom, from which you can move the bounding filters on the left and right. </li> <li>You can zoom in and zoom out with the mouse.</li> <li>You can select a region to display more information about the homologs (dots) in that region. </li> </ul> </div> </div> </div> <div class="card" id="local_synteny"> <div class="card-header" id="guide_card_h21"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b21" aria-expanded="false" aria-controls="guide_card_b21"> Local synteny </button> </h5> </div> <div id="guide_card_b21" class="collapse" aria-labelledby="guide_card_h21" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Local synteny</h2> <p class="card-text summary">OMA allows for visualization of local synteny.</p> <p class="card-text">The synteny view provides an overview of the genomic context of a particular entry and its orthologs in other species. This enables to see conservation or divergence of syntenic regions across species. As synteny is computed with respect to a reference entry, one can first search for a protein sequence of interest and click on the “Local Synteny” tab. Equally, one can directly access the Local Synteny Viewer from the home page -> Explore.</p> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Joint synteny conservation among several genomes" src="/static/image/guide/oma_synteny_local.png"> </figure> </div> </div> </div> <div class="card" id="domain"> <div class="card-header" id="guide_card_h21b"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b21b" aria-expanded="false" aria-controls="guide_card_b21b"> Protein Domains </button> </h5> </div> <div id="guide_card_b21b" class="collapse" aria-labelledby="guide_card_h21b" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Protein Domains</h2> <ul> <li><a href="#domain_annotations" data-toggle="collapse" data-target="#domain_annotations .collapse" aria-expanded="false" aria-controls="domain_annotations">Protein domain annotations</a></li> <li><a href="#domain_based_linking" data-toggle="collapse" data-target="#domain_based_linking .collapse" aria-expanded="false" aria-controls="domain_based_linking">Finding domain-based links between orthologous groups</a></li> </ul> </div> </div> </div> <div class="card" id="domain_annotations"> <div class="card-header" id="guide_card_h22"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b22" aria-expanded="false" aria-controls="guide_card_b22"> Domain annotations of proteins </button> </h5> </div> <div id="guide_card_b22" class="collapse" aria-labelledby="guide_card_h22" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Domain annotations of proteins</h2> <p class="card-text summary">Both OMA and OrthoDB report domain annotations for the proteins in the databases.</p> <p class="card-text">OMA integrates domain annotations from Gene3D for individual protein entries. For each protein, the sequence of annotated domains is depicted using the conventional ‘colored-boxes-on-a-line’ representation, which we include in most protein lists. This makes it possible to easily check whether the domain architecture of a protein is conserved among orthologs, or to identify entries which are likely to be truncated or otherwise problematic. CATH domains (28) are depicted in colors specific to their first and second level classification.</p> <p class="card-text">OrthoDB provides InterPro attributes associated with individual member proteins. Additionally, at the group level, domain information is summerized.</p> </div> </div> </div> <div class="card" id="domain_based_linking"> <div class="card-header" id="guide_card_h23"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b23" aria-expanded="false" aria-controls="guide_card_b23"> Domain-based links between orthologous groups </button> </h5> </div> <div id="guide_card_b23" class="collapse" aria-labelledby="guide_card_h23" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Domain-based links between orthologous groups</h2> <p class="card-text summary">Both OMA and OrthoDB assign domains to orthologous groups and allow for retrieving related groups based on domains.</p> <p class="card-text">In OMA, domains can be used to establish links between HOGs. Given an initial HOG, a user can retrieve a table of the most similar HOGs based on conserved domain architecture. This domain architecture view allows users to estimate how specific or widespread the domains that make up a protein family are, and allows them to make hypotheses about the origin of a protein family.</p> <figure class="figure"> <img class="figure-img img-fluid rounded" alt="Visualization of HOGs with similar domain composition in OMA" src="/static/image/guide/oma_hogs_with_similar_domaincomposition.png" style="max-width:80%; height:auto;"> <figcaption class="figure-caption">One can access this domain-similarity viewer from a Group-centric view on the OMA browser, the choosing Similar HOGs -> Similar domains from the side menu.</figcaption> </figure> <br> </br> <p class="card-text">OrthoDB has a section, <em>Sibling groups</em>, that reflects the sequence non-uniqueness by the fraction of InterPro domains shared with other groups of orthologs. Related groups are ranked by sequence overlap. For each sibling group list of InterPro domains is displayed, users see domain-domain rearrangements at a glance.</p> </div> </div> </div> <div class="card" id="go"> <div class="card-header" id="guide_card_h24"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b24" aria-expanded="false" aria-controls="guide_card_b24"> Gene Ontology </button> </h5> </div> <div id="guide_card_b24" class="collapse" aria-labelledby="guide_card_h24" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Gene Ontology</h2> <p class="card-text">An important application of orthology is the ability to transfer gene function annotations from the few well-studied model organisms to the large number of poorly studied genomes. <a href="http://geneontology.org/">Gene Ontology</a> (GO) is a way of consistently organizing annotated functions of genes.</p> <ul> <li><a href="#go_for_proteins" data-toggle="collapse" data-target="#go_for_proteins .collapse" aria-expanded="false" aria-controls="go_for_proteins">Obtain GO annotations for proteins</a></li> <li><a href="#go_for_groups" data-toggle="collapse" data-target="#go_for_groups .collapse" aria-expanded="false" aria-controls="go_for_groups">Obtain GO annotations for orthologous groups</a></li> <li><a href="#go_annotated_own" data-toggle="collapse" data-target="#go_annotated_own .collapse" aria-expanded="false" aria-controls="go_annotated_own">Make your own GO annotations for your own sequences</a> </li> </ul> </div> </div> </div> <div class="card" id="go_for_proteins"> <div class="card-header" id="guide_card_h25"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b25" aria-expanded="false" aria-controls="guide_card_b25"> Obtain GO annotations for proteins </button> </h5> </div> <div id="guide_card_b25" class="collapse" aria-labelledby="guide_card_h25" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Obtain GO annotations for proteins</h2> <p class="card-text summary">Both OMA and OrthoDB report GO annotations for proteins in their databases.</p> <p class="card-text">One key motivation for orthology inference is to computationally predict the roles that genes play in living organisms—e.g. Cellular Component, Molecular Function and Biological Process of the Gene Ontology. Gene Ontology (GO) annotations from the UniProt-GOA database have been linked to all sequences in OMA, as well as inferred annotations based on orthology relationships: within the orthologous groups, OMA propagates GO annotations across different species. Amongst the available annotations, most are computationally inferred; OMA’s own predictions constitute about 20% of the available annotations. In OrthoDB currently, about 51% of clusters have GO annotation.</p> <p class="card-text">Additional information:</p> <ul> <li><a href="http://geneontology.org/">Gene Ontology</a></li> <li><a href="http://doi.org/10.1093/nar/gku1158">2015 NAR OMA paper</a> explaining the function prediction algorithm in OMA </li> </ul> </div> </div> </div> <div class="card" id="go_for_groups"> <div class="card-header" id="guide_card_h26"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b26" aria-expanded="false" aria-controls="guide_card_b26"> Obtain GO annotations for orthologous groups </button> </h5> </div> <div id="guide_card_b26" class="collapse" aria-labelledby="guide_card_h26" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Obtain GO annotations for orthologous groups</h2> <p class="card-text summary">OrthoDB provides GO annotations for orthologous groups.</p> <p class="card-text">In OrthoDB, Gene Ontology and InterPro attributes associated with individual member proteins provide a general description for the Orthologous Group as a whole. These are summed over the member proteins to indicate the most frequently occurring attributes associated with the Orthologous Group.</p> </div> </div> </div> <div class="card" id="go_annotated_own"> <div class="card-header" id="guide_card_h27"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b27" aria-expanded="false" aria-controls="guide_card_b27"> Make your own GO annotations </button> </h5> </div> <div id="guide_card_b27" class="collapse" aria-labelledby="guide_card_h27" data-parent="#accordion"> <div class="card-body"> <h2 class="card-title">Make your own GO annotations</h2> <p class="card-text">OMA now provides <a href="https://omabrowser.org/oma/functions">a feature to annotate custom protein sequences</a> through a fast approximate search with all the sequences in OMA. The user can upload a fasta formatted file and will receive the GO annotations (GAF 2.1 format) based on the closest sequence in OMA. These results can directly be further analyzed using other tools, e.g. to perform a gene enrichment analysis. This functionality is accessible under the <em>Compute</em> menu in the OMA browser. </p> </div> </div> </div> <div class="card" id="output_data_format"> <div class="card-header" id="guide_card_h28"> <h5 class="mb-0"> <button class="btn btn-link collapsed" data-toggle="collapse" data-target="#guide_card_b28" aria-expanded="false" aria-controls="guide_card_b28"> I want to choose a resource based on output data </button> </h5> </div> <div id="guide_card_b28" class="collapse" aria-labelledby="guide_card_h28" data-parent="#accordion"> <div class=card-body> <h2 class="card-title">I want to choose a resource based on output data</h2> <p class="card-text">OMA and OrthoDB both provide access to their orthology predictions in various formats:</p> <ul> <li>OrthoXML format</li> <ul> <li><strong>OMA</strong> provides for OrthoXML files for each individual Hierarchical Orthologous Groups (HOGs), all HOGs at once as well as for all OMA Groups. </li> </ul> <li>Fasta files</li> <ul> <li><strong>OMA</strong>: Individual and all protein sequences and cDNA sequences, protein sequences for pairwise orthologs, HOGs per taxonomic level, and OMA Group </li> <li><strong>OrthoDB</strong>: All proteins from your selected species from all orthologous groups that match your search </li> </ul> <li>REST API (primarily json)</li> <ul> <li><strong>OMA</strong>: <a href="https://omabrowser.org/api/docs">https://omabrowser.org/api/docs</a> </li> <li><strong>OrthoDB</strong>: <a href="https://www.orthodb.org/?page=api">https://www.orthodb.org/?page=api</a> </li> </ul> <li>Text format:</li> <ul> <li><strong>OMA</strong>: OMA groups, HOGs, pairwise orthologs, protein annotations, identifier mappings, species information: (Taxon IDs, scientific names, genome sources), group descriptions </li> <li><strong>OrthoDB</strong>: all proteins from your selected species from all orthologous groups that match your search, xrefs associated with Ortho DB gene </li> </ul> <li>Other</li> <ul> <li><strong>OMA</strong>: Json, XML, SQL, MS-Excel, CSV (HOGs), SeqXML format for protein sequences, HDF5 pytable (full OMA Browser database dump), OMA Groups/Sequences in COGs format, and PhyloXML for the species phylogeny of HOGs </ul> </ul> </div> </div> </div> </div> </div> </div> <noscript> <img referrerpolicy="no-referrer-when-downgrade" src="https://matomo.sib.swiss/matomo.php?idsite=51&rec=1&action_name=non-js-access" style="border:0" alt="" /> </noscript>> <script src="//cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js" integrity="sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8=" crossorigin="anonymous"></script> <script src="//cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.7/umd/popper.min.js" crossorigin="anonymous"></script> <script src="//stackpath.bootstrapcdn.com/bootstrap/4.3.1/js/bootstrap.min.js" integrity="sha384-JjSmVgyd0p3pXB1rRibZUAYoIIy6OrQ6VrjIEaFf/nJGzIxFDsf4x0xIM+B07jRM" crossorigin="anonymous"></script> <script> $(function () { var scroll_to_card = function (e) { var $card = $(this).closest('.card'); $('html,body').animate({ scrollTop: $card.offset().top }, 'fast'); }; $('#toggleAccordionShow').on('click', function (e) { $('.collapse').off('shown.bs.collapse'); $('#accordion .collapse').removeAttr("data-parent").collapse('show'); $('.collapse').on('shown.bs.collapse', scroll_to_card); }); $('#toggleAccordionHide').on('click', function (e) { $('#accordion .collapse').attr("data-parent", "#accordion").collapse('hide'); }); $('.collapse').on('shown.bs.collapse', scroll_to_card); }); </script>  <script async src="https://www.googletagmanager.com/gtag/js?id=UA-136590259-1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-136590259-1'); </script> </body> </html>

CINXE.COM

SwissOrthology Interactive Guide