Format

Send to:

Choose Destination
See comment in PubMed Commons below
Theor Appl Genet. 2007 Jan;114(2):223-35. Epub 2006 Nov 23.

Evolution of chloroplast mononucleotide microsatellites in Arabidopsis thaliana.

Author information

  • 1Department of Cell and Organism Biology, Genetics, Lund University, Lund, Sweden.

Abstract

The level of variation and the mutation rate were investigated in an empirical study of 244 chloroplast microsatellites in 15 accessions of Arabidopsis thaliana. In contrast to SNP variation, microsatellite variation in the chloroplast was found to be common, although less common than microsatellite variation in the nucleus. No microsatellite variation was found in coding regions of the chloroplast. To evaluate different models of microsatellite evolution as possible explanations for the observed pattern of variation, the length distribution of microsatellites in the published DNA sequence of the A. thaliana chloroplast was subsequently used. By combining information from these two analyses we found that the mode of evolution of the chloroplast mononucleotide microsatellites was best described by a linear relation between repeat length and mutation rate, when the repeat lengths exceeded about 7 bp. This model can readily predict the variation observed in non-coding chloroplast DNA. It was found that the number of uninterrupted repeat units had a large impact on the level of chloroplast microsatellite variation. No other factors investigated--such as the position of a locus within the chromosome, or imperfect repeats--appeared to affect the variability of chloroplast microsatellites. By fitting the slippage models to the Genbank sequence of chromosome 1, we show that the difference between microsatellite variation in the nucleus and the chloroplast is largely due to differences in slippage rate.

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

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Full text links

    Icon for Springer
    Loading ...
    Write to the Help Desk