Published in

BioMed Central, BMC Proceedings, S9(5), 2011

DOI: 10.1186/1753-6561-5-s9-s83

Links

Tools

Export citation

Search in Google Scholar

Old lessons learned anew: family-based methods for detecting genes responsible for quantitative and qualitative traits in the Genetic Analysis Workshop 17 mini-exome sequence data

This paper is made freely available by the publisher.
This paper is made freely available by the publisher.

Full text: Download

Green circle
Preprint: archiving allowed
Green circle
Postprint: archiving allowed
Green circle
Published version: archiving allowed
Data provided by SHERPA/RoMEO

Abstract

Abstract Family-based study designs are again becoming popular as new next-generation sequencing technologies make whole-exome and whole-genome sequencing projects economically and temporally feasible. Here we evaluate the statistical properties of linkage analyses and family-based tests of association for the Genetic Analysis Workshop 17 mini-exome sequence data. Based on our results, the linkage methods using relative pairs or nuclear families had low power, with the best results coming from variance components linkage analysis in nuclear families and Elston-Stewart model-based linkage analysis in extended pedigrees. For family-based tests of association, both ASSOC and ROMP performed well for genes with large effects, but ROMP had the advantage of not requiring parental genotypes in the analysis. For the linkage analyses we conclude that genome-wide significance levels appear to control type I error well but that “suggestive” significance levels do not. Methods that make use of the extended pedigrees are well powered to detect major loci segregating in the families even when there is substantial genetic heterogeneity and the trait is mainly polygenic. However, large numbers of such pedigrees will be necessary to detect all major loci. The family-based tests of association found the same major loci as the linkage analyses and detected low-frequency loci with moderate effect sizes, but control of type I error was not as stringent.