Changes between Version 19 and Version 20 of PhyloWS_workgroup

Show
Ignore:
Timestamp:
2008/02/12 14:45:23 (10 years ago)
Author:
czmasek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PhyloWS_workgroup

    v19 v20  
    1717  * Gene tree analysis: splitting a given set of trees into subsets of trees as a function of compatibility to a given (set of) species tree(s). Degree of compatibility can be expressed as minimal sum of duplications needed to reconcile the gene with a species tree. I.e. measurement of the percentage of gene trees supporting an ecdysozoan versus a coelomata hypothesis. 
    1818  * The analysis mentioned above could be extended by asking questions about the (majority of) functional categories supporting a given species tree. These examples require association of the following data with gene tree nodes: taxonomy identifier, gene identifier. 
    19   * Gene tree analysis: similar to the Zmasek et al (2007) paper, one may want to build alignments and phylogenetic trees for all ortholog families of a  gene family, or a pathway. After loading the trees into a database, one could then query the database for those gene trees that support a certain species phylogeny, for example the Ecdysozoan hypothesis. 
     19  * Gene tree analysis: similar to the Zmasek et al (2007) paper, one may want to build alignments and phylogenetic trees for all members of each protein  (family) of a biological network (e.g. apoptsis). After loading the trees into a database, one could then query the database for those gene trees that exhibit a given pattern (e.g. lineage specific gene expansion or gene loss). 
    2020   * Problem: the query topology will be given with either gene name labels, or species name labels, but the labels of the trees will be OTUs. 
    2121   * Hence, each OTU needs to be linked to the gene name(s) and taxon names, and it needs to be possible to specify that matching tree nodes use the linked taxon or gene names.