|
|
Mammalian Phenotype (MP): liver/biliary system phenotype
(show info)
Phenotype Ontology
Like Gene Ontology (GO), phenotypy ontology classifies and organizes gene-mutant/null phenotypic information from the very general at the top to more specific terms in the directed acyclic graph (DAG) by viewing an individual term as a node and its relations to parental terms (allowing for multiple parents) as directed edges. To navigate this hierarchy, we display all parental phenotypic terms to the current phenotypic term of interest ordered by their shortest distances to the current term. Also, only direct children phenotypic terms of the current phenotypic term are listed. Phenotype ontologies we have incorporated are as follows:
- Disease Ontology (DO) Ontology (DO) DO semantically integrates disease and medical vocabularies through extensive cross mapping of DO terms to MeSH, ICD, NCI thesaurus, SNOMED and OMIM.
- Human Phenotype (HP) Ontology (HP) HP captures phenotypic abnormalities that are described in OMIM, along with the corresponding disease-causing genes. It includes three complementary biological concepts: Mode_of_Inheritance (MI), ONset_and_clinical_course (ON), and Phenotypic_Abnormality (PA).
- Mouse Phenotype (MP) Ontology (MP) MP describes phenotypes of the mouse after a specific gene is genetically disrupted. Using it, Mouse Genome Informatics (MGI) provides high-coverate gene-level phenotypes for the mouse.
- Worm Phenotype (WP) Ontology (WP) WP classifies and organizes phenotype descriptions for C. elegans and other nematodes. Using it, WormBase provides primary resource for phenotype annotations for C. elegans.
- Yeast Phenotype (YP) Ontology (YP) Based on YP which is the major contributor to the Ascomycete phenotype ontology, Saccharomyces Genome Database (SGD) provides single mutant phenotypes for every gene in the yeast genome.
- Fly Phenotype (FP) Ontology (FP) FP refers to FlyBase controlled vocabulary. Specifically, a structured controlled vocabulary is used for the annotation of alleles (for their mutagen etc) in FlyBase.
- Fly Anatomy (FA) Ontology (FA) FA is a structured controlled vocabulary of the anatomy of Drosophila melanogaster, used for the description of phenotypes and where a gene is expressed.
- Zebrafish Anatomy (ZA) Ontology (ZA) ZA displays anatomical terms of the zebrafish using standard anatomical nomenclature, together with affected genes.
- Xenopus Anatomy (XA) Ontology (XA) XA represents the lineage of tissues and the timing of development for frogs (Xenopus laevis and Xenopus tropicalis). It is used to annotate Xenopus gene expression patterns and mutant and morphant phenotypes.
- Arabidopsis Plant Ontology (AP) Ontology (AP) As a major contributor to Plant Ontology which describes plant anatomical and morphological structures (AN) and growth and developmental stages (DE), the Arabidopsis Information Resource (TAIR) provides arabidopsis plant ontology annotations for the model higher plant Arabidopsis thaliana.
- Enzyme Commission (EC) Ontology (EC) Each enzyme is allocated a four-digit EC number, the first three digits of which define the reaction catalysed and the fourth of which is a unique identifier (serial number). Each enzyme is also assigned a systematic name that uniquely defines the reaction catalysed.
- DrugBank ATC (DB) Ontology (DB) In the Anatomical Therapeutic Chemical (ATC) classification system, drugs are classified in groups at five different levels according to the organ or system (1st level, anatomical main group) on which they act and their therapeutic (2nd level, therapeutic subgroup), pharmacological (3rd level, pharmacological subgroup) and chemical properties (4th level, chemical subgroup; 5th level, chemical substance). Only drugs in DrugBank are considered.
- UniProtKB KeyWords (KW) Ontology (KW) Keywords in UniProtKB are controlled vocabulary, providing a summary of the entry content and are used to index UniProtKB/Swiss-Prot entries based on 10 categories (the category "Technical term" being excluded here). Each keyword is attributed manually to UniProtKB/Swiss-Prot entries and automatically to UniProtKB/TrEMBL entries (according to specific annotation rules).
- UniProtKB UniPathway (UP) Ontology (UP) UP is a fully manually curated resource for the representation and annotation of metabolic pathways, being used as controlled vocabulary for pathway annotation in UniProtKB.
Structural Domain Phenotype Ontology and its Annotations
Structural Classification of Proteins (SCOP) classifies evolutionary-related domains into Superfamily level and Family level. Using the phenotype ontologies above, we have generated the domain-centric phenotype annotations, and further identified those phenotype terms which are the most informative to annotate SCOP domains. Promisingly, domain-centric phenotypic annotations can serve as an alternative starting point to explore genotype-phenotype relationships. We provide several relevant files for the download, including the annotation and the corresponding ontology for each phenotype ontology.
- Structural Domain Disease Ontology (DO) Ontology (SDDO) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2DO.txt, and the corresponding ontology:SDDO.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Human Phenotype (HP) Ontology (SDHP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2HP.txt, and the corresponding ontology:SDHP.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Mouse Phenotype (MP) Ontology (SDMP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2MP.txt, and the corresponding ontology:SDMP.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Worm Phenotype (WP) Ontology (SDWP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2WP.txt, and the corresponding ontology:SDWP.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Yeast Phenotype (YP) Ontology (SDYP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2YP.txt, and the corresponding ontology:SDYP.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Fly Phenotype (FP) Ontology (SDFP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2FP.txt, and the corresponding ontology:SDFP.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Fly Anatomy (FA) Ontology (SDFA) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2FA.txt, and the corresponding ontology:SDFA.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Zebrafish Anatomy (ZA) Ontology (SDZA) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2ZA.txt, and the corresponding ontology:SDZA.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Xenopus Anatomy (XA) Ontology (SDXA) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2XA.txt, and the corresponding ontology:SDXA.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Arabidopsis Plant Ontology (AP) Ontology (SDAP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2AP.txt, and the corresponding ontology:SDAP.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain Enzyme Commission (EC) Ontology (SDEC) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2EC.txt, and the corresponding ontology:SDEC.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain DrugBank ATC (DB) Ontology (SDDB) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2DB.txt, and the corresponding ontology:SDDB.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain UniProtKB KeyWords (KW) Ontology (SDKW) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2KW.txt, and the corresponding ontology:SDKW.txt) and mysql tables (Domain2PO.sql.gz).
- Structural Domain UniProtKB UniPathway (UP) Ontology (SDUP) and its Annotations: For details, please visit Document: PO annotation for SCOP domains, wherein Data Availability contains parsable flat files (the annotation:Domain2UP.txt, and the corresponding ontology:SDUP.txt) and mysql tables (Domain2PO.sql.gz).
Supra-domain Phenotype Ontology and its Annotations
Although domain-centric annotations hold great promise in describing phenotypic nature of independent domains, most domains themselves may not just work alone. In multi-domain proteins, they may be combined together to form distinct domain architectures. The recombination of the existing domains is considered as one of major driving forces for phenotypic diversificaation. As an extension, we have also generated supra-domain phenotype ontology and its annotations. Compared to domain-centric phenotype ontology and annotations (SCOP domains at the Superfamily level and Family level), this version focuses on supra-domains and individual SCOP domains ONLY at the Superfamily level. Besides, in terms of individual superfamilies, their annotations from the domain-centric version may be different from those from supra-domains version. Depending on your focus, the former should be used for the consideration of both the Superfamily level and Family level, otherwise the latter should be used if you are interested in domain combinations. Also, we provide several relevant files for the download, including the annotation and the corresponding ontology for each phenotype ontology.
- Supra-domain Domain Disease Ontology (DO) Ontology (SPDO) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2DO.txt, and the corresponding ontology:SPDO.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Human Phenotype (HP) Ontology (SPHO) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2HP.txt, and the corresponding ontology:SPHO.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Mouse Phenotype (MP) Ontology (SPMP) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2MP.txt, and the corresponding ontology:SPMP.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Worm Phenotype (WP) Ontology (SPWP) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2WP.txt, and the corresponding ontology:SPWP.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Yeast Phenotype (YP) Ontology (SPYP) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2YP.txt, and the corresponding ontology:SPYP.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Fly Phenotype (FP) Ontology (SPFP) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2FP.txt, and the corresponding ontology:SPFP.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Fly Anatomy (FA) Ontology (SPFA) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2FA.txt, and the corresponding ontology:SPFA.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Zebrafish Anatomy (ZA) Ontology (SPZA) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2ZA.txt, and the corresponding ontology:SPZA.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Xenopus Anatomy (XA) Ontology (SPXA) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2XA.txt, and the corresponding ontology:SPXA.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Arabidopsis Plant Ontology (AP) Ontology (SPAP) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2AP.txt, and the corresponding ontology:SPAP.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain Enzyme Commission (EC) Ontology (SPEC) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2EC.txt, and the corresponding ontology:SPEC.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain DrugBank ATC (DB) Ontology (SPDB) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2DB.txt, and the corresponding ontology:SPDB.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain UniProtKB KeyWords (KW) Ontology (SPKW) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2KW.txt, and the corresponding ontology:SPKW.txt) and mysql tables (SP2PO.sql.gz).
- Supra-domain Domain UniProtKB UniPathway (UP) Ontology (SPUP) and its Annotations: For details, please visit Document: PO annotation for Supra-domains, wherein Data Availability contains parsable flat files (the annotation:SP2UP.txt, and the corresponding ontology:SPUP.txt) and mysql tables (SP2PO.sql.gz).
Jump to [ Top · Phenotype Hierarchy · Superfamily · Family · Supra-domain ]
Root: MP Hierarchy (mammalian/mouse phenotype from MGI_4.41)
Jump to [ Top · Phenotype Hierarchy · Superfamily · Family · Supra-domain ]
Superfamily(show details)
Jump to [ Top · Phenotype Hierarchy · Superfamily · Family · Supra-domain ]
Family(show details)
Plot distribution on phylogenetic tree for Superfamily and/or Family domains annotated by this phenotype term
 |
Plot tree as:
| |
Download Newick format tree:
|
(show help)
Trees by TreeVector
A presence/absence matrix is generated using protein domain
architecture data for all genomes in SUPERFAMILY. The PAUP
software is used to produce a single, large tree topology using
heuristic parsimony methods. Genome combinations, or specific clades, can be displayed as
if individual trees had been produced. However, this data is extracted from the single
large tree. This produces a higher quality topology than if the trees had been produced
on their own, and allows the trees to be displayed instantly.
Jump to [ Top · Phenotype Hierarchy · Superfamily · Family · Supra-domain ]
Supra-domain (including individual superfamily)
(show details)
(show details)
Supra-domains annotated to this MP term (SPMP level: Moderately Informative)
Highlighted in gray are those with FDR>0.001
| Supra-domain (Duplex) in N- to C-terminal order |
FDR (all) |
Annotation (direct or inherited) |
52980,47781
52980 - Restriction endonuclease-like
47781 - RuvA domain 2-like | 0 | DIRECT |
54637,54637
54637 - Thioesterase/thiol ester dehydrase-isomerase
54637 - Thioesterase/thiol ester dehydrase-isomerase | 0 | DIRECT |
57196,57424
57196 - EGF/Laminin
57424 - LDL receptor-like module | 0 | DIRECT |
57414,57440
57414 - Hairpin loop containing domain-like
57440 - Kringle-like | 0 | DIRECT |
57716,48508
57716 - Glucocorticoid receptor-like (DNA-binding domain)
48508 - Nuclear receptor ligand-binding domain | 0.00001272 | DIRECT |
56645,47203
56645 - Acyl-CoA dehydrogenase NM domain-like
47203 - Acyl-CoA dehydrogenase C-terminal domain-like | 0.0003263 | DIRECT |
48092,47655
48092 - Transcription factor STAT-4 N-domain
47655 - STAT | 0.0004831 | DIRECT |
49417,55550
49417 - p53-like transcription factors
55550 - SH2 domain | 0.0004831 | DIRECT |
47655,49417
47655 - STAT
49417 - p53-like transcription factors | 0.0004831 | DIRECT |
88713,88688
88713 - Glycoside hydrolase/deacetylase
88688 - Families 57/38 glycoside transferase middle domain | 0.0005505 | DIRECT |
49417,81296
49417 - p53-like transcription factors
81296 - E set domains | 0.0008 | DIRECT |
57440,50494
57440 - Kringle-like
50494 - Trypsin-like serine proteases | 0.001367 | INHERITED FROM: abnormal hepatobiliary system morphology || liver fibrosis || abnormal liver morphology || abnormal liver physiology |
57424,57424
57424 - LDL receptor-like module
57424 - LDL receptor-like module | 0.004221 | INHERITED FROM: decreased liver triglyceride level |
63825,57196
63825 - YWTD domain
57196 - EGF/Laminin | 0.01805 | INHERITED FROM: decreased liver triglyceride level || abnormal hepatobiliary system physiology || abnormal liver physiology || abnormal liver triglyceride level |
103473,100895
103473 - MFS general substrate transporter
100895 - Kazal-type serine protease inhibitors | 0.01954 | INHERITED FROM: abnormal hepatobiliary system physiology || abnormal liver physiology |
90123,52540
90123 - ABC transporter transmembrane region
52540 - P-loop containing nucleoside triphosphate hydrolases | 0.02812 | INHERITED FROM: abnormal gallbladder physiology || abnormal hepatocyte morphology || abnormal liver lobule morphology |
49265,49265
49265 - Fibronectin type III
49265 - Fibronectin type III | 0.07167 | INHERITED FROM: abnormal hepatobiliary system physiology || abnormal liver physiology |
51045,51045
51045 - WW domain
51045 - WW domain | 0.07198 | INHERITED FROM: increased liver tumor incidence || increased hepatobiliary system tumor incidence || increased hepatocellular carcinoma incidence |
47454,57959
47454 - A DNA-binding domain in eukaryotic transcription factors
57959 - Leucine zipper domain | 0.2531 | INHERITED FROM: decreased liver weight |
| Supra-domain (Duplex) in N- to C-terminal order |
FDR (all) |
Annotation (direct or inherited) |
52980,47781
52980 - Restriction endonuclease-like
47781 - RuvA domain 2-like | 0 | Direct |
54637,54637
54637 - Thioesterase/thiol ester dehydrase-isomerase
54637 - Thioesterase/thiol ester dehydrase-isomerase | 0 | Direct |
57196,57424
57196 - EGF/Laminin
57424 - LDL receptor-like module | 0 | Direct |
57414,57440
57414 - Hairpin loop containing domain-like
57440 - Kringle-like | 0 | Direct |
57716,48508
57716 - Glucocorticoid receptor-like (DNA-binding domain)
48508 - Nuclear receptor ligand-binding domain | 0.00001272 | Direct |
56645,47203
56645 - Acyl-CoA dehydrogenase NM domain-like
47203 - Acyl-CoA dehydrogenase C-terminal domain-like | 0.0003263 | Direct |
48092,47655
48092 - Transcription factor STAT-4 N-domain
47655 - STAT | 0.0004831 | Direct |
49417,55550
49417 - p53-like transcription factors
55550 - SH2 domain | 0.0004831 | Direct |
47655,49417
47655 - STAT
49417 - p53-like transcription factors | 0.0004831 | Direct |
88713,88688
88713 - Glycoside hydrolase/deacetylase
88688 - Families 57/38 glycoside transferase middle domain | 0.0005505 | Direct |
49417,81296
49417 - p53-like transcription factors
81296 - E set domains | 0.0008 | Direct |
57440,50494
57440 - Kringle-like
50494 - Trypsin-like serine proteases | 0.001367 | Inherited |
57424,57424
57424 - LDL receptor-like module
57424 - LDL receptor-like module | 0.004221 | Inherited |
63825,57196
63825 - YWTD domain
57196 - EGF/Laminin | 0.01805 | Inherited |
103473,100895
103473 - MFS general substrate transporter
100895 - Kazal-type serine protease inhibitors | 0.01954 | Inherited |
90123,52540
90123 - ABC transporter transmembrane region
52540 - P-loop containing nucleoside triphosphate hydrolases | 0.02812 | Inherited |
49265,49265
49265 - Fibronectin type III
49265 - Fibronectin type III | 0.07167 | Inherited |
51045,51045
51045 - WW domain
51045 - WW domain | 0.07198 | Inherited |
47454,57959
47454 - A DNA-binding domain in eukaryotic transcription factors
57959 - Leucine zipper domain | 0.2531 | Inherited |
(show details)
Supra-domains annotated to this MP term (SPMP level: Moderately Informative)
Highlighted in gray are those with FDR>0.001
| Supra-domain (Triple) in N- to C-terminal order |
FDR (all) |
Annotation (direct or inherited) |
63825,57196,57424
63825 - YWTD domain
57196 - EGF/Laminin
57424 - LDL receptor-like module | 0 | DIRECT |
57196,57424,57424
57196 - EGF/Laminin
57424 - LDL receptor-like module
57424 - LDL receptor-like module | 0 | DIRECT |
57414,57440,57440
57414 - Hairpin loop containing domain-like
57440 - Kringle-like
57440 - Kringle-like | 0 | DIRECT |
49503,49503,49503
49503 - Cupredoxins
49503 - Cupredoxins
49503 - Cupredoxins | 0 | DIRECT |
48092,47655,49417
48092 - Transcription factor STAT-4 N-domain
47655 - STAT
49417 - p53-like transcription factors | 0.0004831 | DIRECT |
47655,49417,55550
47655 - STAT
49417 - p53-like transcription factors
55550 - SH2 domain | 0.0004831 | DIRECT |
57424,57424,57424
57424 - LDL receptor-like module
57424 - LDL receptor-like module
57424 - LDL receptor-like module | 0.002687 | INHERITED FROM: decreased liver triglyceride level |
57586,57586,57586
57586 - TNF receptor-like
57586 - TNF receptor-like
57586 - TNF receptor-like | 0.009141 | INHERITED FROM: abnormal hepatobiliary system physiology || abnormal liver physiology |
57196,63825,57196
57196 - EGF/Laminin
63825 - YWTD domain
57196 - EGF/Laminin | 0.01954 | INHERITED FROM: abnormal hepatobiliary system physiology || abnormal liver physiology |
63825,57196,63825
63825 - YWTD domain
57196 - EGF/Laminin
63825 - YWTD domain | 0.01954 | INHERITED FROM: abnormal hepatobiliary system physiology || abnormal liver physiology |
| Supra-domain (Triple) in N- to C-terminal order |
FDR (all) |
Annotation (direct or inherited) |
63825,57196,57424
63825 - YWTD domain
57196 - EGF/Laminin
57424 - LDL receptor-like module | 0 | Direct |
57196,57424,57424
57196 - EGF/Laminin
57424 - LDL receptor-like module
57424 - LDL receptor-like module | 0 | Direct |
57414,57440,57440
57414 - Hairpin loop containing domain-like
57440 - Kringle-like
57440 - Kringle-like | 0 | Direct |
49503,49503,49503
49503 - Cupredoxins
49503 - Cupredoxins
49503 - Cupredoxins | 0 | Direct |
48092,47655,49417
48092 - Transcription factor STAT-4 N-domain
47655 - STAT
49417 - p53-like transcription factors | 0.0004831 | Direct |
47655,49417,55550
47655 - STAT
49417 - p53-like transcription factors
55550 - SH2 domain | 0.0004831 | Direct |
57424,57424,57424
57424 - LDL receptor-like module
57424 - LDL receptor-like module
57424 - LDL receptor-like module | 0.002687 | Inherited |
57586,57586,57586
57586 - TNF receptor-like
57586 - TNF receptor-like
57586 - TNF receptor-like | 0.009141 | Inherited |
57196,63825,57196
57196 - EGF/Laminin
63825 - YWTD domain
57196 - EGF/Laminin | 0.01954 | Inherited |
63825,57196,63825
63825 - YWTD domain
57196 - EGF/Laminin
63825 - YWTD domain | 0.01954 | Inherited |
Plot distribution on phylogenetic tree for Supra-domains (Single/Individual) annotated by this phenotype term
|
Plot tree as:
| |
Download Newick format tree:
|
(show help)
Trees by TreeVector
A presence/absence matrix is generated using protein domains and supradomains
for all genomes in SUPERFAMILY. The RAxML
software is used to produce a single, large tree topology using
heuristic parsimony methods. Genome combinations, or specific clades, can be displayed as
if individual trees had been produced. However, this data is extracted from the single
large tree. This produces a higher quality topology than if the trees had been produced
on their own, and allows the trees to be displayed instantly.
|
