24
views
0
recommends
+1 Recommend
0 collections
    0
    shares
      • Record: found
      • Abstract: found
      • Article: not found

      Stochastic mapping of morphological characters.

      1 ,   ,
      Systematic biology
      Informa UK Limited

      Read this article at

      ScienceOpenPublisherPubMed
      Bookmark
          There is no author summary for this article yet. Authors can add summaries to their articles on ScienceOpen to make them more accessible to a non-specialist audience.

          Abstract

          Many questions in evolutionary biology are best addressed by comparing traits in different species. Often such studies involve mapping characters on phylogenetic trees. Mapping characters on trees allows the nature, number, and timing of the transformations to be identified. The parsimony method is the only method available for mapping morphological characters on phylogenies. Although the parsimony method often makes reasonable reconstructions of the history of a character, it has a number of limitations. These limitations include the inability to consider more than a single change along a branch on a tree and the uncoupling of evolutionary time from amount of character change. We extended a method described by Nielsen (2002, Syst. Biol. 51:729-739) to the mapping of morphological characters under continuous-time Markov models and demonstrate here the utility of the method for mapping characters on trees and for identifying character correlation.

          Related collections

          Author and article information

          Journal
          Syst Biol
          Systematic biology
          Informa UK Limited
          1063-5157
          1063-5157
          Apr 2003
          : 52
          : 2
          Affiliations
          [1 ] Section of Ecology, Behavior and Evolution, Division of Biology, University of California-San Diego, La Jolla, California 92093-0116, USA.
          Article
          WFBKUNE0G83NWNAF
          10.1080/10635150390192780
          12746144
          c01533f1-e241-4e61-b793-e06f55eb9290

          Comments

          Comment on this article