Article added to library!
Pubchase is a service of - free, open access, crowdsourced protocols repository. Explore protocols.
Sign in
Reset password
or connect with
By signing in you are agreeing to our
Terms Of Service and Privacy Policy
Sep 04, 2015
BMC Evolutionary Biology
BACKGROUND: The rice genus (Oryza) contains many wild genetic resources that are vital to the well-being of humans. However, little is known about the process by which the genus diversified or the factors that drove its speciation. Here, we integrated the phylogenetic, molecular dating and biogeographic methods to investigate the spatial-temporal patterns of Oryza diversification, and used a series of model tests to examine whether intercontinental migrations and/or key innovations were associated with significant changes in diversification rates in the genus. RESULTS: Oryza became differentiated in tropical Asia in the Miocene. There were two migrations from the ancestral area into Africa and Australia during the Miocene. We inferred at least 10 migration events out of tropical Asia since the Pleistocene, mainly involving the species adapting open habitat. A rapid increase in diversification rates of the whole Oryza occurred during the Pleistocene. Intercontinental migrations from tropical Asia to other tropical regions were positively correlated with shift in habitat, but not with changes in life history. A habitat preference shift from shade tolerant to open habitat predated the burst in diversification rates. CONCLUSIONS: Rice species may have been pre-adapted to invade open habitat. Significant increase in diversification rates occurred during the Pleistocene and is associated with range expansion and habitat shift, but not with life history. The rice genus provides an excellent case supporting the idea that range expansion and invasion of novel habitats can drive the diversification of a group.

Downloading PDF to your library...

Uploading PDF...

PDF uploading

Delete tag:

The link you entered does not seem to be valid

Please make sure the link points to contains a valid shared_access_token