Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
Syst Biol. 2001 Apr;50(2):194-214.

Multiple molecular data sets suggest independent origins of highly eusocial behavior in bees (Hymenoptera:Apinae).

Author information

  • 1Department of Entomology, University of Arkansas, Fayetteville, Arkansas 72701, USA. scameron@comp.uark.edu

Abstract

Different views of the pattern of social evolution among the highly eusocial bees have arisen as a result of discordance between past molecular and morphology-based phylogenies. Here we present new data and taxa for four molecular data sets and reassess the morphological characters available to date. We show there is no significant character incongruence between four molecular data sets (two nuclear and two mitochondrial), but highly significant character incongruence leads to topological incongruence between the molecular and morphological data. We investigate the effects of using different outgroup combinations to root the estimated tree. We also consider various ways in which biases in the sequence data could be misleading, using several maximum likelihood models, LogDet corrections, and spectral analyses. Ultimately, we concede there is strong discordance between the molecular and morphological data partitions and appropriately apply the conditional combination approach in this case. We also find two equally well supported placements of the root for the molecular trees, one supported by 16S and 28S sequences, the other supported by cytochrome b and opsin. The strength of the evidence leads us to accept two equally well supported hypotheses based on analyses of the molecular data sets. These are the most rigorously supported hypotheses of corbiculate bee relationships at this time, and frame our argument that highly eusocial behavior within the corbiculate bees evolved twice independently.

PMID:
12116928
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Loading ...
    Write to the Help Desk