Display Settings:

Format

Send to:

Choose Destination
    Am J Hum Genet. 2004 Dec;75(6):1106-12. Epub 2004 Oct 18.

    Ignoring linkage disequilibrium among tightly linked markers induces false-positive evidence of linkage for affected sib pair analysis.

    Source

    Department of Epidemiology, University of Texas M. D. Anderson Cancer Center, Houston, TX 77030-4009, USA.

    Abstract

    Most multipoint linkage programs assume linkage equilibrium among the markers being studied. The assumption is appropriate for the study of sparsely spaced markers with intermarker distances exceeding a few centimorgans, because linkage equilibrium is expected over these intervals for almost all populations. However, with recent advancements in high-throughput genotyping technology, much denser markers are available, and linkage disequilibrium (LD) may exist among the markers. Applying linkage analyses that assume linkage equilibrium to dense markers may lead to bias. Here, we demonstrated that, when some or all of the parental genotypes are missing, assuming linkage equilibrium among tightly linked markers where strong LD exists can cause apparent oversharing of multipoint identity by descent (IBD) between sib pairs and false-positive evidence for multipoint model-free linkage analysis of affected sib pair data. LD can also mimic linkage between a disease locus and multiple tightly linked markers, thus causing false-positive evidence of linkage using parametric models, particularly when heterogeneity LOD score approaches are applied. Bias can be eliminated by inclusion of parental genotype data and can be reduced when additional unaffected siblings are included in the analysis.

    PMID:
    15492927
    [PubMed - indexed for MEDLINE]
    PMCID:
    PMC1182145
    Free PMC Article

    Images from this publication.See all images (1) Free text

    Figure  1

      Supplemental Content

      Icon for Elsevier Science Icon for PubMed Central

      Save items

      loading

      Recent activity

      Your browsing activity is empty.

      Activity recording is turned off.

      Turn recording back on

      See more...
      Write to the Help Desk